Planning Use SEO page 498

HS code lookup tool vs Duty Surprise Scan

Planning Use only. Broker review required for Entry Use.

An HS code lookup tool answers one part of the problem. A Duty Surprise Scan asks whether the number is safe enough to use for sourcing, pricing, or catalog cleanup before review. Those are different jobs.

quick answer

Use an HS code lookup tool when you need to search official tariff text. Use a Duty Surprise Scan when you need to know whether supplier data, origin, value, and product evidence are too weak to trust yet.

what to compare

A lookup tool starts with search. It can help find possible tariff language. It does not automatically prove that a product fits the language, that origin is supported, or that duty exposure is complete.

A Duty Surprise Scan starts with the shipment or SKU. It checks product facts, Missing Facts, supplier codes, HTS Candidate families, Authority Sources, and duty exposure risk.

missing facts

Missing Facts include material, function, origin, supplier-code support, value basis, trade remedy assumptions, set contents, labels, technical specs, and whether the product has changed since a prior code was used.

The scan should make these gaps visible before the importer relies on a lookup result.

HTS candidate notes

A lookup tool may show tariff headings and notes. TariffCase turns that research into HTS Candidate families tied to Product Evidence. The record should say why each candidate is plausible and which facts still need support.

This is the difference between finding tariff text and building a reviewable file.

authority sources

Authority Sources are official sources checked during the scan. The scan should link the source back to the facts in the product file.

Duty Surprise Scan workflow

The scan reviews supplier code depth, product facts, origin, value, duty stack exposure, and missing evidence. If the risk is low, the importer has a cleaner planning file. If the risk is high, the SKU should move into a Classification Record or Ruling Packet preparation.

It is a better fit than a plain lookup when the importer is about to quote landed cost, approve a supplier, update a catalog, or move inventory.

review file contents

The scan should produce a compact file: product description, evidence list, supplier code, Missing Facts, HTS Candidate families, Authority Sources, origin notes, value basis, and duty exposure flags.

The file should also say why the importer ran the scan. Sourcing decision, catalog cleanup, checkout estimate, and broker preparation are different planning jobs.

That context changes the next action. A sourcing scan may need a margin warning; a broker-prep scan needs cleaner evidence and sharper questions.

Keep the scan result linked to the SKU. If the product moves from planning into purchase order review, the same gaps should not be rediscovered from scratch.

questions importers ask

Do I still need a lookup tool?

Yes. Official lookup is useful. The scan checks whether the lookup path fits the product evidence.

What does the scan catch?

Weak supplier codes, missing origin support, product-fact gaps, and duty stack assumptions.

When should I scan?

Before shipment, before checkout estimates go live, or before a high-volume catalog update.

internal links

planning boundary

This lookup versus Duty Surprise Scan page is a planning artifact. It is not an Entry Use decision, 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 →