The Complete EDI Guide for 2026: What Every Supplier Needs to Know

What EDI actually replaces

Electronic Data Interchange, or EDI, is the structured exchange of business documents between two computer systems without manual re-entry. Instead of a retailer emailing a PDF purchase order that someone in your sales office retypes into an ERP, EDI delivers the same order as a machine-readable file that lands directly in your accounting or warehouse software. The documents themselves have not changed — orders, invoices, delivery notes, dispatch advices — but the way they travel between companies has, and that shift removes the slow, error-prone manual step that used to sit in the middle of every transaction.

For suppliers working with large retail chains, EDI is rarely optional. Kaufland, Carrefour, Lidl, Auchan, Mega Image, Metro, Selgros, Penny, Profi, Cora and dozens of other retailers in Romania require their supplier base to exchange orders and invoices electronically because it lets their own systems process thousands of transactions a day without human intervention. A supplier that cannot connect through EDI either loses the account or ends up doing the retailer's data entry manually, which is slower and far more likely to produce mismatched quantities, wrong prices or missed delivery windows.

The core EDI standards you will encounter

Most Romanian and Western European retail EDI traffic is built on EDIFACT, a United Nations standard for structured business documents, and its retail-specific subset EANCOM, which defines exact message formats for orders (ORDERS), invoices (INVOIC), dispatch advices (DESADV) and more. American and some multinational partners may instead request ANSI X12, the equivalent standard used widely in North America. Both standards describe the same underlying business events — an order was placed, goods were shipped, an invoice is due — but they format the data differently, so a platform that speaks both is what lets a single supplier serve both markets without maintaining two separate systems.

On top of the message format sits the transport layer: how the file physically moves from your system to the retailer's. Common protocols include AS2, OFTP2, SFTP, and connections routed through a Value Added Network (VAN). Retailers typically mandate which protocol they support, and a supplier working with several retailers usually ends up needing to support two or three of them simultaneously. This is one of the main reasons companies choose a managed EDI provider rather than building direct point-to-point connections for every partner.

Web EDI versus full ERP integration

Suppliers generally choose between two ways of working with EDI messages. A Web EDI portal presents incoming orders as readable screens where staff can view, confirm and generate documents through a browser, which suits smaller volumes or companies without an ERP. Full ERP integration instead connects EDI messages directly into systems like SAP, Dynamics 365, NetSuite, WinMentor, Charisma, Senior, Clarvision or Odoo, so orders appear automatically as sales orders and invoices are generated and sent back without anyone touching a keyboard.

Many suppliers start with Web EDI to meet a retailer deadline quickly, then move specific high-volume partners to ERP integration once the process is proven and worth automating further. A platform that supports 40+ ERP systems out of the box, alongside a Web EDI portal, lets a company move between the two models without changing provider or renegotiating retailer connections, which keeps the transition low-risk.

• Web EDI: browser-based, fast to deploy, ideal for lower order volumes
• ERP integration: automatic order and invoice flow, best for higher volumes
• Hybrid: some retailers via Web EDI, others via ERP, on one platform

Compliance: e-Factura and e-Transport

In Romania, EDI now overlaps with tax compliance. ANAF's e-Factura system requires businesses to submit invoices in UBL 2.1 XML format through the national platform, and e-Transport requires advance notification of certain goods movements. Suppliers already sending EANCOM invoices to retailers need those invoices reconciled with what is reported to ANAF, so a connectivity platform that can generate both the retailer-facing EDI invoice and the ANAF-compliant e-Factura from the same underlying data avoids duplicate work and reduces the risk of mismatched figures between the two systems.

Treating e-Factura as a separate project from retailer EDI often leads to two disconnected data entry points and reconciliation headaches at month-end. Suppliers who plan for both requirements together, ideally on a single platform, generally get a smoother rollout and a much smaller ongoing administrative burden.

Planning a realistic project timeline

A well-scoped EDI onboarding project with a single retailer, using an existing connectivity platform rather than a from-scratch build, can go live in under seven business days once master data and testing are prioritized. The clock mostly depends on your side: how quickly product catalog data, pricing, and delivery locations can be confirmed, and how fast your team can review a handful of test orders. Building a connection entirely in-house, negotiating specifications on both sides, is a considerably longer undertaking and rarely finishes as fast.

Multi-retailer rollouts take longer only because there are more parties to coordinate, not because each individual connection is inherently slow. Sequencing retailers by order volume or urgency, rather than trying to launch everything simultaneously, is usually the more manageable approach for internal teams with limited EDI experience.

Budgeting for EDI

Pricing for managed EDI connectivity in the Romanian market typically starts from 24 EUR per month for a base subscription, with the total cost depending on the number of retailer connections, message volume, and whether ERP integration is included. This is generally far lower than maintaining in-house EDI infrastructure, which requires specialized staff, VAN subscriptions and ongoing maintenance of mapping rules whenever a retailer changes its specification.

Before selecting a provider, it is worth comparing not just the monthly fee but what is included: onboarding support, the number of supported document types, whether ANAF e-Factura is bundled, and how additional retailer connections are priced as the business grows.

FAQ

Is EDI mandatory for suppliers to Romanian retailers?

Most large retailers, including Kaufland, Carrefour, Lidl and Auchan, require electronic order and invoice exchange as a condition of doing business, though the exact enforcement varies by chain and category.

What is the difference between EDIFACT and EANCOM?

EDIFACT is the general UN standard for electronic business documents; EANCOM is a retail-focused subset of EDIFACT with stricter, more specific message definitions used by grocery and retail chains.

Can I use EDI without an ERP system?

Yes. A Web EDI portal lets staff process orders and generate invoices through a browser without any ERP integration, which is common for smaller suppliers.

Does EDI replace e-Factura reporting to ANAF?

No, they serve different purposes. EDI handles retailer-to-supplier document exchange; e-Factura is the mandatory ANAF tax reporting channel. Both can be generated from the same source data on one platform.

How long does it take to connect to a new retailer?

With an established connectivity platform, the first retailer connection can typically go live in under seven business days once catalog and delivery data are ready.