Planning Use SEO page 429

Wrong HS code customs duty: build the case file

Planning Use only. Broker review required for Entry Use.

A wrong HS code can make a duty estimate look harmless until the shipment is already moving. The code number is only part of the risk. The stack behind it matters too: base duty, special rates, tariff actions, fees, origin treatment, and the product facts that support the path.

quick answer

If you suspect a wrong HS code changed customs duty, compare the duty stack under the supplier code against the strongest supported HTS Candidates. Do that comparison in a Planning Use record with product evidence and official sources before anyone treats the estimate as Entry Use.

facts to collect before drafting

• Product name, SKU, photos, specs, invoice description, and supplier HS or HTS code.
• Declared value, quantity, currency, Incoterms, assists, packaging costs, freight, and insurance notes.
• Country of origin and the production steps used to support that origin.
• Product composition, function, principal use, included accessories, and whether it is sold as a set.
• Current duty estimate from the supplier, marketplace, carrier, broker quote, or calculator.
• Shipment timing, port expectations, and whether a tariff action or duty-rate change is being monitored.

missing facts

Missing value adjustments can make the math weak even when the code is right. Missing product facts can make the code weak even when the math is tidy. Record both. A useful file says which facts are absent, who can supply them, and whether the duty spread is large enough to stop the shipment plan.

HTS candidate notes

Build a small table with the supplier code, at least one alternative candidate, the fact pattern for each, and the duty-stack result. Do not choose the cheaper path because it is cheaper. The better candidate is the one with product facts, HTS language, and ruling support behind it.

authority sources

• USITC HTS
• CBP CROSS
• 19 CFR 177.2
• USTR Section 301 tariff actions
• CBP ruling program

USITC gives the tariff schedule text. CROSS helps test fact patterns. USTR pages matter when Section 301 exposure is part of the duty surprise. Keep the source links in the file so the review trail is visible.

planning path

Start with the landed-cost estimate the team already trusted. Then rebuild the estimate from product facts: candidate code, origin, value basis, duty rate, additional tariff exposure, and missing assumptions.

If the difference is small, the record may become a normal broker-review note. If the difference changes margin, retail price, sourcing, or delivery timing, the SKU needs a Classification Record before the purchase order or catalog code is reused.

Keep the old estimate in the file. It explains the business risk. If the supplier, marketplace, or calculator showed a low duty number, write down the input code, origin, and value used for that estimate. Then place the corrected Planning Use scenario beside it.

The point is not to scare the team. It is to show which assumption moved the duty bill.

related planning questions

• wrong hs code customs duty
• wrong tariff code duty
• hs code duty mistake
• import duty changed
• customs duty surprise

questions importers ask

Can the wrong HS code change the duty bill?

Yes. Classification can affect base duty and trade-remedy exposure. Origin and value facts can change the result too.

Is a calculator enough?

No. A calculator is only as good as the code, origin, and value inputs.

What should I give a broker?

Give the product evidence, supplier code, candidate comparison, missing facts, and the source links used for the Planning Use record.

internal links

• /hts-code-lookup
• /classification-record
• /duty-surprise-scan
• /reasonable-care-file

planning boundary

This page helps prepare a Planning Use record. It does not decide Entry Use, does not bind CBP, and is not legal advice. The importer remains responsible for reasonable care and must obtain broker or customs authority review before filing.