Outbound from you
EDI 832: the price and product catalog
The 832 publishes your catalog to a trading partner: items, descriptions, identifiers, units and prices, in their structure. A partner that requires it will not put an item on a purchase order until the 832 introducing it has arrived and been accepted.
It is the document that decides whose numbers the whole relationship runs on.
What the document carries
The product identifiers both sides will trade under, the pack and unit definitions, and the prices. New items are introduced through it, and price changes travel through it ahead of whatever effective date the agreement names.
Once accepted, it becomes the reference the partner's systems check your invoices against. That is its quiet power: the 832 you sent is the price file your 810 is judged by.
How Odoo sources it
The products and pricelists Odoo already maintains are the source. The mapping decisions are which pricelist governs this partner, how your units and casepacks translate into their pack definitions, and which identifier, yours, theirs, or a GTIN, leads each line.
Generated from the live records, the catalog the partner holds and the prices your invoices carry stay the same numbers, because they came from the same place.
Where it goes wrong
Drift. A price changes in Odoo and the 832 announcing it never goes out, or goes out late. From that moment the partner's file and your invoices disagree, and every 810 in the gap comes back short paid with a price-difference code on the remittance advice.
The fix is procedural: the price change and the 832 travel together, with the effective date the agreement requires. The chargebacks guide covers what the drift costs when they do not.
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