Classifications should be reviewed on a cadence and on triggers: at least annually for the active catalogue, and immediately when a product changes materially, a ruling issues on a similar product, or duty outcomes look wrong. Classifications do not expire, but products, notes, and interpretations move, and stale codes quietly misprice every shipment.
Why classifications go stale
A code is chosen for a product as it existed at a moment. Then the supplier changes a material, adds a feature, bundles an accessory, or moves production, and the code that was right describes a product you no longer import. Nobody files a memo saying classification review needed. The product file just drifts away from the code file.
For more on this, see this related guide and our earlier explainer on the same theme.
Tariff schedules and rulings also move. Annual schedule updates, new chapter notes, and rulings on comparable products can shift the correct treatment of an unchanged product. A code untouched for five years is not a sign of stability. It is usually a sign of inattention.
Set the annual cycle by risk
Review the whole active catalogue yearly, prioritised by duty exposure: high volume multiplied by duty rate multiplied by classification uncertainty. The top of that list gets expert review. The long tail of low duty, unambiguous goods gets a lighter confirmation pass. Uniform deep review of everything is unaffordable and unnecessary.
Tie the cycle to a fixed business event, catalogue planning or the annual supplier review, so it survives staff changes. A review that depends on someone remembering is a review that happens after an audit letter, when it costs the most.
Triggers that force an immediate review
New supplier for the same product, a specification or material change, a new feature or bundle, entry into a new market with different rules, a customs query on any entry, and a ruling published on a similar product: each should open a classification ticket automatically in your process.
Readers also found this companion piece from our archive useful.
Make the trigger list part of product onboarding paperwork. The person who changes the product rarely knows the classification consequence. The form has to ask, because the system cannot rely on expertise sitting in the wrong department.
Document reasoning, not just results
For each reviewed code, keep the reasoning: the product description relied on, the headings considered, the notes or rulings applied, and the reviewer and date. In an audit, reasoning on file is the difference between a correction and a penalty discussion, because it evidences reasonable care.
Store the file where entries are made, not in a departed employee's drive. Brokers and internal teams should classify from the same record. Two teams working from two product descriptions will eventually file two different codes for one product, and that inconsistency is itself an audit finding.
Frequently asked questions
Does customs ever tell you a classification is wrong proactively?
Sometimes, through a request for information or a notice on a specific entry, but silence is not approval. Entries liquidate and audits reach back years, so absence of challenge today does not validate a code. Your own review cadence is the control.
Who should do the review, broker or in house?
Either can, provided the reviewer sees accurate product information and documents reasoning. Many importers have the broker propose and an internal owner approve for high exposure items. The importer remains liable either way, so internal visibility matters.
How long should classification records be kept?
Keep them with entry records, generally at least five years, and longer while a product remains in the catalogue. Reasoning files for current products should be living documents, updated at each review, not archived and forgotten.
What is the most common classification drift you see?
Bundles and kits. A product gains an accessory or becomes a set, which can change classification entirely under the rules for composite goods, while the catalogue keeps filing the original single item code out of habit.