WinMentor + EDI for Carrefour / Kaufland / Auchan — How it works (2026)
Technical and operational guide: integrating WinMentor with major retailers' EDI systems. ORDERS, DESADV, INVOIC, RECADV. How Azuvio EDIconnect enhances WinMentor.
Cosmin Boruz — EDI Specialist & Helpdesk Lead · 2026-05-23 · 11 min · ERP & Integrations
Why implement EDI with major retailers
Carrefour, Kaufland, Auchan, Mega Image, Lidl, Profi, Penny — all require mandatory EDI for their suppliers. Without EDI: penalties, blocked listings, and unacceptable orders via email/fax. With EDI: automated orders, automated dispatch notes, automated invoicing, and automated receipt confirmation.
Standard EDIFACT / EANCOM EDI flows
ORDERS — The retailer sends you the Purchase Order (PO).
ORDRSP — You confirm the order (optional, but recommended).
DESADV — You send the Despatch Advice (shipping notice) including pallets and SSCCs.
INVOIC — You send the EDI electronic invoice.
RECADV — The retailer confirms receipt (including any discrepancies).
REMADV — The retailer sends the payment remittance advice.
WinMentor Native Capabilities
WinMentor has an optional EDI module, but it is limited: it covers some basic EANCOM formats, but every retailer has its own "dialect" (field mapping, GLN codes, SSCC structures, certificates). Configuring each retailer manually can take weeks or months per integration.
Why you need a dedicated EDI Hub
Challenges of direct WinMentor ↔ Retailer integration:
1. Every retailer = different mapping + different certificates + different communication protocols (AS2, SFTP, OFTP2, WebEDI).
2. Format errors = lost orders, retailer penalties.
3. Retailer changes (new DESADV versions) = costly re-implementation.
4. Lack of visibility: what was sent, what was confirmed, where is it stuck?
The solution: an EDI hub that speaks every retailer's language and exposes a single internal format to WinMentor.
How Azuvio EDIconnect handles it (since 2014)
EDIconnect is the Azuvio EDI hub, in production for over 10 years. The workflow:
1. Retailer sends ORDERS (in their specific format) → EDIconnect normalizes it → writes the order into WinMentor (dedicated EDI series).
2. WinMentor generates DESADV + INVOIC (from internal data) → EDIconnect converts it to the retailer's format → sends it via the correct channel (AS2/SFTP/etc.).
3. Retailer sends RECADV → EDIconnect parses discrepancies → marks them in WinMentor + alerts the operator.
All managed via a live dashboard: status per order, per retailer, error logs, and automatic retries.
Supported Retailers (built-in)
Carrefour, Auchan, Kaufland, Mega Image, Lidl, Profi, Penny, Cora, Selgros, Metro — all with production-validated mappings.
Implementation Timeline
Per retailer: 2-4 weeks (config + UAT + go-live). First retailer (hub setup): +2-3 weeks one-time. After the first, each additional retailer is added incrementally.
Avoided Costs
Average penalties from major retailers for missed EDIs or incorrect DESADV: €500-2,000 per incident. With 5-10 incidents per month, the EDI hub pays for itself within 2-3 months.
Conclusion
WinMentor + Direct EDI = theoretically possible, practically risky. WinMentor + Dedicated EDI Hub = the standard pattern used by all professional distributors delivering to modern retail. See how EDIconnect works.