What is Order Network eXchange?
The shift to agentic commerce
The way people shop is moving into AI. Discovery, comparison, checkout, and even post-purchase monitoring increasingly happen inside AI assistants rather than on a search results page or a brand's own site. This isn't a fringe behavior: 73% of consumers are already using AI in their shopping journey. And the money is following — Accenture estimates that by 2030, more than 30% of online commerce will run through AI agents, close to $3.1 trillion in transactions.
From scraping to brand-controlled protocols
Until now, AI assistants learned about products by scraping the open web – guessing at prices, availability, and specs from whatever pages they could read.
That era is ending.
Brands and the platforms behind these assistants are converging on agentic-commerce protocols: structured, brand-published feeds and endpoints that tell an AI exactly what you sell, what it costs, whether it's in stock, and how to complete a purchase. The difference is control – the brand, not a scraper, becomes the source of truth.
The catch is pace. Several of these protocols have emerged in just the last year, each backed by different platforms, and they ship new releases frequently. Staying compliant is an ongoing commitment, not a one-time integration. And each protocol takes a different approach.
What is ONX?
ONX – the Order Network eXchange – is an open standard for exchanging order and fulfillment data across commerce systems, so that AI agents and the systems behind them can move an order from capture through delivery without bespoke, point-to-point integrations. To quote the ONX spec, it provides "a common language for selling channels to speak with fulfillment channels."
This is the supply-chain and order-operations layer of agentic commerce. Where other protocols help an agent discover products and check out, ONX is what happens after the buy button: creating the order, checking live inventory, triggering fulfillment, tracking shipments, and handling returns. Today every player in that chain — brands, platforms, OMS and WMS vendors, ERPs, and 3PLs — speaks a different dialect. ONX replaces those fragile, duplicated connections with one shared interface.
Built on MCP
ONX runs on top of the Model Context Protocol. An ONX server is an MCP server that exposes a standardized set of fulfillment and order-operations tools — actions like creating, updating, and cancelling orders, fulfilling orders, and creating returns, alongside queries for orders, customers, products, product variants, inventory, fulfillments, and returns. Because it's MCP underneath, an AI assistant that already speaks MCP can interact with any compliant fulfillment system through the same well-described tool surface, rather than learning a new API per vendor.
Who's behind it
ONX is stewarded by the Commerce Operations Foundation, a vendor-neutral body operating under open governance – no single company controls the standard. The foundation lists a broad set of supporting organizations across the order lifecycle, spanning order-management and fulfillment vendors including Manhattan Associates, IBM Sterling, and ShipHero; commerce platforms such as commercetools, Shopware, and osa; 3PLs such as Ryder, Quiet, Radial; and brands including IPSY and Logitech.
Where it fits
ONX is fundamentally a supply-chain-data problem dressed up as a protocol: the hard part isn't the tool definitions, it's mapping your real order, inventory, and fulfillment data onto them and keeping that mapping correct as the spec evolves. That work usually means changes deep in fulfillment, IT, and operations.
You can run a completely free check to see how your brand measures up against the published ONX spec right now. And if you'd rather skip the technical implementation entirely, CorgiMaps connects to your existing order and fulfillment data to expose a compliant ONX surface – and keeps it current as the standard changes – with no changes to your fulfillment stack or operations.