Operations teams
“A supplier operations team can see partner setup, validation, exceptions, and QuickBooks handoff in one workspace instead of chasing spreadsheets.”
X12 transaction set reference
X12 856 — Advance Ship Notice (ASN)
The X12 856 advance ship notice (ASN) tells a buyer what shipped, when, and how cartons and items are packed — often before the shipment arrives.
EDI 856 facts
- GS01 for 856 groups is SH — distinct from PO (850) and IN (810) functional groups in the same partner relationship.
- HL loops encode shipment → order → pack → item structure; big-box retailers enforce specific level patterns.
- SignalEDI validates HL/MAN structure against partner ASN rule packs before production send.
Where EDI 856 fits
- Direction
- Supplier → buyer / retailer
- GS functional ID
- SH
- Workflow position
- 856 follows 850 (and optional 855): supplier ships against the PO, sends 856, then submits 810 invoice referencing the same PO and shipment.
Related sets: 850, 810, 997 · Document guide
Key segments in EDI 856
Sample EDI 856
ST*856*0002~ BSN*00*SHIP8842*20260504*1450~ HL*1**S~ HL*2*1*O~ HL*3*2*P~ MAN*GM*008012345678901234~ CTT*3~ SE*8*0002~
Validate samples with the free EDI validator.
Send EDI 856 with SignalEDI
POST /api/v1/documents/outbound
{
"partnerId": "retailer-demo",
"documentTypeCode": "856",
"payload": { "shipmentId": "SHIP8842", "purchaseOrderNumber": "PO1001" }
}Your side can reach partner-ready setup in days, not weeks — partner certification calendars may still take longer. See the API quickstart.
Common EDI 856 errors
- HL hierarchy missing pack or item levels required by retailer
- MAN SSCC not matching physical carton label
- BSN ship date after carrier pickup
- PO reference on HL order level does not match original 850
Related reference
FAQ
EDI 856 FAQ
Common causes are missing carton hierarchy, SSCC/label mismatch, late ASN timing, or PO quantity mismatches.
Yes for most retail programs — order-level HL loops carry PO references for three-way match with invoice.
Trust & proof
Built for SMB teams that need API-first EDI, healthcare diligence, and predictable pricing.
SignalEDI keeps the public promise consistent across every route: real-time processing, transparent monthly plans, no per-document fees, QuickBooks-friendly handoffs, and core healthcare X12 workflows on paid plans.
HIPAA-aware handlingBAA path documentedSecure API + webhooksNo per-document fees
Healthcare billing
“837, 835, and 270/271 workflows are explained in plain English, with HIPAA-aware handling and a documented BAA review path for diligence.”
Developer teams
“JSON/CSV in and X12 out, with API docs, webhooks, real-time status, and validation responses that make EDI feel like modern infrastructure.”