Merlin ERP + EDI for Retailers (Carrefour, Metro, Auchan, eMAG) — 2026 Solutions
Merlin ERP lacks native EDI. Comparison of 3 integration options for major retailers: custom development, third-party platforms, and the Azuvio Smart Layer. Real costs, ROI, and pitfalls.
Cosmin Boruz — EDI Specialist & Helpdesk Lead · 2026-08-12 · 11 min · ERP & Integrations
The EDI Challenge for Merlin Users
If you supply Carrefour, Metro, Auchan, Kaufland, Selgros, Dedeman, Mega Image, Lidl, or eMAG Marketplace, you are contractually obligated to exchange electronic documents (EDI): purchase orders (ORDERS), dispatch advice (DESADV), invoices (INVOIC), and receiving advice (RECADV).
Merlin ERP does not have native EDI. You must choose between 3 options.
Option 1: Custom Development per Retailer
Mechanism: Prodigy or an external developer builds a dedicated connector per retailer (parsing EDIFACT/XML, mapping Merlin fields, connecting to the retailer's portal).
Cost: €5,000-€15,000/retailer (initial) + €1,500-€3,500/year maintenance per retailer.
For 5 retailers: ~€50,000 initial + €12,500/year (~€115,000 over 5 years).
Problems:
Every retailer schema change = re-development
Fragmented troubleshooting (5 separate systems)
Lack of centralized visibility
Dependency on a specific developer
Option 2: Third-Party EDI Platforms
Providers: EDIconnect (Soft Net), Comarch EDI, GS1 Romania.
Average cost: €28,000-€73,000/year for 5-7 retailers (subscription + transaction fees).
Advantages: Centralized dashboard, maintenance included, support for schema changes.
Disadvantages:
Extremely high cost for mid-market companies
Integration with Merlin remains custom (file export/import)
Vendor lock-in
Option 3: Azuvio EDIconnect Smart Layer
Azuvio native module with pre-built connectors for the top 15 retailers in RO + EU.
Cost: €3,600-€7,200/year for 5-7 retailers (depending on volume).
Advantages:
Native integration with Merlin via API (automatic mapping)
Pre-submission validation (prevents chargebacks)
Centralized dashboard
Schema updates included in support
Automatic retry mechanism
5-Year Cost Comparison (5 Retailers)
| Option | Year 1 | Year 2-5 /year | 5-Year Total |
|---------|------|------------|-------------|
| Custom dev | €50,000 | €12,500 | €100,000 |
| Third-party platform | €45,000 | €45,000 | €225,000 |
| Azuvio Smart Layer | €6,000 | €5,500 | €28,000 |
Typical Smart Layer EDI ROI
Real-world scenario: FMCG distributor, 8 retailers, 12,000 invoices/year.
Current costs (custom + manual):
Retailer chargebacks (manual EDI errors): ~€38,000/year
Manual processing time (1 FTE part-time): ~€22,000/year
Custom connector maintenance: ~€18,000/year
Total: ~€78,000/year
With the Smart Layer:
Azuvio cost: ~€7,000/year
Reduced chargebacks (-95%): ~€1,900/year
Manual labor eliminated: €0
Total: ~€9,000/year
Net Savings: ~€69,000/year. ROI: 10x.
Conclusion
For a Merlin user supplying major retailers, the EDIconnect Smart Layer is by far the best cost-benefit option. Custom development seems cheaper initially, but hidden costs (chargebacks, maintenance, refactoring) cause it to quickly exceed the alternatives.
See also: «FMCG Distributor Case Study».