X12 Moves Its EDI Standard From 008 to 009
ASC X12's EDI Standard jumps from version 008 to 009 in January 2027. Here's what the version bump changes for trading partner agreements and testing.
ASC X12 closed the last ballot window for inclusion in version 009010 on November 18, 2026, with the next annual publication expected in January 2027, according to X12's own release schedule. If you manage EDI for a manufacturer, retailer, or carrier network, this is the version jump that matters more than the ones you've been quietly absorbing every January for the last several years.
This is not the same event as last year's routine bump from 008070 to 008080. That was a release-level change, the kind X12 ships every twelve months. The move to EDI standard version 009010 is a version-level change, and those happen far less often.
Why the version digit changed, not just the release digit
X12 uses a six-digit identifier for every publication of the EDI Standard. X12 explains it plainly: Each publication of X12's EDI Standard is enumerated with a six-digit identifier indicating the version, release. The first three digits are the version which spans a number of calendar years. The fourth and fifth digits are the release. If you've only ever worked with 004010 or 005010, that's the pattern you already know, just further along the number line.
The release digits increment every year. The version digits don't. At roughly 5 to 7 year intervals, X12's EDI Standard is vetted through a process maintained by the American National Standards Institute (ANSI), and when ANSI approves, the EDI Standard's version number is incremented. That ANSI re-approval is the trigger, and it's a different process than the routine annual maintenance ballots that produce 008070, 008080, and so on. The ANSI approved version is identified with a release of 00, thereafter the release is incremented each calendar year.
For context on how long a version typically runs: 008010 was approved for ASC Stakeholder Ballot in October 2019 and became available in Glass in January 2020, with the underlying 008000 base approved by ANSI in 2020. That means version 008 has carried the standard from 2020 through the 008080 release cycle that this blog has already tracked. Version 009010 represents the next full ANSI cycle, not another incremental patch. X12 has also been running a separate consensus process this year for the underlying 009000 proposal, with a notice posted in August 2026 noting that X12 is forming the consensus body that will vote on the Version 009000 proposal.
Key dates to put on your calendar
- November 18, 2026 — last ballot period for inclusion in version 009010 begins, per X12's published schedule
- Through early December 2026 — Batch 141 member review and final subcommittee comment periods run
- January 2027 — expected publication, since the EDI Standard is published once per year, usually in January
- 12 to 36+ months after that — realistic window before most trading partners request or mandate 009010 in production, based on how slowly 005010 adoption actually spread
What this does, and doesn't, change for your EDI operation
Nothing breaks on your VAN tomorrow. A new base version doesn't force anyone off 004010 or 005010 overnight. Unlike the HIPAA-mandated transaction sets in healthcare, adoption of a new X12 version in supply chain and transportation EDI is bilateral and contractual. Your trading partner agreements still govern what version you actually exchange, and most of the industry will keep running 005010-era transaction sets for years after 009010 exists on paper.
Where it does matter is in the plumbing. Your translator's handling of ISA15 and GS08 version qualifiers needs to recognize 009010 as a valid string once partners start referencing it, whether you're on Cleo, Boomi, SPS Commerce, TrueCommerce, OpenText, or IBM Sterling. A partner who jumps ahead unilaterally and sends a 009010-flagged envelope against a mapping built for 008010 is a 999 or 864 rejection waiting to happen. Check your VAN and AS2 partner profiles now, not after the first rejected interchange shows up in your error queue.
Transportation sets feel this first
For this blog's readers running 204 load tenders, 214 status messages, 990 responses, and 210 freight invoices, the practical question is whether your TMS or carrier-connectivity platform has confirmed compatibility before certifying anything against 009010. MercuryGate, Descartes, Transporeon, Alpega, Oracle TM, SAP TM, Blue Yonder, and multi-carrier tools from ShippyPro to EasyPost will each move on their own timeline. Shippers using multi-carrier platforms, including newer carrier-connectivity tools like Cargoson, should ask their provider directly for a 009010 roadmap rather than assume silent compatibility somewhere down the line.
What to actually do before January
- Ask your VAN or translator vendor for their written 009010 support timeline, not a verbal "we'll handle it."
- Check whether any trading partner's 2027 onboarding kit already references 009010 as a requirement.
- Re-test your 999 and 864 rejection logic against an unexpected version qualifier to confirm it fails gracefully instead of silently.
- Add a version-change clause to any trading partner agreement coming up for renewal in the next year.
The real deadline here isn't January 2027. It's whenever your first trading partner emails you asking to test against 009010. For most of you, that's still a while off. For a few of you, especially in automotive and parts-heavy manufacturing supply chains that move fast on new ANSI versions, it could be sooner than you think.