Classify products: how the process runs, step by step

Product classification starts when a new or changed item enters the product master. Technical owners supply the facts. A trade compliance specialist assigns the tariff code and export control status. A reviewer approves the result, and master data staff record it so brokers, logistics and finance all use the same answer.

The steps in order

1. Raise the classification request. Product management, engineering or procurement creates or changes an item in the product master. The system or a manual form flags it as needing a trade classification before it can be shipped, bought across a border or sold abroad.

1. Assemble the product facts. The engineer or product owner supplies what the item is made of, what it does and how it is packaged. Drawings, data sheets and photographs help. For purchased goods, the buyer collects this from the supplier. Weak descriptions here cause most later disputes.

1. Determine the tariff classification. A trade compliance analyst reads the facts against the customs tariff and its interpretive rules. Explanatory notes and published rulings guide the choice of heading and subheading. The analyst then picks the national code for each country where the item is imported, because these differ below the shared international level.

1. Assess export control status. An export control officer, sometimes the same analyst, checks the item against dual use and military control lists. Software and technology get the same scrutiny as physical goods. The outcome is a control code or a finding that the item is not listed, plus any licence the destination would require.

1. Note origin and preference details. Where free trade agreements matter, the analyst or a supply chain colleague records country of origin and whether the item can qualify for reduced duty. This often needs a bill of materials and supplier declarations.

1. Review and approve. A senior specialist or the customs manager checks the reasoning, especially for items that sit between headings. Unclear cases may go to outside counsel or a customs broker. When the risk justifies it, the company applies to the customs authority for a binding ruling and holds the item until it arrives.

1. Record the decision. The master data team enters the codes in the ERP or trade management system, along with a short written rationale and links to supporting documents. Shipments stay blocked until these fields are populated.

1. Communicate downstream. Brokers and freight forwarders receive the codes for declarations. Finance uses them to estimate duty for landed cost and accruals. Sales operations needs the export status to screen orders.

1. Maintain the classifications. When tariff schedules are revised, control lists change or a product is redesigned, the analyst revisits affected items. Errors found in audits or broker queries lead to corrections and, where duty was underpaid, a disclosure to the authority prepared with legal and finance.

Where the handoffs break

The weakest point is usually between steps two and three. Analysts receive a part number and a vague name, then guess or chase engineers for days. Some teams classify from the description alone and never see the product.

Another gap sits at step seven. A correct decision that never reaches the master data, or reaches it for one country only, produces declarations that contradict each other.

Maintenance is the step most often skipped. Codes assigned years ago stay in place long after the tariff or the product changed.

Questions to ask the people who run it

The written procedure and the daily practice rarely match. These questions tend to surface the difference.

• When a request arrives without enough technical detail, what actually happens? Does someone wait, guess or copy a similar item?
• Who has the final say on a disputed code, and is that written down anywhere?
• Do brokers ever classify items themselves when the master data is blank? Does anyone check what they used?
• How are country specific codes kept in step with the shared heading when one of them changes?
• Where is the rationale for each decision stored, and could an auditor find it without asking the analyst?
• What prompts a review of existing classifications? Is it a schedule, a tariff update or only a problem at the border?
• Are export control checks done for software releases and technical data shared by email, or only for physical shipments?
• When finance sees a duty charge that looks wrong, who do they tell, and does it change the master record?
• Which items are shipped under a code someone privately doubts?

What to watch when changing the process

Moving the fact gathering earlier, into product design or supplier onboarding, usually helps more than speeding up the analyst. Requiring a rationale field before a code can be saved makes reviews and audits far easier. Any automation that suggests codes still needs a qualified person to approve them, because customs authorities hold the importer responsible regardless of the tool used.

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.