Inbound to you

EDI 850: the purchase order

The 850 is your customer's purchase order as a structured X12 document: the same order that used to arrive as a PDF, now readable by a system. It is the one that starts everything: every acknowledgment, ship notice and invoice that follows refers back to it.

Received properly, it becomes a sales order in Odoo without anyone typing. This page is what that takes.

What the document carries

An 850 names the buyer and the ship-to location, the requested dates, and then the lines: the buyer's item number, a quantity, a unit of measure and a price. Large retailers order for many stores or distribution centres, so the ship-to on one order may be a location your Odoo has never seen.

Everything in it is written in the buyer's vocabulary. Their item numbers, their location codes, their units. The whole receiving problem is translating that vocabulary into yours without a person in the middle.

What it becomes in Odoo

The clean landing is a sales order: right customer, right warehouse, right products, right prices, confirmed dates. Getting there is a set of mapping decisions made once per trading partner. Which res.partner an order belongs to, how their item number cross-references to your internal reference, what happens when they order in cases and you stock in units, and which price wins when their 850 disagrees with your price list.

Each of those is a business decision wearing a technical costume, which is why the configuration conversation involves the person who runs order desk today.

Where it goes wrong

An unknown item number, a casepack that does not divide cleanly, a ship-to that maps to nothing. Each of those either blocks the order or, worse, creates a wrong one that ships.

The failure mode to design for is silence: an order that arrived electronically, failed to land, and sat in a queue nobody watches while the requested date got closer. The morning routine has to include a view of what arrived and what refused to land, and building that view is part of the work.

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.

If the buyer changes an order after it arrives, the EDI 860 purchase order change has to amend that same Odoo sales order.

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