The retail order is packed, the shipping notice is prepared, and the truck is waiting. Then twelve cases are removed from one pallet because of damage. The warehouse may record the short shipment correctly while the retailer still expects the original quantity.
That is a handoff worth examining. Message transmission and physical dispatch are related events, but one does not prove the other is accurate.
Connect the notice to the load
An advance shipping notice, or ASN, tells the receiving operation what is coming. GS1's logistic-label guidance says the despatch advice should identify each logistic unit by its Serial Shipping Container Code and describe the contained goods; the data should match the actual goods. The SSCC identifies the logistics unit, not merely the purchase order. GS1 logistic label guideline
The retailer's own current specification controls its required format, timing and correction process. Do not assume a general GS1 principle supplies every retailer's operating rule or that all use identical acknowledgments.
Work the late-change example
Our constructed load contains three pallets. For simplicity, each case holds the same quantity of one product. Pallets A, B and C were planned with 40 cases each: 120 cases total. After the damage exception, the actual load is 40, 40 and 28: 108 cases.
| Record | Planned quantity | Final loaded quantity | Check needed |
|---|---|---|---|
| Pallet A | 40 cases | 40 cases | Identity and contents still agree |
| Pallet B | 40 cases | 40 cases | Identity and contents still agree |
| Pallet C | 40 cases | 28 cases | Contents record and notice need reconciliation |
| Shipment total | 120 cases | 108 cases | Twelve-case difference must remain visible |
A total-only correction is insufficient if the receiving system still expects 40 cases against pallet C's identifier. Conversely, changing the pallet record without correcting the shipment total leaves another inconsistency. The actual implementation must follow the trading partner's rules, including whether repacking affects identification.
This example is a desk exercise, not a warehouse observation. It tests agreement between three records: the physical load, the unit-content record and the outbound notice.
Put a final check where changes happen
Define who reconciles a late removal, substitution or repack. That person needs access to the loaded-unit record and a way to trigger the approved notice correction. A dock exception should not depend on someone remembering to send an informal message after the truck leaves.
Keep the original record and its correction connected. Record the reason, changed quantity, responsible person and applicable message version. If the retailer rejects the correction, the issue stays open with a named owner rather than disappearing into a successful transport status.
Ask for evidence beyond a green transmission icon
In a provider demonstration, request one unchanged load and one late-change case. Ask which record establishes what actually departed, how the changed contents reach the retailer and how the team knows the correction was accepted under that retailer's process.
Do not treat a syntactic acknowledgment as proof that the warehouse loaded the right goods or that the retailer accepted every business detail. Establish what each status means.
The useful control is a final agreement check, with a defined exception path. It helps the brand distinguish a shipping shortage from an information shortage—and prevents a corrected warehouse count from leaving an outdated expectation at the other end.
Related reading
Sources
- Logistics-unit identifiers and despatch-advice content — accessed 2026-10-05.