UCP vs ACP in 2026: Google and OpenAI Competing Visions for Agentic Commerce

Two Protocols, Two Philosophies

In early 2026, agentic commerce has two serious protocol contenders: UCP (Universal Commerce Protocol), co-developed by Shopify and Google, and ACP (Agent Commerce Protocol), developed by Amazon. Both promise to let AI agents browse products, initiate checkouts, and complete purchases without human hand-holding. But they take almost opposite approaches to the problem, and the distinction matters enormously for merchants, developers, and the long-term shape of e-commerce.

This post breaks down exactly where the two protocols differ, which AI labs are aligning with which, and what the strategic implications look like heading into the second half of 2026.

Design Philosophy: Open vs. Integrated

The most fundamental difference is not technical. It is philosophical.

UCP is designed as an open, federated protocol. The goal is a common language that any merchant, any agent, and any payment processor can speak without being inside a particular company's ecosystem. Shopify provides the reference implementation and most of the merchant volume, but a retailer running a custom commerce stack can implement UCP independently. No partnership agreement required, no rev-share, no dependency on a single gatekeeper.

ACP is designed as a tightly integrated system within Amazon's ecosystem. It works excellently within Amazon's marketplace, and Amazon has opened parts of the spec to external retailers, but the model is hub-and-spoke rather than peer-to-peer. Amazon sits at the center, routing agent requests, enforcing policies, and handling fulfillment coordination. The trade-off is a more polished, higher-reliability experience inside the Amazon world at the cost of openness outside it.

Neither model is inherently wrong. They reflect different theories about how trust and quality get enforced in a world where AI agents are making purchases on behalf of real people.

Technical Architecture

UCP is built on standard web primitives. Merchants expose a /.well-known/ucp manifest at their domain root, which declares their supported capabilities, API endpoints, supported payment processors, and identity requirements. The manifest is plain JSON, publicly discoverable by any agent or crawler.

An example manifest looks like this:

{
  "ucp_version": "1.2",
  "merchant_id": "shopify:example-store",
  "capabilities": ["discovery", "checkout", "order_management", "identity_linking"],
  "endpoints": {
    "discovery": "https://example-store.com/ucp/v1/discovery",
    "checkout": "https://example-store.com/ucp/v1/checkout",
    "orders": "https://example-store.com/ucp/v1/orders"
  },
  "payment_processors": ["stripe", "shopify_payments", "adyen"],
  "identity_providers": ["google", "shopify_identity"]
}

Agent interactions are RESTful, use standard OAuth 2.0 scoped token flows for identity and authorization, and are JSON throughout. There is no proprietary SDK required on the agent side. If your agent can make HTTP requests and handle JSON, it can implement UCP.

ACP uses Amazon's existing API infrastructure. Agent interactions go through Amazon's Alexa Skills Kit or the newer ACP Gateway, which provides a centralized routing layer. Authentication is Amazon account-based rather than OAuth-federated. Payment handling routes exclusively through Amazon Pay. The agent experience is polished and consistent, but it requires registration and approval from Amazon to access production endpoints.

Merchant Reach

This is where UCP has a structural advantage that is hard to overstate.

Shopify powers roughly 15% of all U.S. e-commerce by revenue. More importantly, it powers the long tail: hundreds of thousands of independent brands, niche retailers, and DTC operators. For all Shopify merchants on Plus, Advanced, or Basic plans, UCP is a toggle in the admin panel. The addressable merchant count for UCP starts at a very large number.

The March 2026 expansion of the UCP ecosystem added Salesforce Commerce Cloud as a native UCP platform, which brings enterprise and mid-market brands into the protocol alongside Shopify's long tail. The UCPList directory now tracks over 140 verified UCP-enabled implementations across merchants, platforms, SDKs, and agent integrations.

ACP's merchant reach is centered on the Amazon marketplace, which is massive but represents a specific type of retailing. Third-party marketplace sellers are well-served by ACP. Brands with their own storefronts need to implement an Amazon Pay integration and register with the ACP program separately.

Payment Handling

UCP supports any payment processor that implements the UCP token exchange specification. Stripe, Adyen, Visa, Braintree, and Shopify Payments are all active participants. Payment tokens are one-time-use, scoped to a specific transaction, and never expose raw card numbers to the agent. The consumer pre-authorizes payment methods through their identity provider; the agent passes a token, and the merchant's processor handles the rest. This multi-processor model means merchants do not need to switch payment providers to participate in UCP.

ACP routes all payments through Amazon Pay. This is clean and simple from an integration standpoint, Amazon Pay has strong fraud detection and consumer protection features, but it introduces a hard dependency on Amazon's payment infrastructure. For merchants who do not already use Amazon Pay, adding ACP means adding a new payment processor.

Identity Models

UCP uses an OAuth-style federated identity model. Consumers pre-authorize agents to act on their behalf through an identity provider (Google Identity, Shopify Identity, or any compliant UCP identity service). Tokens are scoped: an agent might have browse-and-compare permission but not purchase permission, or purchase permission capped at a specific dollar amount. Consumers revoke access at the identity provider level, not by contacting individual merchants.

ACP ties identity to Amazon accounts. For consumers who are already Amazon customers (which is most of the U.S. adult population), this is frictionless. The agent acts as an Alexa skill or registered ACP agent operating on behalf of the Amazon account. The trade-off is that non-Amazon consumers, or consumers who prefer not to link their Amazon account to third-party agents, face a harder path.

Agent Support: Who Is Using Which Protocol

This is where the industry dynamics are shifting quickly in early 2026.

Google is the most significant backer of UCP on the AI side. Google's AI Mode in Search uses UCP for direct commerce actions, and Google Shopping's agent capabilities are built on UCP endpoints. For agents built on Google's infrastructure, UCP is the natural path.

OpenAI has made a different bet. OpenAI's shopping features in ChatGPT, and the commerce capabilities in the new Operator product, lean heavily on ACP. Amazon and OpenAI announced an expanded partnership in early 2026, and the shopping flow in ChatGPT defaults to ACP-enabled merchants when available, falling back to affiliate links for non-participating retailers. This gives ACP a significant distribution advantage for the current largest consumer AI chatbot.

Anthropic and Perplexity have implemented UCP but remain relatively protocol-agnostic, supporting both where available.

Comparison Table

Strategic Implications

The current state looks like a two-protocol world with fragmented AI alignment. Google-backed agents will favor UCP. OpenAI-backed agents will favor ACP. Merchants with serious agent commerce ambitions probably need to support both, at least for now.

The deeper strategic question is whether the open-protocol model or the integrated-ecosystem model captures more of the eventual market. Amazon's historical strength has been in building ecosystems with high lock-in and high reliability. Shopify's strength has been in building open infrastructure that the long tail of commerce can adopt without negotiating enterprise deals.

There is a scenario where UCP wins on breadth (more merchants, more payment options, more agent compatibility) and ACP wins on depth (richer Amazon-specific experiences, tighter Alexa integration, OpenAI distribution). Both can co-exist and serve different segments. There is also a scenario where one protocol achieves enough critical mass that agents implement only one, and the other fades. That outcome is probably 18 to 24 months away from being clear.

For merchants deciding which to prioritize today: if you are on Shopify, UCP is essentially free to enable and should be your first move. If you sell primarily on the Amazon marketplace, ACP is the obvious path. If you operate both channels, you want both.

The UCPList directory tracks the full UCP ecosystem as it grows, including SDKs, conformance tools, and verified merchant implementations. For a look at what the UCP tool landscape actually looks like right now, start there.