UCP on WooCommerce, what works today

Google’s Universal Commerce Protocol (UCP) is how AI Mode and Gemini can sell a product for you: the shopper picks it in a Google answer and checks out there, or the cart is handed to your site. If you run a WooCommerce store, you have probably seen plugins and agency posts promising to make your store “UCP ready” before Black Friday.

The short answer for October 2026: WooCommerce has no built-in UCP support yet, and Google’s checkout is open only to US merchants it selects, with Canada and Australia due next year. What works today is the groundwork every UCP path starts from: clean product data, a complete Merchant Center account and a clear idea of which products could ever qualify. Here is what is real, what isn’t, and what I’d do this week.

What is UCP, in plain words?

UCP is an open standard that lets an AI agent find a store, build a cart and complete a purchase while the store stays the seller of record. Google announced it in January 2026 with large retailers and Shopify, and the specification lives at ucp.dev.

Three ideas from the specification are worth knowing:

• A profile at a fixed address. A store publishes a JSON profile at /.well-known/ucp. It declares the protocol version, the services, the payment handlers and the public keys used to verify the store’s messages.
• Named capabilities. The profile lists what the store can do, such as dev.ucp.shopping.checkout, dev.ucp.shopping.cart, dev.ucp.shopping.order and dev.ucp.common.identity_linking. The agent and the store use only the capabilities both support.
• More than one transport. The specification describes REST, MCP, A2A and an embedded protocol. Google’s own profile example uses REST.

The MCP part is why this matters to me. It is the same protocol I write about for WordPress in Should your WordPress site have an MCP server?, but pointed at shoppers instead of site owners.

Does WooCommerce support UCP yet?

No. WooCommerce’s agentic commerce page lists Google’s UCP and Stripe’s Agentic Commerce Protocol as “Coming soon”, and the only protocol it marks as available is MCP, in beta. The feature request for native UCP support has been open since January 13, 2026, and as I write it has 34 votes and no reply from WooCommerce staff.

Don’t confuse the two. WooCommerce’s MCP support lets an AI assistant read and manage your products and orders as a logged-in user. It is a tool for running the store, and it changes in WooCommerce 11.3, which I covered in WooCommerce 11.3 removes its MCP endpoint. UCP is about a stranger’s agent buying from you. Having one does not give you the other.

What does Google need before your products get a Buy button?

Google needs a working integration, a selection decision and a Merchant Center account that meets its checkout rules. Its onboarding help page sets the order: build the integration first, fill in the interest form, then wait to be selected. Selected merchants get a sandbox in Merchant Center to test before going live.

Google’s account preparation guide adds these requirements:

• A Merchant Center account in good standing, with products approved for free listings.
• Return policies in Merchant Center that include the return cost, the return window and a link to the full policy. They show on Google’s checkout screen.
• At least one customer support contact: a support page URL, an email address or a phone number.
• The native_commerce(checkout_eligibility) attribute set to true on each product you want to sell this way. Missing or false means no Buy button.

Some products are excluded whatever you do: subscriptions and instalments, personalised goods, pre-orders, used or final sale items, special shipping, age-restricted items, and digital goods and services. Google also says the integration applies only to products sold within the United States.

Google’s Universal Cart, which started rolling out in the US in mid-October, uses the same plumbing. A shopper can check out on Google, or the cart is transferred to the merchant through the UCP Cart API’s CreateCart call. In this first release the transfer is one-way: carts are created, not updated or synced.

Will a UCP plugin get my WooCommerce store into AI Mode checkout?

Not on its own. A plugin can publish a profile and answer checkout requests, but Google still decides who gets in, and outside the US nobody does yet. The UCP plugins I found on WordPress.org have tens of active installs, were last updated eight or nine months ago and don’t say which version of the specification they follow.

Versions matter too. The current specification is dated 2026-08-25, while Google’s implementation guides cover 2026-04-08 and 2026-01-23. A plugin built on an early draft may match neither.

Before I’d put any UCP plugin near a live store, I’d want answers to these:

• Which specification version does it publish, and how fast does it follow new ones?
• How does it handle payment? Google’s example profile declares a Google Pay handler with gateway tokenisation, which is not the same as “any WooCommerce gateway works”.
• Does it sign the messages it sends? The specification requires stores to sign webhooks to the platform and to publish the matching public keys.
• What can an unauthenticated agent do through it: read the catalogue only, or create orders?

If those answers aren’t clear, it belongs on staging, not production.

What can a WooCommerce store do for UCP today?

Get everything ready that Google checks before the protocol itself. None of it is wasted if UCP takes longer than expected, because the same feed and policies drive your free listings today.

1. Check what your store answers at /.well-known/ucp with the first command below. On a plain WooCommerce store you should get a 404. If you get a 200, find out which plugin publishes the profile and whether you meant it to.
2. Open Merchant Center and confirm your products are approved for free listings. It worked if the diagnostics page shows no account-level issues and your main products are approved.
3. Add or complete your return policy with the cost, the window and a link to the policy page on your site. It worked if the policy shows in Merchant Center with all three filled in.
4. Add a customer support contact in Merchant Center. It worked if at least one method is saved.
5. Tag the products that could never qualify, such as subscriptions, personalised items, pre-orders and final sale stock, with a WooCommerce tag of your own. It worked if you can filter the product list by that tag and the rest is your candidate list.
6. Write down how your feed IDs map to WooCommerce product IDs. It worked if you can name the WooCommerce ID behind any item in Merchant Center.

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

curl -s https://yourstore.com/.well-known/ucp | grep -o '"version": *"[^"]*"' | head -n 1

The second command prints the specification version a profile declares, if there is one. On the last step: Google for WooCommerce sends product 23 to Merchant Center as gla_23. Google’s guide says the feed ID must match the product ID your checkout API expects, or you map it with the merchant_item_id attribute, which takes precedence in agent requests. I’d plan on that attribute rather than removing the prefix: WooCommerce’s own FAQ warns that removing it adds every product again and breaks the link to past reports.

Why do caching and redirects matter for a UCP profile on WordPress?

Because the specification is strict about how the profile is served, and WordPress sites love to redirect and cache. The specification says the profile must be served over HTTPS, must not redirect, and must carry a Cache-Control header with public and a max-age of at least 60 seconds. Google adds that it must be public, with no login.

On the sites I run, these are the things I’d check in the first command’s output once a profile exists:

• The status is 200, not a 301 or 302 to a trailing slash, a www version or a login page.
• The content type is JSON, not an HTML page from a security plugin or maintenance mode.
• Cache-Control includes public and a max-age of 60 or more. Page caching plugins and CDNs often rewrite this header, so check it from outside, not in the plugin settings.

Should a store outside the US bother with UCP now?

Yes, but only with the groundwork, not the protocol. Google’s help page says Canada and Australia follow next year, without a date, so a Canadian store can’t get a Buy button in AI Mode this holiday season however ready it is. What it can do is arrive with a clean feed, complete policies and a product list already sorted, so the integration is the only job left when access opens.

For the next few weeks, I’d leave production alone. Black Friday is November 27, and it is the worst week to discover that an experimental checkout plugin creates orders you didn’t expect. Spend the time on Merchant Center, run the two commands once, and revisit UCP after the holidays, when WooCommerce and Google have both moved.