Metro EDI — connect as a Metro supplier via EDIconnect Metro Cash & Carry operates Metro Group international EDI standards. EDIconnect connects you to ORDERS, DESADV, INVOIC and RECADV in 4–6 weeks, with support for Metro-specific B2B and HoReCa flows. Why you need EDI as a Metro supplierMetro has a hybrid model — selling both to small retail (B2B Cash & Carry) and to HoReCa operators (direct delivery). EDI requirements differ slightly between the two flows. EDIconnect is configured for both and recommends mapping suited to your profile. What Metro requires from an EDI supplierRequirements vary by category. EDIconnect knows the current profile and guides you step by step — you don't decipher the technical manual alone. Message standardEDIFACT (D96A retail standard)Mandatory messagesORDERS, DESADV, INVOIC, RECADV — plus, optionally, catalogue (PRICAT) and forecast (DELFOR) messages.GS1 identifiersSupplier GLN + Metro location GLN, GTIN on items, SSCC on palletsTransportAgreed VAN or direct EDI provider (EDIconnect operates both)ANAF e-InvoiceYes — EDI INVOIC automatically also generates ANAF XMLTypical onboarding time4–6 weeks Typical EDI messages in the Metro relationshipAn active Metro supplier typically exchanges 3–6 EDI messages. EDIconnect maps everything from your existing ERP. ORDERS — Order: Metro sends ORDERS with items, quantities, delivery location (warehouse or store GLN), requested date. Lands directly in your ERP.ORDRSP — Order response: Reply to ORDERS — confirm, change quantity or reject lines. Sent in minutes, not days.DESADV — Dispatch advice: Before delivery, you send DESADV with SSCCs and items per pallet. Enables fast receipt, no re-weighing.INVOIC — Invoice: Structured electronic invoice — auto-matches DESADV and ORDERS. Simultaneously generates the ANAF e-Invoice XML.RECADV — Receipt advice: Metro returns RECADV with quantities actually received. EDIconnect updates the ERP automatically for reconciliation. Metro supplier portal vs direct EDIMetro uses a portal for commercial documents and reporting. For medium and high-volume order flows, direct EDI is standard. EDIconnect coexists with the portal without issues. How we implement EDI for Metro4–6 weeks. For HoReCa direct-delivery flow, extra fields may be required (time windows, cold/hot requirements). Discovery (Week 1) — We inventory your items, Metro GLNs, ERP structure and required messages.Technical setup (Week 2) — Configure the connection (VAN or direct), install the EDIconnect connector on top of your ERP, map items.Message mapping (Week 3) — Detailed mapping ORDERS → ERP, DESADV ← WMS, INVOIC ← accounting. GS1 validations active.End-to-end test (Week 4) — Test with Metro using real messages in UAT. Fix any mismatch (GLN, VAT, format).Go-live (Week 5–6) — Gradual switch to production. EDIconnect monitors 100% of messages in the first 30 days. Typical problems Metro EDI solves Problem: Operator re-keying ORDERS from the Metro portal into the ERP Solution: ORDERS lands directly in the ERP. Operator only checks exceptions.Problem: EAN code errors blocking receipt Solution: GS1 validation in EDIconnect before transmission. Messages with invalid code blocked at source.Problem: DESADV sent too late or with inconsistent SSCC Solution: DESADV auto-generated from WMS at picking, with validated SSCC. Penalty eliminated.Problem: Slow reconciliation delivered vs received Solution: RECADV lands automatically in the ERP. Discrepancies appear as tasks immediately, not after 2 weeks.Problem: Orders with strict time windows for HoReCa Solution: EDIconnect brings them into the ERP with automatic delay alerts. FAQ Can I become a Metro supplier without EDI?For real operational volume, Metro requires EDI as standard. Exceptions exist for micro suppliers or non-standard flows. EDIconnect brings you to the required EDI profile in 4–6 weeks, regardless of your current ERP.How long does Metro EDI implementation take?4–6 weeks. For HoReCa direct-delivery flow, extra fields may be required (time windows, cold/hot requirements).Can I use EDIconnect for other retailers in parallel?Yes — EDIconnect is built exactly for the "one supplier, multiple retailers" case. The same platform simultaneously connects Metro and the other major retailers (Lidl, Kaufland, Carrefour, Auchan, Metro etc.). One ERP integration only.What happens if Metro changes message format?Mapping updates are EDIconnect's responsibility, included in support. You re-implement nothing — we version and deploy the new mapping with no downtime.I have an old ERP (Charisma, WinMentor, Senior). Will it work?Yes. EDIconnect has validated connectors for all common Romanian ERPs. For custom ERPs we use a generic API or staging tables.What's the difference between EDI and ANAF e-Invoice?e-Invoice is fiscal XML required by ANAF, EDI is the full commercial flow (ORDERS, DESADV, INVOIC, RECADV) required by retailers. EDI INVOIC contains the data needed for e-Invoice, so EDIconnect generates both from a single source.What does Metro EDI cost via EDIconnect?Azuvio EDI plan starts at €12/month/user. Initial implementation depends on complexity, but typically pays back in 3–6 months from operator time savings + zero penalties alone. Other retailers where EDIconnect connects youEDI AuchanEDI LidlEDI KauflandEDI CarrefourEDI Mega ImageEDI ProfiEDI DedemanEDI HornbachEDI Leroy Merlin All EDI capabilities Start your Metro EDI connectionBook a 20-minute call with an EDIconnect expert. We tell you the exact Metro technical profile, what to prepare, and a realistic timeline for you.