Everything EDI. One Knowledge Hub.
Learn EDI, understand integrations, discover jobs, solve mapping problems, and connect with EDI professionals.
Interactive
Explore the EDI Ecosystem
From business systems to EDI standards, transactions, trading partners, and AI-assisted processing — click any node to explore.
Transaction Directory
Popular EDI Transactions
The most frequently referenced X12, EDIFACT, and healthcare transaction sets.
Purchase Order
The X12 850 is the electronic purchase order a buyer sends to a supplier to request goods or services, replacing paper or PDF POs with a structured, machine-readable document.
Advance Ship Notice
The X12 856 (ASN) tells the buyer exactly what was shipped, how it was packed (pallet/case/item hierarchy), and when it will arrive — before the truck reaches the dock.
Invoice
The X12 810 is the electronic invoice a supplier sends after (or with) a shipment, billing the buyer for goods or services delivered.
Functional Acknowledgment
The X12 997 confirms that an interchange was received and whether it passed structural (syntax) validation — it does not confirm business acceptance of the content.
Motor Carrier Load Tender
The X12 204 is a shipper's offer (tender) of a freight load to a carrier, specifying origin, destination, equipment, and commodity details.
Eligibility, Coverage or Benefit Inquiry
The HIPAA X12 270 is a request from a healthcare provider to a payer asking whether a patient has active insurance coverage and what benefits apply.
Eligibility, Coverage or Benefit Information
The HIPAA X12 271 is the payer's response to a 270 inquiry, detailing whether the patient is covered and describing plan benefits, copays, and limitations.
Purchase Order Message
UN/EDIFACT ORDERS is the international equivalent of the X12 850 — a structured purchase order used widely across Europe and global trade lanes.
Learn
Featured EDI Guides
In-depth, segment-by-segment guides written and reviewed by practicing EDI professionals.
X12 850 Purchase Order: Complete EDI Guide
A complete, segment-by-segment walkthrough of the X12 850 Purchase Order — what it is, how it's structured, how to map it, and how to troubleshoot the errors that show up most often in production.
X12 856 Advance Ship Notice: The Complete EDI Guide
Everything you need to build, validate, and troubleshoot an X12 856 ASN — including the HL hierarchy that trips up almost every new implementation.
X12 270/271 Eligibility Inquiry and Response: A Practical Guide
How the HIPAA X12 270/271 pair works together to verify patient insurance eligibility in real time, with the segment structure and benefit codes that matter most.
EDIFACT ORDERS: A Complete Guide to the International Purchase Order Message
How UN/EDIFACT ORDERS compares to the X12 850, its segment structure, and what to watch for when trading with European and global manufacturing partners.
EDI Mapping Explained: From ERP Fields to X12 and EDIFACT Segments
A practical guide to how EDI mapping actually works — the concepts, common source formats, and a worked example translating SAP IDoc fields into an X12 850.
Reference
EDI Standards
The standards bodies behind every transaction on EDIBlogs.
Signature Feature
Interactive EDI Message Visualizer
Click any segment of a real X12 850 Purchase Order to see exactly what it means — in plain business language.
ISA
This is an envelope or control segment. Select a highlighted segment on the left (shown in green) for a full business explanation.
Signature Feature
EDI Mapping Visualizer
See how the same business fields translate across SAP, Oracle, CSV, JSON, XML, and EDI formats.
EDI Mapping Visualizer
Pick a source and target format to see how fields translate.
Source · SAP
Target · X12
Business fields represented: Item / Material · Quantity · Unit Price · Delivery Date · Order Reference. Hover a row to trace it across formats.
Discover
EDI Jobs
A sample of current openings across EDI analyst, developer, and architect roles.
EDI Analyst
HybridFull-timeConfidential Retail Distributor · Columbus, OH
Support daily EDI operations, monitor transaction failures, and onboard new retail trading partners onto existing X12 maps.
Source: LinkedIn Jobs · Posted 2026-09-15 · $65,000 – $80,000
EDI Developer
RemoteFull-timeLeading 3PL Provider · Remote (USA)
Build and maintain EDI maps across X12 and EDIFACT for a growing logistics network, working closely with WMS and TMS integration teams.
Source: Indeed · Posted 2026-09-17 · $90,000 – $115,000
SAP EDI Consultant
On-siteContractGlobal Manufacturing Group · Chicago, IL
Configure SAP IDoc-to-EDI mapping for a plant expansion project, integrating with SEEBURGER middleware for automotive supply chain partners.
Source: Company Careers Page · Posted 2026-09-10 · $70 – $95/hr
Connect
Community Questions
Real questions from EDI practitioners, answered by the community.
How do I map X12 856 HL loops correctly for a multi-pallet shipment?
I'm building an 856 ASN map for a new retail trading partner. My shipment has 3 pallets, each with 2 cartons, each carton containing multiple line items. I keep getting HL hierarchy errors on the 997. What's the correct HL01/HL02/HL03 structure for a Shipment → Pack (pallet) → Pack (carton) → Item hierarchy?
2 answers · 1820 views · asked by jmartinez_edi (EDI Practitioner)
What's the actual difference between a 997 and an 855 in terms of what they confirm?
My manager keeps saying 'the customer acknowledged the PO' whenever we get a 997 back, but I thought the 997 was just a technical acknowledgment. Am I wrong, or is there a business-level confirmation happening in the 997 that I'm missing?
1 answers · 3104 views · asked by newtoedi_ops (EDI Beginner)
Should I learn X12 or EDIFACT first as a new EDI analyst in the US?
I just got hired as a junior EDI analyst at a manufacturing company that sells both domestically and to European customers. Most of our training material so far is X12-focused. Is it worth self-studying EDIFACT now, or will I pick it up naturally once I'm deeper into X12?
2 answers · 1450 views · asked by kevin.chen.edi (EDI Beginner)
Getting CARC 45 constantly on 835s from one payer — is this normal?
We bill a specific payer regularly and almost every claim comes back with a CAS segment using group code CO and reason code 45. Payment is still coming through but always less than billed. Is this expected behavior or a sign something's wrong with our contracted rates setup?
1 answers · 980 views · asked by billing_lead_rms (EDI Practitioner)
Discover
EDI Tools & Platforms
Compare the platforms EDI teams use to translate, transmit, and manage trading partner connections.
IBM Sterling B2B Integrator
IBM
An on-premises and cloud-capable B2B integration platform used for EDI translation, trading partner management, and secure file transfer at enterprise scale.
Cleo Integration Cloud
Cleo
A cloud-based B2B integration platform providing EDI translation, partner onboarding, and API-based integration with visibility into transaction flows.
MuleSoft Anypoint Platform
Salesforce (MuleSoft)
A general-purpose integration and API management platform that supports EDI connectivity through dedicated connectors and transformation modules (DataWeave).
Boomi Integration
Boomi
A cloud-native integration platform (iPaaS) with visual process-building tools, offering EDI connectivity alongside broader application and data integration.
SPS Commerce Fulfillment
SPS Commerce
A managed EDI service focused on retail supply chains, connecting suppliers to retailers through a pre-built network of trading partner specifications.
TrueCommerce EDI Solutions
TrueCommerce
An EDI and supply chain integration provider offering managed EDI, a trading partner network, and integrations with common ERP and e-commerce platforms.
Signature Feature
EDI Knowledge Graph
Trace the relationships between standards, transactions, business concepts, and integration platforms.
EDIBlogs + EDI Agent AI
Need to process EDI files?
EDIBlogs helps you learn and understand EDI. EDI Agent AI parses, maps, validates, and automates it — two focused products, one connected ecosystem.
Try EDI Agent AI →Stay current on EDI
A monthly digest of new guides, transaction updates, and community discussions. No spam.