HS Codes and Country of Origin in Product Data

A shipment gets held at customs because the Harmonized System code on the paperwork doesn’t match what customs believes the product actually is. Nobody entered it wrong on purpose — the code was typed in once, on a shipping form, by someone who wasn’t a trade compliance specialist, and it’s been copied forward ever since. This is what happens when trade classification lives as a per-shipment field instead of structured catalog data attached to the product itself.

What these fields actually are

HS (Harmonized System) codes classify a product for customs and tariff purposes, internationally standardized at the six-digit level, with countries extending further for their own tariff schedules. The code determines duty rates, whether the product needs specific import documentation, and whether it’s subject to trade restrictions.

Country of origin determines where a product is considered to have been manufactured for trade-law purposes — which isn’t always where it was shipped from, and matters for tariffs, trade agreements, and increasingly for compliance and sustainability requirements downstream.

Both are attributes of the product, not the shipment. The same product should carry the same HS code and origin every time it crosses a border, but when these fields are entered per shipping transaction rather than stored once on the canonical product record, that consistency depends entirely on whoever fills out that specific form.

Where this typically breaks

• Inconsistent codes for the same product across different shipments or different people filling out paperwork, because there’s no single stored value being referenced.
• Codes copied from a similar-but-not-identical product when someone is uncertain and grabs the nearest match rather than researching correctly.
• Country of origin conflated with country of shipment, particularly for products assembled in one location from components sourced elsewhere.
• No normalization or validation catching an HS code that doesn’t match the product category it’s assigned to.

Structuring it properly

Treat HS code and country of origin as fields on the canonical product record — set once, correctly, per product — rather than fields re-entered per shipment. That means researching and assigning them during product onboarding or enrichment, validating that the assigned code is consistent with the product’s classification and attributes, and flowing that stored value through to every downstream system (ERP, shipping documentation) that needs it — the same integration discipline that applies to any attribute meant to stay consistent across systems.

Trade documentation errors tracing back to inconsistent HS codes? Book a 30-minute call.

Related reading

FAQ

Why do HS codes for the same product sometimes differ across shipments? +

When the code is entered per shipment rather than stored once on the product record, consistency depends on whoever fills out each individual shipping document, leading to drift over time.

Is country of origin the same as country of shipment? +

No. Country of origin reflects where a product is considered manufactured for trade-law purposes, which can differ from where it was shipped from — particularly for products assembled from components sourced in other countries.