Kontext
EN ES Let's talk
EDI

ANSI X12: the telegram that never died (the EDI language of the Americas)

What ANSI X12 is, explained simply: the EDI syntax that dominates commerce across the Americas, how to read its segments and elements (ST, BEG, PO1), what the numbers 850, 856 and 810 mean, and why a format designed for 1980s computers still rules retail.

Jul 11, 2026 · Greicodex Software · 4 min read

ANSI X12: the telegram that never died (the EDI language of the Americas)

An IT manager at a Venezuelan distributor gets her first EDI requirement from a retail chain. She opens the test file they sent, expecting something like a PDF or a spreadsheet, and finds this:

ST*850*0001~
BEG*00*SA*4471**20260717~
PO1*1*40*CA*12.50**EN*7591234567890~

Her first reaction is everyone’s first reaction: “this file is corrupted.” It isn’t. It’s written in X12, the language commercial electronic documents are written in across most of the Americas. And although it looks like hieroglyphics, in ten minutes you’ll be able to read it.

What is X12, in one sentence?

ANSI X12 is an EDI syntax: the set of rules that defines how a purchase order, an invoice or a ship notice is written so that another company’s computer understands it with no human help. ANSI is the United States standards institute; X12 is the committee that created these rules in 1979 and maintains them to this day.

Watch out for a distinction that trips everybody up: the syntax is the language of the document, not the medium it travels on. The transport — the certified envelope — is a different standard: AS2 and friends, which we covered earlier in this series. X12 can travel over AS2 the way a letter in Spanish or English can travel in the same envelope. They are two separate decisions, and your customer will require both.

The metaphor: a telegram

Why does X12 look so cryptic? Because it is, quite literally, a telegram. When it was designed, transmitting data cost a fortune and computers had less memory than your watch does today. So the designers did what people did with telegrams: abbreviate everything, strip the padding, and agree in advance on what each position means.

  • Each line is a segment: one “sentence” of the document. ST says “a document starts here.” BEG says “here is the order header.” PO1 says “here is a line item: product and quantity.”
  • Inside each segment, values are separated by asterisks: those are the elements. In the PO1 above: line 1, 40 units, in cases (CA), at 12.50, identified by its EAN barcode.
  • Nothing carries a label (“quantity:”, “price:”). Meaning comes from position, just as a telegram’s convention might be that the third word is the date.

Abbreviated, positional, not one wasted byte: built for 1980s computers. So why is it still alive in 2026? For the most boring and most powerful reason in the world: it works. Millions of documents a day, forty years of systems that speak it, and zero incentive to break what isn’t broken. X12 is the telegram that never died.

The numbers: 850, 856, 810

In X12, documents don’t have names — they have numbers. The three you’ll meet first:

  • 850 — the purchase order: your customer tells you what they want.
  • 856 — the advance ship notice or ASN: you announce what’s on the truck (we covered it in full here).
  • 810 — the electronic invoice: you get paid.

That trio is the basic cycle: order, ship, bill. Around it orbit others we’ve already covered in this series: the 830 demand forecast and the 832 electronic catalog. So when your customer says “we need you to receive the 850 and return 856 and 810,” you’ll know they’re asking for the full cycle — not three separate projects.

Where does X12 rule?

North America, no contest: retail, pharma, automotive, healthcare, ground transportation. And by commercial inheritance, retail across most of the Americas: chains in Colombia, Panama, Mexico — and Venezuela — built their systems on North American practice, and that practice speaks X12. If your customer is a supermarket chain, a pharmacy chain or a department store on this continent, the file they ask you for will most likely be X12.

And the rest of the world? Europe, ocean carriers and customs authorities speak another language of the same family: EDIFACT, the United Nations standard. We dedicate the next article in this series to it, because if you export, you will run into it — guaranteed.

Common myths

  • “That’s obsolete technology.” Obsolete is what nobody uses anymore. X12 moves more commerce today than any fashionable API. Old is not the same as dead.
  • “We’ll have to learn to read that by hand.” No. That’s what EDI translators are for: software that converts X12 into whatever your system understands, and back. You need to understand the concept, not memorize segments.
  • “We’ll just send them a modern JSON instead.” The buyer decides, not you. If the chain asks for an 850, the right answer isn’t to argue about the format — it’s to have someone who translates it.

X12 is the language; the business is in speaking it without your team having to learn it. If you’d like to see how your current system can receive an 850 and answer with an 856 and an 810 with zero rekeying, take a look at our solutions or get in touch.

← Back