Planning Use SEO page 3

HTS code lookup: check the facts before import

Planning Use only. Broker review required for Entry Use.

An HTS code lookup is a good first move. It is a bad last move.

The search box can get you into the tariff schedule. It can show headings, duty rates, notes, and possible subheadings. It can also make a weak answer look finished because the result has a number on it.

That number still needs a product file behind it.

TariffCase should use lookup intent as the start of a Classification Record: product facts, Missing Facts, HTS Candidates, Authority Sources, and review status.

quick answer

Use HTS code lookup to find possible tariff provisions in the Harmonized Tariff Schedule of the United States. Do not treat the first plausible result as ready for entry paperwork. For Planning Use, the right output is a short record that explains why a code path may fit and what facts still need Broker review.

This sounds slower than a lookup. In practice, it saves time because the reviewer is not guessing what the importer meant by "adapter", "case", "part", "kit", or "sample."

Short product descriptions cause real classification mistakes.

what to search first

Start with the plain product name. Then search the function, material, and commercial name.

For example, "phone case" may not be enough. You may need to know whether it is plastic, leather, textile, silicone, or part of a set. "Cable" may not be enough either. The connector type, voltage use, and whether it is imported with another product can matter.

When a lookup result looks promising, do not stop. Read the heading language, subheading language, chapter notes, and any notes that seem to narrow the category. Then check whether CBP has published rulings for similar products.

The lookup gives you candidates. It does not do the reasoning for you.

product facts to collect

Before relying on an HTS code lookup result, collect:

• Product name as sold.
• Commercial invoice description.
• Photos of the product and packaging.
• Material composition.
• Main function and ordinary use.
• Whether the product is imported alone, in a set, or as a replacement part.
• Country of origin.
• Supplier HS or HTS code, if available.
• Spec sheet, product page, bill of materials, or catalog export.
• Any prior broker entry or ruling reference.

If you do not have these facts, mark the lookup result as provisional.

missing facts

Missing Facts are the facts that could move the product to another heading, change the duty stack, or make a supplier code unreliable.

• Material is unknown or described only as "premium", "durable", or "mixed".
• Function is unclear or the product has more than one function.
• The item may be a part, accessory, kit, set, or composite good.
• Origin is assumed from the supplier address instead of production facts.
• The supplier code is copied from a non-US market.
• The product may trigger Section 301, AD/CVD, quota, PGA, or special program checks.
• A similar CBP ruling exists, but the facts do not match cleanly.

Write these down. A blank field is easier to miss than a visible warning.

authority sources

Use these sources for the record:

• USITC HTS
• CBP CROSS
• 19 CFR 177.2
• CBP rulings guidance

USITC is the main lookup source for the US tariff schedule. CROSS is useful when a ruling has product facts close to yours. The regulation matters when the file may become a ruling request.

Do not use random lookup sites as authority. They can help you find terms to research, but they cannot replace the official sources.

how TariffCase should handle lookup pages

The page should meet the reader where they are: they need a code, probably fast. Give them the lookup path, then make the risk visible.

TariffCase should ask:

• What product are you importing?
• Which candidate code did you find?
• What facts support that code?
• Which facts are missing?
• Which authority sources were checked?
• What should a Broker review before Entry Use?

That is more useful than a naked code because it creates a record someone can inspect.

common lookup traps

Supplier code copied from another country. Same product name, different material. Product sold as a set. Accessory treated as a part. Part treated as a finished article. Old shipment copied into a new SKU. Origin guessed from where the vendor is located.

None of these mistakes are exotic. They happen because lookup work feels done too early.

The fix is not a longer article. The fix is a better record.

related planning questions

• hts code lookup
• hs code lookup
• hts code finder
• hs code finder
• harmonized tariff schedule search
• us hts code lookup
• hs tariff code lookup
• tariff classification

These searches overlap, but the US entry question should come back to the HTS record.

internal links

• /classification-record
• /duty-surprise-scan
• /reasonable-care-file
• /tariff-calculator

questions importers ask

Is an HTS code lookup enough for import?

No. It is a research step. Entry Use needs Broker or customs authority review based on the actual product facts.

What if my supplier already gave me a code?

Use it as a starting point. Check whether it is a six-digit HS code, a US HTS code, or a code copied from another market. Then compare it to the product facts.

Why do lookup tools disagree?

They may use different assumptions, old data, shallow product descriptions, or non-US code levels. Official sources and product facts should drive the record.

What should I do after finding a candidate code?

Save the candidate, collect evidence, list Missing Facts, check authority sources, and send the record for Broker review before Entry Use.

planning boundary

This HTS code lookup 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.