Your Supplier Gave You an HS Code — Does It Survive the Border? Classification, Declared Value and the SKU-Level Duty File China-Origin Merchants Need (2026)

If you source from China and ship into Amazon FBA, a third-party warehouse, or your own facility, a supplier will eventually send you an HS code in a chat message or scribble it onto a packing list — and everyone on the thread will assume the customs question is settled. It usually is not.

A supplier's HS code is an input, not an authority. The classification that matters is the line that appears on the entry filed in the destination country, and the party accountable for its accuracy is the importer of record — normally you or your entity, even when a licensed customs broker prepares and transmits the filing on your behalf. Liability for classification does not transfer just because someone else filled in the form.

One boundary up front: WooliiPorter is a fulfillment and first-mile partner, not a customs broker. We do not file entries, we do not advance or pay duties for you, and we make no promise about a clearance outcome or a duty rate. What we can do is capture and retain the SKU-level data that an entry is built from, so that when a customs authority asks a question you have a file rather than a memory.

1. Who is legally responsible for the code on the entry?

The importer of record is responsible for the accuracy of the entry, including classification and declared value. For US imports, that obligation sits in the entry-summary requirements of 19 U.S.C. §1484, with the penalty framework in 19 U.S.C. §1592. In the European Union, the importer is the customs debtor under the Union Customs Code, and the declaration must be accurate regardless of who submits it. The broker prepares and transmits; the importer owns the answer.

Treat the supplier's code as a lead to verify, not a result. A practical three-step check:

1. Compare against the official nomenclature text, not a search result. For US imports, read the Harmonized Tariff Schedule published by the USITC and work through the General Rules of Interpretation in order, including section and chapter notes. For EU imports, work from the Combined Nomenclature and TARIC. A code that looks plausible in a search box is not evidence.
2. Test the code against three attributes: function, material, and end use. Most misclassification hides in three places: treating a part or accessory as a complete article, or a kit as a single good; getting the material wrong where the material decides the chapter (plastic versus textile versus metal, or goods containing cells and batteries); and codes borrowed from the export side, chosen for export rebate or export-control convenience rather than for your destination's import tariff. If any of the three attributes does not match the heading text, the code needs another look.
3. Have a second person review it and keep a versioned record per SKU. For each SKU, record the code, its source, the date it was confirmed, the rationale (spec sheet, composition, intended use), and who signed off. When an authority asks why you classified it that way, the deliverable is that file.

2. What happens when a code is wrong, and how corrections actually work

There are two failure modes: over-declaring, where you pay more than the law requires, and under-declaring, where duty is short. Operationally, the expensive part is rarely the duty delta by itself — it is the exam, the hold, the storage and handling that follow, and the staff time spent assembling documents after the fact. Under-declaration also enters a penalty framework.

Mechanically, the correction path in the United States generally runs through the Post Summary Correction process before liquidation, and through protest after liquidation. On penalties, 19 U.S.C. §1592 distinguishes between negligence, gross negligence, and fraud, and the prior disclosure provisions give importers a framework for correcting errors proactively, before the government finds them, in exchange for more favorable treatment. In the EU, the Union Customs Code framework provides for amendment or invalidation of declarations and for post-clearance recovery and repayment procedures.

Notice what is deliberately absent here: any specific duty rate, penalty multiple, or dollar figure. Those vary by product, by country, and over time, and a fixed number quoted to you by anyone should not be treated as a basis for a decision. Ask a licensed broker or customs counsel about your specific shipment.

3. What belongs in declared value

After classification, declared value is the second most common place things go sideways. In the United States, transaction value is the starting point: the price actually paid or payable for the goods when sold for export to the United States, plus specified additions such as certain assists, packing, and royalties where applicable. International freight and insurance are generally not added into US transaction value, while many other customs territories value on a CIF-type basis that includes them. Which basis applies depends on the destination country — do not assume the convention on your supplier's invoice is the right one.

Three messy categories to separate before you transmit data:

• Samples, tooling or mold charges, and reimbursed development costs often ride on the same invoice as the goods and have to be split out.
• When you buy the same SKU from two suppliers at different prices, value has to be tracked per purchase order line, not blended into an average.
• The unit you buy in and the unit you declare in frequently differ (bought by carton, declared by piece), so the alignment has to happen at the packing list and ASN level.

The goal is plain: the data your broker or your own filing system receives should map one-to-one onto packing lists and inbound receiving records. If it does not, every later step becomes guesswork.

4. How consolidation changes the structure of an entry

Once parcels from several suppliers are combined into a single shipment in China, the entry no longer maps one-to-one onto supplier invoices. You are choosing between one entry with multiple tariff lines and splitting the shipment. The trade-offs show up in three places: line-level accuracy requirements go up; a later correction to one line can affect the whole entry; and examination scope — one line pulled for review can set the pace for everything on that entry.

That is why certain decisions have to be locked the moment goods arrive inbound: supplier, purchase order, SKU, code, declared value, and declaration elements (quantity, unit, material, end use, specification). Once that mapping exists, it becomes the shared data foundation for the customs file, for inventory fulfillment, and for line-level routing between stocked fulfillment and supplier direct ship. To be clear about the mechanism: consolidation can affect volumetric and chargeable weight and how lines are split for declaration, but it is not a guarantee of lower freight. The result depends on the goods, the packaging, and the lane.

5. Pre-shipment self-check list, per SKU

• Does every SKU have a reviewed import-side code, and not just whatever the supplier sent?
• Is the rationale for that code captured in a document — spec sheet, composition, intended use — rather than in a chat thread?
• Does the record carry a version and an approver? Was it re-evaluated after the last product revision?
• For SKUs bought from more than one supplier, is value tracked per PO line?
• Do packing lists and ASNs agree on units of measure and quantities?
• Have samples, tooling charges, and freight been separated from the value of the goods?
• Is the consolidation plan fixed before inbound, with declaration lines pre-mapped to tariff codes?
• If an authority asks for supporting documents, how fast can you produce inbound photos, weights, and counts?

6. Merchant FAQ

My factory says they already cleared export. Do I still need to worry about import classification?

Yes. Export clearance in China and import classification at destination are separate processes. The code the factory used on the export side may be at a different digit level and may serve export rebate or export-control purposes rather than your destination's import tariff. A clean export filing is not a basis for import classification.

Can the same SKU use different codes across batches?

Classification follows the goods as they actually are at importation. If the product has not substantively changed, the code should stay consistent. If a revision, a material substitution, or a packaging change genuinely alters the classification, version the record, note the reason, and note which batch it takes effect from. The real risk is not that the code changed — it is that it changed and nobody recorded it.

Customs is asking for more documentation. What can the warehouse give me?

Inbound evidence we can retain includes arrival photos, weight records, piece counts, packing lists and ASNs, and the supplier / purchase order / SKU mapping. You can hand that to your broker to support quantity, value, and the physical form of the goods. To be explicit: we do not act as your customs broker, do not represent you before customs, and do not issue binding classification rulings.

How much work is this to maintain?

The first SKU is the slowest. After that, maintenance is incremental per SKU. Compared with the cost of a late document request, a hold, or a corrected entry, upfront maintenance is usually the easier sell inside a team. If you want classification and declaration fields flowing into your own systems or an AI agent workflow, the developer surface is the place to start.

Where to go next

If you are managing multi-supplier consolidation and want a traceable file per SKU from the moment goods arrive inbound, start with supplier parcel forwarding at /for-merchants/supplier-parcel-forwarding and China inventory fulfillment at /for-merchants/china-inventory-fulfillment. The mechanics of combining parcels are described at /services/consolidation; declaration elements and restricted categories are covered by /tools/china-shipping-restrictions-checker; chargeable weight basis is explained at /pricing/shipping-calculator.

If you would rather walk one shipment's data flow with a person — which fields are missing, which codes need review, how the declaration lines should be arranged after consolidation — submit /request-workflow-review. For ongoing use, open an account at /auth/signup and choose Merchant. Teams wiring inbound data into their own systems or AI agents should begin at /developers.