Planning Use SEO page 358

Commodity code vs HS code for US import planning

Planning Use only. Broker review required for Entry Use.

Commodity code and HS code are often used loosely in supplier emails, marketplaces, and shipping tools. For US import planning, the practical question is narrower: what code system is being used, how many digits are present, and whether the product facts support a US HTS candidate.

Use this page to translate the terminology into a Planning Use classification record.

quick answer

For "commodity code vs HS code", treat the HS code as the international starting point and the US HTS candidate as the import-planning path that needs product facts and source review. A supplier commodity code can be useful context, but it may be from another country, too short, or based on missing facts.

Do not let vocabulary hide the evidence problem.

facts to collect before using either code

Collect:

The exact code provided, digit count, country or system it came from, and who supplied it.
Product name, SKU, invoice wording, photos, labels, specs, and product page.
Composition, function, material, construction, power source, food-contact, textile, or battery facts when relevant.
Country of origin evidence and manufacturing steps.
Whether the code is for export, import, marketplace listing, carrier paperwork, or supplier catalog use.
US HTS candidate rows, rejected alternatives, and source notes.
Value, quantity, shipment timing, and any trade-remedy question.

If the code has only six digits, write that limitation into the file.

missing facts

Mark the file incomplete when:

The code system or country is unknown.
The digit count does not match the decision being made.
Product facts do not support the code.
Supplier support is only a screenshot or catalog default.
Origin evidence is missing.
No USITC HTS or CBP CROSS source check has been logged.
Broker review has not happened for Entry Use.

These gaps are common. They are also exactly where duty surprises start.

HTS candidate notes

Build candidate rows that separate supplier code, HS-level family, and US HTS candidate. Each row should show the product fact that supports it, the fact that could move it, and the source checked.

Rejected alternatives should stay visible so a reviewer can see why the imported article did not follow the supplier code.

authority sources

Use USITC HTS for the US tariff schedule. Use CBP CROSS for fact-matched rulings. Use 19 CFR 177.2 when a ruling request may be needed. Use USTR when origin and candidate line create a Section 301 question.

planning path

First identify the code type. Then collect product facts, map the code to US HTS candidates, write Missing Facts, and route the record to broker review.

The simplest rule: never upgrade a supplier commodity code into a US import answer without source support.

When in doubt, save the original supplier code and the US candidate side by side.

questions importers ask

Is a commodity code the same as an HS code?

Sometimes people use the terms loosely. Check the country, digit count, and source.

Can I use a supplier HS code for US imports?

Use it as a lead. Verify it against US HTS text and product facts.

internal links

planning boundary

This commodity 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.

Turn this search into a file

Run a free Duty Surprise Scan, then build a Planning Use Classification Record when the Missing Facts matter.

Start scan today →