/ 4 min read / broker request / customs response / import records
Broker More-Information Request Response Files
When a broker asks for more information, the answer should become a reusable import record.
What to check in the order file
A broker's request for more information is not just an email to answer quickly. It is a signal that the import file needs a clearer product, value, origin, or party explanation. The buyer should treat the response as a record that may be reused on the next shipment.
Create a response file with the broker's question, the answer sent, supporting documents, supplier explanation, and any corrected invoice or packing list. If the answer changes product wording, origin support, or value logic, update the standard wording before the next order ships.
Do not let the supplier answer the broker indirectly without buyer review. The supplier may use a sales description, local export wording, or a shortcut that does not match the importer's obligation. The buyer should own the final answer even when the supplier provides facts.
After clearance, keep the response file with the entry and shipment folder. If the same question returns on a reorder, the team can improve the file instead of sending a rushed version of the same explanation.
When a broker asks for more information, the answer should become a reusable import record. This is an order-specific exception, so the answer needs to be settled before broker filing or cargo departure. The broker more files file should show how this point was resolved.
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 sign-off, while the newer one shows what the supplier now wants the importer to accept. Name this point in the customs response closeout rather than leaving it in chat.
Make the decision before the next handoff
A vendor 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. Put that result in the import records note for the current PO.
Send the decision to the importer, customs broker, and logistics owner. If a broker reply, bank confirmation, inspection record, or vendor letter is still missing, label the approval as conditional and name the person expected to close it. Record the outcome with the broker request evidence before handoff.
Escalation is appropriate when the broker may receive a cleaner or different product story than the order owner can support from its own records. Higher value, regulated goods, changed counterparties, customer-facing claims, and repeated corrections all justify a stronger check. Attach the evidence to the broker more files version that now controls the order.
The working steps are to save the broker's exact question, attach the files used to answer, review supplier wording before sending, and update standard wording if the answer corrected a weak field. Store the result under the PO number and supplier name, using a file name that identifies the issue and file version. Name this point in the import records closeout rather than leaving it in chat.
Save the exception narrow by naming the order, document version, affected quantity or value, and the date when it expires or must be checked again. Use the broker request record to show who accepted the result and on what date.
Outside guidance defines the review boundary, while the order owner's own records prove the transaction. Keeping those roles separate prevents a general web page from being treated as counterparty evidence. The next reviewer should find the answer under customs response without reopening the whole case.
Close the record for the next order
At the next checkpoint, compare the closed note with the supplier's new record. A repeated mismatch is a supplier-management problem, not another isolated correction. Make this result visible in the broker more files decision record.
Compare file dates as carefully as file fields. A correction received after approval needs a different note from one received before the buyer committed funds or released cargo. Keep the supporting file beside the broker request entry in the order folder.
Separate fact from judgment. State what changed first, identify the evidence reviewed second, and record the commercial decision only after those facts are visible. Record the outcome with the customs response evidence before handoff.
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. Link the answer to the import records checkpoint for this order.
Use the next reorder to see whether the supplier corrected its process. If the same field fails again, strengthen the sign-off gate instead of writing another one-off explanation. Link the answer to the broker more files checkpoint for this order.
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. Record the outcome with the customs response evidence before handoff.
Working checklist
- Save the broker's exact question.
- Attach the documents used to answer.
- Review supplier wording before sending.
- Update standard wording if the answer corrected a weak field.
- Keep the response with the entry record.