Planning Use SEO page 296
HTS code vs HS code: the US import difference
Planning Use only. Broker review required for Entry Use.
An HS code and a US HTS code are related, but they are not the same file for an importer. HS gives the international six-digit structure. The US Harmonized Tariff Schedule adds US statistical and duty detail beyond that. A supplier's six-digit code can still be too shallow for a US duty decision.
Use this page to turn the glossary question into a Planning Use record.
quick answer
For "HTS code vs HS code", treat the HS code as the shared six-digit starting point and the US HTS code as the US import schedule path checked against product facts, origin, value, and trade-action exposure.
The practical question is whether the path is supported well enough for broker review.
what HS and HTS mean
HS usually refers to the six-digit Harmonized System structure used across many customs systems. A supplier outside the United States may provide those six digits, or a local tariff code from its own country.
HTS, in this US import context, means the Harmonized Tariff Schedule of the United States. It uses the HS structure and adds US-specific detail that can affect duty, reporting, programs, and trade remedies.
A supplier code can fail for ordinary reasons:
- It may stop at six digits.
- It may be from the exporter's country, not the US schedule.
- It may match a broad name but not the actual material, function, or set.
- It may ignore origin-based duty stack questions.
TariffCase stores the code as evidence, then asks for the facts behind it.
facts to collect before trusting a code
Collect:
- Product name, invoice wording, SKU, product page, and photos.
- Material, function, use, size, power source, or other classification facts.
- Country of origin and production support.
- Supplier HS code, supplier HTS code, and any explanation behind it.
- Value, quantity, freight terms, and shipment timing.
Do not combine unrelated SKUs under one code unless the facts match.
missing facts
Mark the file incomplete when:
- The supplier gives only six digits.
- The code comes from a non-US schedule.
- Material, function, or use is unsupported.
- Origin is assumed from the seller address.
- The product is a retail set but component facts are missing.
- Section 301 or other trade-action exposure is possible but not checked.
- Value adjustments are missing.
These gaps can change the duty stack.
HTS candidate notes
For Planning Use, write candidate rows. Each row should show the candidate path, supporting facts, weak facts, rejected alternatives, and source links.
If the HS code is useful, say why. If it is too broad, say that too. A clean record often says: "supplier provided six digits; US HTS detail still needs support."
authority sources
Use USITC HTS for US tariff text. Use CBP CROSS for ruling examples. Use 19 CFR 177.2 to check whether the fact file is strong enough for a ruling-style review. Use USTR when the candidate and origin may trigger Section 301 exposure.
planning path
Start with the supplier code, but do not end there. Add product facts, origin, value, source notes, and Missing Facts. Then route the file to broker review if it may affect Entry Use.
This is the difference TariffCase cares about: HS and HTS are code systems; the Classification Record is the evidence trail around the code.
questions importers ask
Should I delete the supplier code?
No. Keep it in the record as evidence, then test it.
internal links
planning boundary
This HTS code vs HS code page is a planning artifact. It is not an Entry Use classification, not a binding ruling, and not a legal opinion. The importer remains responsible for reasonable care and must obtain broker or customs authority review before filing.
Run a free Duty Surprise Scan, then build a Planning Use Classification Record when the Missing Facts matter.
Start scan today →