/ 4 min read / pre-shipment / review file / inspection
How to Build a Pre-Shipment Review File
A pre-shipment file helps buyers catch document, product, and quantity problems while correction is still possible.
Why it matters
The final days before shipment are often busy, but they are also the last practical window to correct many mistakes. A pre-shipment review file gives the buyer a structured way to compare documents, inspection evidence, and order details before goods leave the supplier's control.
Evidence to collect
Collect final invoice, packing list, photos, inspection report if used, product specification, label artwork, carton markings, quantity table, shipping terms, and supplier confirmation. Compare these with the PO and sample approval.
How to review it
Look for mismatches in quantity, model numbers, packaging, product descriptions, shipping marks, and invoice details. If the buyer uses a third-party inspection, make sure the inspection report references the same order and product.
Where buyers get misled
Importers get misled when they focus only on whether goods are finished. Finished goods can still ship with wrong labels, vague documents, quantity errors, or product variations that create downstream problems.
Practical next step
Use the pre-shipment file as a release gate. If key documents or photos do not match the order, hold shipment until the supplier corrects the issue or provides an acceptable explanation.
Order-specific review
A pre-shipment file helps buyers catch record, product, and quantity problems while correction is still possible. This is an order-specific exception, so the answer needs to be settled before pickup, loading, or warehouse receipt. Keep the supporting file beside the how build file entry in the order folder.
The working file should contain the final invoice, packing list, carton or pallet record, booking instruction, loading evidence, and transport draft. Both versions matter: the older record explains the original approval, while the newer one shows what the vendor now wants the importer to accept. Name this point in the review file closeout rather than leaving it in chat.
A supplier explanation is not enough when it cannot be tied to a record. 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. The next reviewer should find the answer under inspection without reopening the whole case.
Send the decision to logistics, warehouse receiving, and the purchasing team who approved shipment release. If a broker reply, bank confirmation, inspection record, or supplier letter is still missing, label the approval as conditional and name the person expected to close it. Use the pre-shipment record to show who accepted the result and on what date.
Escalation is appropriate when the physical shipment may no longer match the quantities, parties, or descriptions in the commercial file. Higher value, regulated goods, changed counterparties, customer-facing claims, and repeated corrections all justify a stronger check. Keep the supporting file beside the how build file entry in the order folder.
The working steps are to compare invoice and packing list, check carton markings, match inspection report to order, and confirm quantities. Store the result under the PO number and counterparty name, using a file name that identifies the issue and file version. Name this point in the inspection closeout rather than leaving it in chat.
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. Use the pre-shipment 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 vendor evidence. The next reviewer should find the answer under review file without reopening the whole case.
At the next checkpoint, compare the closed note with the vendor's new document. A repeated mismatch is a vendor-management problem, not another isolated correction. State the remaining limit in the how build file note before the file is closed.
Compare record dates as carefully as record fields. A correction received after decision needs a different note from one received before the buyer committed funds or released cargo. Attach the evidence to the pre-shipment version that now controls the order.
Separate fact from judgment. State what changed first, identify the evidence reviewed second, and record the commercial decision only after those facts are visible. Use the review file record to show who accepted the result and on what date.
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. Put that result in the inspection note for the current PO.
Use the next reorder to see whether the counterparty corrected its process. If the same field fails again, strengthen the decision gate instead of writing another one-off explanation. Link the answer to the how build file checkpoint for this order.
When a screenshot matters, save the underlying file 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. Use the review file record to show who accepted the result and on what date.
Working checklist
- Compare invoice and packing list.
- Check carton markings.
- Match inspection report to order.
- Confirm quantities.
- Review labels before shipment.