HS Code vs HTS Code: What's the Difference?

HS codes are the global six-digit root. HTS codes are the U.S. tariff extension. Learn where they overlap, where they diverge, and how to manage both in product data.

published classificationtariffstrade compliance

HS and HTS are often used interchangeably in supplier spreadsheets, but they are not the same thing. An HS code is the six-digit international root maintained through the Harmonized System. An HTS code is the U.S. Harmonized Tariff Schedule extension used for U.S. import duty and statistical reporting. The overlap is real: the first six digits of a U.S. HTS number come from the HS. The risk is assuming that the six-digit code is enough for a customs entry, landed-cost calculation, or product-data governance workflow.

For catalog teams, the practical answer is simple: store the global HS root, the country-specific tariff code, the evidence behind the assignment, and the market where that code applies. Claro helps teams maintain that layer by normalizing tariff codes across supplier feeds, detecting inconsistent code lengths, preserving provenance, and keeping classification data connected to the product record rather than trapped in one customs spreadsheet.

HS vs HTS in one table

Term What it means Typical length Who uses it Product-data risk
HS code International Harmonized System product classification root 6 digits Customs authorities and trade systems worldwide Too broad for many national duty calculations
HTS code U.S. Harmonized Tariff Schedule classification 10 digits U.S. importers, brokers, CBP filings, landed-cost teams U.S.-specific; should not be reused as if it were valid for every market
National tariff code A country or customs-union extension of the six-digit HS root Often 8, 10, or more digits Importers selling into a specific market Same product can require different extensions in different markets

The six-digit HS root gives everyone a shared starting point. National schedules add precision. In the United States, that means the HTS. In the European Union, teams usually deal with the eight-digit Combined Nomenclature and the ten-digit TARIC layer. In Canada, importers use the Canadian Customs Tariff. The first six digits may look familiar across markets, but the downstream duty rate, quota treatment, statistical suffix, and documentation rules can diverge.

How to read the digits

A tariff code becomes easier to govern when you split it into levels:

  1. 1
    Chapter: first two digits

    The chapter identifies a broad section of goods, such as apparel, machinery, chemicals, furniture, or medical instruments.

  2. 2
    Heading: first four digits

    The heading narrows the product family. This is where products that look similar commercially may begin to separate legally.

  3. 3
    HS subheading: first six digits

    The six-digit HS subheading is the international root. It is the best field to use for cross-market comparison, but it is not the whole import classification for most markets.

  4. 4
    National extension: remaining digits

    The extra digits identify country-specific tariff lines, statistical categories, trade measures, or agency requirements. This is where U.S. HTS, EU CN/TARIC, and other schedules diverge.

Why the difference matters

The code attached to a SKU affects more than a customs form. It can change duty rates, free-trade-agreement eligibility, anti-dumping exposure, quota treatment, admissibility review, and landed-cost projections. It can also affect what your ecommerce, ERP, PIM, or procurement system believes about a product.

Common failure patterns include:

  • Supplier files mix six-digit HS roots with ten-digit HTS numbers in the same column.
  • A U.S. HTS number is copied into a European feed where an EU CN or TARIC code is required.
  • Apparel products are classified without enough fiber, construction, gender, or use attributes.
  • Regulated products carry a tariff code but lack the agency data needed for FDA, EPA, or other partner-government review.
  • Duty analytics roll up codes at the wrong level, making margin and landed-cost models unreliable.

Claro’s classification workflow avoids those failures by treating codes as evidence-backed attributes. A supplier value can be accepted, corrected, or routed for review, but it is not blindly promoted to the canonical product record without checking the product attributes and the market context.

A practical product-data model for tariff codes

If you manage products in multiple markets, use a structure like this:

Field Example Why it matters
hs_root 940161 Lets teams compare products globally at the six-digit level
market US Prevents U.S. and EU tariff codes from being treated as interchangeable
national_code 9401.61.4011 Stores the filing-level code for the destination market
source broker ruling, supplier declaration, official schedule lookup Shows why the code was chosen
effective_date 2026-07-13 Tariff schedules change; old decisions need dates
confidence approved / review / supplier-only Separates trusted classifications from unverified inputs

That model gives customs, finance, ecommerce, and data teams the same source of truth. It also makes future tariff updates manageable: you can query every product with an affected HS root or national code, review only the impacted records, and write the update back through a controlled process.

FAQ

Is an HS code the same as an HTS code?

No. An HS code is the internationally harmonized six-digit product classification root. An HTS code is the U.S. national extension used to determine U.S. tariff rates and statistical categories. The first six digits should align, but the full U.S. code carries additional U.S.-specific detail.

How many digits are in an HTS code?

U.S. HTS numbers are commonly handled as ten digits for import classification. The first six digits are the HS root, while the remaining digits identify U.S. tariff and statistical subdivisions.

Can I use a supplier's six-digit HS code for U.S. import entry?

Usually not by itself. A six-digit HS code is a starting point, but U.S. import entry normally requires the appropriate HTS number and may require additional chapter notes, special tariffs, or agency data depending on the product.

How does Claro help with HS and HTS data?

Claro treats tariff codes as governed product attributes: it normalizes supplier codes, flags mixed lengths and suspicious mappings, links code decisions to source evidence, and writes validated classifications back to the catalog systems teams already use.

Claro

See where your catalog breaks — free

Claro runs this automatically: resolve identity, fill missing attributes, validate updates, and write clean records back into your PIM/ERP. Upload a sample supplier file for a free catalog audit.

Get a free catalog audit