/ 4 min read / shipment documents / pre-shipment / import records
How to Build a Shipment Document Pack Before Goods Leave
A shipment pack helps buyers catch invoice, packing, marking, and product-description issues while they can still be fixed.
What to check in the order file
A shipment document pack should come together before goods leave the supplier. At that point, the buyer can still correct descriptions, quantities, carton markings, invoice names, and missing product support.
Start with the commercial invoice and packing list. Compare seller name, buyer name, product description, model, quantity, carton count, weight, dimensions, Incoterm, and shipment reference. Small differences can create broker questions later.
Add product evidence. Photos of goods, carton markings, labels, inspection notes, test reports where needed, and sample approval references help connect the shipment to the order file.
Record who prepared each document. If a freight forwarder or export agent changes document wording, the buyer should know which version the supplier approved.
Use the pack as a release gate. A buyer can create a simple table with four columns: document, field, expected value, and confirmed value. Put invoice issuer, product model, carton count, gross weight, shipping marks, origin wording, and final destination into the table. This makes the review faster than rereading every PDF from the beginning.
Version control matters. Suppliers often send a revised invoice after the forwarder requests wording changes or after the buyer catches an error. Keep the old version, mark the approved version, and record why the change happened. If a broker later asks why the invoice wording differs from the PO, the buyer can answer from the file instead of memory.
Do not wait for perfect documents to ask questions. If the packing list is missing weights, the carton photos are not ready, or the certificate does not match the model, record the missing item and assign it to the supplier before balance payment or shipment release. The pack is useful because it shows gaps while the buyer still has leverage.
Make the decision before the next handoff
Store the pack by shipment, rather than only by supplier. Import questions usually arrive at shipment level, and the team needs the exact files tied to that entry.
A shipment pack helps buyers catch invoice, packing, marking, and product-description issues while they can still be fixed. This is an order-specific exception, so the answer needs to be settled before pickup, loading, or warehouse receipt. Attach the evidence to the how build leave version that now controls the order.
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 sign-off, while the newer one shows what the counterparty now wants the buyer to accept. Name this point in the pre-shipment closeout rather than leaving it in chat.
A supplier explanation is not enough when it cannot be tied to a document. Ask for a dated answer that names the PO, invoice, shipment, product, or claim, then decide whether the missing proof changes the next approval. The next reviewer should find the answer under import records 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 vendor letter is still missing, label the decision as conditional and name the person expected to close it. Record the outcome with the shipment documents evidence before handoff.
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. The how build leave file should show how this point was resolved.
Close the record for the next order
The working steps are to compare invoice and packing list, check seller and purchasing team names, save product and label photos, and record file preparer. Store the result under the PO number and counterparty name, using a file name that identifies the issue and file version. Make this result visible in the import records decision record.
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 shipment documents 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. Put that result in the pre-shipment note for the current PO.
At the next checkpoint, compare the closed note with the counterparty's new file. A repeated mismatch is a counterparty-management problem, not another isolated correction. Name this point in the how build leave closeout rather than leaving it in chat.
Compare record dates as carefully as record fields. A correction received after sign-off needs a different note from one received before the buyer committed funds or released cargo. Attach the evidence to the shipment documents 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. Record the outcome with the pre-shipment evidence before handoff.
Working checklist
- Compare invoice and packing list.
- Check seller and buyer names.
- Save product and label photos.
- Record document preparer.
- Store files by shipment.