Mastering EDI Segments: The Complete List and Guide for Seamless Data Exchange

In the world of modern supply chain management and business-to-business (B2B) communication, Electronic Data Interchange (EDI) is the backbone of efficiency. At the heart of every EDI message lies a structured language of data, broken down into specific units known as EDI segments. Understanding the EDI segments list is crucial for any business looking to automate ordering, invoicing, shipping, and payment processes.

This article, inspired by the comprehensive resources found at Dreamfulfill’s EDI information hub, provides a clear, detailed breakdown of standard EDI segments, their functions, and why they matter for your business.

What Exactly is an EDI Segment?

An EDI segment is a group of related data elements. Think of it as a sentence in a structured conversation. Each segment begins with a specific three-letter identifier (the "Segment ID") and ends with a terminator, typically an apostrophe ('). The data within is separated by delimiters (like *).

For example, the N1 segment identifies a name. A simple version might look like: N1*BY*ACME Corp*92*12345'

This tells the system: "This is a Name segment (N1). The type is 'BY' (Buyer). The name is 'ACME Corp'. The identification code qualifier is '92' (Assigned by Buyer or Buyer's Agent), and the code is '12345'."

The Essential EDI Segments List (Standard X12)

While there are dozens of segments depending on the specific transaction set (e.g., 850 for Purchase Orders, 810 for Invoices, 856 for Ship Notices), mastery of the following core segments is essential for most implementations.

1. Core Transaction & Header Segments (The "Envelope")These segments define the beginning and end of the entire message.

• ISA (Interchange Control Header): The "outer envelope." Contains sender/receiver IDs, date, time, and control number.
• GS (Functional Group Header): The "inner envelope." Groups related transaction sets (e.g., all Purchase Orders) together.
• ST (Transaction Set Header): Starts the specific business document (e.g., an 850 Purchase Order).
• SE (Transaction Set Trailer): Ends the business document, confirming the number of segments.
• GE (Functional Group Trailer): Ends the functional group.
• IEA (Interchange Control Trailer): Ends the entire interchange.

2. Business Data Segments (The "Content")These are the segments that carry the actual business information for Purchase Orders (850), Invoices (810), and Advanced Ship Notices (856).

• BEG (Beginning Segment for Purchase Order): Identifies the document type, PO number, and date.
• REF (Reference Identification): Provides additional reference numbers, such as contract numbers, department numbers, or customer order numbers.
• PER (Administrative Communications Contact): Contains contact names, phone numbers, and email addresses.
• N1, N2, N3, N4 (Name & Address Segments): The "Loop" for party information.
  • N1: Name (e.g., Buyer, Seller, Ship-To, Bill-To).
  • N3: Address line (Street address).
  • N4: Geographic location (City, State, ZIP code).
• ITD (Terms of Sale/Deferred Terms of Sale): Specifies payment terms, discount percentages, and due dates.
• PO1 (Purchase Order Line Item): The most critical line-item segment. Contains the line number, item identifier, quantity, unit price, and unit of measure.
• PID (Product/Item Description): A textual description of the item.
• TD1 (Carrier Details (Quantity and Weight)): Used in shipping documents to describe total weight, volume, and number of units.
• TD5 (Carrier Details (Routing Sequence/Transit Time)): Specifies the carrier, routing, and mode of transport (e.g., UPS Ground, FedEx Air).
• REF (in the Ship Notice context): Often used for Bill of Lading numbers or the carrier's PRO number.
• CTT (Transaction Totals): Provides a summary of the number of line items and total quantity.
• IT1 (Invoice Line Item): The line-item segment for an invoice, including quantity invoiced, unit price, and product ID.

How to Interpret and Use the EDI Segments List

A powerful tool for understanding how these segments fit together is the EDI Mapping Guide or Specification Document. As highlighted in the resources from Dreamfulfill, these guides provide explicit rules for every segment.

Here’s a practical example (Purchase Order - 850):

1. ISA... * (Identifies the sender and receiver)
2. GS... * (Identifies the group as Purchase Orders)
3. ST... * (Starts the 850 document)
4. BEG... * (Provides PO number and date)
5. N1... * (Buyer name)
6. N3... * (Buyer address)
7. N4... * (Buyer city, state, ZIP)
8. PO1... * (First item: 10 units of product ID "X123" at $5.00 each)
9. PO1... * (Second item: 5 units of product ID "Y456" at $12.00 each)
10. CTT... * (Total line items: 2; Total quantity: 15)
11. SE... * (Ends the 850, counts segments)
12. GE... * (Ends the group)
13. IEA... * (Ends the interchange)

Why This Matters for Your Business

According to insights from the Dreamfulfill platform, a deep understanding of the EDI segments list leads to:

• Fewer Trading Partner Errors: Correctly mapping the N1 loop ensures the right customer gets billed.
• Faster Onboarding: When you know the exact REF segment for a customer's PO number, you eliminate manual data entry.
• Cost Reduction: Automating the interpretation of PO1 and IT1 segments reduces human error in order-to-cash cycles.
• Enhanced Visibility: Knowing the TD5 and REF segments in an 856 Ship Notice gives real-time tracking data.

Conclusion

The EDI segments list is not just a technical specification; it is the language of modern commerce. Whether you are integrating with a major retailer or a logistics partner, mastering these segments—from the ISA header to the CTT total—is the key to reliable, automated data exchange. For a deeper dive into your specific trading partner's requirements, always consult the official EDI mapping guide provided by your integration partner. A platform like Dreamfulfill, accessible through resources like their product information page, can be an excellent starting point for building your EDI knowledge and ensuring your business stays competitive in a rapidly automating world.