UCP vs ACP: Which AI Commerce Protocol Should You Implement First?
Two protocols now define how AI agents discover and buy from online stores. Google and Shopify built UCP. OpenAI and Stripe built ACP. They are not competing standards -- they serve different parts of the AI commerce stack. Here is everything you need to know to decide which to implement first, or why you might want both.
TL;DR
UCP handles AI product discovery and the full shopping journey within Google's ecosystem. ACP handles instant checkout within ChatGPT and the OpenAI ecosystem. They solve different problems and complement each other. Most merchants should plan to implement both, but your starting point depends on your platform, payment processor, and where your traffic comes from.
What is UCP? A Quick Recap
The Universal Commerce Protocol (UCP) is an open-source standard announced by Google at NRF 2026 in January. Developed in partnership with Shopify, UCP defines how AI agents discover products, understand store capabilities, and complete purchases across the web.
UCP works through a machine-readable business profile published at /.well-known/ucp on your domain. This profile tells AI agents what your store sells, what capabilities it supports (checkout, identity linking, order management), and how to interact with it programmatically.
The protocol is transport-agnostic, supporting REST APIs, Model Context Protocol (MCP), and Agent-to-Agent (A2A) communication. Shopify stores get native UCP support through Agentic Storefronts. For everyone else, implementation requires development work or waiting for platform-level integrations from BigCommerce, Adobe Commerce, and others.
UCP is backed by over 20 launch partners including Visa, Mastercard, PayPal, Stripe, Target, Walmart, Best Buy, and Etsy. Full documentation is available at ucp.dev.
What is ACP? A Quick Recap
The Agentic Commerce Protocol (ACP) is an open standard developed by OpenAI and Stripe that powers ChatGPT's Instant Checkout feature. ACP defines how AI agents create, update, complete, and cancel checkout sessions on behalf of users.
ACP is a RESTful HTTP interface with four core endpoints. When a user tells ChatGPT to buy something, the AI agent calls your Create Checkout endpoint with a product SKU. You return cart data and pricing. As the user makes selections, Update Checkout keeps things in sync. When they confirm, Complete Checkout processes payment through a Shared Payment Token -- Stripe's mechanism for letting AI agents facilitate purchases without ever seeing credit card numbers.
ACP is rolling out through what OpenAI calls the Agentic Commerce Suite, with support coming for WooCommerce, BigCommerce, Squarespace, Wix, and more. Etsy is already live for US sellers. If you already process payments with Stripe, enabling agentic payments can be done with minimal code changes. Full documentation is available at openai.com.
Head-to-Head Comparison
Here is a detailed side-by-side breakdown of UCP and ACP across every dimension that matters for e-commerce merchants:
| Dimension | UCP | ACP |
|---|---|---|
| Created by | Google + Shopify | OpenAI + Stripe |
| Primary purpose | Discovery + checkout across the full shopping journey | Instant checkout within AI conversations |
| How it works | Business profile at /.well-known/ucp with capabilities + extensions | RESTful HTTP API with 4 checkout endpoints |
| Native platform support | Shopify (live now) | Etsy (live), WooCommerce, BigCommerce, Squarespace, Wix (rolling out) |
| Payment methods | Payment Token Exchange (Visa, Mastercard, PayPal, Stripe, etc.) | Shared Payment Token via Stripe |
| AI agents supported | Google AI Mode, Gemini, and any agent using UCP transport | ChatGPT (primary), any agent adopting ACP spec |
| Scope | Product discovery, cart, checkout, identity, order lifecycle | Checkout creation, updates, completion, cancellation |
| Transport layer | REST, MCP, A2A (transport-agnostic) | REST (HTTP) |
| License | Apache 2.0 (open source) | Open standard |
| Merchant of Record | Merchant retains ownership | Merchant retains ownership |
| Current availability | Shopify live, others announced | Etsy live, major platforms rolling out Q1 2026 |
| Merchant requirements | UCP business profile, capability endpoints, certification | 4 REST endpoints, Stripe integration, OpenAI certification |
UCP Strengths: Google's Ecosystem Advantage
UCP's biggest advantage is its scope. Where ACP focuses narrowly on the checkout transaction, UCP covers the entire shopping journey from discovery to post-purchase order management. This makes sense given Google's position as the starting point for most product searches.
Massive reach through Google AI Mode. When someone asks Google's AI Mode for product recommendations, UCP-compatible stores are the ones that get surfaced. Google processes billions of shopping queries annually. Being discoverable in AI Mode means access to the largest pool of high-intent shoppers on the internet.
Broad payment ecosystem. UCP's Payment Token Exchange supports Visa, Mastercard, PayPal, Stripe, and others. You are not locked into a single payment provider. This flexibility matters for merchants who process payments through multiple channels or who use a non-Stripe processor.
Transport flexibility. UCP is transport-agnostic, meaning it works over REST APIs, Model Context Protocol (MCP), or Agent-to-Agent (A2A) communication. As the AI agent ecosystem evolves and new communication standards emerge, UCP can adapt without requiring merchants to rebuild their integrations.
Industry coalition. With over 20 launch partners spanning retailers (Target, Walmart, Best Buy), payment networks (Visa, Mastercard), and platforms (BigCommerce, Adobe Commerce, Salesforce), UCP has the broadest industry backing of any AI commerce standard. This coalition reduces the risk of the protocol being abandoned or sidelined.
ACP Strengths: OpenAI's Checkout Innovation
ACP's power lies in its focus. Rather than trying to standardize the entire commerce stack, it solves one specific problem exceptionally well: letting AI agents complete purchases securely and instantly.
ChatGPT's user base. ChatGPT has hundreds of millions of users. When those users ask for product recommendations and can buy without leaving the chat, that is a direct sales channel. ACP is the only way to participate in ChatGPT Instant Checkout. If a meaningful percentage of your target customers use ChatGPT, ACP puts your products where they are already spending time.
Stripe's payment infrastructure. The Shared Payment Token is ACP's standout innovation. Users save their payment method with Stripe once, and every future AI-assisted purchase uses a scoped, temporary token. No credit card numbers flow through the AI agent. No PCI compliance headaches for the new channel. For merchants already on Stripe, enabling ACP can require minimal code changes.
Simpler implementation. ACP has four endpoints: Create, Update, Complete, and Cancel. The spec is focused and well-documented. For a development team familiar with REST APIs and Stripe, the path from reading the spec to going live is shorter than a full UCP implementation, which requires business profiles, capability declarations, extensions, and certification across multiple touchpoints.
Faster platform rollout. ACP support is rolling out to WooCommerce, BigCommerce, Squarespace, and Wix through the Agentic Commerce Suite. Because ACP is narrower in scope, platform integrations can ship faster. Etsy is already live. For non-Shopify merchants, ACP may reach your platform before UCP does.
They Complement Each Other -- Not Compete
This is the most important insight in the entire UCP vs ACP discussion: these protocols are not rivals. They address different parts of the AI commerce experience.
UCP is about discovery. It tells AI agents what your store sells, what capabilities you support, and how to interact with your catalog. It answers the question: "Should this store be recommended to the user?"
ACP is about transaction. Once an AI agent has decided to recommend your product, ACP handles the actual purchase. It answers the question: "How does the user buy this without leaving the conversation?"
Think of it like a physical retail analogy. UCP is the storefront, signage, and window display that gets customers through the door. ACP is the checkout counter that processes the sale. You need both for the full experience.
Stripe itself is a UCP launch partner, which signals that these standards are designed to coexist. A store can be UCP-discoverable through Google AI Mode and ACP-transactable through ChatGPT at the same time. In fact, this dual implementation is where the maximum AI commerce coverage lies.
Decision Framework: Which Should You Implement First?
If you plan to implement both eventually (and you should), the question becomes: where do you start? Use this framework based on four factors.
Factor 1: Your Platform
Start with UCP if...
You are on Shopify (native support live now) or BigCommerce (UCP announced as a launch partner)
Start with ACP if...
You are on WooCommerce, Squarespace, or Wix (ACP rolling out through Agentic Commerce Suite)
Factor 2: Your Traffic Sources
Start with UCP if...
Most of your organic traffic comes from Google Search. AI Mode is where your customers are headed next.
Start with ACP if...
Your audience skews younger or more tech-forward. ChatGPT users tend to be early adopters with high purchase intent.
Factor 3: Your Payment Processor
Start with UCP if...
You use a non-Stripe payment processor. UCP supports Visa, Mastercard, PayPal, and others natively.
Start with ACP if...
You already process payments through Stripe. ACP integration is significantly easier with existing Stripe infrastructure.
Factor 4: Your Goals
Start with UCP if...
Your primary goal is AI discoverability and getting recommended alongside competitors in AI search results.
Start with ACP if...
Your primary goal is conversion optimization and enabling frictionless AI-powered checkout for existing traffic.
Platform-Specific Recommendations
Here is actionable guidance for the three most common non-Shopify platforms:
WooCommerce merchants should start with ACP. The Agentic Commerce Suite is actively rolling out WooCommerce support, and most WooCommerce stores already use Stripe or can add it easily. Enable ACP through your Stripe dashboard once your platform integration is available.
In parallel, prepare for UCP by ensuring your structured data is complete (Product schema with GTINs, offers, and BuyAction), your Google Merchant Center feed is optimized, and your store policies are machine-readable. When WooCommerce UCP support arrives, you will be ready to activate it immediately.
Timeline: ACP available now via Stripe API. Platform-native integration expected Q1 2026.
BigCommerce is a UCP launch partner, meaning native UCP support is coming to the platform. BigCommerce merchants should prepare for UCP by optimizing their product data, Google Merchant Center integration, and structured data now. When native support ships, enable it immediately.
Then add ACP. BigCommerce is also in the ACP rollout pipeline. If you use Stripe for payments, you can potentially enable ACP before native BigCommerce support arrives by implementing the four REST endpoints directly against the Stripe API.
Timeline: UCP native support expected H1 2026. ACP available via Stripe API now.
Adobe Commerce (Magento) is a UCP launch partner, and the platform's extensibility makes it well-suited for custom implementations of either protocol. If you have developer resources, you can implement both protocols in parallel.
If resources are limited, prioritize based on your traffic sources. Google-heavy traffic? Start with UCP. Already on Stripe? Start with ACP. Either way, both protocols are realistic targets for Magento stores given the platform's API-first architecture.
Timeline: UCP as a launch partner. ACP via custom Stripe integration available now.
Find Out Where Your Store Stands
Our free Agent Ready Score checks your store against UCP, ACP, structured data, product feeds, and 20+ other factors that determine AI agent discoverability -- in under 60 seconds.