Process trade preferences: who knows what, and where the gaps bite

Trade preferences depend on facts scattered across people who rarely talk. Procurement knows where parts come from, engineering knows what goes into the product, the broker knows what was declared, and finance sees the duty bill. Trouble starts when a preference claim rests on one person's assumption about another's knowledge.

Trade compliance knows the rules, not the parts

The trade compliance specialist can read a rule of origin and say what a product must satisfy to qualify. A tariff shift here, a regional value threshold there. What they usually cannot see is the factory floor. They depend on a bill of materials someone else maintains and on supplier statements someone else collected. So a qualification decision can be technically sound and factually wrong.

Procurement holds origin and treats it as a form

Buyers know which supplier ships which component. They know when a source changed because a cheaper vendor came along. They rarely know that the switch broke a preference claim. To a buyer, an origin declaration is one more document in the onboarding pack. Nobody told them it carries legal weight, so it gets chased once and forgotten when it lapses.

Suppliers know their own origin best, and often guess. A distributor signs a standing declaration covering goods it buys from several mills. Ask how it determined origin and the answer is often silence.

Engineering owns what the product is made of

Product teams change specifications for good reasons. A part is discontinued. A cheaper resin performs just as well. Each change can move a tariff classification or tip the value balance. Engineers seldom know a classification exists, let alone that their change order should trigger a fresh origin review.

The broker sees the declaration, not the business

The customs broker files entries and claims whatever preference code arrives with the shipment instructions. Brokers know what the authorities have challenged lately and which claims draw queries. They do not know whether the certificate behind a claim is current or whether the product has changed since it was issued. Many will apply a preference simply because it appeared on the last entry for the same part number.

Finance sees savings now and exposure later

Finance books the duty saved and likes the number. The liability sits elsewhere. A wrong claim surfaces in a verification or audit long after the goods cleared, with back duty and interest owed. Because the saving and the cost land in different periods, and often in different budgets, finance can end up rewarding a claim nobody verified.

Finance also tends to hold knowledge about drawback or duty deferral arrangements that interact with preference choices. That knowledge seldom reaches compliance.

Sales makes promises to customers

Customers ask for origin certificates so they can claim reduced duty on their own imports. Sales agrees, because losing a deal over a form seems absurd. The person issuing the certificate then signs for an origin they never tested, under pressure from a colleague who has already promised it.

Where the gaps cause trouble

Most failures share a shape. A fact changes in one corner of the business and the claim built on it keeps running somewhere else. A supplier moves production offshore. A certificate expires and the broker keeps filing against it. Nobody acted in bad faith. Each person did their job with what they could see.

Ownership is the other recurring failure. When an origin query arrives from a customs authority or a customer's auditor, it lands with whoever signed. That person then discovers the supporting records sit with a buyer who has moved on and a supplier that no longer answers.

Before redesigning anything, map who holds each fact a claim depends on, and who would notice if it changed. The second half of that question is usually where the redesign earns its keep.

Questions to ask the people who run it

• When a supplier changes, who tells the person responsible for origin, and how do they find out?
• Which preference claims are filed because they were filed last time?
• What happens when a supplier declaration expires? Who notices first?
• Does an engineering change order ever reach trade compliance, or only purchasing?
• Who signs certificates of origin for customers, and what do they check before signing?
• When was a claim last challenged, and who could find the evidence?
• Does the broker apply preference codes from written instructions or from past entries?
• Who in finance understands how much of the duty line depends on preferences being right?
• If a customer asked for the proof behind a certificate, where would the file actually be?

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.