A delivery dispute rarely starts with a missing law. It starts with a missing fact.

The cargo is late, wet, short, held at customs or delivered to the wrong point. Sales says the supplier was responsible. Logistics says risk had already transferred. Finance has a freight invoice but not the booking confirmation. The warehouse has photographs but no timestamped receiving record. Three weeks later, everyone is debating a three-letter Incoterms rule while the documents that could settle the argument are scattered across five inboxes.

A strong delivery file is therefore not a pile of shipping paperwork. It is a decision record. It lets a reviewer answer four questions quickly: what the contract required, where delivery and risk were supposed to change hands, what physically happened, and what each party did after the problem appeared.

Here are the 14 record groups worth preserving.

1. The signed sales contract and every incorporated document

Start with the version that actually became binding, not the latest Word draft someone happens to find.

Keep the signed contract, accepted purchase order, order acknowledgement, incorporated standard terms, schedules and any document the contract expressly pulls in. If the Incoterms rule appears only in a purchase order or quotation, preserve the acceptance trail showing whether that document became part of the deal.

A reviewer should be able to see the exact rule, the named place or point and the version, for example FCA [named terminal], Incoterms® 2020.

Without that, the dispute may begin one step earlier: did the parties agree the same delivery term at all?

2. The quotation and commercial assumptions behind the price

The final price often hides a transport model.

Keep the quotation that shows whether freight, terminal handling, insurance, customs work, duties, taxes or last-mile delivery were included. Preserve any assumption about shipment size, route, port, carrier mode, free time or destination address.

Why does this matter? Because a charge dispute can look like a legal allocation problem when it is actually an undocumented pricing assumption.

A later route change from one port to another can also change costs without changing the product price. The file should make that visible.

3. The purchase order and acceptance trail

A purchase order can add dates, quantities, delivery locations, reference specifications or a different Incoterms line.

Preserve the original PO, amendments, seller acknowledgement and any email that accepts or rejects changed terms. If the parties use portals, export the relevant order history rather than assuming the platform will retain it forever.

The purpose is not to collect every message. It is to establish the final commercial instruction.

4. The transport map and named-point note

One page can prevent days of reconstruction.

Write the real chain: factory → truck → export terminal → vessel → import terminal → rail → warehouse. Then mark the intended delivery/risk point and the separately named carriage destination where those are different.

This is particularly useful with C rules. The seller may pay carriage to a destination while risk transfers earlier when the goods are delivered to the carrier under the incorporated rule.

The note is not a substitute for the contract. It is an operating map that tests whether the contract and the physical flow match.

5. Carrier booking and routing instructions

Keep the booking confirmation, carrier instructions, nominated carrier details, route, voyage/flight/truck information, pickup window and changes.

A common dispute is not “who had risk?” but “who changed the route, and when?” A carrier substitution, rolled vessel, transshipment or delivery appointment change can affect timing and evidence.

If the buyer nominated the carrier, preserve that instruction. If the seller selected the carrier, preserve the basis of the booking. Control of carriage can matter independently from risk allocation.

6. Handoff evidence at the delivery point

This is often the most important operational record.

Depending on the rule and mode, it may include a carrier receipt, terminal interchange record, signed pickup record, mate's receipt, on-board notation, warehouse release or other evidence of physical handoff.

The record should identify the goods, date and time, location and receiving party or carrier.

If damage is discovered later, this record helps place the cargo on a timeline. It does not automatically prove who caused the damage, but it narrows the factual window.

7. Bills of lading, waybills and other transport documents

Preserve the issued transport document and any amendment, surrender instruction or release record.

Do not treat every transport document as if it has the same legal function. A bill of lading can have different attributes from a sea waybill, air waybill or road consignment document. Electronic records can also raise jurisdiction-specific issues.

UNCITRAL's MLETR provides a model-law framework for electronic transferable records, including records used in transport and trade, but its legal effect depends on adoption and the relevant legal system.

The file should therefore record not only the PDF, but what document was actually issued and how it was controlled or transferred.

8. Packing, weight, seal and loading records

When goods arrive short, wet, crushed or contaminated, small operational records become large evidence.

Keep packing lists, weight records, container number, seal number, loading photographs, pallet counts and any pre-loading condition report. For sensitive goods, preserve temperature or humidity logs where relevant.

A seal mismatch does not by itself decide liability. A loading photograph does not by itself prove condition at destination. Together, however, they can build a coherent chronology.

9. Insurance certificate, policy and claims instructions

CIP and CIF include seller insurance obligations, but the minimum structure and transport-mode context differ.

Keep the certificate, policy wording, insured value, covered voyage, exclusions, deductible, beneficiary/claimant information and claims-notification procedure.

The practical mistake is preserving only a one-page certificate and discovering after loss that nobody has the policy terms or knows the notification deadline.

Insurance evidence belongs in the delivery file before a claim exists.

10. Export and import clearance records

Preserve declarations, broker instructions, classifications used, permits or licenses where relevant, duty/tax records, customs holds and release messages.

This is especially important when a destination rule is chosen. DDP, for example, places significant import-formality responsibility on the seller under the rule, but whether the seller can legally and practically act in that role is a local-law question.

A customs problem can be caused by classification, documentation, importer eligibility, sanctions, product rules or missing data. “DDP” alone will not diagnose which one.

11. Inspection, condition and receiving evidence

At destination, keep receiving time, quantity count, visible-condition notes, exception notations, photographs and inspection reports.

Make the process repeatable. Photographs should show context as well as close-ups. Record container or package identifiers. Preserve who inspected, when, and before or after unloading.

If product conformity is also disputed, separate transit condition from specification testing. A box crushed in transit and a product manufactured out of specification are different factual questions even if they appear in the same claim.

12. Delay chronology and milestone timestamps

For a delay dispute, build a neutral timeline before arguments harden.

Track promised ship date, actual pickup, gate-in, departure, transshipment, arrival, customs release, delivery appointment and actual receipt. Mark who controlled each milestone and what changed.

Then separate three questions:

  • Did the contract require shipment by a date or arrival by a date?
  • Did the chosen Incoterms rule define a delivery point distinct from arrival?
  • What remedy, if any, does the contract or applicable law provide for the relevant delay?

A timestamped chronology is more useful than twenty emails saying “urgent.”

13. Notice, reservation and escalation communications

Preserve the first notice of loss, shortage, delay or damage, plus any reservation made to the carrier or counterparty.

Keep the actual message and proof of sending, not just a screenshot of the draft. Note contractual or carrier notice windows. If the CISG applies, examination and notice issues can matter in conformity disputes; other laws and contracts can operate differently.

Do not wait for a perfect claim letter before sending a factually careful preservation notice where timing matters.

A good early notice states what is known, what remains under investigation and what evidence is being preserved.

14. The decision log

This is the record most companies do not keep.

When the team chooses to reroute, accept damaged goods, pay a charge under protest, replace inventory, notify insurance, settle commercially or pursue a formal claim, write down the decision, date, decision-maker and evidence available at the time.

Why? Because six months later a reviewer otherwise sees only the result and invents reasons that were never part of the original decision.

A short decision log also prevents circular internal debate.

What not to collect

More is not always better.

Do not export entire mailboxes “just in case.” Do not duplicate thousands of irrelevant messages. Do not retain personal data without a business and legal basis. Do not mix privileged legal communications into a shared operational folder without access controls.

The objective is a defensible transaction record, not an uncontrolled data lake.

Start with the 14 groups above, then expand only when the dispute raises a specific issue.

A simple folder structure that people can actually use

A practical structure might be:

  1. 01 Contract and PO
  2. 02 Quote and pricing assumptions
  3. 03 Incoterms and transport map
  4. 04 Booking and carrier
  5. 05 Handoff and transport documents
  6. 06 Packing and loading
  7. 07 Insurance
  8. 08 Customs and regulatory
  9. 09 Receiving and inspection
  10. 10 Timeline and notices
  11. 11 Claims and decisions

Use filenames that begin with date and event: 2026-09-14_carrier_booking_confirmed.pdf, not scan-final-v2.pdf.

The five-minute completeness test

Give the file to someone who did not manage the shipment and ask:

  1. What Incoterms rule and named point did the parties agree?
  2. Where was risk supposed to transfer under that rule?
  3. What evidence shows the physical handoff?
  4. When and where did the problem first appear?
  5. What notice and decision followed?

If the reviewer cannot answer those five questions without calling the logistics team, the delivery file is incomplete.

Bottom line

The strongest delivery evidence is created before anyone knows there will be a dispute.

Preserve the contract, operating assumptions, handoff evidence, transport documents, condition records, customs trail, notice chronology and decision log in one coherent file. Incoterms can then be applied to facts instead of being used as a slogan after the facts have disappeared.

General commercial information only, not legal advice. The result in a specific transaction depends on the incorporated rule, the named place or point, the contract, the transport facts and applicable local law.

Related Reading

Sources and Scope Notes

  • Incoterms® 2020 rules for any mode or modes of transport — International Chamber of Commerce; checked 2026-10-03. Boundary: Official ICC explanatory text for EXW, FCA, CPT, CIP, DAP, DPU and DDP. The rule must be incorporated into the contract with a precise named place/point; local mandatory law and the rest of the sales contract still matter.
  • Incoterms® 2020: C or D rules? — ICC Academy; checked 2026-10-03. Boundary: Current ICC educational guidance on the difference between shipment-side risk transfer under C rules and destination-side delivery/risk under D rules. It is explanatory guidance, not a substitute for the incorporated rule text.
  • United Nations Convention on Contracts for the International Sale of Goods (CISG) — UNCITRAL; checked 2026-10-03. Boundary: The CISG can govern qualifying international sales when its scope and connecting rules are met, subject to party choices and applicable law. It is not a universal sales code and does not govern every issue, including all questions of validity or property effects.
  • UNCITRAL Model Law on Electronic Transferable Records (MLETR) — UNCITRAL; checked 2026-10-03. Boundary: A model-law framework for electronic transferable records such as electronic bills of lading where enacted or otherwise adopted. It is not automatically binding in every jurisdiction.