Planning Use SEO page 17

HS code classification: where the easy answer breaks

Planning Use only. Broker review required for Entry Use.

HS code classification looks simple from the outside. Find the product, choose the code, move on.

Real files are messier. Product descriptions are vague. Suppliers send codes without reasoning. Marketplace categories are copied into customs fields. The product has mixed materials, more than one use, or accessories in the box. A six-digit HS family may be plausible, but the US import path still needs work.

This is why classification should be a record, not a guess.

quick answer

HS code classification is the process of matching a product to a Harmonized System code family. For US imports, use that result for Planning Use, then build a Classification Record with Product Facts, Missing Facts, HTS Candidates, Authority Sources, and Broker review status before Entry Use.

The goal is not to sound certain. The goal is to make the reasoning inspectable.

what makes classification hard

Classification depends on facts that are often missing from normal commerce data.

A product title may say "holder" without saying what it holds. A listing may say "premium fabric" without fiber content. An invoice may say "parts" without explaining the machine. A product may be sold with accessories, but the shipment file treats it like one item.

Those are not edge cases. They are normal import problems.

The record should slow the decision down just enough to catch them.

product facts to collect

For HS code classification, collect:

Product name and invoice description.
Product photos and packaging.
Material composition.
Main function and ordinary use.
Whether the item is a part, accessory, set, kit, or finished article.
Country of origin.
Supplier HS code and explanation.
Product page, spec sheet, bill of materials, or catalog export.
Prior ruling or entry reference.

Each fact should have a source. "Supplier said so" is useful, but it is not the same as a spec sheet or production record.

missing facts

Mark the classification incomplete when:

Material percentages are unknown.
Function is unclear.
The product may be a part or accessory.
The product may be a set or kit.
Origin is not supported.
Supplier code has no reasoning.
US HTS detail has not been checked.
CBP rulings have not been compared.
Extra tariff programs may apply.

Missing Facts are not side notes. They are the reason a classification may change.

authority sources

Use official sources for the classification file:

USITC gives the tariff language. CROSS can show how CBP treated similar facts. The regulation helps when a ruling request may be needed.

what TariffCase should produce

TariffCase should produce a Planning Use Classification Record:

Product summary.
Evidence list.
Supplier code.
HTS Candidates.
Missing Facts.
Authority Sources.
Rejected alternatives.
Review status.

This gives a Broker a file to review instead of a code to reverse-engineer.

internal links

questions importers ask

Is HS code classification enough for US import?

No. It starts the review. US imports need HTSUS detail and Broker or customs authority review before Entry Use.

Why keep rejected alternatives?

Rejected alternatives show the reasoning. They help the reviewer see why the preferred path is stronger.

What if facts are missing?

Mark the record incomplete and ask for the documents. Do not hide the gap.

Can TariffCase decide the entry code?

No. TariffCase can prepare a Planning Use record. Entry Use needs Broker or customs authority review.

planning boundary

This HS code classification 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 →