Short answer: The EU's Combined Nomenclature, the 8-digit extension of the HS system used for customs declarations, is updated every year with changes taking effect on January 1. Codes split into more specific subheadings, merge, or gain new legal notes, and duty rates can change with them. For brands shipping to the EU, the annual update means last year's correct classification can silently become this year's wrong one, with the wrong duty attached.
How the annual cycle works
The European Commission publishes the updated Combined Nomenclature in the autumn, usually October, and it applies from the following January 1. The update reflects decisions from the World Customs Organization, EU policy changes, and statistical needs. Most years bring a few hundred changes across the thousands of codes.
Changes come in three flavors. Splits divide one code into two or more specific subheadings, often because trade in a product category grew enough to deserve its own line. Merges combine rarely used codes. And legal notes get added or amended, changing how a code is interpreted without changing the code itself.
The correlation tables published alongside the update map old codes to new ones, but they are a starting point, not an answer. A one-to-many mapping means someone has to decide which new code fits the actual product.
Why it matters for duty calculations
Duty rates attach to the CN code, so a code change can change the duty overnight. A product that moved to a new subheading with a higher rate costs more to land on January 1 than it did on December 31, with no change to the product, the price, or the supplier.
The bigger risk is using an expired code. Declarations with codes that no longer exist get rejected or, worse, accepted under a wrong mapping that understates the duty. Understated duty discovered in a later audit comes back with interest and penalties.
For brands showing duty-inclusive checkout totals, stale codes mean wrong customer-facing prices. The total was calculated against last year's tariff, and the difference comes out of margin when the real duty is assessed.
Which products need a yearly review
Priority goes to products near code boundaries: items whose classification was ever debatable, products in categories the Commission has been subdividing, and anything with a high duty rate where a small change moves real money. New product launches from the past year deserve a check too, since they were classified under the old nomenclature.
Volume matters as well. A one-percentage-point duty change on a hero SKU shipping thousands of units a month dwarfs a bigger change on a slow mover. Rank the review queue by duty spend, not by SKU count.
Also watch products with binding tariff information. A BTI references specific codes, and nomenclature changes can affect its scope. Most regimes handle the transition, but the classification logic should be revalidated rather than assumed.
An operational checklist for the update
When the new nomenclature publishes in autumn, pull the correlation tables and run your SKU list against them. Flag every product whose code split, merged, or changed notes. This is a data exercise that should finish before the holiday shipping peak, not during it.
For flagged products, revalidate the classification against the new legal notes and confirm the duty rate. Update the product master data, the checkout calculation tables, and any binding rulings that reference the old codes.
Then set a calendar reminder for next October. The update is annual and predictable, which makes it one of the easiest customs risks to manage, as long as someone owns it. Assign the ownership explicitly, because predictable risks are the ones teams forget.
Questions buyers ask
Do I need to reclassify every SKU each year?
No. Most codes do not change in a given year. The efficient approach is to screen the full list against the correlation tables and revalidate only the products whose codes were touched.
What if I keep using an old code by mistake?
Declarations may be rejected at filing, or accepted and later corrected in an audit with back duties and penalties. Voluntary disclosure before an audit generally produces a better outcome than waiting to be caught.