Every eCommerce retailer and dropshipper depends on knowing exactly when products ship, what's inside each shipment, and when it will arrive. Without that visibility, customer inquiries pile up, inventory counts drift, and fulfillment errors multiply.
The EDI 856—formally known as an advance ship notice (ASN)—solves this by giving trading partners a detailed, machine-readable snapshot of every shipment the moment it leaves the warehouse. If you rely on electronic data interchange (EDI) to coordinate with suppliers, the 856 document type is one of the most important transactions in your workflow.
Below, you'll learn what an EDI 856 is, how the process works from purchase order to delivery, what data the document contains, and how to see a real EDI 856 example broken down segment by segment.
An EDI 856 is an electronic document—sometimes called an EDI ASN 856—that a supplier sends to a buyer before a shipment arrives. It follows the ANSI X12 standard and provides a structured, machine-readable description of everything in the shipment: what was packed, how it was packed, which carrier is handling delivery, and the tracking numbers needed to follow it in transit.
While the 856 EDI document type is used across manufacturing, automotive, healthcare, and government supply chains, it is especially critical in retail and eCommerce. Major retailers such as Walmart, Amazon, Target, and Costco require their suppliers to send compliant EDI 856 documents for every order, and non-compliance often results in chargebacks.
Here's why trading partners rely on the EDI 856 advance ship notice:
Faster, error-free communication. The ASN replaces manual emails, phone calls, and spreadsheets with a single standardized transaction. Because the data flows directly into warehouse management and ERP systems, there is no re-keying—and far fewer mistakes.
Smarter receiving and inventory planning. When a distribution center knows exactly what is arriving and when, staff can pre-allocate dock doors, schedule labor, and update inventory counts before the truck pulls in. This is the backbone of just-in-time inventory management.
Universal standardization. The EDI 856 format follows specifications maintained by the American National Standards Institute (ANSI) under the X12 standard. That means any compliant system—regardless of vendor—can generate, transmit, and interpret the document without custom integrations.
The EDI 856 doesn't exist in isolation. It is one step in a broader purchase-order-to-payment cycle. Here is the typical process, illustrated with a real-world example.
Imagine a consumer-electronics retailer needs to restock a popular smartphone model. The retailer sends the supplier a purchase order—usually an EDI 850—specifying the SKU, quantity, requested delivery date, and ship-to address. In some cases the retailer may instead send a planning schedule (EDI 830) or shipping schedule (EDI 862) to manage ongoing replenishment.
Once the supplier confirms they can fulfill the order, their warehouse begins the pick, pack, and ship process.
Before the shipment leaves the dock, the supplier's system generates an EDI 856 advance ship notice. This document is built according to the ANSI X12 856 transaction set and includes every detail the buyer will need to receive the goods:
The completed EDI 856 is transmitted electronically—typically through a value-added network (VAN), AS2 connection, or SFTP—to the buyer's EDI system. This happens within minutes of the shipment leaving the warehouse, giving the buyer maximum lead time to prepare.
When the buyer's system successfully parses the EDI 856, it returns an EDI 997 Functional Acknowledgement. This confirms that the advance ship notice was received and that its structure is valid. If there are formatting errors, the 997 flags them so the supplier can correct and resend.
Armed with the ASN data, the buyer's warehouse management system can allocate dock space, assign receiving staff, print barcode labels, and stage put-away locations—all before the truck arrives. When the shipment does arrive, workers scan carton labels against the EDI 856 data to verify counts and flag discrepancies instantly.
Advance ship notices can range from bare-minimum header-level data to highly granular item-and-serial-number detail. The level of detail often depends on the trading partner's compliance guidelines. Here are the core components every EDI 856 document contains:
Trading partner identification. The sender (supplier) and receiver (buyer) are identified with unique codes—often DUNS numbers or mutually agreed IDs—so the document routes to the correct system.
Purchase order reference. Each shipment links back to one or more purchase orders (EDI 850), enabling the buyer to match incoming goods to open orders and automate three-way matching against the invoice.
Carrier and transport details. The ASN specifies the carrier name, SCAC code, equipment type, and service level. This data feeds directly into the buyer's transportation management system for real-time tracking.
Shipment and tracking information. Physical characteristics—weight, cube, number of handling units—plus tracking numbers allow the buyer to monitor transit status and predict delivery windows.
Hierarchical packaging structure (HL loops). This is the defining feature of the EDI 856 format. The document uses a nested hierarchy to describe exactly how items are packed: shipment → order → pallet → carton → item. Each level can carry its own identifiers, quantities, and descriptions.
Item-level detail. At the most granular level, the ASN lists every SKU, UPC, quantity, lot number, expiration date, and serial number included in the shipment. Retailers use this data to update inventory, generate receiving labels, and support item-level RFID programs.
At first glance, a raw EDI 856 file looks like a wall of codes and delimiters. But every segment follows a predictable structure defined by the ANSI X12 standard. Here's what each section in the example above represents:
Interchange and group headers (ISA / GS segments). The ISA segment opens the interchange envelope and contains authorization codes, security qualifiers, and the sender/receiver IDs. The GS segment defines the functional group—identifying this as a ship-notice transaction set (856), stamping the date and time, and assigning a group control number.
Transaction set header and beginning segment (ST / BSN). The ST segment marks the start of the individual 856 transaction. The BSN (Beginning Segment for Ship Notice) records the ASN number, shipment date, shipment time, and the purpose of the notice (original, replace, or cancel).
Hierarchical loops (HL segments). The HL segments create the nested packaging hierarchy. A typical EDI 856 example will include HL loops at the shipment level (S), order level (O), tare/pallet level (T), pack/carton level (P), and item level (I). Each loop can carry its own TD (transport detail), REF (reference), and MAN (marks and numbers) segments.
Item detail (LIN / SN1 segments). Within the lowest HL loop, LIN segments identify each item by UPC, SKU, or vendor part number. The SN1 segment reports the quantity shipped. Additional segments like PID (product description) and DTM (date/time) provide supporting detail.
Trailer segments (CTT / SE / GE / IEA). These close out the transaction set, functional group, and interchange envelope, each carrying control counts that receiving systems use to verify the document was transmitted completely.
If you're a retailer or dropshipper, manually processing advance ship notices from every supplier is not sustainable. Each supplier may use a different EDI format variant, ship on a different timeline, and require a unique mapping—all of which drain your team's time and increase the risk of fulfillment errors.
Spark Shipping eliminates that complexity. Our platform automatically ingests EDI 856 advance ship notice documents from your suppliers, extracts the tracking numbers, carrier details, and item data, and pushes fulfillment updates directly to your eCommerce storefront and customers—no manual data entry required.
Whether you work with five suppliers or five hundred, Spark Shipping makes EDI 856 integration fast, reliable, and hands-free. Request a demo to see how it works for your business.