← Back to Blog

UCP vs ACP: The Two Agentic Commerce Protocols, Compared

Quick Answer: ACP and UCP are the two competing agentic commerce protocols shaping how AI agents buy from online stores. OpenAI and Stripe announced ACP on September 29, 2025; Google launched UCP on January 11, 2026 with more than 20 companies including Shopify and Visa. UCP covers six commerce domains while ACP focuses on checkout. OpenAI dropped in-chat Instant Checkout in March 2026, moving purchases back to merchants’ sites. Both protocols demand clean, machine-readable product data — the real preparation is the same regardless of which protocol wins.

What is the difference between UCP and ACP?

ACP is OpenAI and Stripe’s agent-led checkout for ChatGPT, while UCP is Google’s broader standard for many agents and surfaces to talk to merchants. The two protocols emerged within four months of each other — ACP on September 29, 2025 and UCP on January 11, 2026 (Search Engine Journal, 2026; Search Engine Land, 2026) — and they solve the same core problem from different directions: how does an AI agent complete a purchase on a customer’s behalf?

ACP was built to let ChatGPT handle the checkout step. A customer asks the agent to buy something, the agent talks to the merchant’s Stripe integration, and the transaction closes inside the chat. UCP takes a wider view. Instead of focusing on one step, it defines how agents interact with merchants across six commerce domains: discovery, checkout, discounts, fulfillment, order management, and payments (Search Engine Journal, 2026). That means UCP isn’t just a checkout protocol — it’s attempting to standardise the full lifecycle of an agent-driven transaction.

Here’s the thing… the distinction matters because it shapes what a store has to build. An ACP integration wires up one step. A UCP integration means exposing structured data across every stage of the customer journey — and that’s a fundamentally different infrastructure commitment.

UCP covers six commerce domains — discovery, checkout, discounts, fulfillment, order management, and payments — while ACP focuses on the checkout step alone (Search Engine Journal, 2026).

Who built ACP and when?

OpenAI and Stripe announced ACP on September 29, 2025 as an open standard for agent-driven purchases (Search Engine Journal, 2026). The protocol was designed around a specific workflow: a customer tells ChatGPT what they want, the agent finds the product, and Stripe processes the payment without the customer ever leaving the conversation.

That “Instant Checkout” model was ACP’s headline feature and its biggest bet. By keeping the entire transaction inside ChatGPT, OpenAI positioned ACP as a frictionless alternative to traditional e-commerce — no redirects, no abandoned carts, no slow-loading checkout pages. For store owners already using Stripe, the integration path was relatively short: connect your Stripe account, map your product catalogue, and the agent handles the rest.

The open-standard framing was deliberate. OpenAI published ACP’s specification publicly, inviting other agent platforms to adopt it. Whether that openness translates to multi-platform adoption is another question — one that UCP’s arrival made considerably more complicated.

Related: How Stripe joined Google’s UCP Tech Council just ten days after WooCommerce shipped ACP

Who built UCP and when?

Google launched UCP on January 11, 2026 with partners including Shopify, Etsy, Wayfair, and Target (Search Engine Land, 2026). Where ACP arrived as a two-company initiative, UCP landed with an industry coalition already in place — a signal that Google had been building consensus behind the scenes while ACP was still finding its footing.

The partner list tells a story. More than 20 companies across retail and payments endorsed UCP at launch, including Visa and American Express (Search Engine Land, 2026). That’s not a single-vendor play. When payment networks, marketplaces, and major retailers all endorse the same protocol on day one, the message is clear: this is intended to be the default, not an option.

For WooCommerce store owners, UCP’s launch created a practical question. Shopify got native UCP support as a launch partner. WooCommerce didn’t. That infrastructure gap means WordPress-based stores need to build their own UCP compliance — or find tools that do it for them.

Which protocol covers more of the journey?

UCP spans discovery, checkout, discounts, fulfillment, order management, and payments — a wider scope than ACP’s checkout focus (Search Engine Journal, 2026). Translation: ACP lets an agent complete a sale. UCP lets an agent find the product, apply a coupon, buy it, track the shipment, and handle a return — all through structured APIs.

That breadth is both UCP’s strength and its complexity. A store that fully implements UCP exposes its entire operation to agent interaction, which means agents can answer post-purchase questions (“where’s my order?”), process discount codes, and manage returns without the customer ever opening the store’s website. ACP doesn’t touch any of that. Its scope ends at payment confirmation.

DomainUCPACP
Product discoveryYes — structured catalogue exposureLimited — relies on agent’s own search
CheckoutYesYes — core focus
Discounts and promotionsYes — machine-readable offersNo
Fulfillment trackingYesNo
Order managementYes — returns, cancellationsNo
Payment processingYes — multi-providerYes — Stripe

The question isn’t which protocol does more. The question is which commerce interactions you want agents to handle. If the answer is “just checkout,” ACP’s narrower scope is simpler. If it’s “the whole journey,” UCP is the only current option.

How broad is UCP’s backing?

More than 20 companies across retail and payments endorsed UCP, including Visa and American Express (Search Engine Land, 2026). The coalition spans platforms (Shopify, Etsy), retailers (Target, Wayfair), and payment networks — the kind of cross-industry alignment that typically precedes a de facto standard.

ACP’s backing is narrower. OpenAI and Stripe are the primary sponsors, with adoption concentrated among merchants already in the Stripe ecosystem. That’s not a weakness — Stripe processes payments for millions of businesses — but it’s a different kind of support. ACP’s adoption is organic and merchant-by-merchant. UCP’s is institutional and top-down.

The inflection point came when Stripe itself joined Google’s UCP Tech Council, barely ten days after WooCommerce shipped its first ACP integration. When the payment processor behind one protocol endorses the other, the competitive landscape shifts. It doesn’t mean ACP is dead — but it does mean the company processing ACP’s payments sees UCP as the bigger opportunity.

Related: Why WooCommerce stores now need to publish both UCP and ACP

Did ACP’s in-chat checkout last?

No — OpenAI dropped in-chat Instant Checkout in March 2026 and moved purchases back to merchants’ own sites (Search Engine Journal, 2026). The feature that defined ACP’s launch — completing a transaction without leaving ChatGPT — lasted roughly five months before OpenAI reversed course.

The pivot wasn’t a failure of the protocol itself. It was a recognition that in-chat checkout created liability and trust problems that outweighed the convenience. Customers wanted to see the merchant’s own checkout page. Merchants wanted control over the purchase experience. And the compliance questions around an intermediary holding payment credentials were mounting.

Let that sink in. The headline feature of one of the two agentic commerce protocols was live for less than half a year. What remains is still functional — ACP can initiate and coordinate a purchase — but the transaction now completes on the merchant’s site, which makes the end-user experience closer to UCP’s model than ACP’s original pitch.

OpenAI dropped ACP’s in-chat Instant Checkout in March 2026, moving purchases back to merchants’ own checkout pages (Search Engine Journal, 2026).

Do I have to choose one protocol?

Not necessarily — the guidance is to be transactable through at least one protocol rather than bet everything on one ecosystem (Search Engine Journal, 2026). In practice, the protocols aren’t mutually exclusive. A store can publish UCP-compliant structured data for Google’s surfaces and maintain an ACP integration for ChatGPT without architectural conflict, because the underlying data requirements overlap heavily.

The real risk isn’t choosing the wrong protocol. It’s choosing neither. A store with no machine-readable commerce data is invisible to every AI shopping agent regardless of which protocol those agents use. The preparation work — clean product feeds, structured pricing, accurate availability — is the same for both.

For WooCommerce stores specifically, the practical path is to get the data infrastructure right first and then layer protocol-specific integrations on top. Both protocols demand clean, complete, machine-readable product data because agents read feeds and APIs, not web pages (Search Engine Journal, 2026). If your product data is structured, adding protocol compliance is configuration. If it isn’t, neither protocol can help you.

LIFETIME LOCK on Harvest Annual Plan

Push your WordPress event data server-side seamlessly into BigQuery so AI can analyse it.

Let's Do It !

What do both protocols demand from a store?

Both protocols demand clean, complete, machine-readable product data, because agents read feeds and APIs, not pages (Search Engine Journal, 2026). That’s the unsexy answer, but it’s the correct one. The protocol-level differences between UCP and ACP matter less to a store owner than whether the store’s product data is accurate, structured, and accessible in the first place.

Here’s what “machine-readable” means in practice: every product needs a unique identifier, an accurate price that updates in real time, a current availability status, a structured description (not just marketing copy), and clean category taxonomy. If any of those are missing or stale, an agent either skips the product or shows the customer wrong information — and wrong information in an agent-driven transaction creates returns, chargebacks, and trust damage.

The stores that are ready for agentic commerce aren’t the ones that picked the right protocol first. They’re the ones that got their data infrastructure right — and protocol compliance followed as a configuration step, not a rebuild.

Is UCP the same as Google Merchant Center?

No, but they overlap significantly. UCP is a broader protocol that standardises how AI agents interact with merchants across the full commerce journey, while Google Merchant Center is one surface that consumes UCP data. Think of Merchant Center as one door into the Google commerce ecosystem — UCP is the hallway that connects all the doors.

UCP extends well beyond what Merchant Center handles today. Where Merchant Center focuses on product listings and Shopping ads, UCP adds fulfillment tracking, order management, discount APIs, and multi-agent discovery (Search Engine Journal, 2026). A store that’s compliant with Merchant Center has a head start on UCP, but it isn’t automatically UCP-ready — the post-purchase and operational APIs are new ground.

What happens to stores that ignore both protocols?

Stores that publish no machine-readable commerce data become invisible to AI shopping agents. It’s not a penalty — it’s an absence. When a customer asks an AI agent to find a product, the agent queries structured feeds and APIs. A store that doesn’t publish those feeds simply doesn’t exist in the agent’s search space, regardless of how strong its website SEO might be.

The risk compounds over time. As more purchase decisions route through AI surfaces — voice assistants, chat agents, comparison tools — an unstructured store loses a growing share of transactions it would have captured through traditional search. The gap between stores with machine-readable data and those without widens with every new agent surface that launches (Search Engine Journal, 2026).

Related: What is the Unified Commerce Protocol (UCP) and does WooCommerce need to publish it for Microsoft Copilot?

LIFETIME LOCK on Harvest Annual Plan

Push your WordPress event data server-side seamlessly into BigQuery so AI can analyse it.

Start NOW !

Key Takeaways

  • Two protocols, one prerequisite: UCP (Google, January 2026) and ACP (OpenAI/Stripe, September 2025) both require clean, machine-readable product data.
  • UCP covers 6 commerce domains; ACP focuses on checkout — the scope difference shapes what a store must expose to agents.
  • 20+ companies back UCP including Shopify, Visa, and American Express — institutional support that positions it as the emerging default.
  • ACP’s in-chat checkout lasted 5 months: OpenAI dropped Instant Checkout in March 2026, moving transactions back to merchant sites.
  • You don’t have to choose one: the protocols aren’t mutually exclusive, and the data-readiness work is the same for both.
What is the difference between UCP and ACP?

ACP is OpenAI and Stripe’s agent-led checkout protocol for ChatGPT, launched September 29, 2025. UCP is Google’s broader standard launched January 11, 2026, covering discovery, checkout, discounts, fulfillment, order management, and payments across many agents and surfaces. ACP focuses on the checkout step; UCP aims to standardise the entire commerce journey.

Who built ACP and when?

OpenAI and Stripe announced the Agentic Commerce Protocol on September 29, 2025 as an open standard for agent-driven purchases. It was designed to let AI agents handle checkout on behalf of customers inside ChatGPT, with Stripe processing the payments.

Who built UCP and when?

Google launched the Universal Commerce Protocol on January 11, 2026 with partners including Shopify, Etsy, Wayfair, and Target. More than 20 companies across retail and payments endorsed it at launch, including Visa and American Express.

Which protocol covers more of the journey?

UCP covers six commerce domains: discovery, checkout, discounts, fulfillment, order management, and payments. ACP focuses primarily on the checkout step. That makes UCP the broader protocol, though ACP’s narrower scope gave it a faster initial implementation path for stores already using Stripe.

How broad is UCP’s backing?

More than 20 companies endorsed UCP at launch, spanning retail and payments. The list includes Shopify, Etsy, Wayfair, Target, Visa, and American Express. This cross-industry support suggests UCP is positioning itself as the default standard rather than one vendor’s proprietary channel.

Did ACP’s in-chat checkout last?

No. OpenAI dropped in-chat Instant Checkout in March 2026 and moved purchases back to merchants’ own sites. That pivot means ACP no longer completes transactions inside ChatGPT — it now redirects to the merchant’s checkout, which narrows the gap between the two protocols’ end-user experience.

Do I have to choose one protocol?

Not necessarily. The practical guidance is to be transactable through at least one protocol rather than betting everything on a single ecosystem. Supporting both is possible and, for stores selling through multiple AI surfaces, increasingly advisable — especially since both share the same data-readiness requirements.

What do both protocols demand from a store?

Both protocols demand clean, complete, machine-readable product data. AI agents read feeds and APIs, not web pages, so structured data — accurate prices, availability, descriptions, and identifiers — is the common prerequisite regardless of which protocol a store adopts.

Is UCP the same as Google Merchant Center?

No, but they overlap. UCP is a broader protocol that standardises how AI agents interact with merchants across the full commerce journey. Google Merchant Center is one surface that can consume UCP data. UCP extends beyond Merchant Center to cover fulfillment, order management, and multi-agent discovery.

What happens to stores that ignore both protocols?

Stores that publish no machine-readable commerce data become invisible to AI shopping agents. As more purchases route through AI surfaces, an unstructured store loses the transactions those agents would have sent — not because the store is penalised, but because the agent simply cannot read it.

References

  1. Search Engine Journal (2026). Agentic commerce: what SEOs need to consider — ACP & UCP. Source
  2. Search Engine Land (2026). Google launches Universal Commerce Protocol. Source
  3. Search Engine Journal (2026). Fix AI shopping errors. Source
  4. Search Engine Journal (2026). Surviving the impression squeeze: how agentic commerce is changing Google Ads. Source
  5. Search Engine Journal (2026). Agentic commerce and the new rules of Google Ads. Source