A supplier's commodity code reflects their export jurisdiction, their national tariff schedule and, on occasion, their preference for a more favourable export control classification. It carries no legal authority on a UK import declaration. None whatsoever.
Then there is the companion assumption, equally familiar to anyone working in this field:
"We used this code before Brexit. We have always used it."
Before the UK's departure from the European Union, that approach carried limited consequence. Goods moved freely across borders, declarations were largely administrative and classification errors rarely surfaced. That operating environment no longer exists.
What your commodity code actually determines
The commodity code on a UK import declaration today determines:
- The rate of customs duty applied to your goods.
- Whether trade remedy measures apply — anti-dumping duties, safeguard provisions or retaliatory tariffs.
- Whether an import licence, certificate or authorisation is required.
- Whether the goods are subject to controls, prohibitions or restrictions at the border.
- The scope of your exposure in the event of an HMRC audit — which can reach back four years.
Where the liability sits
The legal liability in each of those scenarios rests with the importer of record. Not the supplier who issued the invoice. Not the customs broker who processed the declaration. Not the procurement colleague who advised using the same code as last time.
With you.
HMRC's Customs Declaration Service captures every import declaration electronically. HMRC has the analytical infrastructure to identify patterns of systematic misclassification across an importer's entire declaration history. When they find it, they find all of it — not just the most recent shipment.
When a review is overdue
If your commodity code base has not been subject to a structured review since your supply chain changed, since Brexit, since your sourcing strategy evolved or since trade remedy measures began affecting your sector — that review is overdue.
"We have always used it" is not a defensible position in a post-Brexit compliance environment. It is, however, a reliable audit finding.