Who knows what when products are classified, and where it goes wrong

Engineers know what a product is made of and what it does. Trade compliance knows how the tariff and export control rules read. Brokers know what customs will accept. Finance sees the duty bill. Trouble starts when one of them assigns a code without the others' facts.

What engineering and product management hold

The people who design the product know its composition, its function and its principal use. They know which revision is current and what changed from the last one. That is exactly the evidence a classification rests on.

What they usually do not know is that small design choices move the code. A switch from one alloy to another, a new coating, or a firmware update that adds encryption can change both the tariff heading and the export control status. To an engineer these are routine improvements. Nobody tells compliance, because nobody on the design side sees a reason to.

What the classifier holds

The trade compliance specialist knows the interpretive rules, the section and chapter notes, published rulings and the company's own precedent. They know when an item could reasonably sit under two headings and why the less exposed one was chosen.

They often work from thin material: a spec sheet, a catalogue description, sometimes a photograph. Marketing language is a poor guide. A product described as a "smart device" may be a plain sensor, and a "kit" may be a set of parts that customs will treat separately. The classifier's reasoning is the most valuable thing they produce, and it is the thing least often recorded. The item master gets the code. The argument behind it stays in an inbox or in one person's head.

What procurement and suppliers hold

Buyers know where a product actually comes from, who made it and whether a preferential origin certificate exists. Suppliers frequently send their own code. That code reflects the exporting country's national digits, which can differ from the importing country's even when the shared international portion matches.

The common failure is quiet. Someone in procurement copies the supplier's code into the item record during setup, and it is treated as reviewed when it never was. Origin information has the same weakness: a supplier changes factories, and the certificate on file describes a place the goods no longer come from.

What the broker and logistics team hold

The broker sees what the border actually does. They know which entries drew queries, which were held and which a customs officer reclassified. They know the practical reading of a heading at a particular port.

Under pressure to release a shipment, a broker may amend the code at filing. The goods clear, the problem looks solved, and the correction never travels back to the master record. Over time the code the company believes it uses and the code it has declared drift apart. That gap is what an audit finds first.

What finance holds

Finance knows the duty actually paid, the accruals, the landed cost used in pricing, and any refund or drawback claims. Finance often spots a classification problem before anyone else, because a duty rate jumps or a supplier invoice no longer reconciles to the expected landed cost.

What finance lacks is the cause. A spike might be a tariff change, a new origin, a broker amendment or a genuine error. A reclassification can also open exposure on past entries, and the decision on whether to disclose that sits awkwardly between finance, compliance and legal. When those teams have not agreed on who owns the call, it stalls.

Where the gaps cause the most damage

New products launch before anyone classifies them, so sales quotes a delivered price built on a guessed duty rate. Export shipments leave on an assumed "no licence required" status that nobody confirmed against the actual technical specification. Bundles and kits are classified as a single item in one system and as separate parts in another. And the reasoning for a borderline call disappears when the person who made it moves on, so the next reviewer reverses it without knowing why it was made.

Each of these is a handoff problem. The facts existed somewhere in the business. They just did not reach the person holding the pen.

Questions to ask the people who run it

• When a product design changes, how does compliance find out, and how long after release does that usually happen?
• Who is allowed to enter or edit a classification in the item master, and does procurement ever paste in a supplier's code?
• Where is the reasoning for a borderline classification written down, and could someone new find it?
• When the broker changes a code at filing, what happens next? Who updates the record?
• Which entries have been queried or reclassified by customs, and has anyone compared those to the codes held internally?
• How are export control classifications confirmed for items with software, encryption or dual use potential?
• When finance sees duty that does not match expectation, who do they ask, and do they get an answer?
• How are kits, sets and spare parts handled, and is that treatment the same across every system?
• Who decides whether a past error is disclosed, and has that decision ever actually been made?
• What does the team do by habit that the written procedure does not describe?

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.