ANSI X12

ANSI X12 is the dominant electronic data interchange (EDI) standards family for North America, covering retail, healthcare, transportation, and supply chain. Maintained by the Accredited Standards Committee X12 (ASC X12) — an ANSI-chartered, non-profit, cross-industry body — it provides the transaction-set vocabulary through which US and Canadian retailers, distributors, and their suppliers exchange structured business documents. Its three-digit numeric transaction codes (850 Purchase Order, 856 Advance Ship Notice, 810 Invoice) are the de facto compliance language mandated by every major North American retailer including Walmart, Target, Amazon Vendor Central, Home Depot, and Kroger.

Governance and version history

ASC X12 has operated under ANSI accreditation for more than 40 years. It publishes the EDI standard once per year via its Annual Release Cycle (ARC), with the most recent consolidated release being Version 008060, published February 2025 and formally announced June 3, 2026. (as-of 2026-06-03; source: x12.org 2026)

Version progression in the supply-chain domain: 4010 → 5010 → 6020 → 8010 → 8060. Retail trading-partner agreements commonly accept 4010 or 5010; newer setups default to 5010. (as-of 2026; source: Crstl.ai Walmart guide 2026, AccountableHQ) Note: intermediate versions 6020 and 8010 are referenced in vendor aggregator content; the official X12 release archive is paywalled and these were not independently confirmed from a primary ASC X12 source.

Healthcare transactions are governed differently: HIPAA mandates X12 Version 5010 for healthcare EDI (837 claims, 835 remittance, 270/271 eligibility), and any healthcare migration to 008060 requires separate federal rulemaking. Retail/supply chain version adoption is set by bilateral trading-partner agreements, not federal regulation. (Source: AccountableHQ, x12.org 2026)

ASC X12 subcommittees by domain: X12C (Communications and Controls), X12I (Transportation), X12J (Technical Assessment), X12M (Supply Chain), X12N (Insurance). (Source: x12.org 2026)

neX12 modernisation initiative

ASC X12 is running a modernisation programme called neX12, with three components: Glass (online standards viewer), Bridge (standardised, syntax-neutral X12 metadata representation), and ARC (formalised annual release cycle). Alongside this, CICA (Context Inspired Component Architecture) is being developed to modularise X12 transaction sets and make them syntax-neutral — described as the long-term architectural direction of ANSI X12. In April 2026, ASC X12 published guidance on "Using AI with X12 Standards: What's Allowed, What's Not, and Why It Matters." (Source: x12.org 2026)

Document structure

Every X12 EDI document uses a three-level envelope hierarchy:

Level	Segments	Function
Interchange	ISA / IEA	Partner addresses and interchange control numbers
Functional Group	GS / GE	Document type (e.g., functional ID "PO" for 850; "IN" for 810)
Transaction Set	ST / SE	Individual business document (the actual 850, 856, etc.)

Within a transaction set, segments are typed M (mandatory) or O (optional), and documents are structured as Header → Detail → Summary. Data elements use * as separator, segments use ~ as terminator. (Source: SEEBURGER July 2026, EDI2XML April 2025)

Key transaction sets in retail

X12 Code	Name	Direction	Core retail use
850	Purchase Order	Buyer → Seller	Item, quantity, price, ship-to, requested delivery date
855	PO Acknowledgment	Seller → Buyer	Confirms acceptance within ~24 hours of 850 receipt
856	Advance Ship Notice (ASN)	Seller → Buyer DC	Detailed carton/pallet manifest; must arrive before physical shipment
810	Invoice	Seller → Buyer	Sent after shipment; must match shipped qty (not ordered qty)
997	Functional Acknowledgment	Receiver → Sender	Syntactic receipt confirmation; closes the EDI loop for each transmission
820	Payment Order / Remittance	Buyer → Seller	EFT remittance advice
830	Delivery Forecast	Buyer → Seller	Planning-level demand signal
832	Price/Sales Catalog	Seller → Buyer	Item and pricing reference data
846	Inventory Inquiry/Advice	Either direction	Stock level sharing (required for some Walmart/Amazon programs)
860	PO Change Request	Buyer → Seller	Post-850 modification
865	PO Change Acknowledgment	Seller → Buyer	Confirmation of 860

(Source: SEEBURGER July 2026, Crstl.ai Walmart/Target/Amazon guides 2026)

Standard retail EDI flow

A full order cycle runs: 850 (PO from buyer) → 855 (PO Ack from supplier, typically within 24h) → 856 (ASN from supplier, transmitted before DC arrival; best practice: within 30 minutes of carrier pickup for Walmart) → 810 (Invoice, typically within 24h of shipment) → 997 (Functional Acknowledgment returned to sender at each step).

The 856 ASN carries GS1-compliant SSCC (Serial Shipping Container Code) for each carton. Walmart specifies a mandatory ASN hierarchy: Shipment (HL Level 1) → Order (HL Level 2) → Tare/Pack (HL Level 3) → Item (HL Level 4); incorrect HL nesting causes document rejection. (Source: Crstl.ai Walmart guide 2026 — vendor; Walmart Retail Link portal is login-gated)

Transmission protocols

X12 defines the content of EDI documents; the transport layer is separate. Three dominant transmission methods in retail (as-of 2026):

AS2 (Applicability Statement 2): Encrypted internet-based EDI, preferred by Walmart, Target, and Amazon Vendor Central. Eliminates per-transaction VAN fees; provides direct, auditable, encrypted channel. MDN receipts confirm delivery (not document processing — same caveat as EDIFACT). See AS2 (Applicability Statement 2).

VAN (Value-Added Network): Managed store-and-forward intermediary routing X12 between trading partners. Still required or accepted by many retailers; provides mailboxing, partner management, and multi-standard translation. Approved VAN lists are published by retailers (e.g., Kroger). See Value Added Network (VAN).

SFTP/FTPS: Used by some vendors and distributors; less automated than AS2; plain FTP has largely been replaced by SFTP or FTPS for security reasons. (Source: Commport 2025, Orderful 2025)

Retailer requirements (as-of 2026)

Walmart: Pioneered retail EDI, mandated supplier EDI in 1988. Required X12 version 4010 or 5010 over AS2 protocol. Core required transaction sets: 850, 855, 856, 810, 846, 860, 865, 820. OTIF (On-Time In-Full) threshold approximately 98%; failures below threshold trigger automatic chargebacks. (Source: Crstl.ai Walmart guide 2026)

Amazon Vendor Central: Required X12 version 4010 or higher (5010 now the norm). Five mandatory documents: 850, 855, 856, 810, 846. AS2 preferred; Amazon-hosted SFTP and VANs also supported. For new Direct Fulfillment integrations, Amazon now establishes via SP-API rather than traditional EDI. Recommended 2026 approach: dual-integration strategy — SP-API for real-time operations and new setups, X12 EDI for ongoing compliance workflows (ASNs, invoices, PO acknowledgments). (Source: Crstl.ai Amazon guide 2026 — vendor)

Target: X12 EDI required for all vendors. Core documents: 850, 855, 856, 810. AS2 protocol or approved VAN. All products require GS1-compliant GTINs; all cartons require SSCC-18 matching the ASN. (Source: Crstl.ai Target guide 2026 — vendor)

Chargeback risks (as-of 2026, vendor-sourced)

Violation	Reported penalty
OTIF failure	3% of affected PO value
ASN accuracy failure	$50–500 per incident
Labelling violation	$25–200 per carton
Routing violation	Freight cost difference
Packaging non-compliance	$100+ per pallet

ASN-related errors (856) are reported to account for more supplier chargebacks than any other X12 document type. (Source: Crstl.ai 2026, YouTube source agent metadata)

Implementation timeline (vendor estimates, as-of 2026)

Traditional EDI provider onboarding: 8–14 weeks (Walmart context) / 7–12 weeks (Target context). Phases: provider setup, AS2 configuration, document mapping, certification testing. (Source: Crstl.ai 2026 — EDI vendor; timelines reflect their own competitive positioning)

ANSI X12 vs EDIFACT

Dimension	ANSI X12	EDIFACT
Governing body	ASC X12 (ANSI-chartered)	UN/CEFACT
Primary region	North America (US, Canada)	Europe, Asia-Pacific, global
Code format	3-digit numeric (850, 856, 810)	6-char alphanumeric (ORDERS, DESADV, INVOIC)
Envelope	ISA/IEA → GS/GE → ST/SE	UNB/UNZ → UNG/UNE → UNH/UNT
File size	Verbose — typically 20–40% larger	Compact — suited to bandwidth-constrained networks
Regional flexibility	Low — consistent structure, minimal variation	High — supports regional customisation (tariffs, labelling)
Key security	ASC X12.58 Security Structures	ISO 9735-5/6/7/9
Primary industries	US/Canadian retail, healthcare, logistics	European retail, global automotive, international freight

Direct functional equivalents: ORDERS = 850, DESADV = 856, INVOIC = 810, ORDRSP = 855. Modern Value Added Network (VAN)|VANs translate between X12 and EDIFACT natively. (Source: Astera July 2024, BOLD VAN June 2026)

ASC X12 and GS1 describe their standards as complementary for supply chain: "The complementary use of X12 Standards and GS1 Standards enable efficiencies across the supply chain." (Source: x12.org 2026)

EDI and API coexistence (as-of 2026)

The clearest 2026 example of hybrid coexistence is Amazon Vendor Central: SP-API for real-time Direct Fulfillment operations, X12 EDI for ongoing compliance workflows (ASNs, invoices, PO acknowledgments). Stedi (API-first EDI (Electronic Data Interchange)|EDI platform) translates X12 ↔ JSON, covers 300+ transaction sets, and handles AS2 and SFTP connectivity. (Source: Crstl.ai Amazon 2026, web agent 2026)

Market indicators (as-of 2025–2026)

• EDI software market: USD 2.54 billion in 2024; projected USD 7.49 billion by 2035 (CAGR 10.33%, 2025–2035). (Source: commercial research firms — methodology undisclosed; as-of 2024)
• Retail and consumer goods: largest EDI vertical at 22.3% market share. (Source: same)
• SPS Commerce (largest North American EDI network): 300K+ trading relationships; FY2025 revenue USD 751.5 million; acquired Carbon6 Technologies in early 2025 for approximately USD 210 million. Launched MCP (Model Context Protocol) support February 2026. (Source: web agent 2026)

Key terms

Term	Meaning
ASC X12	Accredited Standards Committee X12 — ANSI-chartered body governing ANSI X12 standards
Transaction Set	An individual X12 EDI document (e.g., the 850)
ISA/IEA	Interchange envelopes — outermost X12 wrapper containing sender/receiver identifiers
GS/GE	Functional group envelopes — document type grouping within an interchange
ST/SE	Transaction set envelopes — individual document wrapper
SSCC	Serial Shipping Container Code (GS1) — required on each carton in an 856 ASN
OTIF	On-Time In-Full — Walmart's supplier scorecard metric; ~98% threshold
FA (997)	Functional Acknowledgment — syntactic receipt confirmation, not processing confirmation
ARC	Annual Release Cycle — ASC X12's yearly standard publication cadence
CICA	Context Inspired Component Architecture — X12's modular, syntax-neutral architecture initiative
neX12	ASC X12's modernisation initiative (Glass + Bridge + ARC)