Odoo EDI integration and configuration by Steersman

Send and receive EDI documents in your Odoo ERP with Steersman.
Steersman integrates Odoo with Kleinschmidt VAN (value-added network) for EDI (electronic data interchange) processing. We work closely with Kleinschmidt to set up and manage EDI document exchange for our Odoo clients. When choosing an EDI VAN, we researched various providers, including SPS Commerce, OpenText, and Kleinschmidt, among others.
EDI documents currently supported in Odoo by Steersman
- Invoice 810 – inbound & outbound
- Inventory feed file 846 – outbound
- Purchase order 850 – inbound & outbound
- Purchase Order Acknowledgement 855 - inbound & outbound
- Advance shipment notification 856 – inbound & outbound
- No-ship ASN 856 (0 quantity) – outbound, when the order is cancelled
Trading Partners Integrated via EDI for Existing Steersman Clients on Odoo
Steersman’s Odoo clients are trading EDI documents with these EDI trading partners. Various trading partners use different data fields to exchange information; thus, though EDI provides a standardized data exchange format, some configuration and testing are needed to establish data exchange with a new customer or vendor. For example, trading partners don’t always use consistent fields to identify products, shipping methods, etc. With multiple fields that can be used for this in EDI documents, like vendor part number, part number, customer part number, UPC barcode, there is a need to define primary match fields and fallbacks per partner. Furthermore, a company’s Odoo database may have special fields to identify products aside from the standard “internal reference” and “barcode” fields.
- 3M
- Army and Air Force Exchange Service (AAFES)
- Amazon
- Americold
- Applied Industrial Technologies
- AutoZone
- Boeing
- Chick-Fil-A Supply
- Cummins-Meritor
- Dayton Parts
- Donaldson Company
- DXP Enterprises
- ECCO
- Envalior
- Fastenal
- Fred Meyer
- Gates Corporation
- General Services Administration (GSA/FSS)
- Grainger
- Graybar
- Grote Industries
- Kimberly-Clark
- Kit Masters
- Kodak
- Kroger
- LC Industries (LCI)
- Mann+Hummel
- Marine Corps Exchange (MCX)
- MEI Corporation
- Motion Industries
- MSC Industrial Supply
- Office Depot
- Rexel
- SDI
- SDI Digital Supply Chain Canada
- SDI Mexico
- Staples
- Staples Advantage
- RS Integrated Supply US
- Target
- Truck-Lite
- Tyson Foods
- Tractor Supply Company (TSCO)
- Vallen Distribution
- Zoro Tools
EDI configuration in Odoo
Some EDI configuration is enabled right in Odoo to schedule and map data exchange.
Configurations per EDI customer (trading partner) are
- Received 850 purchase orders, delivery method mapping, and configuration in Odoo
- Based on three different fields received, plus the destination state of the order
- Signature requirements mapped together with delivery method selection
- “Default” country can be defined per customer for addresses received via EDI
- Inventory feed 846 can be scheduled to send at desired frequencies
- Inventory feed 846 has a separate product selection criteria per EDI customer to ensure the proper product selection is sent
Global EDI configuration is possible in Odoo
- Received 850 purchase orders can result in draft sales orders (quotes) or can automatically approve if products, delivery methods, and addresses were matched/created successfully
- If an 850 purchase order lists a price that differs from the current price set for the customer in Odoo, the EDI configuration can be set to confirm the order as received, update to the current price and confirm, or leave the order in a draft state.
- EDI configuration allows setting a remit address for use on invoices, if the EDI customer requires it, and the remit address is different from the company’s main address
EDI integration automation Steersman will provide in Odoo
- Addresses created in Odoo will be automatically validated via the EasyPost API and adjusted to improve the deliverability of products.
- Products from received EDI orders are automatically matched to existing products in Odoo by product internal reference or customer alias.
- The customer purchase order number is received and routed into the order reference field.
- All files support customer aliases for products – the customer can have their own part numbers and product names
- Customer-facing documents will list client alias names and numbers
- Client can send its own part number aliases on 850 purchase order EDI documents
- Product shipped/pulled from stock is the standard product
All documents sent or received via EDI are recorded in an EDI event log in Odoo, enabling easy auditing with log records linked to their corresponding deliveries, sales orders, and invoices.
Steersman continues to work on Odoo EDI integration enhancements, including requests to process outbound purchase orders, inbound invoices, and advance shipping notices, as well as other documents.
Steersman’s EDI and other modules are included in our subscription-based Odoo services.
Related posts

Sending Sales Order Acknowledgments using EDI in Odoo
Steersman’s EDI 855 outbound exchange document provides a simplified solution for sending Sales Order Acknowledgments (SOAs) to trading partners directly from Odoo. Our EDI integration ensures that businesses can efficiently confirm, modify, or reject sales orders (EDI 850) received from trading partners.

Receiving EDI Purchase Order document (850) in Odoo
An EDI 850 PO inbound transaction occurs when a Odoo Seller's system receives an EDI 850 Purchase Order (PO) document from a trading partner (buyer) and that inbound PO generates a new sales order (SO) in the seller's system.

Sending EDI Purchase Order document (850) in Odoo
An EDI 850 outbound transaction occurs when a buyer initiates a purchase order (PO) through Odoo, which is then received by the supplier as a sales order (SO) in their system.

Odoo ERP implementation for equipment & design manufacturer of accessories for electronic devices
Steersman’s Odoo ERP implementation for M-Edge and how they solved their EDI and shipping difficulties.