Back to Blog
AI CommerceApril 17, 20264 min read · 956 words

Agentic Commerce Protocols: ACP, MCP, UCP

N7

No7 Engineering Team

Growth Architecture Unit

AI Commerce — Agentic Commerce Protocols: ACP, MCP, UCP — illustration

Three years ago, "agentic commerce" was a keynote slide. In April 2026 it is a shipping feature on Shopify Plus — and three separate open standards now mediate how AI agents discover products, get the right context, and complete purchases on behalf of buyers. This post is the plain-English map of what each protocol is, who owns it, and what a merchant should actually wire up.

The Three Protocols That Matter

Landscape as of April 2026

ACP

Agentic Commerce Protocol

Maintained by OpenAI and Stripe. Connects buyers and their AI agents to merchants so the agent can complete a checkout inside ChatGPT. Powers ChatGPT Instant Checkout.

MCP

Model Context Protocol

Maintained by Anthropic and a growing open consortium. Lets any AI agent call tools and read data from any compliant server. Shopify now ships four MCP servers: Dev, Storefront, Customer Account, Checkout.

UCP

Universal Commerce Protocol

Announced by Google and Shopify at NRF in January 2026. Standardises how AI agents discover merchants, search catalogues, and transact. Endorsed by 20+ retailers and platforms out of the gate.

ACP — OpenAI and Stripe

ACP is narrow on purpose. It answers one question: "How does an AI agent complete a purchase on a specific merchant?" The spec covers capability negotiation (what can this merchant accept?), order handoff, fulfilment feedback, and a handful of payment primitives that lean on Stripe's existing payment surface. It is the protocol behind Buy it in ChatGPT.

For Shopify merchants on Plus, ACP is already plumbed in through Shopify Catalog + Shopify's Agentic Storefronts channel — you do not implement ACP directly. For merchants on custom or non-Shopify platforms, the GitHub repo (agentic-commerce-protocol) has a reference server you can wrap your order API around.

MCP — Model Context Protocol

MCP is the general-purpose protocol. Originally shipped by Anthropic in November 2024, it has become the de-facto interface for giving AI agents structured access to any tool or data source. Shopify's engineering team shipped four specialised MCP servers in Q1 2026:

  • Storefront MCP — product search, variant details, collections, pricing, inventory snapshot.
  • Customer Account MCP — authenticated customer actions: order history, saved addresses, loyalty balance.
  • Checkout MCP — cart lifecycle, shipping quotes, tax estimation, order creation.
  • Dev MCP — for developers building on Shopify — CLI + documentation + code snippets accessible from inside Cursor, Claude Code, and similar tools.

The Storefront MCP is the one that matters for agentic discovery. Any agent that speaks MCP — ChatGPT, Claude, Copilot, Gemini (via adapters), and every enterprise agent built on top of Claude/OpenAI/Google APIs — can plug into a Shopify store in minutes rather than building a bespoke integration.

UCP — Universal Commerce Protocol

UCP is the newest and the most ambitious. Google and Shopify announced it at NRF 2026 as a "single open standard for agent-to-merchant commerce." It is explicitly positioned above ACP and MCP: UCP specifies how agents discover merchants in the first place (via a federated registry), how they authenticate, how they exchange structured product intent, and how they negotiate fulfilment.

In practice, UCP-compatible merchants are discoverable by Google's AI Mode, Gemini, and any other agent that ingests Google's index. Shopify Plus merchants inherit UCP support through Shopify Catalog. BigCommerce has committed to UCP support by Q3 2026; other platforms are in varying stages.

How They Fit Together

  • UCP — Discovery layer. "Which merchant should I buy from?"
  • MCP — Context layer. "What does this merchant sell, at what price, with what inventory?"
  • ACP — Checkout layer. "Complete the purchase on behalf of the buyer."

In an end-to-end agentic purchase on Shopify Plus today: UCP surfaces your merchant profile to the agent, MCP provides the structured catalogue and cart operations, ACP finalises payment and order creation. On non-Shopify platforms, the three are usually stitched together with more glue.

What Merchants Should Actually Do

Ranked by ROI in April 2026:

  1. Complete your Shopify metafields and Google Merchant feed. All three protocols are only as good as the structured product data underneath them. This is 80% of the work.
  2. Enable Shopify Agentic Storefronts. It is a one-click switch in Plus admin. Activates the ACP + MCP + UCP channel without any custom code.
  3. Verify your Shopify MCP endpoints work. Test from Claude Desktop or Cursor with the official Shopify MCP config. If tests fail, fix your permissions before chasing any other integration.
  4. Do not build custom ACP or MCP servers until Shopify's native coverage is exhausted. 95% of merchants do not need bespoke servers — you need better product data.
  5. Monitor agent-sourced orders as a distinct channel. Tag them channel = Agentic in order segmentation so you can track citation share and conversion separately from direct traffic.

Protocol Fragmentation is Real

There are at least eight competing standards in this space, including Visa TAP, Mastercard Agent Pay, and Klarna's Agentic Product Protocol. Most will not survive. ACP, MCP, and UCP are the ones that actually have agent-side adoption today — so they are the ones worth building around. We revisit this list every quarter because the picture is moving fast.

Implementation reading: how GPT-5.5 changes the agentic checkout surface, what ChatGPT workspace agents mean for commerce, enabling Shopify's four native MCP servers, scaling MCP in production, optimising for ChatGPT and Perplexity Shopping, and what AI search actually moves the needle on real merchants. For multi-channel reach beyond AI agents, see TikTok Shop integration patterns and Markets vs multi-store for international, and browse our full AI Commerce & Agentic Search coverage. Engineering baseline: run our free AI visibility tool to see whether ACP, MCP, and UCP-aware agents can actually discover and cite your domain — the protocols only matter if the technical signals are in place first.

Frequently Asked Questions

The questions buyers and engineers ask us most about this topic.

What is the difference between ACP, MCP, and UCP?

They sit at different layers. UCP (Universal Commerce Protocol, Google + Shopify) is the discovery layer — how AI agents find merchants. MCP (Model Context Protocol, Anthropic) is the context layer — how agents read structured product, customer, and cart data. ACP (Agentic Commerce Protocol, OpenAI + Stripe) is the checkout layer — how agents complete a purchase on behalf of a buyer. A real agentic transaction usually touches all three.

Do Shopify merchants need to implement these protocols themselves?

For most Shopify Plus merchants, no. Shopify ships the protocol plumbing through its native Agentic Storefronts channel and four MCP servers (Storefront, Customer Account, Checkout, Dev). Merchants enable Agentic Storefronts in admin and inherit ACP, MCP, and UCP support without custom code. Custom MCP servers are only worth building when you need to expose proprietary data (loyalty, B2B catalogues, custom config) that Shopify’s native servers do not cover.

How do I track orders that come from AI agents?

Shopify exposes the source channel in the order payload. Tag agentic orders with channel = Agentic in your reporting layer to track citation share, conversion rate, and AOV separately from direct or paid traffic. Most merchants we audit are not yet doing this and are blind to whether agentic traffic is converting better or worse than other channels.

Working on this? Send us the details — we'll take a look.