Guide

HS Code vs HTS Code vs Schedule B for Ecommerce

Choose the right US classification system for an import, export, supplier record, product catalog, commercial invoice, or marketplace shipment without mixing HS, HTS, and Schedule B.

Answer Summary

Preparation checklist

HS is the international six-digit foundation, not the name of every national code used in a US transaction.

HTSUS is the US import classification schedule administered by the US International Trade Commission; Schedule B is the US export commodity schedule maintained by the Census Bureau.

A product catalog should retain system, direction, full code, source, edition/date, and supporting product facts so import and export values are never silently substituted.

Required fields or decision table

Fields to prepare before the document draft

Field or decisionWhat to prepare
HS subheading

Six-digit international base used by countries that apply the Harmonized System. Use it to bridge systems, not to assume the same national extension.

HTSUS import number

Ten-digit number used to classify goods imported into the United States. Use the current USITC HTS and review legal notes, national subdivisions, and Chapter 99 measures.

Schedule B export number

Ten-digit commodity number used for exports from the United States. Use the current Census Schedule B and its official search/classification resources.

Transaction direction

Record whether the goods are entering or leaving the United States. A US seller can have both an HTS import record for sourcing and a Schedule B export record for outbound sales.

Product facts

Material, function, construction, included components, power/battery details, and set presentation support both systems. The marketing title alone is insufficient.

Country of origin

Origin can affect import duty and measures, but it does not replace classification. Keep manufacturing origin separate from ship-from country.

Value and filing trigger

Export reporting requirements can depend on value and licensing. Use current Census/AES guidance for the actual transaction rather than a memorized threshold alone.

Source and version

Store USITC or Census source URL, schedule edition, lookup date, reviewer, status, and any ruling or notes consulted.

Platform field mapping

Map Shopify, Amazon, carrier, broker, and ERP fields to an explicitly named source field. A generic “tariff code” export should never hide whether it contains HS, HTSUS, or Schedule B.

Step-by-step preparation

How to prepare the draft

  1. Identify whether the workflow is a US import, a US export, or a catalog record intended for several destinations.
  2. Collect the physical product facts and origin before searching. Keep variants separate when material, function, construction, or included components differ.
  3. Use the US HTS Code Lookup and current USITC schedule for import candidates. Follow chapter notes, headings, subheadings, statistical suffixes, and any applicable Chapter 99 cross-reference.
  4. For exports from the United States, use the current Census Schedule B system. Start from the verified six-digit HS subheading, then select the Schedule B-specific final digits.
  5. Do not copy the last four HTS digits into Schedule B or vice versa unless the current official systems show the same number for that product.
  6. Record origin, value, destination, licence or control flags, and filing context separately from classification. HS/HTS/Schedule B does not replace ECCN or other export-control screening.
  7. Validate catalog completeness with the CSV Catalog Checker, then map the reviewed system-specific fields to each platform output.
  8. For ambiguous, high-value, regulated, or repeatedly imported products, retain the source trail and use a qualified ruling or professional review path before filing.
Ecommerce example

How this looks in a seller workflow

A US-based seller imports stainless steel water bottles from Vietnam, stores them in a US warehouse, and later exports orders to customers in several countries. The inbound entry needs a reviewed 10-digit HTSUS candidate and origin evidence. The outbound US export workflow needs a reviewed 10-digit Schedule B number.

The catalog keeps hs6_candidate, us_hts10_import, us_schedule_b10_export, country_of_origin, source_url, source_date, and review_status in separate columns. The seller does not overwrite the inbound HTS field when a carrier asks for a six-digit HS code on an outbound label.

  • Inbound US import: current HTSUS candidate plus origin/measure review.
  • Outbound US export: current Schedule B candidate plus export-filing checks.
  • Marketplace/carrier label: map the field requested for that shipment.
  • Catalog: retain all systems and source dates separately.
  • Changed bottle material or insulation: return the SKU to classification review.
Verification checklist

Verify the US import or export record before it reaches a filing workflow

  • The workflow says import, export, or both.
  • The source is USITC for HTSUS or Census for Schedule B.
  • The full 10-digit number belongs to the correct current system.
  • The first six digits and product description agree across systems.
  • The final four digits were verified rather than copied.
  • Origin, value, Chapter 99, and export-control fields remain separate.
  • Each marketplace or carrier export maps the correct field.
  • The record includes source date, reviewer/status, and evidence.
  • A higher-review path exists for ambiguous or consequential products.
Source-backed checks

What external guidance supports this workflow?

Common mistakes

What to avoid

  • Calling a 10-digit HTSUS number a universal HS code.
  • Using Schedule B for a US import entry.
  • Using HTSUS for AES export reporting without checking Schedule B.
  • Assuming matching first six digits guarantee matching last four digits.
  • Mixing classification with ECCN, licensing, origin, or Chapter 99 fields.
  • Letting a marketplace’s generic “HS code” label overwrite the source system.
  • Failing to re-review variants with different material or construction.
Editorial

Editorial review note

Written by the TariffCatalog Editorial Team for ecommerce document preparation workflows. The page is designed as a preparation checklist, not a filing outcome.

Maintained by Ryan Cole, with review focused on ecommerce catalog, document, and source-check workflow clarity.

Document requirements may be required differently by carrier, destination, shipment value, and product facts. Use the methodology, sources, and corrections pages to understand how the page is maintained.

Maintainer

Reviewed by Ryan Cole

Ryan Cole maintains TariffCatalog from the perspective of a long-time ecommerce operator with 15+ years of experience in product catalog, international shipping, and pre-shipment data workflows. This page is reviewed for document preparation workflow clarity, source-check clarity, and estimate-only or candidate-only wording.

TariffCatalog is a preparation aid, not a customs broker, legal, tax, or freight-forwarding service. Verify final classifications, rates, documents, and filing treatment with official sources or qualified professionals.

Last reviewed: · Maintainer entity: Ryan Cole · Source policy: verified against official customs and tariff sources

Official source note

References to verify

Use official sources, carrier guidance, postal operator rules, and destination requirements to verify before filing or shipping.

FAQ

Common questions

What is the difference between HS and HTS?

HS is the international six-digit foundation. HTSUS extends it to 10 digits for US imports.

What is Schedule B used for?

Schedule B is the US 10-digit commodity classification used for exports and trade statistics.

Can the HTS and Schedule B number be identical?

Sometimes, but not always. Verify the final four digits independently in the current official systems.

Which code should a Shopify seller enter?

Use the field requested for the actual shipment and destination. Preserve separate HS-base, HTSUS, and Schedule B fields rather than one ambiguous value.

Which code is used for a US import?

Use the current 10-digit HTSUS number, along with separate origin and measure checks.

Which code is used for a US export?

Use the current 10-digit Schedule B number and follow current Census/AES reporting guidance.

Is Schedule B the same as ECCN?

No. Schedule B classifies the commodity for export reporting; ECCN belongs to the US export-control system and answers a different question.

How should these codes be stored in a catalog?

Use separate named columns with direction, destination/system, source URL, lookup date, and review status.

Last reviewed: 2026-08-02

Disclaimer

TariffCatalog provides informational tools and preparation workflows only. Verify final classification, rates, document requirements, and filing treatment with official sources or licensed professionals.