ACP vs UCP vs MCP: the three protocols reshaping how AI sells your products

If you sell online and you’ve spent the last few months hearing “ACP,” “UCP,” and “MCP” thrown around like they’re the same fight, they’re not. They’re three layers of the same emerging stack: how an AI agent finds your products, how it talks to tools and data, and how it pays for what it picks. Confusing them leads to the wrong bet. Here is what each one does, who backs it, and what to do about it this week versus what to leave alone for now.

The three layers, in plain terms

Think of an AI shopping agent doing three things in sequence: it looks around (discovery), it calls tools to check facts or take actions (agent-tool access), and it completes a purchase (checkout/transaction). Each protocol was built for one of those layers, not all three.

MCP: how an agent talks to tools and data

MCP (Model Context Protocol) is an open standard from Anthropic, released in late 2024. It defines how an AI client calls tools on a server: list products, check inventory, fetch a return policy, update a cart. It’s plumbing, not a storefront and not a payment rail. MCP has since been adopted well beyond Anthropic’s own models: OpenAI, Google, and Microsoft all consume it now, and there’s an official MCP Registry for discovering servers.

For a merchant, MCP is the layer that determines whether an agent can actually interrogate your catalog with precision, structured facts, real attributes, accurate stock, instead of guessing from whatever text is on your product page.

ACP: how a product gets discovered and (sometimes) bought inside ChatGPT

ACP (Agentic Commerce Protocol) comes from OpenAI, built with Stripe, and it’s open-sourced under Apache-2.0. It launched with Instant Checkout inside ChatGPT in 2025, letting a shopper complete a purchase without leaving the chat. That feature was scaled back around March 2026. In its place, OpenAI extended ACP into a product discovery role: merchants apply through a feed-based path at chatgpt.com/merchants so their catalog can surface in ChatGPT’s shopping results.

That program is US merchants only today. Shopify and Etsy catalogs are auto-eligible; WooCommerce is not an integrated platform yet. Where checkout does happen through ACP, OpenAI takes roughly 4% of the transaction.

UCP: Google and Shopify’s shared commerce layer

UCP (Universal Commerce Protocol) is Google’s, co-developed with Shopify. It’s built to auto-surface eligible merchants directly inside Google’s AI surfaces, without a separate application step the way ACP currently requires. Checkout through UCP is gated to select markets and merchants, it isn’t universally live yet. Worth noting: AP2 (Agent Payments Protocol) is a separate Google spec for the payments handshake itself. UCP is the commerce layer; AP2 is the money-movement layer underneath it.

None of these compete for the same job. MCP is the wiring. ACP and UCP are two different companies’ answers to discovery and checkout. They stack, they don’t cancel each other out.

Where the Shopify Agentic Plan fits

Shopify’s Agentic Plan is a separate, adjacent piece: it lets brands on any platform, including WooCommerce and BigCommerce, list in Shopify Catalog and get sold through agentic storefronts. It solves the connection problem, getting your products plumbed into the agentic commerce pipes, not the data problem. Shopify Catalog auto-classifies your products into categories, but it will not write your descriptions, score your agent-readiness, or flag missing attributes an agent needs to recommend you over a competitor. That part is still on you.

What to actually do this week

Skip the temptation to chase all three at once. Here’s the honest breakdown:

• Fix your product data first, regardless of protocol. Every one of these systems reads from the same underlying catalog. Thin descriptions, missing attributes, and no structured facts will sink your visibility in ACP discovery, UCP surfacing, and any MCP tool call alike. This is the highest-leverage move and it’s protocol-agnostic.
• If you’re on Shopify, get on Shopify Catalog / the Agentic Plan. It’s the connection layer for UCP and adjacent agentic storefronts. Low effort, real upside, worth doing now.
• If you’re a US merchant on Shopify or Etsy, apply for the ACP merchant feed. You’re auto-eligible on the catalog side; the application at chatgpt.com/merchants is the gate. If you’re on WooCommerce, there’s nothing to apply to yet, it isn’t an integrated platform. Don’t build custom ACP integration work for a program that doesn’t accept your platform.
• Don’t build bespoke MCP tooling from scratch unless you have a specific reason to. The value of MCP for a merchant is having a well-structured, agent-readable surface (a public MCP server exposing your catalog, or feeding into someone else’s). If your product data is already clean, adding an MCP surface is straightforward, if it’s not, the surface will just expose the mess faster.
• Wait, don’t chase, on UCP checkout access. It’s gated to select markets and merchants right now. There’s nothing actionable to apply for broadly yet. Keep your catalog clean and your Shopify connection current so you’re ready when it opens further, but don’t spend cycles trying to force early access.
• Track AP2 separately from UCP. If a payments provider or your platform starts talking about AP2 compliance, understand that’s the money-movement handshake, not the same thing as being discoverable through UCP.

The checklist

• Audit your product data quality (descriptions, attributes, structured facts) before touching any protocol integration.
• Shopify merchants: enable Shopify Catalog / Agentic Plan for the connection layer.
• US Shopify or Etsy merchants: apply at chatgpt.com/merchants for ACP discovery.
• WooCommerce merchants: hold on ACP, it isn’t integrated yet; focus effort on data quality and MCP readiness instead.
• Expose a clean, structured MCP surface once your catalog data is actually good, not before.
• Leave UCP checkout access alone until Google/Shopify widen eligibility; there’s no application to make yet.

The pattern underneath all three protocols is the same: the pipes are being built by people much bigger than any single merchant, and fast. The part that stays yours to control, the thing no protocol solves for you, is whether the data flowing through those pipes is good enough for an agent to recommend you.