Universal Commerce Protocol (UCP): What It Is and How to Check Your Store Supports It

On November 4, 2026, Google started letting Canadian shoppers buy from lululemon, Shoppers Drug Mart, Simons and selected Shopify stores without leaving AI Mode or the Gemini app.

Three weeks earlier, it launched Universal Cart in the US: one cart across Google Search and Gemini, with checkout at Nike, Sephora, Target, Walmart, Wayfair and many Shopify merchants.

Both run on the same thing: the Universal Commerce Protocol, or UCP.

If you sell online, UCP decides whether an AI agent can find your products, fill a cart and hand the shopper to your checkout. And there’s a quick way to see whether your store already speaks it: one URL you can open in your browser right now.

What Is UCP?

TL;DR The Universal Commerce Protocol (UCP) is an open standard that lets AI agents discover what a store can do, then search its catalog, build a cart, check out and track the order, without a custom integration for every agent.

Google announced UCP on January 11, 2026, at the NRF retail show. It was co-developed with Shopify, and partners at launch included Etsy, Wayfair, Target and Walmart, plus payment companies like Visa, Mastercard, American Express and Stripe.

The idea is simple. Today, every AI shopping agent would need its own connection to every store. UCP replaces that with one shared language. A store publishes what it supports once, and any agent that speaks UCP can use it.

Universal Commerce Protocol at a glance

How UCP Works

UCP has three moving parts: a manifest, capabilities, and a transport.

1. The manifest

Every UCP store publishes a small JSON file at the same address: yourstore.com/.well-known/ucp.

Think of it as your store’s business card for agents. It says which version of UCP you support, what you can do, where the agent should send its requests, and which payment handlers you accept.

Here’s a simplified example of what one looks like:

Real manifests carry more detail, and field names shift slightly between protocol versions. But every one answers the same three questions: which version, which capabilities, and where to send requests.

2. Capabilities and extensions

UCP splits shopping into building blocks, so you only switch on what you’re ready for:

• Catalog: product search and product details.
• Cart: building a basket before the shopper commits to buying.
• Checkout: creating a checkout session and completing the purchase.
• Order: order status and post-purchase updates.
• Identity linking: connecting a shopper’s account with you, so loyalty pricing or free shipping still applies.

Extensions sit on top of capabilities. Discounts, for example, extend checkout. An agent only sends a promo code if your manifest says you accept one.

3. The transport

UCP doesn’t care how the agent talks to you. A store can offer its capabilities over a REST API, an MCP server or Agent2Agent (A2A).

Most stores on a hosted platform never see this layer, because the platform handles it.

PRO TIP: The version number matters more than it looks. Google’s Cart API, which powers Universal Cart’s hand-off to your site, only exists from UCP version 2026-04-08. A manifest on an older version can still work for checkout, but your cart won’t transfer.

Where UCP Is Live Today

UCP went from announcement to real checkouts in under a year. Here’s where it stands in November 2026.

Google Universal Cart (US). Launched October 15, 2026, across Google Search, AI Mode and the Gemini app. Shoppers collect products from different stores in one cart. At checkout, participating merchants either take payment with Google Pay inside the cart, or receive the cart on their own site. Both routes run on UCP.

AI Mode and Gemini checkout in Canada. Since November 4, 2026, Canadian shoppers can buy from lululemon, Shoppers Drug Mart, Simons and selected Shopify merchants inside AI Mode and Gemini. The retailer stays the seller.

Google Merchant Center. On October 6, Google started rolling out a UCP integration hub to US merchants. Inside it, you choose which capabilities to support: cart transfer to your site, native checkout on Google, and identity linking. You still need to implement UCP first, then apply.

Shopify. Shopify switched on Agentic Storefronts by default on March 24, 2026, for roughly 5.6 million stores. If your store is eligible, your catalog is already reachable by UCP-speaking agents, with no app or extra fee.

How many stores are ready?

Not many, outside Shopify. Cloudflare Radar’s agent-readiness scan on November 2, 2026, found that only 4.7% of 115,468 popular websites publish a UCP manifest. Among ecommerce domains it rises to 22.1%.

A separate probe of 19,044 storefronts by TechnologyChecker found manifests on 73% of Shopify stores. Platform defaults are doing most of the work, which means stores on custom builds, WooCommerce or Magento are the ones most likely to be missing.

UCP vs ACP

You’ll often see UCP mentioned next to ACP, the Agentic Commerce Protocol from OpenAI and Stripe. They overlap, but they aren’t the same thing.

ACP’s flagship use, Instant Checkout in ChatGPT, has been scaled back: OpenAI has stepped back from a standalone checkout inside ChatGPT, which now mostly hands shoppers to the store’s own site. UCP, meanwhile, keeps expanding.

You don’t have to pick one. Shopify supports both, and most stores will end up with both. We’ll compare them, along with AP2, in more depth in an upcoming guide.

How to Check If Your Store Supports UCP

This takes about five minutes. You don’t need developer access for the first two steps.

Step 1: Open your manifest URL

In any browser, go to your domain followed by /.well-known/ucp, for example: https://yourstore.com/.well-known/ucp

Then look at what comes back:

• A block of JSON text starting with {“ucp”: you have a manifest. Move on to step 2.
• A 404 or “page not found”: you don’t have one.
• Your homepage or another page: you don’t have one either. Your site is redirecting unknown URLs, and agents will treat that as a no.

Step 2: Read the three lines that matter

You don’t need to understand every field. Look for these:

1. The version. It should be 2026-04-08 or later if you want Universal Cart to hand carts to your site.
2. The capabilities. Check which of catalog, cart, checkout and order appear. Missing ones are things agents can’t do at your store.
3. The endpoint. It should point at a real address on your own domain or your platform’s, not a placeholder.

Step 3: Check that agents can actually reach it

A manifest a browser can open isn’t always one an agent can. Firewalls and bot protection sometimes block automated requests. Ask your developer to run this from outside your network:

curl -sI https://yourstore.com/.well-known/ucp

You want to see a 200 status and a content-type of application/json. A 403 or a challenge page means your bot protection is turning agents away, and you’ll need an exception for this path.

Step 4: On Shopify, check Agentic Storefronts

In your Shopify admin, go to Settings → Apps and sales channels, then open Agentic storefronts. You’ll see each AI channel, whether it’s switched on, and which products are available to it. If a channel is off, agents on it can’t sell your products even though your manifest exists.

Step 5: In the US, check Google Merchant Center

Look for the UCP integration hub in Merchant Center. It’s still rolling out, so it may not appear yet. If it does, it shows which UCP capabilities you’ve chosen and whether your integration has been validated.

Step 6: Run a full agent-readiness check

A manifest is only one signal. Run your store through AccessibilityChecker.org to see how agents read your product pages, buttons and forms, and what to fix first.

PRO TIP: Check a competitor’s manifest the same way. If they’re live on UCP and you’re not, their products can land in a shopper’s Universal Cart and yours can’t.

No UCP Manifest? What to Do Next

What you do depends on how your store is built.

On Shopify. Eligible stores get UCP through Agentic Storefronts automatically. If your manifest is missing, check the Agentic storefronts settings first, then ask Shopify support whether your store is eligible.

On another hosted platform. Google’s own advice to merchants on third-party platforms is to ask the provider about its UCP plans. Do that before paying anyone to build it, because your platform may switch it on for you.

On a custom, headless or open-source build (WooCommerce, Magento, Medusa, Laravel and similar). Someone has to implement it. The full specification and developer guides live at ucp.dev, and open-source packages already exist for frameworks such as Laravel,

Spring Boot and Medusa. Start with discovery and catalog, then add cart and checkout.

Whichever route you take, fix your product data first. Google’s onboarding only helps stores whose feeds are already in good shape: complete attributes, GTINs, accurate prices and stock, and structured data on product pages.

Why Your Product Pages Still Matter

It’s tempting to think UCP makes your website optional. It doesn’t.

UCP covers the structured part of a purchase. But most agentic shopping today is still assisted: an agent researches and compares, then the shopper finishes on the store’s own site. Universal Cart’s cart transfer does exactly that. It sends the shopper, and their cart, to your checkout.

And when agents do browse your pages, they don’t see them the way people do. As we explain in The Best AI Agents, they lean heavily on the accessibility tree, the same structure screen readers use.

So the problems that block screen reader users block agents too:

• An “Add to cart” button with no accessible name.
• Size and color pickers built from plain divs instead of real form controls.
• Prices and stock that only appear after JavaScript runs.
• Checkout errors shown only in red, never announced.

UCP gets agents to your door. An accessible site lets them, and every shopper who follows, actually get through it.

Want to see what agents see? Start with The Accessibility Tree, Explained, then read our full guide to agentic commerce.

UCP FAQs