SHIPMENT RECORD / 01
Identify the shipment before comparing files.
Commercial records may be drafted by different people and updated at different times. This guide is a comparison framework, not a universal document template or a statement of what a carrier, bank, customs authority or destination market requires.
01 / CONTROLLED BASELINE
Identify the agreed order
Record the PO, seller, buyer, product revision, packing version, quantity and shipment ID. Add the route and delivery term. Resolve conflicting versions before comparing the files.
Where the product definition changed, first identify the current product and packing baseline →. Where the order changed, retain the buyer’s specific revision decision.
A product name, broad destination or previous invoice is not evidence that the current invoice and packing list refer to the same approved order.
02 / COMMERCIAL INVOICE
Check the current commercial invoice
Record its number, date, seller, buyer, currency, goods, quantities, values and order reference. Note whether it is a draft, final or amended version, and keep the reason for each change.
A pro forma invoice (also written proforma) sets out a proposed transaction. Compare it with the commercial invoice used for this shipment. Ask why any quantity, price or party changed.
The invoice needs the same seller and order context that was actually agreed. Keep quotation assumptions visible before comparing totals →
An invoice can describe a commercial transaction. It is not, by itself, proof of payment, title, export declaration, customs clearance or delivery.
03 / PACKING LIST
Match the packing list to the goods
Record the list number, date, package count and type, marks, item-to-package mapping, weights and dimensions. Use the agreed packing version and note who supplied each figure.
Packaging marks and counts should be treated as shipment-specific data, not copied forward solely because a prior order used the same product name.
Check net and gross weight separately. Confirm whether volume uses measured carton dimensions. Match shipping marks to the actual cartons so the receiving warehouse can identify them. Ask the forwarder how measurements affect the freight quote.
A packing list describes the stated packages. It does not prove that every item was packed, weighed, inspected, loaded or accepted for carriage.
04 / SHARED FIELD COMPARISON
Compare the shared fields
Compare names, order reference, goods, quantities, marks, dates and delivery term. Record each difference, who can explain it and which instruction depends on the answer.
The WCO Data Model distinguishes goods-transaction documents such as invoices and packing lists from transport-contract records. Keep transport responsibility and named points in a separate handover record →
Check changes from the proforma invoice, then compare the final shipment details with the bill of lading. Keep agreed amendments beside the original records.
A field match is a reason to continue the review. It is not evidence that all regulatory, carrier, banking or destination-market data requirements have been met.
05 / VERSION AND OWNER
Keep versions and responsible contacts
For each file, keep its source, date received, revision, preparer, checker and recipient. Name the person who must correct it. Keep transport instructions separate; leave missing references unresolved.
If documents changed because the product, packing, factory or timing changed, record the affected scope and buyer decision →
A forwarded file does not establish that its sender has authority to approve a commercial change or issue an instruction for the buyer.
06 / EXCEPTIONS AND NEXT DECISION
Resolve differences before the next instruction
Log missing references or changed parties, goods, quantities, marks, dates and terms. For each issue, record the evidence, responsible person and any agreed deadline. Retain the buyer’s next instruction.
Inspection answers what was checked under its scope. Keep an inspection report separate from invoice, packing and release decisions →
A consistent pair of records, or an inspection result, is not an automatic instruction to release goods, pay a balance, accept a charge or waive an exception.
CONTROL TABLE / 02
Keep one comparison record
| Control | Record | Question to resolve | Do not infer |
|---|---|---|---|
| Order baseline | PO, product and packing revision, quantity, seller, buyer and shipment ID | What current commercial decision do these files describe? | That a familiar product name identifies the same order |
| Invoice identity | Number, date, issuer, buyer, currency, value fields and revision | Which invoice version is being reviewed? | That an invoice proves payment, title or clearance |
| Packing identity | Number, date, package count/type, marks and stated weight or measure fields | Which packing configuration does it describe? | That a list proves packing, loading or carriage acceptance |
| Shared fields | Names, order/shipment ID, goods, quantities, marks, dates and delivery notation | Which differences need clarification? | That agreement proves all external requirements are met |
| Version trail | Source, received date, preparer, checker, recipient and amendment reason | Who owns the next correction? | That a forwarded file is authorised |
| Exception | Affected scope, visible evidence, owner and buyer decision state | What must be resolved before relying on the record? | That a file match is an automatic release or payment decision |
MEASURED / THE SELLER FIELD
Check the seller’s registered identity
Matching names on two files can still leave the seller unclear. In a licensed platform search of 45 Chinese manufacturer names on 21 August 2026, shortened Chinese names produced 44 valid responses; one query was skipped.
| Candidates returned | Queries |
|---|---|
| Exactly one | 4 |
| 2–20 | 17 |
| 21–4,999 | 18 |
| At the 5,000 display ceiling | 5 |
Match the seller to a current registered name and identifier. A single search result still needs checking. For a mainland company, compare its Unified Social Credit Code with the licence and dated company record.
Five responses reached the display ceiling; their true totals are unknown. These are search candidates, not confirmed suppliers or duplicate legal names. The 45-company NHTSA-derived cohort does not represent all Chinese suppliers.
DECISION STATES / 03
Choose the next document action
| State | Visible meaning | Permitted next action |
|---|---|---|
| Baseline incomplete | Order, product or packing version is unclear | Clarify the controlled baseline before comparing files |
| Draft comparison | Invoice and packing-list fields can be reviewed against the baseline | Identify and assign visible differences |
| Version aligned | The two records identify the same known order and packing context; limitations remain visible | Obtain any required party-specific confirmation |
| Exception pending | A difference or missing record affects the current instruction | Hold the affected decision for the appropriate process |
| Buyer instruction recorded | The buyer’s scope-specific decision is retained with the current version | Proceed only within that recorded scope; revisit when facts change |
METHOD AND LIMITATIONS / 04
This is a comparison guide, not a customs, carrier, banking or legal service.
WCO Data Model guidance on main class levels distinguishes goods-transaction documents, including invoices and packing lists, from transport-contract information. China Customs’ goods-declaration guide is an official reference for its own service context. Neither source makes this page a universal list of required documents for a particular transaction or destination.
We did not inspect any supplier, goods, invoice, packing list, carrier booking, declaration, payment or destination-market requirement described by a reader. The current page language is English; the workflow is not limited to English-speaking countries or markets.
OFFICIAL SOURCES / 05
Check the applicable official procedure.
Sources reviewed on 6 September 2026. These references explain document roles. Confirm the current procedure with the authority or broker handling your shipment.
WCO Data Model guidance
Explains how goods-transaction documentation and transport-contract records belong to different procedural contexts.
Read WCO guidance →China Customs goods declaration
Official service guidance for its declared goods process; actual requirements depend on the applicable procedure and current authority instructions.
Read China Customs guide →QUESTIONS / 06
Common comparison questions
Does an invoice have to match a packing list word for word?
Not necessarily. Compare the fields that should identify the same order and shipment, record any difference and ask the appropriate owner to explain it. This page does not decide which fields a specific authority, carrier, bank or buyer requires.
Does a matching pair mean that the shipment can proceed?
No. Transport acceptance, export or import procedure, inspection, payment and buyer release are separate decisions with their own evidence and responsible parties.
What if the supplier sends an amended invoice?
Keep the prior and new references, the affected fields, reason given, source and the person whose instruction is required. Do not silently overwrite the record used for the prior review.
Need tariff input before the invoice is final? Collect the product facts used for classification first.