The Message Before the Truck
Packing, loading, shipment notices, acknowledgments and the discipline of accurate declarations.
Part 6 of 18 · Before the Shelf
The dock needs a forecast of the actual load
eComm Inc schedules people and dock space for 1,000 books. Maya sends half today and half later. The purchase order is correct, but the receiving plan is wrong: it was built from the amount bought rather than the load coming through the gate.
An advance shipment notice, or ASN, describes the shipment the sender declares. It can tell the receiver which order lines, products, quantities and containers to expect. It is useful because receiving work can be prepared before the truck arrives. It remains a declaration that may need correction.
Pack, identify, confirm
For the full teaching shipment, Maya expects 10 pallets and 100 cartons. Before release she needs a process that connects the actual packed goods with the right labels and shipment record. A barcode attached to the wrong pallet is readable and wrong.
GS1's logistics-label guidance connects the ASN with logistics-unit identifiers and their contents, and emphasizes matching the data to the actual goods. It also distinguishes receiver checks from acceptance based on declared contents. We use those public concepts; the controls below are proposed examples for our fictional business.
Three messages that should not become one status
First, the shipment notice is sent. Second, a receiving system may acknowledge that it accepted the message format or processed it. Third, people and equipment observe the physical goods. “Message accepted” must not silently become “shipment received.”
In a separate message-correction example, Maya transmits an ASN for 1,000 books, then discovers a damaged carton before loading. The truck actually carries 990. A controlled correction should preserve the earlier declaration, identify the replacement, and make the current expected quantity clear. Deleting the original record removes the explanation for anyone who planned work from it.
Likewise, resending the same message after a timeout must not create a second shipment. But two genuine partial shipments against the same PO must remain distinct. A useful identity scheme distinguishes the business event from each attempt to transmit it.
The minimum useful shipment record
The record needs the parties, source and destination, shipment identity, relevant order lines, product and unit-of-measure mappings, container structure, expected quantities and useful timestamps. Depending on the goods and route, it may also need lot, condition, handling, origin and compliance information. Required fields depend on the receiving program and governing rules; there is no universal checklist that covers every product.
Separate event time from recording time. A truck collected at 10:00 can have its event entered at 11:15. That is late information, not automatically a late pickup. An estimated arrival should also remain distinguishable from an observed arrival.
GS1's EPCIS standard provides a public vocabulary for sharing supply-chain event information. The fictional event record here is conceptual and does not claim to be a complete EPCIS payload.
Packing is a design choice, not decorative wrapping
A package must protect the book, fit the handling system and communicate identity. More protection can consume more space; less protection can create damage and rework. A carton that is easy for Maya to assemble can be awkward for eComm Inc to receive. Reusable pallets and packaging also require return or recovery arrangements.
The best choice should be tested with the intended product and route. A drawing of a stable pallet is not a physical safety assessment. Neither a packaging label nor a transmitted message is evidence that all preparation requirements were followed.
Keep the promise, the message and the truck in view
Maya's last check before departure should reconcile the shipment notice to the actual load. The receiver needs the current declaration early enough to prepare, along with a clear way to recognize corrections. Both sides need a workable response when the data is missing or the systems are unavailable.
The exception queue should distinguish “no notice,” “notice rejected,” “notice differs from load” and “physical shortage.” Those conditions may lead to the same frustrated phone call, but they require different work. A missing message can be resent. Missing books cannot.
When the system acknowledges Maya's message while the truck remains at her factory, the information has advanced farther than the goods. Keep both positions visible. The next chapter assigns responsibility for the physical journey, so that a successful message is never mistaken for a completed transport promise.
Public sources and evidence boundary
Public material checked on 18 October 2026. Sources support the named definitions or frameworks; the scenarios, diagrams, calculations and proposed decisions are original teaching examples. No private company systems or performance data are described.