X12 856 Advance Ship Notice: The Complete EDI Guide

The 856 Advance Ship Notice is arguably the most technically demanding of the common retail EDI transactions — not because any individual segment is complicated, but because its HL (Hierarchical Level) structure requires you to correctly model a physical packing hierarchy in flat, sequential EDI segments. Get the hierarchy wrong and nothing downstream works.

1. What is X12 856?

The 856 tells a buyer exactly what was shipped, how it's packed, and when it will arrive — sent before or at the moment of shipment, so the receiving dock knows what to expect.

2. Why ASNs matter

• Enables scan-based receiving: workers scan a pallet's barcode and the system pulls up its full contents automatically.
• Lets warehouses plan labor and dock schedules ahead of a truck's arrival.
• Forms the backbone of retailer vendor-compliance programs — late or inaccurate ASNs are one of the most common sources of chargebacks.

3. The HL hierarchy

Unlike the flat PO1 loops in an 850, the 856 uses HL segments to build parent-child relationships. A typical structure has four levels: Shipment (S), Order (O), Pack (P), and Item (I). Each HL segment declares its own ID number and points to its parent's ID number.

4. Example 856

5. SSCC labels explained

The MAN segment carries the SSCC (Serial Shipping Container Code) — an 18-digit GS1 identifier printed as a barcode on the physical carton or pallet label. When the SSCC on the label matches the SSCC in the ASN's MAN segment, receiving software can pull up the full contents of that container with a single scan, with no manual counting required.

6. How X12 856 works, end to end

Zooming out from individual segments, here's the complete business and technical journey the 856 takes — from the supplier's warehouse all the way through to inventory being updated on the buyer's dock. Press Play Flow to watch the ASN travel through each stage, or click any step for a deeper explanation, including its common segments.

7. Mapping example

8. Validation rules

• Every HL loop must reference a valid parent via HL02, except the top-level Shipment loop.
• MAN02 (SSCC) must be exactly 18 digits and pass GS1 check-digit validation.
• PRF (PO number reference) must match an open, previously received 850.
• CTT01 must equal the total count of HL loops in the transaction.

9. Common errors

10. ASN compliance and chargebacks

Most major retailers enforce ASN timing and accuracy requirements through their vendor compliance programs, with financial chargebacks for violations — late transmission, missing SSCC labels, or quantity mismatches between the ASN and what physically arrives. Building ASN generation directly off final pack confirmation (not off an earlier wave-release event) is the single highest-leverage change most suppliers can make to reduce these penalties.