/ 4 min read / HS code / classification / broker questions
Reviewing a Supplier's Suggested HS Code
Supplier HS code suggestions can help research, but buyers should not treat them as final classification.
What to check in the order file
Suppliers often provide an HS code because they use it for export paperwork or prior customers. That suggestion can help start the discussion, but it should not become the buyer's final classification without review.
Ask what product and market the supplier's code came from. A code used for export from one country may not settle import classification in the buyer's destination. Product material, function, components, and use still matter.
Give the broker a better file than a number. Provide product description, material, photos, specification sheet, catalog page, use case, and any questions the supplier already answered. A broker can work more effectively from product evidence than from a supplier's unsupported code.
If the supplier changes product description to fit a preferred code, pause. Classification should follow the goods, not the other way around.
Supplier HS code suggestions can help research, but buyers should not treat them as final classification. The immediate question is whether the order file supports a decision on reviewing supplier code before broker filing or cargo departure. The reviewing supplier code file should show how this point was resolved.
Start with the last version the buyer approved, then compare it with the commercial invoice, product description, origin support, classification note, broker question, and entry instructions. Identify the changed name, value, quantity, address, product detail, or instruction rather than relying on the counterparty's summary. Name this point in the classification closeout rather than leaving it in chat.
Make the decision before the next handoff
Test the file by handing it to someone who missed the call. That reader should be able to identify the old position, review the vendor's evidence, and understand why the change was accepted, rejected, or limited. Link the answer to the broker questions checkpoint for this order.
Ownership sits with the importer, customs broker, and logistics owner. The handoff note needs the active decision, controlling record, unresolved point, and date of the next check so teams do not act from different versions. Use the HS code record to show who accepted the result and on what date.
Incomplete evidence leaves a practical exposure: the broker may receive a cleaner or different product story than the importer can support from its own records. Put that consequence in the approval note and choose a hold point, narrower approval, or outside review when the value warrants it. The reviewing supplier code file should show how this point was resolved.
Before closing the review, ask where the suggested code came from, send product evidence to the broker, do not rely on export code alone, and check material and function details. The final note should be short enough to scan and specific enough for finance, logistics, quality, or customer service to use. State the remaining limit in the broker questions note before the file is closed.
Write the sign-off boundary in plain terms. It may cover this PO, shipment, value, model, or vendor answer, but it should not imply acceptance of every future variation. Carry the result into the HS code instruction used by the next team.
The cited sources provide background for HS code; the decision still rests on current order documents. Keep a source only when it supports the actual question being asked. Link the answer to the classification checkpoint for this order.
Close the record for the next order
Carry one useful control into the next order: the control that addresses the mismatch actually found. There is no reason to turn every reorder into a full investigation. Name this point in the reviewing supplier code closeout rather than leaving it in chat.
Read the documents in transaction order: approved baseline, counterparty request, revised record, buyer check, and final approval. That sequence shows whether the change arrived before or after money, production, pickup, or a customer commitment moved. Keep the supporting file beside the HS code entry in the order folder.
Do not close with a vague instruction to monitor the vendor. Name the next file, deadline, owner, and approval gate so the open point has a route to closure. Use the classification record to show who accepted the result and on what date.
Identify one record as final. Rejected drafts can remain for history, but their file names should make clear that they no longer authorize payment, shipment, or claims. Link the answer to the broker questions checkpoint for this order.
A month later, the file should still answer who changed the record, why the importer accepted the result, and what remained unverified. That is the practical test of whether the matter was documented rather than merely discussed. Link the answer to the reviewing supplier code checkpoint for this order.
Separate supplier evidence from purchasing team conclusions. Store the original record first, then add the comparison and approval note so later corrections can be tested without rewriting history. Carry the result into the classification instruction used by the next team.
Working checklist
- Ask where the suggested code came from.
- Send product evidence to the broker.
- Do not rely on export code alone.
- Check material and function details.
- Save classification questions and answers.