EDI guide: document 856

EDI 856 Advance Ship Notice: the document that decides whether your 3PL gets charged back

The 856 is the one EDI document the warehouse owns. It describes the shipment carton by carton, pallet by pallet, so the retailer's dock can scan it in. Get it late or wrong and the chargeback lands on the brand, then on the 3PL.

  • 856ANSI X12 transaction set
  • HLthe nested hierarchy of the shipment
  • SSCC18-digit code on every pallet or carton
  • Freeno signup

What it is

What an EDI 856 is and why it matters

An EDI 856 is the advance ship notice. It goes from the shipper to the retailer once the shipment is packed and before the truck arrives, and it lists the shipment's structure: which orders are on it, which pallets, which cartons in each pallet, which items and quantities in each carton, plus carrier, tracking and expected delivery date. The retailer's receiving system uses it to plan the dock and to check the delivery in by scanning labels rather than counting.

The 856 matters more than any other document because it is where physical accuracy and data accuracy have to match. The serial shipping container code (SSCC) printed on each pallet or carton label must appear in the ASN's MAN segment, the quantities must add up through the hierarchy, and the ASN must arrive before the truck. Retailers publish a compliance guide with the exact rules and fine every miss: late ASN, missing ASN, ASN that does not match what was received, label that does not scan.

This is the 3PL's document even when the brand's EDI provider technically transmits it. The warehouse builds the pallets, generates the SSCCs, prints the labels and knows the carton contents. The cleanest setups have the WMS create the 856 data at pack confirmation and send it to the EDI provider automatically; the worst have someone re-keying pallet counts into a web form after the truck has left.

Sample layout

The EDI 856 segment by segment

Illustrative values. Each retailer or carrier publishes an implementation guide with the exact subset of segments and codes it accepts.

SegmentWhat it carriesExample
STStart of the transaction setST*856*0001
BSNBeginning ship notice: purpose 00, shipment ID, date, time, hierarchical structure code (0001 = shipment, order, pack, item; 0004 = shipment, order, item, pack)BSN*00*SHP0092811*20260922*1415*0001
HL (S)Shipment level: one per ASN. Children carry carrier, weight, references and addressesHL*1**S
TD1 / TD5Packaging and lading quantity with weight; routing with carrier SCAC and transport methodTD1*PLT94*4****G*1820*LB / TD5*B*2*RBTW*M*Roadway
REFBill of lading (BM), carrier PRO (CN), packing list (PK)REF*BM*BOL-55810
DTM011 shipped date, 017 estimated deliveryDTM*011*20260922
N1 (ST / SF)Ship-to with the retailer DC number; ship-from, usually the 3PLN1*ST*DC 6021*92*6021
HL (O) + PRFOrder level: one per PO on the shipment, with the PO number from the 850HL*2*1*O / PRF*4500123456
HL (P) + MANPack level: one per pallet or carton, with the SSCC-18 from the labelHL*3*2*P / MAN*GM*00012345678000000011
HL (I) + LIN + SN1Item level: product IDs and the quantity shipped in that packHL*4*3*I / LIN**UP*012345678905 / SN1**12*CA
CTT / SECount of HL segments and end of setCTT*4

How it flows

How an EDI 856 moves from one system to the next

  1. Pack confirmation in the WMSAs cartons are packed and palletised, the WMS assigns an SSCC to each pack level, prints the GS1-128 label and records exactly which items went into which container.
  2. The 856 is generated and sentThe WMS or EDI provider builds the HL hierarchy from the pack data, adds carrier and BOL references, and transmits it. Target: before the truck leaves the dock, always before it arrives.
  3. The retailer receives by scanAt the DC, each label is scanned and matched to the ASN. Matches go straight to stock. Mismatches create an exception, a manual count and usually a chargeback.

Common rejection reasons

Why an EDI 856 gets rejected or fined

The failures that show up in 997s, exception queues and retailer chargebacks.

  • ASN arrives after the truckThe single most fined miss. Late transmission, a queued EDI job or an ASN sent only at the end of the day all count. Send at ship confirmation.
  • SSCC on the label does not match MANReprinted labels, hand-typed SSCCs or a WMS that generates the label from a different table than the ASN. The scan fails and the pallet is counted by hand.
  • Hierarchy does not add upItem quantities under a pack do not sum to the pack, or packs under an order do not match the 855. Retailer translators validate the totals.
  • Wrong structure codeThe retailer's guide requires pick-and-pack structure 0004 (item then pack) but the WMS sends 0001. Same data, rejected file.
  • PO or DC number mismatchPRF does not equal the 850's BEG PO number, or N1*ST carries a store number where the retailer wants the DC. Receiving cannot match the shipment to an order.
  • Missing weight, carrier or BOLTD1 weight, TD5 SCAC or REF*BM left blank. Mandatory in most retailer guides; the ASN is accepted with errors and the shipment is flagged.

Before you sign

What a 3PL needs to run the 856 properly

Questions to settle with the warehouse
  • Ask the 3PL to show a live 856 from its WMS for a retailer you sell to, and the label it printed for the same pallet. The SSCC must match.
  • Confirm the ASN is triggered automatically at ship confirmation rather than batched or keyed later.
  • Get ASN on-time and accuracy rates in writing, and agree who absorbs a chargeback that traces to the warehouse.
  • Make sure the retailer's routing guide (pallet build, label placement, structure code) is configured as pack rules in the WMS, per retailer.
3PLs that run this documentRetail and EDI 3PLs

Warehouses already sending 856 ASNs to Target, Walmart, Costco and other compliance-heavy retailers.

Questions

EDI 856 FAQ

What is an SSCC and where does it come from?
The serial shipping container code is an 18-digit GS1 identifier for one logistics unit (a pallet or a carton). It is generated from the shipper's GS1 company prefix plus a serial number, printed in a GS1-128 barcode on the label, and sent in the ASN's MAN*GM segment so the retailer can scan the unit against the document.
Who sends the 856, the brand or the 3PL?
Either can transmit it, but the data has to come from the warehouse. Common setups: the WMS sends pack data to the brand's EDI provider, which builds and sends the 856; or the 3PL's own EDI connection sends it directly under the brand's trading partner ID.
When exactly must the ASN be sent?
Retailer guides usually say at time of shipment, and before receipt at the DC. In practice that means the ASN should be transmitted as the truck is closed, since a 997 and any correction need time before the delivery appointment.
What is the difference between 0001 and 0004 structures?
0001 nests pack under order and item under pack (shipment, order, pack, item), typical for full-case shipments. 0004 nests item under order and pack under item (shipment, order, item, pack), used when one item spans many cartons. The retailer's implementation guide specifies which it wants.

Retailer asking for EDI?

Get matched with a 3PL that already runs the 856

3PL Hub matches brands with warehouses already exchanging this document with the retailers and carriers you sell through. Free for brands, commission-free, from a directory of 5,400+ providers.

Ready to shortlist 3PLs?

Free for brands. No commissions. Your details go only to the 3PLs you match with.

Get matched to 3PLs
3PL Hub

The commission-free 3PL directory and matchmaking platform. 5,000+ 3PLs, 200+ verified members, and 3PLs never pay us to be recommended.

Taking Inventory

The 3PL newsletter, every two weeks

3PL, fulfillment, M&A, eCommerce and trade, written by a human. Read by 3,000+ operators and the logistics ecosystem.

Subscribe to Taking Inventory Free. Every two weeks. Unsubscribe any time.