What Is EDI (Electronic Data Interchange)?
Also known as: Electronic Data Interchange, ANSI X12, EDIFACT
Definition
EDI (Electronic Data Interchange) is the computer-to-computer exchange of business documents such as purchase orders, invoices, and shipping notices between trading partners in a standardized structured format, without human intervention.
EDI (Electronic Data Interchange) Explained
EDI predates the internet and remains the backbone of B2B commerce in manufacturing, retail, automotive, healthcare, and logistics. Its purpose is to eliminate rekeying: a customer's purchase order becomes a sales order in the supplier's ERP automatically, and the resulting shipment notice and invoice flow back the same way. Volume is the justification - a supplier processing thousands of order lines a week cannot absorb manual entry error rates, and large buyers commonly make EDI capability a condition of doing business.
Two standards dominate. ANSI ASC X12 is the North American standard, using three-digit transaction set numbers such as 850 for purchase order, 856 for advance ship notice, 810 for invoice, and 997 for functional acknowledgment. UN/EDIFACT is the international standard, using mnemonic names such as ORDERS, DESADV, and INVOIC. Industry subsets refine them further, including VDA and Odette in European automotive and HIPAA-mandated X12 transactions in US healthcare.
The physical structure is hierarchical and delimiter-driven. An interchange begins with an ISA segment and ends with IEA, wrapping one or more functional groups bounded by GS and GE, each containing one or more transaction sets bounded by ST and SE. Inside, data is organized into segments identified by two- or three-character codes, with elements separated by a delimiter and segments terminated by another. Versions matter: X12 004010 and 005010 differ in available segments and qualifiers, and a partner running one version cannot parse the other reliably.
Transport is a separate decision from format. AS2 provides signed and encrypted transfer over HTTPS with a message disposition notification as proof of receipt and is the retail and general B2B default. SFTP is widely used in manufacturing. Value Added Networks act as intermediaries providing mailboxes, routing, and partner onboarding. OFTP2 is standard in European automotive. Increasingly, API-based exchange sits alongside EDI, with the EDI document format preserved but the transport modernized.
The hard part is never the standard - it is the partner-specific implementation guide. Every trading partner publishes its own requirements specifying which segments are mandatory beyond the base standard, which qualifiers are allowed, how identifiers are formatted, and what business rules apply. Two customers both sending an 850 will differ in dozens of details. This is why EDI programs are measured in partners onboarded rather than transactions supported, and why mapping and testing dominate project effort.
Why It Matters
- Large customers make EDI capability a condition of supply, so the ability to trade electronically is a direct revenue gate.
- Automated order-to-cash removes rekeying errors that cause wrong quantities, wrong prices, and chargebacks on retail and automotive accounts.
- Partner-specific implementation guides mean each new customer is a mapping project, making onboarding capacity a real constraint on growth.
- Acknowledgment and error handling design determines whether a failed transaction is caught in minutes or discovered when a customer calls about a missing shipment.
In Practice
A 997 functional acknowledgment confirms syntax, not business acceptance. Suppliers routinely treat a received 997 as proof the order was processed, then discover weeks later that the order failed business validation inside the ERP - unknown part number, invalid ship-to, or price mismatch - and sat in an error queue nobody monitored. Separate the two: automate 997 generation at the translator, and build a monitored exception queue with an owner and an aging threshold for documents that pass syntax but fail business rules.
Frequently Asked Questions
What is the difference between X12 and EDIFACT?
ANSI ASC X12 is the North American EDI standard and identifies documents by three-digit transaction set numbers such as 850 or 856. UN/EDIFACT is the international standard maintained under the United Nations and identifies documents by mnemonic message types such as ORDERS or DESADV. They serve the same purpose with different syntax, segment names, and version conventions, and translators typically support both.
Is EDI being replaced by APIs?
Not replaced, but supplemented. EDI remains entrenched because thousands of trading relationships and decades of business rules are encoded in it, and large buyers have no incentive to migrate. APIs are increasingly used for real-time needs such as inventory availability and shipment tracking, and modern integration platforms often carry EDI documents over API or event-based transports while preserving the document formats themselves.
Related Terms
EDI 850 Purchase Order
The EDI 850 is the ANSI X12 transaction set used to transmit a purchase order electronically from a buyer to a supplier, carrying header terms, ship-to and bill-to parties, and line item details such as quantity, price, and product identifiers.
Middleware
Middleware is software that sits between applications and handles the communication, transformation, routing, and reliability concerns of moving data between them, so that the applications themselves do not need to know about each other directly.
Data Mapping
Data mapping is the process of defining how each field in a source system corresponds to a field in a target system, including the transformation rules, value translations, default values, and conditional logic needed to move data correctly between them.
Go Deeper
AS9100 Audit Readiness Checklist
A 30-point checklist for AS9100 Rev D certification and surveillance audits, weighted toward the aerospace-specific requirements where auditors write the most findings.
Lot Traceability in Electronics Manufacturing
Lot traceability in electronics manufacturing explained: component-level genealogy, ERP lot control setup, IPC-1782 levels, recall readiness, and AI-driven trace.
Serialization Strategies for Defense Electronics
Serialization strategies for defense electronics: IUID and MIL-STD-130 marking, ERP serial control, DFARS compliance, genealogy, and AI-driven serial management.
Working with EDI (Electronic Data Interchange) in a live environment? Our engineers do this every day - and our AI agents automate most of it.