Updated
EDI in one paragraph
EDI (Electronic Data Interchange) is the automatic exchange of business documents between two companies’ systems, in an agreed standard format. Typical documents are purchase orders, order responses, despatch advice, receiving advice, stock reports and invoices.
Instead of an order being emailed and retyped into an ERP, it leaves the buyer’s system and lands directly in the supplier’s, with no manual step. Documents can travel between different companies or between applications in the same organisation.
How EDI works
Trading partners first agree which documents they will exchange and in which format: a standard such as EDIFACT or X12, or an internal format such as XML, JSON or CSV. Each partner publishes an implementation guide with its required fields.
- Extract: the document leaves the ERP, WMS or TMS, usually as a file or through an API.
- Map: the data is converted to the partner’s format (for example, from internal XML to an EANCOM ORDERS message).
- Transmit: the message travels over a secure channel such as AS2, SFTP, an API or a VAN.
- Acknowledge and monitor: the partner confirms receipt, and errors are flagged to the side that can fix them.
The hard part is not transmission but getting the mapping right and testing it with each partner. That is where most delays happen, and where a managed service makes the biggest difference.
EDI standards: EDIFACT, EANCOM, X12
- UN/EDIFACT is the United Nations international standard, widely used across Europe in retail, logistics, transport and automotive.
- EANCOM is the GS1 subset of EDIFACT for retail and consumer goods. Romanian retail chains (Kaufland, Lidl, Carrefour and others) generally work with EANCOM.
- ANSI X12 is the dominant standard in the United States and North America, including automotive.
- XML, JSON and CSV are used to integrate internal systems, e-commerce platforms and partners without classic EDI.
The same business flow can use a different format at each end. The EDI platform’s job is to translate between them without anyone stepping in. See ERP, WMS and TMS integration.
Common EDI messages
Each document type has a standard message name. These are the ones you meet most often in retail, logistics and transport:
- ORDERS
- Purchase order
- ORDRSP
- Order response (confirmation, change, rejection)
- DESADV
- Despatch advice (ASN), with pallets, SSCC, batches
- RECADV
- Receiving advice, with any differences
- INVOIC
- Invoice
- REMADV
- Remittance advice
- PRICAT
- Price and product catalogue
- PRODAT
- Product data
- PARTIN
- Party and location data (GLN)
- INSDES
- Delivery instruction to a warehouse
- INVRPT
- Inventory report
- IFTMIN
- Transport instruction
- IFTSTA
- Transport status
Together, ORDERS, ORDRSP, DESADV, RECADV and INVOIC make up the order-to-cash cycle. In X12 the equivalents are the 850, 855, 856, 861 and 810 transaction sets.
Types of EDI solution
- Dedicated EDI software: a standalone application for very large companies with high volumes and an in-house EDI team. Plenty of control, but purchase, maintenance and specialist staff costs.
- EDI module in the ERP, WMS or TMS: affordable, but limited once customisation gets complex or partners use different formats.
- EDI service provider: an external partner that converts and transmits documents. Flexible and more affordable, provided they respond quickly and stay involved.
- Fully managed EDI: the provider doesn’t just transmit; it maps, tests, onboards partners and runs the flows every day. This is the ZenB2B model.
Whatever the model, response time matters: a rejected message left for a day can hold up a delivery. That is why, at ZenB2B, errors trigger automatic alerts, to us and to you.
Benefits of EDI
- Orders are processed in minutes, not hours or days.
- No more transcription errors or lost documents.
- Faster receiving, because the warehouse knows what is coming.
- Invoices reconcile automatically with the order and the delivery.
- Status updates and partner KPIs can be tracked in real time.
- Adding a new partner no longer means more manual work.
The exact gain depends on the process and the partners, but order processing time can drop by 75% or more compared with manual entry.
EDI and e-invoicing (e-Factura)
Many countries now require e-invoicing. In Romania, e-Factura is the national system run by ANAF, the tax authority, through which B2B invoices must be reported to the state. EDI is the direct exchange of documents with trading partners, from order to invoice.
One does not replace the other. The same invoice reaches the retailer by EDI (INVOIC) and ANAF through e-Factura, usually from the supplier’s ERP or invoicing tool. With ZenB2B, the invoice lands in your invoicing system, consolidated with the rest, and that system sends it to e-Factura. Likewise, shipment data can generate the UIT code for Romania’s e-Transport. See invoicing from EDI.
Will AI replace EDI?
We don’t think so. The EDI standards are here to stay, and AI could not replace them without relying on them. EDIFACT, EANCOM and X12 are more than file formats. They hold decades of business knowledge agreed across an entire industry: what an order, a despatch advice or a receiving advice means, which data is mandatory, and how products and locations are identified (GTIN, GLN). Even two AI systems sending each other orders would need those same definitions for the result to be correct, verifiable and accepted by both sides.
Channels can change, and some flows are already moving to APIs. The structure and meaning of the documents remain. On that foundation, AI can bring real improvements to EDI implementation and operations: reading partner specifications, proposing mappings, flagging suspect data early and turning orders that still arrive as PDFs or emails into structured data.
We are also testing AI that reads purchase orders sent as PDFs and flags what is missing instead of guessing, in a pilot programme separate from ZenB2B.