EDI Glossary: Key Terms and Definitions

Acknowledgment (997 / 999)

An EDI document sent by the recipient back to the sender to confirm that a transaction set was received and either accepted or rejected. A 997 is the standard functional acknowledgment in ANSI X12; a 999 is used in healthcare (HIPAA). Receiving a 997 does not mean the order was fulfilled — it only confirms the file arrived in valid format.

Advance Shipping Notice (ASN)

An EDI document sent by a supplier to a buyer before a shipment arrives. It covers the contents, packaging, and expected delivery date. The ASN (856 in ANSI X12) is one of the most important EDI documents in retail supply chains. Many large retailers charge chargebacks when it's missing or inaccurate.

ANSI X12

The dominant EDI standard in the United States, developed by the American National Standards Institute. ANSI X12 defines the structure and format of dozens of business document types, from purchase orders (850) to invoices (810), so that different companies' systems can exchange data without custom integrations. Most U.S. retailers, grocery chains, and 3PLs require ANSI X12-compliant EDI.

API (Application Programming Interface)

A defined set of protocols and tools that allows software applications to communicate with each other. In the context of EDI, APIs are increasingly used to send and receive business documents in real time, either as an alternative or a complement to traditional EDI file-based exchange.

AS2 (Applicability Statement 2)

A widely used protocol for transmitting EDI documents securely over the internet using HTTP/S. AS2 wraps data in digital certificates and encrypts it before transmission, then sends a Message Disposition Notification (MDN) to confirm receipt. Many large retailers, including Walmart and Target, require AS2 for EDI connections.

B2B (Business-to-Business)

Transactions conducted directly between businesses, such as a brand selling wholesale to a retailer. EDI is the standard protocol for automating B2B document exchange at scale.

B2C (Business-to-Consumer)

Transactions conducted directly between a company and individual consumers. While B2C commerce typically uses web storefronts rather than EDI, many B2C brands still need EDI to manage the wholesale and retail side of their supply chain.

Batch Processing

A method where EDI transactions are accumulated and processed together at scheduled intervals, such as every hour or at end of day, rather than individually in real time. Most legacy EDI systems run on batch processing. Modern platforms support real-time processing, which cuts down on delays in order fulfillment.

Business Process Integration

The alignment and connection of business processes, including order management, fulfillment, and invoicing, through automated data exchange. EDI is a core enabler of business process integration because it eliminates manual data entry between trading partners' systems.

Certification Authority

An organization that issues digital certificates to verify the identity of businesses and individuals in secure communications. In EDI, certification authorities are part of the Public Key Infrastructure (PKI) that keeps data exchanges trustworthy and tamper-proof.

Chargeback

A financial penalty issued by a retailer to a supplier for non-compliance with EDI or fulfillment requirements. Common triggers include a missing ASN, incorrect labeling, or a late shipping notice. Chargebacks are one of the main reasons brands prioritize getting their EDI setup right.

Clearinghouse

A third-party intermediary that receives, validates, and routes EDI transactions between trading partners. Clearinghouses are common in healthcare EDI, where they check claims for errors before forwarding to payers.

Cloud EDI

EDI that runs on cloud infrastructure rather than on-premise servers. Cloud EDI eliminates the need for companies to manage their own EDI hardware and software. Cloud-native platforms offer faster setup and vendor-managed maintenance.

Composite Data Structure

A group of related data elements used together within a single segment to convey complex information. Composite structures allow multiple pieces of data to be bundled under one element position in an EDI document.

Compliance Checking

The process of validating an EDI document against the agreed standards and partner-specific requirements before or after transmission. Compliance checking catches formatting errors, missing fields, and guideline violations that would otherwise cause transaction failures or chargebacks.

Communication Protocol

The rules that govern how EDI data is transmitted between systems. Common EDI communication protocols include AS2, SFTP, FTP, and HTTPS. The protocol used is typically defined in the Trading Partner Agreement.

Cross-Docking

A logistics practice where incoming shipments are unloaded and moved directly to outbound trucks with minimal storage time. Cross-docking depends heavily on accurate, timely ASNs sent via EDI so receiving teams can coordinate transfers without delays.

Data Element

The smallest named unit of information in an EDI document, such as a quantity, a date, or a price. Data elements are grouped into segments, and segments make up a full transaction set.

Delimiter

Special characters used to separate data within an EDI file. The most common delimiters in ANSI X12 are an asterisk (*) between elements and a tilde (~) at the end of segments. Incorrect delimiters are a frequent cause of EDI parsing errors.

Digital Certificate

An electronic document that proves the identity of a business and contains its public encryption key. Digital certificates are required for protocols like AS2, ensuring that EDI transmissions are authenticated and tamper-evident.

Direct EDI / Point-to-Point EDI

An EDI setup where two trading partners exchange documents directly with each other, without routing through a third-party VAN or network. Direct EDI is faster and often cheaper per transaction, but requires each party to manage the technical connection themselves.

EDI (Electronic Data Interchange)

The computer-to-computer exchange of standard business documents between trading partners. Instead of emailing PDFs or entering orders manually, companies use EDI to send structured data (purchase orders, invoices, shipping notices) directly between systems. EDI has been the backbone of B2B commerce since the 1970s and remains required by most major retailers, grocers, and 3PLs today.

EDI Outsourcing

Hiring a third-party provider to manage your EDI operations, including trading partner setup, mapping, monitoring, and compliance. EDI outsourcing (also called managed EDI) is common among smaller brands that don't have in-house EDI expertise but need to meet retailer requirements.

EDI Translator

Software that converts EDI-formatted documents into a format your internal systems can read, and vice versa. For example, an EDI translator might convert an 850 purchase order into a format your ERP can process, or convert your ERP's outbound data into a valid 810 invoice.

EDIFACT

An international EDI standard developed by the United Nations, used primarily in Europe, Asia, and Latin America. EDIFACT serves the same purpose as ANSI X12 but uses different message types and syntax. Companies trading internationally often need to support both standards.

Encryption

The process of encoding data so that only authorized parties can read it. In EDI, encryption protects sensitive business data like prices, quantities, and financial terms as it travels between systems. Protocols like AS2 and SFTP include encryption by default.

E-commerce

The buying and selling of goods or services using electronic systems and the internet. E-commerce platforms increasingly rely on EDI to manage the backend supply chain operations that power online storefronts, including order fulfillment, inventory management, and shipping.

Envelope (EDI)

The outer wrapper of an EDI transmission that identifies the sender, recipient, and transmission details. In ANSI X12, the envelope is defined by the Interchange Control Header (ISA) and Interchange Control Trailer (IEA) segments.

ERP (Enterprise Resource Planning)

Business software that manages core operations like inventory, finance, order management, and manufacturing in a single system. Common ERPs include NetSuite, SAP, Microsoft Dynamics, and Oracle. When EDI is integrated with an ERP, purchase orders, invoices, and shipping data flow automatically without manual data entry.

Functional Acknowledgment (FA)

An EDI message sent by the recipient to confirm that a transaction set was received and processed, either accepted or rejected. A 997 functional acknowledgment is one of the most exchanged EDI documents. It confirms the file was technically valid, not that the underlying order has been acted on.

Functional Group

A grouping of related transaction sets within an EDI interchange, bounded by a Group Header (GS) and Group Trailer (GE) segment. A single EDI transmission can include multiple functional groups, each containing one or more transaction sets of the same type.

GS1

The international organization that develops and maintains global standards for supply chain identification and communication, including barcodes, GTINs, and GLNs. GS1 standards are referenced in EDI transactions to uniquely identify products, locations, and trading partners.

GS1-128

A barcode standard used to encode product and shipment data, including lot numbers, expiration dates, and serial numbers, on labels and cartons. GS1-128 labels are commonly required alongside EDI ASNs so that warehouse teams can scan and verify incoming shipments automatically.

GTIN (Global Trade Item Number)

A globally unique number used to identify a product or service, typically encoded in a barcode. GTINs appear in EDI purchase orders and invoices to ensure both the buyer and supplier are referencing the exact same product.

HIPAA EDI

A set of EDI standards mandated by the Health Insurance Portability and Accountability Act for exchanging healthcare transactions, including insurance claims (837), eligibility checks (270/271), and remittance advice (835). HIPAA EDI uses ANSI X12 as the underlying standard but applies strict privacy and security requirements on top.

Integration Broker

A middleware layer that manages data translation and routing between different business systems. A common example is connecting an ERP to a WMS through EDI. Integration brokers handle format conversion, mapping rules, and routing logic so that data flows correctly without manual intervention.

Interchange Control Header (ISA)

The opening segment of every ANSI X12 EDI file. The ISA segment contains the sender and receiver IDs, the transmission date and time, the interchange control number, and other metadata. It's the first thing an EDI system reads to understand who sent the file and where it's going.

Interchange Control Trailer (IEA)

The closing segment of an ANSI X12 EDI file, which summarizes the number of functional groups included and references the control number from the ISA. The ISA and IEA together form the outer envelope of the transmission.

Invoice (810)

An EDI document sent by a supplier to request payment for goods or services. The 810 invoice in ANSI X12 is the electronic equivalent of a paper invoice and is typically sent after a shipment has been dispatched. It references the original purchase order number to help buyers match and approve payments.

JSON (JavaScript Object Notation)

A lightweight, human-readable data format used widely in modern APIs. In the EDI world, JSON is increasingly used as an alternative to traditional flat-file EDI formats, especially in API-first platforms.

Just-In-Time (JIT)

A production and inventory strategy where materials arrive at a facility exactly when they're needed, not before. JIT depends on fast, accurate EDI communication between suppliers and buyers to keep the supply chain synchronized without excess inventory buildup.

Loop

A repeating group of segments within an EDI transaction set, used to represent multiple instances of related data. For example, in an 850 purchase order, a loop might repeat once for each line item ordered. Understanding loops is essential when building or debugging EDI maps.

Mapping (EDI Mapping)

The process of defining how data fields in one system correspond to data fields in an EDI standard or another system. For example, mapping tells your EDI software where to pull the ship-to address from your order management system and where to place it in the correct segment of an 856 ASN. EDI mapping is one of the most labor-intensive parts of trading partner onboarding.

Message Standards

The predefined rules and formats that specify how EDI messages must be structured. Message standards ensure that a purchase order sent by one company can be correctly interpreted by a completely different system at the receiving end. ANSI X12 and EDIFACT are the two most widely used message standard families.

Partner Profile

A configuration record that defines the EDI rules, document types, communication protocols, and validation requirements for a specific trading partner. Each trading partner typically has their own profile because retailers, 3PLs, and distributors all have slightly different EDI guidelines.

Payment Order / Remittance Advice (820)

An EDI document that conveys payment details, including which invoices are being paid and any adjustments or deductions. The 820 helps suppliers reconcile payments against outstanding invoices automatically, reducing the need for manual accounts receivable work.

PKI (Public Key Infrastructure)

A framework of roles, policies, and procedures for creating, managing, and distributing digital certificates. PKI is the foundation of secure EDI communication, ensuring that documents are encrypted, authenticated, and haven't been tampered with during transmission.

Purchase Order (850)

An EDI document sent by a buyer to a supplier to request goods or services. The 850 is one of the most common EDI transaction sets and is often the starting point for the entire order-to-cash cycle. It specifies what products are ordered, in what quantities, at what prices, and where to ship them.

Real-Time Processing

Processing EDI transactions immediately as they arrive, rather than holding them for batch processing. Real-time processing reduces delays in order fulfillment, status updates, and invoice reconciliation.

SAP IDoc (Intermediate Document)

A data format developed by SAP for exchanging business information between SAP systems and external partners. IDocs are commonly used as the internal format that gets translated to and from standard EDI formats like ANSI X12 or EDIFACT.

Segment

A group of related data elements in an EDI document that serves a specific functional purpose. For example, the N1 segment in ANSI X12 identifies a party (buyer, seller, ship-to), while the PO1 segment contains line-item details in a purchase order.

Ship Notice / Manifest (ASN)

An EDI document (856 in ANSI X12) that provides detailed information about a pending delivery, including what's in each carton, how it's packed, and the tracking information. The ASN is critical for retailers because it allows receiving teams to plan for incoming shipments.

SKU (Stock Keeping Unit)

A unique identifier assigned to each distinct product for inventory tracking and management. SKUs appear throughout EDI transactions and must match between trading partners to avoid order and fulfillment errors.

Supply Chain Management

The coordination of the entire production and delivery flow of a product, from raw materials to the end consumer. EDI is a foundational technology in supply chain management because it automates the document exchange between every link in the chain.

Trading Partner Agreement (TPA)

A formal agreement between two companies that defines the rules for their EDI relationship, including which documents will be exchanged, what standards and protocols to use, and how errors and disputes will be handled.

Transaction Set

A complete EDI document that represents a specific business function, such as a purchase order (850), invoice (810), or shipping notice (856). A transaction set is bounded by a Transaction Set Header (ST) and Transaction Set Trailer (SE) in ANSI X12.

UCC (Uniform Code Council)

The predecessor organization to GS1 US, responsible for developing and managing the Universal Product Code (UPC) system and related supply chain standards used in EDI.

VAN (Value-Added Network)

A private third-party network that routes EDI documents between trading partners. While VANs were the standard approach for decades, many companies now use API-based EDI platforms that offer faster onboarding, lower costs, and real-time document processing.

Web EDI

A browser-based approach to EDI that lets companies send and receive EDI documents through a web portal instead of setting up direct system-to-system connections. Web EDI is popular among smaller suppliers who need to meet retailer EDI requirements without investing in full EDI infrastructure.

XML (eXtensible Markup Language)

A markup language that defines rules for encoding documents in a format readable by both humans and machines. XML is sometimes used as an alternative to traditional flat-file EDI formats, particularly in industries that have adopted newer integration standards.