What is EDI? A Complete Plain-English Introduction

EDI stands for Electronic Data Interchange. It is the standardized electronic format that businesses use to exchange routine documents - purchase orders, invoices, shipping notices, payments, and more - directly between their computer systems, without paper, email attachments, or anyone re-typing the data by hand.

That last point is the whole reason EDI exists. When a retailer wants to order 10,000 units from a supplier, it does not send a PDF that a human on the other side opens, reads, and re-keys into an order-entry screen. Instead it transmits a structured EDI document that the supplier's system ingests automatically. Machines talk to machines, in a format both sides agreed on in advance.

A short history, and why it still matters

EDI is not new. Its roots go back to the 1960s and 1970s, when industries like transportation and retail began standardizing electronic documents to replace telexes and paper forms. The standards that dominate today - ANSI X12 in North America and UN/EDIFACT internationally - were formalized in the 1980s and have been refined ever since.

Despite being decades old, EDI is very much alive in 2026. Newer technologies like REST APIs and webhooks handle a growing share of real-time integrations, but EDI remains the backbone of business-to-business document exchange in retail, manufacturing, automotive, logistics, and healthcare. The reason is simple: enormous amounts of existing infrastructure, trading-partner agreements, and compliance requirements are built on it. A large retailer cannot simply tell its thousands of suppliers to abandon EDI overnight.

Why businesses use EDI

The benefits cluster around four themes:

• Speed. A purchase order that once took days by mail or fax is transmitted and acknowledged in seconds. Order-to-cash and procure-to-pay cycles shrink dramatically.
• Accuracy. Eliminating manual re-keying removes a whole class of errors. A single mistyped quantity or price can trigger an incorrect shipment, a disputed invoice, or a chargeback. EDI removes the human keyboard from the loop.
• Cost. Less paper, less postage, less manual labor, and fewer costly disputes. At scale, the savings are substantial.
• Scalability. A retailer trading with thousands of suppliers, or a manufacturer with hundreds of parts vendors, simply cannot operate by hand. EDI makes high transaction volume possible.

Because of these advantages, large buyers - major retailers, automakers, government agencies, and healthcare payers - frequently require their partners to support EDI as a condition of doing business. For many small and mid-sized suppliers, "being EDI capable" is not optional; it is the price of entry.

What an EDI document actually looks like

A raw EDI file is dense and unfriendly to human eyes. Here is a small fragment of an ANSI X12 purchase order:

ST*850*0001~
BEG*00*SA*PO-99831**20240115~
PO1*1*100*EA*12.50**UP*012345678905~

It looks like noise, but the structure is consistent and learnable. Three concepts unlock almost everything:

• Segments. Each line is a segment, beginning with a two- or three-letter tag (ST, BEG, PO1) and ending with a segment terminator (here the tilde ~). A segment is roughly like a row of related data.
• Elements. Within a segment, individual values are elements, separated by a delimiter (here the asterisk *). So in PO1*1*100*EA*12.50, the elements are 1, 100, EA, and 12.50.
• Meaning by position. Each element's meaning is defined by its position. In a PO1 segment, the first element is the line number, the second is the quantity, the third is the unit of measure, and the fourth is the unit price. So that line reads: line 1, quantity 100, unit of measure EA (each), price 12.50.

Once you internalize "segments contain positional elements separated by delimiters," reading EDI becomes a matter of knowing what each segment tag means - which is exactly what a viewer like EdiPeek does for you.

Envelopes: how documents are wrapped

EDI documents do not float around loose. They are wrapped in envelopes that handle routing and control. In X12, the structure nests like this:

• ISA / IEA - the interchange envelope (the outermost wrapper, identifying sender and receiver)
• GS / GE - the functional group (groups related documents of the same type)
• ST / SE - the transaction set (one actual business document, such as one purchase order)

The ST segment is the one that tells you which document type you are looking at. ST*850 means a purchase order; ST*810 means an invoice. We cover this envelope structure in depth in our guide on the ISA, GS, and ST envelope.

The two big standards

There is no single worldwide EDI format. Two dominate, and which you encounter depends largely on geography:

• ANSI X12 - used mainly in North America. Document types are numbered: 850 (purchase order), 810 (invoice), 856 (advance ship notice), 837 (healthcare claim), and hundreds more.
• UN/EDIFACT - the international standard used across Europe, Asia, and most global trade. Document types have names: ORDERS, INVOIC, DESADV, IFTMIN.

They express the same business documents in different syntax. An X12 850 and an EDIFACT ORDERS are both purchase orders. We compare them side by side in X12 vs EDIFACT.

How EDI documents travel

The document content is separate from how it is transmitted. Over the years, EDI has moved across several transport methods:

• VANs (Value-Added Networks) - private third-party networks that act like a managed post office for EDI, historically the dominant method.
• AS2 - a secure internet-based protocol that sends EDI directly between partners with encryption and signed receipts (MDNs).
• SFTP - secure file transfer, common for batch exchanges.
• APIs - increasingly used to wrap or replace traditional EDI flows.

As someone reading or troubleshooting EDI, you usually care about the document content rather than the transport. The file you receive is the same regardless of how it arrived.

Common transaction types you will meet

A handful of document types account for most day-to-day EDI traffic:

Frequently asked questions