EDI 856: the advance ship notice retailers fine you for getting wrong

The EDI 856 is the advance ship notice — the electronic document a supplier sends a retailer to say what is on its way, before it arrives. It describes the shipment as a hierarchy: the shipment, the orders inside it, the cartons packed for each order, and the items inside each carton. In European practice the same message is called a DESADV.

Retailers rely on it to receive goods without opening them, which is why they enforce it commercially rather than politely. A late, missing or inaccurate 856 attracts a deduction from the invoice — a vendor compliance chargeback — and those deductions are applied automatically, per shipment, whether or not anyone at the supplier notices.

What the EDI 856 has to match

• The physical pack. Every carton described in the file must exist, with the contents and quantities stated, and no carton may be missing from it.
• The carton labels: each carton’s serial number in the file corresponds to the barcode on the label physically attached to it.
• The purchase order, at the level of detail the retailer’s specification requires.
• Ship date and expected delivery, within whatever window the routing guide sets.
• The retailer’s own structure requirements, which vary — the same document sent to two retailers is frequently valid for one and rejected by the other.
• And it must arrive before the goods do. An 856 transmitted after delivery is treated as missing.

Why the file and the pallet drift apart

The 856 is normally generated from the warehouse system when the shipment is confirmed. It goes wrong when something changes after that point and nobody regenerates it: a short pick, a substituted carton, a pallet split across two trailers, a last-minute addition made on the dock. Every one of those produces a file that was accurate when it was created and inaccurate when it arrived. The discipline that fixes it is simple and often unpopular — nothing changes on the dock after the ASN is transmitted, or the ASN is cancelled and resent.

Read the retailer’s vendor compliance guide before the first shipment, not after the first deduction. It specifies the structure, the timing window, the label placement and the fee schedule, and every retailer’s is different. It is also the document you need when disputing a deduction you believe is wrong.

Deductions are worth reconciling

Compliance fees appear as deductions on remittance advice, often thinly described, and suppliers routinely absorb them because tracing one costs more than it recovers. In aggregate they are rarely small. Log each deduction against the shipment, the reason code and the retailer’s stated rule, and review the pattern quarterly — the value is less in disputing individual charges than in seeing that eighty per cent of them come from one recurring cause you can fix.

Keeping the paperwork behind the file

What you need when a deduction is disputed is the shipment file: the transmitted 856, the pack list, the labels generated, the carrier pickup record and the retailer’s rule you were measured against. Ettex Records holds that per shipment and per retailer, Ettex Sheets tracks the deductions with reasons and outcomes so the recurring cause is visible, and the label side of the same obligation is covered in gs1 128 label.

Being direct: this is records and reconciliation, not EDI software. Translating, mapping and transmitting X12 or EDIFACT messages is what EDI providers do, and any supplier trading with a large retailer needs one. What this covers is the file around the transmission and the deductions that follow it.