Planning Use SEO page 427

Supplier HS code audit: check the code before it enters your catalog

Planning Use only. Broker review required for Entry Use.

A supplier HS code audit is a sanity check before a code becomes catalog truth. Supplier codes are often six digits, copied from another country, reused across SKUs, or based on incomplete product facts.

quick answer

For supplier hs code audit, compare the supplier code against product facts, origin, USITC HTS candidates, CBP CROSS rulings, missing facts, and duty exposure. Keep the result in Planning Use until Broker review.

facts to collect before drafting

Supplier code, digits provided, source document, date received, and whether it came from invoice, quote, product page, or spreadsheet.
Product name, SKU, model, material, function, components, use, packaging, and imported condition.
Country of origin, manufacturing steps, supplier country, and whether the code came from a non-U.S. market.
Photos, spec sheets, BOM, labels, product page, invoice, catalog export, and prior broker records if available.
USITC HTS candidate families, CROSS rulings reviewed, rejected alternatives, and Section 301 or trade-remedy prompts.
Missing facts that prevent the supplier code from being trusted.
Whether the code is used in Shopify, ERP, freight forwarder data, landed-cost estimates, or purchase orders.

missing facts

Ask what evidence supports the supplier code. If the supplier cannot explain material, function, origin, or candidate family, record the gap. A code with no support should not flow into Entry Use data.

HTS candidate notes

Start with the supplier code as a clue, then build independent HTS Candidates from official sources. If the supplier code is six digits, the U.S. suffix still needs review. If it came from another country, do not assume it maps cleanly to U.S. duty exposure.

authority sources

Use official sources to test the code. The supplier document belongs in evidence, not authority.

planning path

Create an audit table with supplier code, product facts, source, evidence strength, missing facts, HTS Candidates, duty-risk notes, and review decision. Mark the supplier code as supported, weak, rejected, or needs review.

For SKU catalogs, group codes that repeat across unrelated goods. A copied code across apparel, electronics, and accessories is a warning sign. For supplier spreadsheets, keep the original file and audit date in the record.

The audit should produce a clean next action: accept for Planning Use, ask supplier for evidence, route to Classification Record, or prepare Broker review.

Audit work is most useful before a purchase order is locked. Once the code is copied into Shopify, ERP, broker instructions, and landed-cost sheets, the wrong value starts to look official. Keep the supplier code out of operating fields until the file says what evidence supports it.

For repeat suppliers, track patterns. If one supplier gives unsupported codes for several SKUs, ask for a better evidence packet instead of fixing every line in isolation. If another supplier provides rulings, photos, and composition sheets, record that support too.

questions importers ask

Is a supplier HS code enough?

No. It is a clue until product facts and official sources support it.

What if the supplier only gives six digits?

Record that as incomplete for U.S. import planning.

Should old catalog codes be audited?

Yes, especially when duties changed, origin changed, or SKUs were copied.

internal links

planning boundary

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