EDIconnect for Odoo: Certified mapping for Carrefour, Kaufland, Lidl and 27 other retailers
Odoo does not generate native EDIFACT. Discover how Azuvio EDIconnect adds certified mapping for the top 30 EU retailers directly onto Odoo — no custom modules, no manual uploads.
Cosmin Boruz — EDI Specialist & Helpdesk Lead · 2026-10-30 · 9 min · ERP & Integrations
The EDI Problem in Odoo
Odoo lacks a native module for EDIFACT/EANCOM generation. While community modules exist ('EDI Framework', 'Factur-X'), they come with significant drawbacks:
No certified mapping per retailer (each retailer has its own subset of segments, codes, and rules)
No semantic validation before transmission
No error code management (conformance, syntax errors, duplicate detection)
No automated retry logic
The result: operators export CSV/PDF files from Odoo and manually upload them into each retailer's portal = 4-10 hours/week per retailer. With 4-6 active retailers, this equals 1-1.5 FTE.
Financial Impact
For an FMCG producer with €20M turnover and 5 active retailers (Carrefour, Kaufland, Lidl, Auchan, Metro):
Dedicated EDI operator: 1 FTE = €35k/year
Penalties for late DESADV/INVOIC: 0.6-1.2% of delivery value = €85-170k/year
Delivery rejections due to incorrect documentation: €12-28k/year
Management time lost on escalations: 15-25 hours/month
Opportunity cost: 2-3 new retailers missed because you cannot support EDI onboarding in <8 weeks
Total impact: €132-233k/year.
Solution: Azuvio EDIconnect + Odoo
Architecture: EDIconnect pulls orders, deliveries, invoices, and stock levels from Odoo via REST API. It transforms them into EDIFACT/EANCOM/XML per retailer specifications and transmits them via VAN/AS2/SFTP. Confirmations and statuses are pushed back into Odoo.
Capabilities:
Certified Mapping: Top 30 EU retailers (Carrefour, Kaufland, Lidl, Auchan, Metro, Selgros, Profi, Mega Image, Penny, Cora + Edeka, Rewe, Aldi, Tesco, IKEA, Decathlon, Leroy Merlin, Mercadona, El Corte Inglés, Billa, Auchan HU, Kaufland BG, etc.)
Supported Messages: ORDERS, ORDCHG, DESADV, RECADV, INVOIC, IFTSTA, INVRPT, SLSRPT, PRICAT
Semantic Validation: 60+ rules per retailer checked before sending (GLN, SSCC, EAN, quantities, dates, CN codes, payment terms)
Retry & Alerts: 3 retry levels, WhatsApp/SMS/Email alerts on failure, manual escalation in <2h
Status Dashboard: Track 'in transit' → 'received' → 'invoiced' → 'payment scheduled' for every retailer
Fast Setup: 2-4 weeks per retailer (vs. 3-6 months for custom development)
Results
EDI operator role eliminated: +€35k/year
Penalties reduced by 95%: +€128k/year
Rejections eliminated: +€22k/year
2 new retailers accessed (e.g., Mega Image + Kaufland BG): +€85k/year profit
Management freed up 15h/month
Investment: Setup for 5 retailers €28k + recurring €14k/year (VAN + SaaS). Year 1 ROI: (35+128+22+85) / 42 = 6.5x. Payback in 1.9 months.
Conclusion
Odoo doesn't do native EDI. EDIconnect does. Together, they allow an FMCG producer to connect to enterprise retail in 2-4 weeks per retailer. See Odoo Limitations or request an EDIconnect demo.