EDI 856 ASN Best Practices: Getting Ship Notices Right

The EDI 856 Advance Ship Notice is the most complex — and most chargeback-prone — document in the EDI transaction set. Here’s how to get it right every time.

What the ASN Must Include

A complete EDI 856 contains:

• Shipment level: Carrier, pro number, ship date, ship-from address
• Order level: PO number, PO date
• Pack level: Carton count, SSCC-18 for each carton
• Item level: UPC, description, quantity per carton

The hierarchical structure of the 856 — shipment → order → pack → item — must be built correctly or the retailer’s system will reject it.

Timing Is Everything

Most retailers require the ASN within:

• Walmart: Within 30 minutes of carrier pickup
• Target: Before the shipment arrives at the DC
• Amazon: Within 24 hours of shipment

Automate this. If you’re manually creating ASNs, you will eventually miss a window.

The Pack-to-Ship Match Rule

The most common 856 failure: your ASN says one carton contains items A, B, and C — but the actual carton has different items or quantities. Retailers scan each carton on receipt and compare it to the ASN. Any discrepancy triggers an ASN accuracy chargeback.

Integration Is the Answer

The only reliable way to send accurate, timely 856s is to generate them directly from your shipping/WMS system at the moment of packing. Spring Systems’ integrated service connects your back-office systems to the EDI network so ASNs are created and sent automatically.