What Is EDI? Electronic Data Interchange, Explained

EDI (electronic data interchange) is the machine-to-machine exchange of standard business documents between companies: purchase orders, invoices, shipping notices, customs declarations. No email, no PDFs, no retyping. One system talks straight to another in an agreed format.

The formats are the point. ANSI X12 dominates North America and EDIFACT most of the rest of the world, with each document type numbered: an X12 850 is a purchase order, an 856 is an advance ship notice, an 810 is an invoice. Because both sides implement the same spec, a retailer's system can send an order that a supplier's system books automatically, seconds later.

Retail and logistics run on this. Large retailers commonly require EDI from every supplier. Carriers exchange booking confirmations and status updates with forwarders over it, and customs systems in many countries accept declarations through EDI channels.

It's an old technology (the standards date back to the 1970s and 80s) and it gets declared dead regularly, yet the document volume keeps growing. APIs are newer and friendlier, but a big trading partner that says "EDI or no contract" settles the argument. In practice the two coexist: EDI with the giants, APIs with everyone else.

Why it matters for custom software

The recurring job in our logistics work is translation between worlds: an EDI feed from a retailer or carrier on one side, a modern ERP or TMS on the other, and a mapping layer we build in between. Get that layer right and orders flow in untouched by human hands. Get it wrong and someone retypes 200 orders a week.