2026-06-12 / 4 min read / HS code / broker question / customs readiness

Write the HS Code Explanation Before the Broker Asks

By Trado Asia editorial desk · Published 2026-06-12 · Updated 2026-07-18

A short classification note helps buyers answer broker questions without guessing under deadline pressure.

What to check in the order file

Many buyers wait for the broker to ask why a product uses a certain HS code. By then the shipment may be close to arrival, and the team starts searching old quotes, supplier pages, and photos under pressure. A short explanation written earlier saves time.

The note should describe what the product is, what it does, its main material, who uses it, whether it includes accessories, and which documents support the description. Match that note to invoice wording. If the invoice says only 'parts' or 'accessories,' the broker may need more detail before filing.

The supplier can help, but the importer should not copy a supplier code without review. The supplier may export to several countries, use a local code, or choose a description that helps sales more than customs. Ask for product specs, photos, material composition, and use cases, then keep the buyer's classification reasoning in the file.

This note does not replace professional classification advice when the product is complex. It does give the broker a better starting point and shows that the importer treated the description as an import record, not a last-minute guess.

A short classification note helps buyers answer broker questions without guessing under deadline pressure. This is an order-specific exception, so the answer needs to be settled before broker filing or cargo departure. The next reviewer should find the answer under write hs asks without reopening the whole case.

The working file should contain the commercial invoice, product description, origin support, classification note, broker question, and entry instructions. Both versions matter: the older record explains the original approval, while the newer one shows what the supplier now wants the buyer to accept. Carry the result into the broker question instruction used by the next team.

Make the decision before the next handoff

A supplier explanation is not enough when it cannot be tied to a file. Ask for a dated answer that names the PO, invoice, shipment, product, or claim, then decide whether the missing proof changes the next sign-off. Keep the supporting file beside the customs readiness entry in the order folder.

Send the decision to the importer, customs broker, and logistics owner. If a broker reply, bank confirmation, inspection record, or counterparty letter is still missing, label the approval as conditional and name the person expected to close it. Name this point in the HS code closeout rather than leaving it in chat.

Escalation is appropriate when the broker may receive a cleaner or different product story than the buyer can support from its own records. Higher value, regulated goods, changed counterparties, customer-facing claims, and repeated corrections all justify a stronger check. Link the answer to the write hs asks checkpoint for this order.

The working steps are to describe product function and material, match the note to invoice wording, ask the vendor for specs and photos, and do not copy vendor codes blindly. Store the result under the PO number and vendor name, using a file name that identifies the issue and file version. Use the customs readiness record to show who accepted the result and on what date.

Keep the exception narrow by naming the order, file version, affected quantity or value, and the date when it expires or must be checked again. State the remaining limit in the HS code note before the file is closed.

Outside guidance defines the review boundary, while the importer's own records prove the transaction. Keeping those roles separate prevents a general web page from being treated as counterparty evidence. Keep the supporting file beside the broker question entry in the order folder.

Close the record for the next order

At the next checkpoint, compare the closed note with the vendor's new file. A repeated mismatch is a vendor-management problem, not another isolated correction. Record the outcome with the write hs asks evidence before handoff.

Compare document dates as carefully as document fields. A correction received after decision needs a different note from one received before the buyer committed funds or released cargo. The next reviewer should find the answer under HS code without reopening the whole case.

Separate fact from judgment. State what changed first, identify the evidence reviewed second, and record the commercial decision only after those facts are visible. State the remaining limit in the broker question note before the file is closed.

Check whether the change alters another team's work. Finance may need a new payment basis, logistics a corrected booking field, quality a revised inspection point, or the broker a different product or party description. Keep the supporting file beside the customs readiness entry in the order folder.

Use the next reorder to see whether the vendor corrected its process. If the same field fails again, strengthen the sign-off gate instead of writing another one-off explanation. The write hs asks file should show how this point was resolved.

When a screenshot matters, save the underlying record or message if it is available. Retain the sender, date, version, and order reference so another reviewer can judge the evidence without a cropped image. Make this result visible in the broker question decision record.