Freight & Logistics Terminology

Electronic Data Interchange (EDI)

Category: Supply Chain Technology • Logistics Automation • Data Exchange
Electronic Data Interchange (EDI) is the automated, computer-to-computer exchange of standard business documents—such as purchase orders, shipment notices, and invoices—between trading partners. By eliminating paper, manual data entry, and email attachments, EDI functions as a seamless data integration network across global supply chains.

Three Pillars of Electronic Data Interchange

1. Standardization

Converts proprietary business data into universally recognized transaction formats (e.g., ANSI X12, UN/EDIFACT) for seamless partner interoperability.

2. Process Automation

Replaces manual document processing with instant system-to-system transmission, reducing lead times and eliminating human data entry errors.

3. Real-Time Visibility

Enables instant status tracking across shipments, inventory levels, load tenders, and customs filings to streamline operational workflows.

Key EDI Logistics Transaction Sets

Supply chain organizations rely on specific standardized EDI code sets to automate freight movements from booking to payment:

  • EDI 204 (Motor Carrier Load Tender): Transmitted by shippers or brokers to offer a shipment to a motor carrier.
  • EDI 211 (Electronic Bill of Lading): Sends detailed cargo, shipper, and consignee details directly to the carrier's operating system.
  • EDI 214 (Transportation Carrier Shipment Status Message): Provides real-time tracking updates, pickup confirmations, and delivery timestamps.
  • EDI 856 (Advance Shipping Notice - ASN): Details pending deliveries, pallet layouts, and itemized contents prior to physical arrival.
  • EDI 210 (Freight Details and Invoice): Transmits carrier payment requests and itemized transportation charges for freight audit.
  • EDI 997 (Functional Acknowledgment): Serves as an automated electronic receipt confirming an EDI document was received and syntax-validated.

Common EDI Transmission Methods

EDI Architecture Connection Type Best Used For
Direct EDI / Point-to-Point AS2 / SFTP / FTP-S High-volume enterprise partners requiring secure, real-time connections without third-party transactional fees.
VAN (Value-Added Network) Hosted Private Network Companies managing connections with hundreds of trading partners via a centralized, secure clearinghouse mail service.
Web EDI Browser-Based Portal Small to mid-sized vendors who fill out web forms that automatically translate entries into standardized EDI formats for buyers.
EDI via API / Hybrid REST API & Cloud Middleware Modern supply chain platforms combining legacy EDI standards with instant REST APIs for real-time cloud integration.

How an EDI Transaction Works in Practice

  1. 1
    Data Extraction & Translation: The sender's ERP or TMS extracts business data (e.g., a load offer) and translates it into a standard EDI document format (e.g., EDI 204).
  2. 2
    Secure Transmission: The translated file is securely transmitted over the internet via AS2 protocol or an EDI VAN to the receiving partner.
  3. 3
    Validation & Ingestion: The receiver's EDI system validates the file structure, sends an automated receipt (EDI 997), and translates the data into their system.
  4. 4
    System Execution: The recipient's software automatically triggers internal workflows, such as reserving driver capacity or issuing a load confirmation.

Difference: EDI vs. Modern APIs in Logistics

While EDI (Electronic Data Interchange) is the long-established industry backbone for batch-processed, standardized documents (like invoices and load tenders), APIs (Application Programming Interfaces) enable instant, event-driven data exchanges (such as live GPS tracking and dynamic spot-rate quotes). Modern logistics technology stacks typically integrate both—using EDI for formal contracting/billing and APIs for real-time visibility.