Too Long; Didn’t Read (TL;DR)
- If you sell to retailers, distributors, manufacturers or 3PLs in the US, sooner or later someone will ask you for EDI X12. It’s the standard almost everyone there uses.
- You don’t need to learn all of it. Most supplier relationships run on a handful of documents: the 850 Purchase Order, 855 PO Acknowledgment, 856 Advance Ship Notice, 810 Invoice and 997 Functional Acknowledgment.
- Every US partner has its own rules on top of the standard, and many large retailers charge you when documents are late or wrong.
- Already running EDIFACT in Europe? You don’t need a second EDI system for the US. Babelway runs X12 and EDIFACT side by side in one self-service cloud platform.
- Related reads: What is EDI X12 850 and how to use it · What is EDI X12 940 · Best EDI & B2B Integration Tools in 2026
You’ve just signed your first big US retail account. Congratulations. A few days later, the onboarding pack arrives: a vendor agreement, a routing guide, a labeling manual, and one line that turns out to be a project of its own: “Please set up EDI with us.”
In the US, that means EDI X12. And usually there’s a date attached, because the retailer wants to see test files before the first order goes out.
If you’re a US supplier, you’ve probably dealt with X12 before. If you’re coming from Europe, it’s often one more standard to add next to the EDIFACT, Peppol or XML flows you already run. Either way, you want the same thing: get connected quickly, avoid chargebacks, and keep orders moving without adding manual work for your team.
This guide walks you through what X12 is, which documents your US partners will ask for, how it compares to EDIFACT, and how to get set up without surprises.
Still choosing the platform that will run your US EDI? Start with the companion guide:
How to Choose Your EDI & B2B Integration Tool Based on Your Business Objective
What is EDI X12?
EDI X12 (you’ll also see it called ANSI X12 or ASC X12) is the EDI standard developed by the Accredited Standards Committee X12, which the American National Standards Institute chartered back in 1979. Today it covers more than 300 document types across retail, manufacturing, transportation, finance, healthcare and government.
Each document type, or transaction set, has a three-digit number. An 850 is a purchase order. An 810 is an invoice. An 856 is an advance ship notice. Once you know the numbers, X12 conversations get a lot easier to follow, and because both sides use the same structure, documents go from one system straight into the other with no retyping.
A few things are worth knowing before you start:
- X12 is what US partners expect. Big-box retailers, grocery chains, home improvement and pharmacy retailers, distributors and carriers all run their supplier EDI programs on it.
- Your partner picks the version. X12 releases a new version every year, but most companies stick with one for a long time. In retail and supply chain, you’ll still see 004010 a lot. US healthcare uses 005010, which HIPAA requires. The partner’s companion guide will tell you which one you need.
- It’s often a condition of doing business. Many large US buyers won’t place the first order until EDI is working, and they’ll apply penalties when documents arrive late or contain errors.
The X12 Documents US Partners Will Ask You For
The good news: you won’t need all 300+ transaction sets. Most US supplier relationships run on the same small group of documents, plus a few extras depending on your industry and how you fulfill orders.
| Transaction | Name | Direction (supplier view) | What it does |
|---|---|---|---|
| 850 | Purchase Order | Inbound | The buyer places an order |
| 860 | Purchase Order Change | Inbound | The buyer changes or cancels an order |
| 855 | Purchase Order Acknowledgment | Outbound | You accept, change or reject the order |
| 856 | Advance Ship Notice (ASN) | Outbound | You tell the buyer what’s shipping, how it’s packed and when it arrives |
| 810 | Invoice | Outbound | You bill the buyer for what you shipped |
| 846 | Inventory Inquiry/Advice | Outbound | You share stock levels, common in drop-ship and e-commerce |
| 820 | Payment Order/Remittance Advice | Inbound | The buyer tells you what they paid and for which invoices |
| 997 | Functional Acknowledgment | Both | Confirms a document arrived and could be read |
| 940 / 945 | Warehouse Shipping Order / Advice | Both | Tells your 3PL what to ship, and confirms it shipped |
| 204 / 214 | Load Tender / Shipment Status | Both | Books freight with carriers and tracks it |
Put together, a typical US order looks like this:
EDI 850 → EDI 997 → EDI 855 → EDI 856 → EDI 810 → EDI 820
If there’s one document to get right early, it’s the 856 ASN. US retailers use it to plan what arrives at their distribution centers and when, and it’s usually linked to the GS1-128 labels on your cartons. When the ASN is late, missing, or doesn’t match what’s actually on the truck, that’s when chargebacks start showing up.
X12 vs EDIFACT: What Changes When You Enter the US
If you already exchange EDIFACT messages with European partners, most of this will feel familiar. The ideas are the same. The names and the syntax are what change.
| Topic | ANSI X12 | UN/EDIFACT |
|---|---|---|
| Main region | United States and North America | Europe and international trade |
| Document names | Numbers: 850, 856, 810 | Names: ORDERS, DESADV, INVOIC |
| Envelope | ISA / GS / ST … SE / GE / IEA | UNB / UNG / UNH … UNT / UNE / UNZ |
| Typical delimiters | * between elements, ~ at segment end | + between elements, ‘ at segment end |
| Interchange header | Fixed-length ISA segment | Variable-length UNB segment |
| Technical acknowledgment | 997 (999 in HIPAA healthcare) | CONTRL |
| Common versions | 004010, 005010 and later | D96A, D01B and later |
What this means in practice: you don’t have to start over. Your ERP data doesn’t change. What changes is the mapping that turns that data into X12 for your US partners and EDIFACT for your European ones. If your platform handles both, adding the US is a matter of setting up a few new channels, not launching a new project.
Sample EDI X12 810 Invoice
Here’s a shortened 810 invoice in version 004010. Real files are usually longer, with extra reference and address segments depending on what your partner asks for.
ISA*00* *00* *ZZ*SUPPLIEREU *08*9251750000 *261006*1030*U*00401*000000123*0*P*>~
GS*IN*SUPPLIEREU*9251750000*20261006*1030*123*X*004010~
ST*810*0001~
BIG*20261006*INV-45821*20260928*PO-778812~
N1*ST*ACME RETAIL DC 6094*92*6094~
N1*RE*EUROGOODS BV*92*VEND01~
ITD*01*3*2**10**30~
DTM*011*20261005~
IT1*1*120*EA*8.50**UP*012345678905*VN*EU-4471~
IT1*2*48*EA*14.25**UP*012345678912*VN*EU-4472~
TDS*170400~
CTT*2~
SE*11*0001~
GE*1*123~
IEA*1*000000123~How to read it: the BIG line holds the invoice date and number plus the PO date and number it refers to. The two N1 lines say where the goods went and who gets paid. ITD sets the payment terms (2% discount within 10 days, otherwise net 30). Each IT1 line is one product, with quantity, unit, price, UPC and your own part number. TDS is the invoice total in cents ($1,704.00), and CTT counts the lines.
How to Get X12-Ready for US Partners: A Step-by-Step Guide
X12 projects rarely run late because of the standard itself. They run late because of the small differences between the standard and what one specific partner wants. Here’s how to stay ahead of that.
Step 1: Get each partner’s companion guide and vendor requirements
Every big US buyer publishes its own X12 guides, along with routing and labeling rules. They tell you which version to use, which segments are mandatory, which product IDs they expect (UPC, GTIN or their own item number) and how quickly documents like the ASN need to arrive. Read these first. They matter more than the generic standard. Babelway already works with many US trading partners, including Walmart, The Home Depot, Wayfair, Rite Aid, Office Depot and Ace Hardware.
Step 2: Set up your IDs and connection
You and your partner need to agree on how you identify each other in the ISA header (often a DUNS number or an ID you both agree on). Then you set up the connection they ask for. In the US that’s usually AS2, a VAN, SFTP or an API. Large retailers often ask for AS2, because every message comes back with a signed receipt.
Step 3: Connect X12 to your ERP or WMS
Incoming 850s and 860s need to show up in your ERP as sales orders. Outgoing 855s, 856s and 810s need to be built from your ERP, warehouse or shipping data. In Babelway, you do this with drag-and-drop mapping, so you can see what goes where and reuse the same maps for the next partner, without writing code.
Step 4: Check the business rules, not just the format
A file can be perfectly valid X12 and still get rejected or charged back. Before anything goes out, check the things your partner will check: does the PO number match the original order, do the quantities match what you shipped, is the ship-to code right, does the price match the PO?
Step 5: Test, go live, and keep an eye on it
Most large US partners want a test phase before you go live. After that, watch every flow. A missing 997, a rejected invoice or a late ASN should reach you the same day, not weeks later as a deduction on a payment.
👉 Before you connect a new US partner, go through the EDI Integration Tune-Up Checklist. It covers the basics that cause most go-live surprises.
Onboarding a US Retailer? See How Babelway Handles X12 from Day One
Bring your partner’s spec, your ERP and your deadline. We’ll show you the full 850 to 810 flow running on your own use case. → Book a personalized Babelway demo · Take the Product Tour
Common X12 Mistakes in the US Market (and How to Avoid Them)
Treating the standard as the spec
Two retailers can both ask for an “X12 004010 856” and still expect very different files. One wants the shipment broken down by order, then pack, then item. The other wants different references and different label data. Build to each partner’s guide, not to the standard.
Sending the ASN late, or getting it wrong
Many US retailers want the 856 before the truck reaches their distribution center. If it arrives after the goods, or the carton contents don’t match the labels, expect a chargeback. The most reliable fix is to generate the 856 automatically from your shipping data, so nobody has to remember to send it.
Missing 860 change orders
US buyers change quantities and dates, or cancel lines, all the time after sending the original 850. If those 860s don’t make it into your ERP, you end up shipping against an old order and sending an invoice that won’t match.
Not checking 997 acknowledgments
If you send an invoice and never get a 997 back, your partner may never have received it. Track acknowledgments for everything you send, so a late payment doesn’t come as a surprise.
Running a separate system for each region
Companies expanding from Europe often add a US-only EDI provider next to their EDIFACT setup. It works, but now you have two sets of maps, two places to monitor and two bills. One platform that handles both keeps everything in one place.
Try Babelway Free for 30 Days and Build Your First X12 Channel
No commitment and no consultant needed. Connect a US partner, map your 850 and 810, and test the whole flow. Most teams have their first channel ready in days. → Start your 30-day Babelway trial · Explore Babelway Academy (free)
Why Babelway is the Right Platform for EDI X12 in the US Market
Any EDI provider can send an X12 file. Where they differ is what happens next: when a retailer updates its guide, when a new distribution center gets added, or when you need to figure out why an ASN failed before it turns into a chargeback.
Babelway is a cloud-based, self-service EDI and B2B integration platform. Your team owns its channels and can make changes itself, instead of waiting in a vendor’s support queue.
- X12 and EDIFACT in one place. Work with US partners in X12 and European partners in EDIFACT, Peppol, XML, JSON or flat files, all from the same account.
- Drag-and-drop mapping. Build or update your 850, 856 and 810 maps visually. No scripting, and no services project every time something changes. See the self-service EDI platform story.
- Ready for US partners. Connections for retailers like Walmart and The Home Depot, with AS2, VAN, SFTP and REST API support built in.
- Alerts when something goes wrong. You see right away which document failed, why, and how to fix it, before it costs you money.
- Clear pricing. Babelway’s pricing plans are public. No surprise fees for changing a map.
Want to see how Babelway compares with other EDI platforms? Take a look at Best EDI & B2B Integration Tools in 2026.
👉 Curious how Babelway fits into your wider EDI strategy? Read Taking Ownership of EDI and B2B Integrations with Babelway.
Check out what Babelway users say about Babelway’s EDI and B2B integration capabilities on G2 → Babelway reviews
Frequently Asked Questions
What is EDI X12 used for in the US?
It’s how US companies exchange business documents between their systems: purchase orders (850), ship notices (856), invoices (810), payment details (820) and more. You’ll find it in retail, manufacturing, distribution, transportation and healthcare.
Do I need EDI to sell to US retailers?
Most of the time, yes. Large US retailers, distributors and marketplaces usually expect orders, ASNs and invoices to go through X12 EDI, and many charge suppliers when documents are missing, late or wrong.
Which X12 version should I use?
Whichever one your partner asks for in its companion guide. In retail and supply chain, 004010 is still very common, and US healthcare uses 005010. Some partners use other versions, so it helps to have a platform that handles several.
What’s the difference between X12 and EDIFACT?
They do the same job in different ways. X12 is mostly used in North America and names documents with numbers (850, 810). EDIFACT is mostly used in Europe and internationally and uses names (ORDERS, INVOIC). The envelope, separators and acknowledgments are different too.
I already use EDIFACT in Europe. Do I need a separate EDI provider for the US?
No. Babelway handles X12 and EDIFACT on the same platform, so you can add US partners as new channels and keep using your existing ERP connection.
Is there an e-invoicing mandate in the US?
Not at the moment. There’s no federal B2B e-invoicing mandate in the US. Trading partners set the rules, which is why the X12 810 is still the most common electronic invoice in US supply chains.
How long does it take to go live with a US partner on Babelway?
It depends partly on your partner’s testing process, but most Babelway customers build and test a standard X12 channel in anywhere from a few days to a few weeks, including the connection, mapping and checks. Because it’s self-service, your team sets the pace.
Where can I learn more before booking a demo?
Try the Babelway Product Tour, take a free course in Babelway Academy, or browse the full list of EDI X12 transaction codes.