International orders on a separate shelf
Every morning the international orders that failed to label are printed out and put to one side. The carrier's system rejected them: description too vague, commodity code missing, country of origin blank. Somebody emails the clients to ask. Some reply the same day, some next week. Meanwhile the orders wait, and the client's overseas customers wait longer.
The ones that did label are not safe either. A parcel with 'clothing' as its description and a guessed code can be held at the destination, and it comes back weeks later with charges attached.
Why customs data is always missing
Clients set up their products to sell in the UK. Their shop platform might have a field for commodity codes, but it was never filled in. Their suppliers know the country of origin, but nobody asked. The warehouse is where the gap becomes visible, because the carrier label is the first system that insists on the data.
| Field | Common problem |
|---|---|
| Commodity code | Blank, or copied from a similar product without checking |
| Country of origin | Left as the UK because that is where the brand is |
| Item description | Too generic for customs purposes |
| Declared value and currency | Shop price including discounts or VAT inconsistently |
| Weight per item | Missing, so the parcel weight is split evenly |
Which codes and values are right is a question for the client and their customs adviser. The warehouse's problem is that it is holding orders it cannot ship.
What holds and failures cost
Orders stuck on your floor, taking space and attention. Parcels returned with charges that someone has to recover. Clients whose international sales suffer and who suspect the warehouse is the problem. And staff time spent chasing data one SKU at a time, which repeats every time a client launches a range.
Held parcels also create unhappy end customers who are not your customers. They contact the brand, the brand contacts you, and you contact the carrier, and by the time the answer travels back along that chain the customer has asked for a refund.
The longer-term cost is that clients start to restrict international selling, or move it to a different warehouse, because it feels unreliable. That is volume you had and lost for want of a few product fields.
The customs data layer we build
- A customs completeness check across each client's SKUs in your WMS, listing what is missing for international shipping.
- A client-facing form or spreadsheet round-trip to collect the missing fields, per SKU, with validation of code formats and required fields.
- An order-level check when an international order arrives: every line has complete customs data, the value is present, the destination's requirements for your carrier are met.
- Holds with a clear reason for orders that fail, and a same-day notice to the client listing exactly what is needed.
- Data passed to the carrier label or electronic customs submission through the carrier's API, so the paperwork matches the order.
- A record of the customs data used per shipment, for any later query.
We do not decide commodity codes or values for your clients. Where descriptions suggest a code is inconsistent, the check can flag it for the client to review.
What changes
Missing data is found when the product is set up, not when a customer in another country is waiting. Failed labels become rare, and when they happen the client knows exactly why. Your team stops chasing data by email.
Is this your international shelf?
- International orders regularly fail at label creation.
- Client product data has no commodity codes or origin.
- Parcels come back from overseas with charges.
- Staff email clients for customs data order by order.
- New ranges launch without anyone checking customs fields.