Retailer EDI requires translating X12 or EDIFACT documents (850 PO, 856 ASN, 810 invoice) to Odoo sale.order, stock.picking, and account.move. Use an EDI gateway or Odoo EDI modules, map partner GLN and SKU cross-references on res.partner and product, automate ASN from validated deliveries with lot data, and invoice from posted pickings with retailer-specific charge codes.
Steps
- Onboard retailer VAN or API gateway credentials and test ISA/GS identifiers.
- Create res.partner with GLN, EDI routing, and ship-to/bill-to hierarchies.
- Map retailer item numbers to product.default_code or pricelist partner SKU fields.
- Import 850 into sale.order with requested ship dates and store allocations.
- Generate pick/pack/ship; on validation build 856 with SSCC and lot segments as required.
- Post invoice and emit 810 aligned to retailer remittance and allowance codes.
- Monitor ack 997/999 and functional ack failures in EDI inbox queue.
Common mistakes
- Shipping before 855 acceptance when retailer requires acknowledgement.
- ASN lot format not matching retailer TLC rules.
- Invoice quantity mismatch with partial ship tolerances.
- Missing UCC-128 labels linked to package SSCC on stock.quant.package.
- No retry on failed 997 causing chargebacks.
Odoo version notes
Native EDI depth varies by Odoo edition and localization; US retail often uses third-party EDI hubs with Odoo 16–18 via API. Enterprise sale_stock supports delivery-based invoicing needed for ASN alignment. Community implementations rely on middleware. Re-certify EDI maps after Odoo upgrades affecting picking and invoice fields.
When to bring in help
If the fix touches custom modules, regulated traceability, or production outages, a focused rescue sprint beats months of trial and error. See our Odoo service.
See our industry practice