HS codes and customs data for ecommerce inventory

Own the classification process

HS classification should have a named owner inside the seller, importer or appointed advisory team. That owner gathers product facts, checks existing classifications and decides when to involve a customs broker or specialist. A warehouse team may see the SKU every day, but it usually does not have enough technical information or authority to classify the product.

Ownership also prevents silent drift. If buying, product development and logistics each keep their own spreadsheet, the same item can travel under different descriptions or codes. A single controlled record reduces confusion when a broker asks for clarification.

• Name the classification owner
• Record who approved each code
• Review classifications when the product changes

Use complete product facts

A customs-ready product record needs more than a marketing title. It should include what the product is, what it is made from, how it is used, whether it has components, the country of origin and the commercial value basis used for customs work. Regulated products may need additional documents or technical descriptions.

Descriptions should be written for customs and brokers, not customers. A phrase such as premium travel kit may be useful on a product page but weak for customs work. A clearer record names the materials and function so a reviewer can understand why a classification was chosen.

• Keep material composition with SKU data
• Store origin evidence separately from sales copy
• Link supporting documents to the product record

Version control the master data

Product data changes. A supplier may change fabric content, a bundle may gain a component, or a replacement part may ship under an old SKU. Without version control, the brand cannot tell which classification or origin data applied to a specific inbound movement.

A practical version record shows effective date, changed field, approver, reason for change and whether the broker has reviewed it. The warehouse only needs the current operational fields, but the brand and broker may need the history when resolving a declaration query.

• Keep old versions readable
• Do not overwrite classification history
• Tie inbound shipments to the data version used

Define broker hand-offs

Broker review should happen before goods are already on the road where possible. The hand-off should include the product data, commercial documents, importer details, Incoterms or delivery terms where relevant, and any earlier classification decisions. Missing information creates delays and avoidable questions.

The broker may ask for samples, technical sheets or supplier declarations. The brand should decide who responds and how fast, but no universal response time should be assumed. The operating rule is simple: unresolved customs data blocks clean movement.

• Agree required broker documents before booking freight
• Route classification questions to the named owner
• Keep advice records with the SKU

Keep the warehouse out of guessing

A fulfilment warehouse can receive cartons against SKU identifiers, check quantities and flag mismatches. It should not create HS codes from visual inspection or change origin data because a carton label looks different. Those decisions belong to the seller, importer and qualified advisers.

The warehouse can still help by refusing incomplete inbound data, flagging mismatched product labels, and recording discrepancies. That support is operational evidence, not customs advice.

Audit before launch

Before the first European inbound, audit the SKU list for missing descriptions, repeated codes used without explanation, blank origin fields, mixed bundles and products with unclear materials. This is easier to fix before inventory is purchased, packed and booked for freight.

The review should also cover new product launch habits. A brand that adds products weekly needs a lightweight gate so customs data is approved before the SKU is released for sale or replenishment.

• Check every active SKU
• Review bundles separately
• Require qualified customs advice for uncertain classifications

Information to include in a fulfilment brief

• HS codes are master data decisions, not warehouse guesses made when cartons arrive.
• A customs-ready SKU record needs function, material, origin, value basis and supporting documents.
• Version control matters because a product change can affect the customs data used for later shipments.
• Broker review is more useful before freight is booked than after an import query appears.
• The warehouse can flag discrepancies, but classification authority should sit with the seller or adviser.
• Qualified customs advice is needed when product facts do not clearly support an existing classification.

VareYa can scope the warehousing and fulfilment work from a clear operating brief. Customs, tax, product and legal responsibilities should be checked with qualified advisers before inventory moves.

Questions teams often ask

Related VareYa Knowledge Center guidance

• Bonded warehouse considerations for ecommerce brands
• How to send inventory to a European fulfilment partner
• Ecommerce warehousing in the Netherlands
• Importer of record responsibilities for EU ecommerce inventory
• EORI numbers for ecommerce inventory entering the EU
• IOSS versus local EU inventory for ecommerce orders