Outbound from you
EDI 856: the advance ship notice
The 856, the advance ship notice, announces a shipment: what is on the truck, how it is packed, and which order it fulfils. Their receiving dock scans against it before a carton is opened.
Retailers enforce it hard, because their receiving is planned around it. Getting the 856 right first is the working rule of retail EDI.
What the structure means
An 856 is hierarchical. Shipment, then order, then pallet, then carton, then item, nested the way the freight is physically packed, with each carton or pallet carrying the serial number that is printed on its label. The retailer's guideline says which levels they require and how the hierarchy has to nest.
That structure is the point: it lets a receiver scan a pallet label and know its contents without opening anything. It is also why an 856 cannot be invented at a desk. It describes physical packing, so it has to come from wherever the packing is recorded.
How it comes out of an Odoo delivery
The source is the delivery order and its packing: which products went into which package, on which pallet, against which customer order. When the warehouse records packing in Odoo as it happens, the 856 is a translation of a validated delivery into the guideline's structure, produced at ship confirmation, ahead of the truck.
When the warehouse does not record packing at that level today, that is the real project. The document is the easy half; the operational habit it reports on is the work, and it is honest to say so before anyone quotes anything.
Where it goes wrong
Late, wrong, or shaped wrong. The truck arrives before the 856 does, the document says twelve cartons and the dock counts eleven, or the hierarchy nests pallets the way your warehouse thinks instead of the way the guideline demands.
Every one of those lands as a compliance deduction on a remittance advice weeks later, which is why the chargebacks conversation and the 856 conversation are the same conversation.
The rest of the set
One document never travels alone. The mandate that asks for this one names its siblings, and the questions repeat: direction, mapping, and what happens when it is late or wrong.
Every code in plain language: the X12 catalog. What a late or wrong document costs: chargebacks and deductions. Who mandates and how it is enforced: the US programmes and the Canadian ones. How the documents fit into purchasing, fulfilment and accounting: EDI across the supply chain.
Start with the letter
The Requirement Check takes two answers: who mandated you and where you stand today. You get back a plain readout of which documents that customer asks for and what has to change inside your Odoo. It is free and it commits you to nothing.
Book a 30-minute call