Confirm the retailer's specific EDI 856 implementation guide, as each retailer customizes required segments, qualifiers, and carton-labeling requirements beyond the base X12 standard
Build the hierarchical loop structure: BSN (beginning segment with shipment ID and date), then HL loops for Shipment > Order > Pack > Item levels, populating TD1 (carrier details), TD5 (routing), and DTM (dates) segments at the shipment level
At the Pack level (HL*P), include the SSC carton barcode in the MAN segment; at the Item level (HL*I), populate the LIN segment with the buyer's item number and UPC/EAN
Wrap the transaction in a GS/GE functional group and ISA/IEA interchange envelope, using the ISA13 interchange control number unique to this transmission
Transmit the EDI file to the retailer via your agreed-upon transport (AS2, SFTP, or VAN) and retain the 997 Functional Acknowledgment they return
Map the ASN shipment ID back to your internal order and shipment records so that a 997 rejection can trigger an automated correction workflow
Known gotchas
Retailers impose financial chargebacks for ASN errors (missing, late, or data-incorrect ASNs); some retailers require the ASN to arrive before the physical goods — late transmission after delivery voids the ASN's purpose and triggers fines
The ISA13 interchange control number must be unique per trading relationship; reusing a control number causes the receiver's EDI system to reject the interchange as a duplicate
GS1-128 carton labels referenced in the ASN MAN segment must physically match the SSCC barcodes on the boxes; a mismatch between the ASN data and the physical label causes automated receiving failures at the retailer's DC
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp