Shipments.
A shipment aggregates logistic units under a business transaction. EPCIS 2.0 links the objects to the transaction identifiers; the gateway records the association and stamps the capturing account (capturedBy) — kept distinct from who, the attested observer.
epcListquantityList
The shipment, tied to its paper.
"bizStep": "shipping",
"bizTransactionList": [
{ "type": "desadv",
"bizTransaction": "urn:epc:id:gdti:0950600.01346.ASN-2214" },
{ "type": "po",
"bizTransaction": "urn:epc:id:gdti:0950600.01346.PO-99801" }
],
"epcList": [ /* the pallets on the truck, by SSCC */ ]Illustrative: a shipping event referencing its documents. The event records the references; the documents live in the systems that own them.
For the engineer reconciling ASN to arrival.
"What actually shipped against this order" is the join between the transaction reference and the event history — one query when both live on the same standard, weeks of spreadsheet work when they do not. The event carries the reference; nothing re-keys the document.
Proof, not adjectives. The gateway's conformance tests pass against GS1's normative artifacts. See What for the dimension, and What ships today for the dated ledger.