ASN Versus Packing List and Bill Of Lading: What Retailers Need To Know

ASN Advance Shipment Notice, commonly transmitted as EDI 856 before a retail shipment arrives. While the ASN is an electronic, machine-readable notice used for advance receiving and system reconciliation, the packing list and bill of lading (BOL) are physical documents that serve different legal and operational roles during transport and receipt.

Retail managers, carriers, and suppliers often receive multiple documents for a single shipment. Understanding the differences reduces confusion at the dock and avoids operational penalties. The ASN focuses on data exchange and pre-receiving; the packing list describes contents for manual verification; and the BOL is the carrier-controlled transport contract that establishes custody and terms of carriage.

Key Differences Explained

• Function: ASN: advance electronic notice for systems; Packing list: human-readable content summary for counting and inspection; BOL: legal carriage document and proof of shipment.
• Format: ASN: EDI 856 or API JSON/XML; Packing list and BOL: printed or PDF documents accompanying the shipment.
• Timing: ASN: sent in advance; Packing list/BOL: created at shipment and travel with freight.

When Each Document Is Used

Retailers use the ASN to pre-stage and map cartons and pallets to expected POs in their WMS. The packing list is used when manual verification is required — for example, for exceptions or non-EDI suppliers. The BOL is presented to carriers during pick-up and to receiving for freight inspection in claims or disputes.

How They Interact Operationally

Best practice is to have systems cross-check the ASN against the packing list and BOL as part of receiving validation. An ASN with pallet-level SSCCs allows scanners to match physical pallets to electronic records; the packing list supports visual checks and customs requirements; the BOL provides carrier, route, and freight terms used to process claims if damage or shortage occurs.

Common Mismatches And Their Consequences

• ASN vs. Packing list mismatch: Triggers manual inspection, slows unloading, and may cause receiving teams to quarantine goods.
• ASN missing BOL references: Complicates carrier reconciliation and can delay claims processing.
• Inaccurate BOL details: Risk of rejected deliveries or disputes over freight charges.

Practical Example

A vendor sends an ASN listing 100 cartons across 4 pallets. The carrier’s BOL lists 3 pallets due to a shrink-wrapping error at shipment. On arrival, the packing list confirms 4 physical pallets. The retailer’s WMS flags the discrepancy between ASN (4) and BOL (3). Because the ASN was sent in advance, receiving alerted logistics and the carrier before unloading, preventing an erroneous freight acceptance and simplifying the resolution.

Tips For Retailers And Suppliers

• Align document references: Ensure PO, ASN, packing list, and BOL numbers are cross-referenced consistently.
• Use unique identifiers: Include GTINs, SSCC pallet IDs, and carton-level identifiers to speed matching.
• Define escalation rules: Create SLAs for resolving discrepancies so appointments aren’t wasted and chargebacks are minimized.

In short, the ASN Advance Shipment Notice, commonly transmitted as EDI 856 before a retail shipment arrives, complements—rather than replaces—physical documents like the packing list and bill of lading. Each document serves a distinct role; aligning them reduces receiving friction and supports faster, more accurate inventory flow.