Skip to content

What happens when the commodity code on your registration changes

A commodity code is not a fact about your product. It is a position in a classification that a different Commission regulation rewrites every year, and that the World Customs Organization overhauls roughly every five. The passport registry stores one, checks it once and keeps the record for ten years. It says nothing about what happens when the code underneath it moves, and the EU has already answered that question once, in customs law, without a grace period.

Sources as at
28 August 2026
Share
LinkedIn X Email
On this page

The short answer

Nothing in the instrument says. That is the honest position, and it is a finding about the instrument rather than about our reading of it.

Commission Implementing Regulation (EU) 2026/1778 stores the commodity code as registration data under Article 8(9)(b), and has the Commission confirm its validity against the permitted ranges for the product group at the moment of registration under Article 8(7)(d). Article 10(3) then keeps that registration data for ten years where Union law sets no specific period. Article 19(2) requires the information in the registry to be kept accurate, complete and up to date at all times.

What the instrument does not contain is any mention of the nomenclature, any requirement to re-check a stored code, any date on which a stored code stops being correct and any transitional arrangement. We looked for all four and found none.

So the duty is clear and the mechanism is absent. The code has to stay right, and nothing tells you when it stopped being right.

Why this is not a small point

Two clocks make it a real problem rather than a theoretical one, and both are published.

The annual clock. The Combined Nomenclature is established under Council Regulation (EEC) No 2658/87, whose Article 12 requires the Commission to adopt a complete version each year, published by 31 October and applying from 1 January following. The current instance is Commission Implementing Regulation (EU) 2025/1926, and its Article 1 does not amend the annex. It replaces it.

The five yearly clock. The World Customs Organization revises the Harmonized System underneath the Combined Nomenclature on a longer cycle, and those are the years that hurt.

Eurostat publishes the arithmetic, and it is the most useful table in this subject. Against a Combined Nomenclature of around 9,500 eight digit codes, Eurostat's own metadata records the changes year by year. In a quiet year the number is small: 18 changes across those roughly 9,500 codes in 2019, and 31 in 2018. In a revision year it is not: 1,260 changes in 2017, 1,725 in 2012, 1,956 in 2007 and 1,434 in 2002, each against a nomenclature of between about 9,400 and 10,400 codes at the time. On those counts a revision year touches something between roughly a seventh and a fifth of the whole nomenclature.

That series stops at 2020. We did not find a published count for any year since, including for the 2022 revision, and that is a gap in the published record rather than a claim that the changes were small.

The next revision is dated. The World Customs Organization has accepted the 2028 edition of the Harmonized System, entering into force on 1 January 2028, comprising 299 sets of amendments. Against a nomenclature of 5,852 subheadings it creates 428 new subheadings and deletes 172, before the Combined Nomenclature's own eight digit subdivisions multiply the effect.

Put the two together. A registration made now is kept for ten years. Ten years spans two Harmonized System revisions.

The EU has answered this question before

This is the part worth knowing, because it is a worked precedent and it is unforgiving.

Binding tariff information is the existing mechanism by which a trader gets an authoritative classification it can rely on. A decision is valid for three years under Article 33(3) of the Union Customs Code. Article 34(1) then says when it stops:

A BTI decision shall cease to be valid before the end of the period referred to in Article 33(3) where it no longer conforms to the law, as a result of either of the following: (a) the adoption of an amendment to the nomenclatures referred to in points (a) and (b) of Article 56(2); (b) the adoption of measures referred to in Article 57(4); with effect from the date of application of such amendment or measures.

Union Customs Code, Article 34(1), quoted verbatim.

Article 34(9) provides a period of extended use, letting a holder keep using a decision for binding contracts for up to six months. Read which grounds it applies to. It opens with "Where point (b) of paragraph 1 or paragraphs 2, 7 or 8 apply". Point (a), the nomenclature amendment, is not among them.

The Commission states the same thing in its own words on its page on the validity of BTI decisions, which lists a change in the Combined Nomenclature among the reasons a decision ceases to be valid and describes no grace period for it.

So the EU's settled answer, in the one place it has had to give one, is that a nomenclature amendment kills a stored classification outright, on the date the amendment applies. The six month cushion exists for other grounds and not for this one.

Two things follow, and only one of them is comfortable.

The customs regime at least dates the failure. It tells a holder exactly when reliance ends. The registry regulation has no equivalent, because it has no cessation rule at all. A stored code that has become wrong is simply registration data that is no longer accurate, which under Article 19(2) is a state you are already in breach of rather than a state you are given time to leave.

Splits are the hard case

Not all changes behave the same way, and the difference decides whether this can be automated.

A renumbering maps one old code to one new code. A machine can do that.

A merge maps several old codes to one new code. A machine can do that too.

A split maps one old code to two or more new ones, and no table can choose between them for a particular product. Somebody has to look at the product.

Splits are not rare and they reach textiles. The World Customs Organization's own correlation tables for the 2028 edition contain entries across chapters 50, 52, 53, 56, 60 and 63, and several are splits: hemp separated out of one heading, cotton buds separated by stick material, protective face masks given their own subheadings. Those are the shape of change that a registry storing one static code per product handles worst.

There is a further wrinkle worth naming. The correlation tables everybody will reach for are published by the World Customs Organization with an explicit statement that they have no legal status and are a guide only, published to facilitate implementation. So the mapping artefact is disclaimed by the body that produces it, and Eurostat's equivalent tables for the Combined Nomenclature are described in its metadata as maintained for statistical comparability over time. We did not find a Commission or Eurostat address for the current year to year table, or any statement of its legal status. National customs authorities publish their own. How this estate types a question it cannot resolve from the source in front of it is set out at how we know.

Where a wrong code actually bites

Three places, and they are not equally urgent.

At the border. ESPR Article 15(2) requires the registration identifier and the commodity code presented to customs to correspond to the data stored in the registry. That is the provision the mismatch runs into, and it is the half of the customs architecture that is not switched on yet, which is set out at what actually happens to a passport at the EU border.

On the proof. The commodity code is one of the five elements a proof of registration carries where relevant. A proof generated after the code moved carries the old value, and what proof of registration proves is narrower than most counterparties will assume in either direction.

In scope. A delegated act defines its product group by commodity code. A code that splits can move a product into or out of scope without anybody at the business touching anything, which is one more reason what a delegated act decides is worth reading before an act arrives rather than after.

What to do about it

The instrument gives no procedure, so what follows is practice rather than compliance.

  1. Treat the commodity code as a maintained value, not a stored one. It is the one field in a registration that a third party rewrites on a published schedule without telling you.
  2. Put the annual nomenclature update on a review cycle. It is published by 31 October each year and applies from 1 January. That is nine or ten weeks of warning, every year, for free.
  3. Find out who owns the code in your business. It is almost never the product team, and the registration is almost never made by whoever files the customs declaration. That gap is where this will fail.
  4. Know which of your codes are in a split. A renumbering is a data job. A split is a classification decision and it needs somebody who can make one.
  5. Record when you last checked. Article 10(1) has the registry log any modification, and what the registry records about you makes that an attributable history. Your own record of when you verified a code is the only version you control.
  6. Do not wait for guidance. We found none, at the Commission or anywhere else, addressing what a business does when the commodity code on a registered passport changes. That is a statement about where we looked, and it is also a reason not to plan around guidance arriving.

The architecture all of this sits inside, and what the registry does and does not hold, is at where your passport data actually lives. Whether any of it reaches your product group yet is kept on the status record.

You might want to read next

Since you have read this, these may answer the questions that usually come next.

Sources

Worth sharing?

Help someone else make sense of product passports.

LinkedIn X Email