Connect Odoo to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between Odoo and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with Odoo EDI
XEDI connects Odoo with retailers, wholesalers and logistics providers so EDI orders, acknowledgements, despatch advice and invoices move between Odoo and your trading partners without manual entry.
One managed platform, no custom code
XEDI maps Odoo to your trading partners and validates every document, so data flows straight into the systems your teams already use.
Odoo's model maps cleanly onto an EDI flow
Odoo already moves a sale through a sales order, a delivery and a customer invoice, which is the same chain an EDI programme runs. A retailer's order becomes the sales order, validating the delivery raises the despatch advice, and the customer invoice goes out as the invoice.
Because Odoo exposes those models over its API, the connection itself is rarely the difficulty. What takes the work is that retailers identify products and delivery points their own way, and those have to resolve to your products and partners every time.
Customisation is the variable
Odoo installations differ more than most ERPs, because modules and studio customisations change field names, required values and the flow between documents. Two Odoo customers can need materially different mappings for the same retailer.
We scope against the Odoo you actually run rather than a stock instance, and the retailer-specific handling stays with us, so a module change or version upgrade does not mean renegotiating every retailer arrangement.
What your team sees day to day
You get an EDI mailbox and a portal that works like an inbox, so retailer orders arrive and are worked immediately rather than waiting on the Odoo integration.
The order then becomes the despatch advice rather than a re-entered one, amended where the delivery differs, with SSCC labels for the pallets, and becomes the invoice on delivery. Delivery of that invoice is confirmed in the dashboard.
The integration sits over that workflow and automates it, so orders land as Odoo sales orders and validated deliveries raise the outbound documents. Smaller teams run the portal alone; our API suits enterprises wanting finer granularity; an Odoo integration is the middle.
Documents you can exchange
- Purchase orders landing as Odoo sales orders
- Order acknowledgements returned to trading partners
- Despatch advice and ASN messages from Odoo deliveries
- Customer invoices raised from Odoo
- Product and price data where a partner maintains a catalogue
Built for Odoo teams
Whoever owns Odoo in your business, XEDI keeps EDI accurate and hands-off.
- Operations and fulfilment teams
- Finance teams
- Retail and wholesale suppliers
- Odoo administrators
- Businesses replacing manual order entry
Odoo EDI document types
The set varies by retailer, but an Odoo supplier programme is usually built from these flows.
| Document | What it carries | Direction |
|---|---|---|
| Purchase orders | Retailer demand landing as an Odoo sales order against the right partner, products, pricelist and delivery address. | Partner to Odoo |
| Order acknowledgements | What the Odoo sales order confirms, line by line, including anything amended or refused. | Odoo to partner |
| Advanced shipping notices | Despatch and pack detail raised when the Odoo delivery is validated, to carton or pallet level where required. | Odoo to partner |
| Invoices | Customer invoices referenced to the order and delivery so the retailer can match them. | Odoo to partner |
| Credit notes | Credit notes carried on the invoice message with a credit document code. | Odoo to partner |
| Product and price data | Product, pack and price data published to retailers that maintain a catalogue. | Odoo to partner |
How to connect Odoo with EDI using XEDI
Odoo's sales order, delivery and invoice chain is already the shape an EDI flow needs, so the build is mapping against your instance. The sequence below is what onboarding looks like from your side.
-
01
We scope the Odoo version, modules and customisations that touch the sales order, delivery and invoice chain.
-
02
We build the mapping between each retailer's documents and your Odoo partners, products and pricelists.
-
03
We configure validation so a document is checked against the retailer's rules before it reaches Odoo.
-
04
We prove the order, delivery and invoice flows against what each retailer requires and against the Odoo instance you actually run.
-
05
You get a connection built against your Odoo rather than a stock one, and we keep it working through module and version changes.
Ready to connect Odoo?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about Odoo EDI
Common requirements
- Odoo access
- Your customisations
- Partner and address records
- Product and unit data
- Which partners you trade with
What we need from you to build it
Only what we cannot hold for you, which with Odoo means your instance as much as your data. Retailer requirements are already ours.
- Odoo access
- An integration user with rights to the sales, inventory and accounting models in scope, on the version and modules you actually run.
- Your customisations
- Which modules and studio changes affect sales orders, deliveries and invoices, since these vary more in Odoo than in most systems.
- Partner and address records
- Each retailer mapped to an Odoo partner, with their delivery points resolvable to a delivery address.
- Product and unit data
- Barcodes at each packaging level and the unit a retailer orders in, against the unit of measure held in Odoo.
- Which partners you trade with
- The retailers you sell to now and intend to. We hold what each of them expects.
Why suppliers choose XEDI for Odoo
- Most retailers are on our network already, so you are not waiting on your Odoo instance to start trading.
- A new retailer is not an Odoo development ticket. We build and verify the connection before it carries live documents.
- The integration is built against the Odoo you run, customisations included, rather than a stock instance.
- Documents are checked against the retailer's rules before they leave, so a problem appears while the Odoo order can still be amended.
- One connection covers current and future retailers, each onboarded by us.
- If a retailer raises a problem, they raise it with us, and we put it right rather than it arriving as a question nobody can answer.
Can XEDI connect Odoo to EDI trading partners?
Yes. XEDI maps each retailer's EDI documents onto Odoo sales orders, deliveries and customer invoices, and returns acknowledgements, despatch advice and invoices in the format each retailer requires.
Does it work with a customised Odoo?
Yes, and that is normally the case. We scope against the modules and customisations you actually run rather than a stock instance, because those change field names and the flow between documents.
Which Odoo versions are supported?
Odoo's sales order, delivery and invoice models are stable enough across supported versions for the flow to work; the version and modules in play are confirmed during scoping.
Plan your Odoo EDI setup
Everything you need to scope, map and go live with Odoo, in one place.