WizPro + EDI Carrefour / Kaufland / Auchan, How it works and your options (2026)
EDI mapping per retailer, costs, and alternatives: Native WizPro vs. EDIconnect Smart Layer. Designed for FMCG distributors with 5+ retailers.
Cosmin Boruz - EDI Specialist & Helpdesk Lead · 2026-05-25 · 10 min · ERP & Integrations
Context
EDI (Electronic Data Interchange) with major retailers (Carrefour, Kaufland, Auchan, Lidl, Profi, Mega Image, Penny) is mandatory for FMCG distributors. Exchanged documents include: ORDERS, ORDRSP, DESADV, RECADV, INVOIC, REMADV.
How native EDI works in WizPro
WizPro generates DESADV (dispatch advice) and INVOIC (invoice) in EDIFACT D96A or XML formats. Transmission is handled via VAN (Value Added Network) or AS2 to the retailer's hub.
Typical steps for a new retailer:
1. EDI contract with the retailer + obtaining a GS1 GLN ID
2. Reviewing retailer technical specifications (each has unique versions and extensions)
3. Mapping development in WizPro (custom XSLT or Wizrom code), 4-8 weeks
4. UAT (User Acceptance Testing) with the retailer, 2-4 weeks
5. Pilot go-live phase - 4-6 weeks
6. Stabilization - 2-3 months
Cost per retailer: €8,000-€15,000 for development + annual maintenance.
Real costs at scale
For an FMCG distributor with 8 retailers:
Development of 8 mappings × €10,000 = €80,000 one-time cost
Maintenance for 8 × €1,500/year = €12,000/year
VAN/AS2 traffic ~€3,000/year
Total 5-year TCO ~€135,000
Plus: any change in retailer specifications (frequently 1-2 per year per retailer) = €1,500-€3,000 extra.
Limitations of native WizPro EDI
1. Slow onboarding - 4-8 weeks per retailer.
2. Rigid mapping - changes require Wizrom code modifications.
3. Basic monitoring - if a DESADV fails, you often find out from a chargeback 2 weeks later.
4. Manual retry - lacks an intelligent retry orchestrator.
5. Manual chargeback reconciliation, no integrated workflow.
The Smart Layer Alternative: EDIconnect by Azuvio
EDIconnect is the Azuvio EDI module active since 2014, featuring 100+ pre-configured mappings for retailers across Romania and SEE.
Advantages vs. Native WizPro EDI:
| Aspect | Native WizPro | Azuvio EDIconnect |
|---|---|---|
| New retailer onboarding | 4-8 weeks | 1-2 weeks |
| Setup cost per retailer | €8k-15k | €1.5k-3k |
| Real-time monitoring | Basic | Live dashboard + alerting |
| Intelligent retry | Manual | Automatic with backoff |
| Specification changes | Wizrom code | UI Config |
| Chargeback reconciliation | Manual | Integrated workflow |
5-year TCO for EDIconnect (8 retailers): ~€50,000 (€15k setup + €7k/year × 5).
Savings vs. native WizPro: ~€85,000 + 70-85% reduction in chargebacks.
How EDIconnect integrates with WizPro
EDIconnect runs as an operational layer between retailers and WizPro:
1. Receives ORDERS from retailers
2. Pushes them into WizPro as sales orders
3. Reads DESADV + INVOIC from WizPro (at the time of invoicing)
4. Sends data to the retailer with retry + monitoring
5. Synchronizes status in WizPro (delivered / invoiced / paid)
WizPro remains the master for invoicing and accounting. EDIconnect serves strictly as the EDI operational layer.
When to choose native WizPro EDI
You only have 1-2 retailers and low volumes
You have an in-house IT team with strong EDIFACT/XML skills
You want everything "in a single system" and accept the resulting rigidity
When to choose EDIconnect Smart Layer
You have 3+ retailers or plan to scale
You need high velocity for new retailer onboarding
You want to minimize chargebacks
You need a real-time dashboard for CFO and Operations
Conclusion
WizPro + native EDI works for small-scale scenarios. At scale (5+ retailers, 500+ orders/month), WizPro + EDIconnect Smart Layer is 3-5x more cost-efficient and significantly faster to onboard. See "WizPro Limitations" or calculate your ROI.