/

/

The History of EDI: From the Berlin Airlift to API-Era Trading Partners

EDI

The History of EDI: From the Berlin Airlift to API-Era Trading Partners

How EDI grew from Edward Guilbert's Berlin Airlift manifests into ANSI X12, EDIFACT, and AS2, with a dated timeline and what it means for suppliers today.

EDI

The History of EDI: From the Berlin Airlift to API-Era Trading Partners

How EDI grew from Edward Guilbert's Berlin Airlift manifests into ANSI X12, EDIFACT, and AS2, with a dated timeline and what it means for suppliers today.

Dashed path linking an airlift-era cargo plane to a server with documents and a satellite dish, showing data moving over time.
No headings found on page

Electronic data interchange started as a fix for a cargo-tracking problem during the 1948 Berlin Airlift, and the transportation industry built the first EDI standards from it in 1975. Retail, grocery, and auto manufacturing adopted it in the late 1970s and 1980s, which is how it became the way suppliers and retailers trade purchase orders, ship notices, and invoices today.

If you sell into big-box retail, you already live with the results. The 850 purchase order that drops into your ERP, the segment-and-element layout your team squints at during testing, and the retailer-specific implementation guides all trace back to decisions made by logistics officers and railroad committees decades ago. Knowing that history makes a few modern headaches easier to explain, such as why two retailers can both send "X12 4010" and still expect different data, or why your ISA ID setup looks the way it does.

1948: the Berlin Airlift and the first standard manifest

In June 1948 the Soviet Union closed road, rail, and barge access into the Allied sectors of Berlin. For the next 13 months the U.S., Britain, and France supplied the city by air, flying in more than 2 million tons of food and supplies (Computerworld via EDI Library).

The bottleneck was paperwork. Manifests arrived in different layouts and sometimes different languages, and ground crews had minutes to unload each aircraft. Edward A. Guilbert and other logistics officers built a standard manifest that could be sent ahead of the plane by telex, radio-teletype, or telephone, so the receiving crew knew what was coming before it landed.

Who was Edward A. Guilbert?

Guilbert is the person most sources call the "Father of EDI." Accounts disagree on his rank. The widely circulated Computerworld history calls him a U.S. Army Master Sergeant, while X12's own history says Air Force Major General William H. Tunner, who ran the airlift, picked Colonel Edward Guilbert as traffic manager for every cargo movement (X12). Either way, the idea is the same one your trading partners rely on today: send standardized data about the shipment before the shipment arrives. That is exactly what an 856 advance ship notice does.

X12 still presents the Edward A. Guilbert Lifetime Achievement Award each year at its winter meeting.

1960s: the first commercial EDI messages

Guilbert took the manifest idea into private industry. In the early 1960s, while at DuPont, he built a standard set of electronic messages for sending cargo information between DuPont and one of its carriers, Chemical Leaman Tank Lines (X12). It was a single shipper and a single carrier agreeing on one format, which is still how most EDI relationships start: two partners, one map.

By the mid-1960s, Holland-America Steamship Line was sending trans-Atlantic shipping manifests as telex messages. The receiving end converted them to paper tape and fed them into the company's computers. Many timelines date the first EDI transmission to 1965 for this reason.

The weakness showed up quickly. Every carrier and shipper that copied the idea invented its own format, so a trucking company serving ten shippers might maintain ten different message layouts. Suppliers who juggle a separate implementation guide for each retailer will recognize the problem.

1968 to 1975: the TDCC writes the first cross-industry standards

By 1968 enough railroads, airlines, truckers, and ocean carriers were sending electronic manifests that they formed the Transportation Data Coordinating Committee (TDCC). Its stated purpose was to create standards so computers at different transportation companies, and the industries they served, could talk to each other. Guilbert served as TDCC president for 19 years (X12).

In July 1975 the TDCC published the first U.S. EDI standards covering air, ocean, motor, and rail. That first manual had 45 transaction sets, 68 segments, and 189 data elements, and it was assembled over three months without computer help. Earl "Buddy" Bass was its principal author, working alongside Guilbert, Joe Carley, and Ralph Notto.

Bass also gave EDI the vocabulary you still see in every implementation guide: transaction set, data segment, and data element. He proposed giving each element fixed attributes such as data type, minimum and maximum length, an identifier, and a name. When your team reads an element definition in a retailer's 810 invoice spec, that layout comes from the 1975 manual.

The early committee assumed that once everyone shared common codes, the rest would sort itself out. It did not, and Bass was brought in specifically to turn the work groups' output into a structured manual that could be updated over time.

1979 to 1980s: ANSI X12 and the first retail mandates

In 1979 the American National Standards Institute chartered Accredited Standards Committee X12 to build a uniform standard for business transactions across industries. The X12 standard extended the TDCC's transportation work and eventually replaced it (iWay Software). X12's own history places ANSI accreditation in 1977, with the Credit Research Foundation as the first secretariat and the Data Interchange Standards Association (DISA) taking over later (X12). The 1979 date is the one most references use for the committee's charter.

How EDI moved from freight to retail

Adoption followed buying power. The grocery and food industry ran an EDI pilot starting in 1977. By the early 1980s Ford and General Motors required suppliers to use EDI, and Sears and Kmart demanded it from theirs (Computerworld via EDI Library). Grocery and general merchandise eventually settled on their own subsets of X12, UCS for grocery and VICS for general merchandise retail, which is why the same purchase order can look slightly different depending on the channel.

The savings went mostly to the large buyers. Smaller suppliers had to pay for translation software and VAN connections, and often ran a separate setup for each big customer because no two retailers used exactly the same subset of the standard. The Computerworld history sums up the deal suppliers faced in four words: no EDI, no sale. By 1991, about 12,000 U.S. businesses were using EDI.

That pressure is still the reason most brands start EDI today. If you are weighing when to begin, our piece on how postponing EDI implementation hurts your bottom line covers the cost side.

1988: UN/EDIFACT and the split between North America and everyone else

While the TDCC worked on U.S. transportation standards, the United Kingdom built its own. HM Customs and Excise, with the Simplification of Trade Procedures Board (SITPRO), developed TRADACOMS for international trade documents (iWay Software).

In 1988 the United Nations chartered UN/EDIFACT to create one internationally approved structure for business messages. EDIFACT messages are called United Nations Standard Messages and map roughly to X12 transaction sets: an EDIFACT ORDERS message does the job of an X12 850, and an INVOIC does the job of an 810.

The result is a two-standard world. North American retail, grocery, and logistics run mostly on X12, while Europe and much of Asia use EDIFACT. If you sell to a Canadian retailer and a European distributor in the same year, expect to support both. Our guide to EDI standards walks through how they differ.

1980s to 2000s: VANs, the internet, and AS2

Through the 1980s most EDI moved over value-added networks. A VAN works like a private post office: each trading partner keeps a mailbox, drops documents in, and the network delivers them, usually for a per-document or per-volume fee. That model worked when private networks and dial-up lines were the only options.

In 1991 the U.S. National Science Foundation lifted restrictions on commercial use of the internet, and EDI over the internet became cheaper than VAN delivery (Computerworld via EDI Library). The Internet Engineering Task Force approved the AS2 protocol around 2001, and an XML alternative, ebXML 1.0, was approved the same year.

Why Walmart's 2002 AS2 decision mattered

In September 2002 Walmart announced it would exchange EDI with thousands of suppliers over AS2 using iSoft's Commerce Suite, replacing dial-up modem connections. iSoft offered the client software to Walmart suppliers for a $300 annual maintenance fee, and suppliers could use other AS2 vendors if they preferred (Computerworld, 2002).

Not everyone was convinced at the time. A Giga Information Group analyst quoted in the same article said AS2 and related internet protocols carried under 10% of EDI traffic, and that suppliers with many connections were still better off on a VAN. Both models survived. Today most suppliers run some mix of AS2, SFTP, and VAN connections depending on what each retailer requires. Our complete guide to the AS2 protocol covers certificates, MDNs, and setup.

EDI today: the same structure, wired into your ERP and WMS

The 1975 vocabulary of transaction sets, segments, and elements is still in daily use, and X12 is still an active standards body. It publishes the EDI standard once a year in January, and its current initiatives include syntax-neutral metadata so the same definitions can be expressed outside the classic X12 format (X12).

What changed is where EDI lives inside a supplier's business. In the 1980s a translator sat on a server and someone printed the output. Now the 850 flows straight into the ERP, the warehouse ships against it, and the 856 and 810 go back out with no rekeying. That only works when the EDI layer is connected to your systems of record, which is why most of the hard work today is integration. See our ERP integration readiness guide and the connector pages for NetSuite and Cin7.

The 1980s problem of every big customer wanting something slightly different has not gone away either. Each retailer still publishes its own implementation guide, and small deviations show up as compliance chargebacks. Our trading partner directory and our write-up on chargeback prevention in CPG and food go into the specifics.

Will APIs replace EDI?

APIs now sit alongside EDI. Marketplaces such as Amazon expose order and inventory data through APIs (our SP-API guide), while big-box retailers still run purchase orders, ship notices, and invoices on X12. Most growing brands end up supporting both, with the EDI and API traffic landing in the same ERP. Testing that kind of hybrid setup is covered in our API testing guide for EDI integration.

EDI timeline at a glance

Year

Milestone

Why it matters to suppliers

1948

Guilbert's standard cargo manifest for the Berlin Airlift

Data sent ahead of the shipment, the idea behind every ASN

Early 1960s

DuPont and Chemical Leaman Tank Lines exchange electronic cargo messages

First shipper-to-carrier EDI agreement

Mid-1960s

Holland-America Steamship Line sends manifests by telex

Often cited as the first EDI transmission (1965)

1968

Transportation Data Coordinating Committee formed

First attempt to replace one-off formats with a shared one

1975

TDCC publishes the first U.S. EDI standards: 45 transaction sets, 68 segments, 189 elements

Origin of the transaction set, segment, and element structure

1977

Grocery and food industry EDI pilot begins

Grocery starts its move to EDI

1979

ANSI charters ASC X12

The standard behind today's 850, 856, and 810

Early 1980s

Ford and GM require supplier EDI; Sears and Kmart follow

Retailer mandates begin: no EDI, no sale

1988

United Nations charters UN/EDIFACT

International standard used outside North America

1991

Commercial internet use opens up; about 12,000 U.S. businesses use EDI

Internet transport starts to compete with VANs

2001

AS2 approved by the IETF; ebXML 1.0 approved

Secure EDI over the public internet

2002

Walmart moves supplier EDI to AS2

Lowers the cost of entry for smaller suppliers

Today

X12 publishes an updated standard every January

EDI runs alongside APIs, integrated with ERP and WMS

Frequently asked questions about EDI history

Who invented EDI?

Edward A. Guilbert is generally credited as the Father of EDI. He standardized cargo manifests during the 1948 Berlin Airlift, built electronic cargo messages at DuPont in the early 1960s, and led the Transportation Data Coordinating Committee for 19 years.

When was EDI first used?

The first commercial EDI messages date to the early-to-mid 1960s, when DuPont exchanged electronic cargo messages with Chemical Leaman Tank Lines and Holland-America Steamship Line sent trans-Atlantic manifests by telex. Many timelines use 1965 as the starting year.

What was EDI originally used for?

Shipping manifests. The earliest standards, published by the TDCC in 1975, covered air, ocean, motor, and rail transportation. Retail, grocery, and automotive adoption followed in the late 1970s and 1980s.

When was ANSI X12 created?

ANSI chartered Accredited Standards Committee X12 in 1979 to build cross-industry standards on top of the TDCC's transportation work. X12's own history dates ANSI accreditation to 1977.

What is the difference between X12 and EDIFACT?

X12 is the North American standard, chartered by ANSI. EDIFACT is the international standard chartered by the United Nations in 1988, used mainly in Europe and Asia. They describe the same business documents with different syntax; for example, X12 calls a purchase order an 850 and EDIFACT calls it ORDERS.

Why do retailers still require EDI?

Retailers have decades of systems, processes, and compliance programs built on X12, and EDI handles high volumes of orders, ship notices, and invoices in a predictable format. Suppliers that cannot exchange EDI usually cannot sell to large retailers, which has been true since the early 1980s.

Is EDI still used today?

Yes. X12 still publishes an updated EDI standard every January, and major retailers continue to require EDI for purchase orders, advance ship notices, and invoices.

More articles

Our platform is designed to empower businesses of all sizes to work smarter and achieve their goals with confidence.

Nov 13, 2026

Your ASN is only as accurate as your 3PL's WMS. The questions brands should ask about receiving, pack data, 945 timing and adjustments before go-live.

Isometric clipboard checklist with three green checkmarks beside a warehouse, a barcode label and a stopwatch.

Oct 27, 2026

A 997 confirms an EDI file parsed cleanly. The order answer comes in the 855. See what the MDN, 997, 999 and 855 each confirm, plus a go-live checklist.

Orange 3D question mark floating above an isometric cream document with a yellow checkmark, on a light blue triangle grid.

Oct 23, 2026

What EDI 824 Application Advice and 864 Text Message rejections mean, how to read them, and how to fix the invoice, ASN, and PO errors behind them.

Illustration of a stack of documents with a red X on the top page, representing rejected EDI documents.

Nov 13, 2026

Your ASN is only as accurate as your 3PL's WMS. The questions brands should ask about receiving, pack data, 945 timing and adjustments before go-live.

Isometric clipboard checklist with three green checkmarks beside a warehouse, a barcode label and a stopwatch.

Oct 27, 2026

A 997 confirms an EDI file parsed cleanly. The order answer comes in the 855. See what the MDN, 997, 999 and 855 each confirm, plus a go-live checklist.

Orange 3D question mark floating above an isometric cream document with a yellow checkmark, on a light blue triangle grid.

Oct 23, 2026

What EDI 824 Application Advice and 864 Text Message rejections mean, how to read them, and how to fix the invoice, ASN, and PO errors behind them.

Illustration of a stack of documents with a red X on the top page, representing rejected EDI documents.

Oct 21, 2026

How the EDI 832 Price/Sales Catalog works, segment by segment, plus the item data errors that cause rejections and chargebacks across retailers and distributors.

Isometric illustration of a central item catalog document linked by dashed lines to three retail stores on a teal grid.

Let's connect!

Let's connect!

Let's connect!