Electronic data interchange (EDI)
Electronic data interchange (EDI) moves standardized business documents, such as purchase orders, ship notices, and invoices, directly between trading partners' systems in agreed machine-readable formats. The dominant standards are ANSI X12 in North America and EDIFACT internationally. Decades old, EDI still carries most high-volume manufacturing transactions because it is reliable, logged, and built into virtually every ERP.
Examples
Release-driven shipping: An axle supplier receives a weekly 830 planning release covering 12 weeks of forecast and a daily 862 firm shipping schedule. It ships four truckloads a day against the 862 and transmits an 856 within 30 minutes of each departure, so the plant books receipts by scanning a label instead of keying a packing slip.
Onboarding economics: Connecting a new contract manufacturer takes six weeks: trading partner agreement, 850/855/856/810 maps, and three test cycles, roughly $8,000 of effort. That pays back fast at 1,500 documents a month and never pays back for a supplier sending four invoices a quarter.
Silent failure: An ERP upgrade changes a date format in outbound 850s and the supplier's translator starts rejecting them. Three days of orders never arrive, caught only because expected 855 acknowledgments stopped coming back. Disciplined EDI teams alarm on missing acknowledgments for exactly this reason.
Definition
EDI works through numbered transaction sets. In ANSI X12, an 850 carries the purchase order, an 855 acknowledges it, an 856 sends the advanced shipping notice before the truck arrives, and an 810 carries the invoice; EDIFACT has equivalents such as ORDERS, DESADV, and INVOIC. Documents travel over value-added networks or direct connections, pass through translation software, and post straight into each partner's ERP system.
For high-volume manufacturing nothing has displaced it. Automotive OEMs have run material releases, ship notices, and invoices over EDI since the 1980s, and many large customers make EDI capability a condition of supply. Its strengths are the unglamorous ones: enormous volume, an acknowledgment and audit trail for every transmission, and maps that run for years untouched once they are stable.
The cost is rigidity. Each trading partner needs its own mapping and test cycles, format changes take weeks to coordinate, and one missing qualifier can reject a whole batch of documents. Small suppliers often cannot justify the setup, so buyers keep portals or email for the long tail, and newer channels such as API integrations and mandated e-invoicing grow alongside EDI rather than replacing it.
Related Terms
*GARTNER is a registered trademark and service mark of Gartner, Inc. and/or its affiliates in the U.S. and internationally, and COOL VENDORS is a registered trademark of Gartner, Inc. and/or its affiliates and are used herein with permission. All rights reserved. Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner’s research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.