Inbound to you
EDI 875: the grocery products purchase order
The 875 is a purchase order with a grocery accent. Food distributors and grocery retailers run programmes written in the grocery subset of X12, and where a general-merchandise guideline names the 850, theirs names the 875.
For a food or beverage supplier on Odoo, it is the document that starts everything. Same work, grocery accent.
What the document carries
The bones are the 850's. The buyer, the ship-to, the dates, and then the lines, each with item identifiers, quantities, units and prices, all of it arranged the way the grocery subset of X12 arranges things and weighted the way grocery buying weights them: cases and pallets over eaches, and delivery windows over delivery dates. The item identification the category runs on carries its own weight. Little of that is optional.
A grocery guideline that asks for the 875 often names grocery-numbered siblings for the rest of the conversation. Which ones travel with it is the guideline's call. Reading it comes first.
What it becomes in Odoo
A sales order, the same landing the 850 gets: right customer, right warehouse, right products, right prices, confirmed dates. The mapping decisions repeat too, their item numbers to your internal references, their case definitions to your units of measure, their ship-to codes to delivery addresses your Odoo knows.
Two details do most of the deciding. Dated windows the warehouse has to hit, and casepack discipline that settles whether a line lands clean or blocks.
Where it goes wrong
The 850's failures, on shorter clocks. An unknown item. A casepack that refuses to divide. A ship-to that maps to nothing. Each one either blocks the order or creates a wrong one that ships, and a grocery delivery window leaves very little room to notice which.
The queue rule holds here too: the morning routine needs a view of what arrived and what refused to land, because an unshipped grocery order misses a window that does not reopen.
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