Universal Commerce Protocol (UCP): what it is, and what your store needs before Google sells for you

The short answer

UCP matters because it moves the checkout, the last step a website still owned, onto someone else's screen. That is a large change for anyone who measures a website by what happens after the click. It is also less sudden than the headlines suggest. Access is by selection, most platforms outside Shopify are not ready, and every design decision in the protocol keeps a path back to the merchant's own site.

What is the Universal Commerce Protocol?

The Universal Commerce Protocol is a shared set of rules that lets AI platforms and online businesses trade without a custom integration for each pair. It defines how an agent searches a catalogue, builds a cart, checks out, links a buyer's account and tracks an order. It is open source, and the business stays the merchant of record.

Google introduced it as "a new open standard for agentic commerce" that works across discovery, buying and post-purchase support (Google, 11 January 2026). The launch post named five co-developers and more than 20 endorsers, including Mastercard, Visa, Stripe and Adyen. It also said UCP works with the other agent standards already in circulation: the Agent2Agent protocol, the Agent Payments Protocol (AP2) and the Model Context Protocol.

The list has grown. The protocol's own site, ucp.dev, now shows 21 companies building it across shopping, lodging and food, among them Amazon, Microsoft, Meta, Salesforce, Booking.com, Marriott and DoorDash. About 50 more brands are listed as endorsers. Five of them are Australian retailers: Adore Beauty, Bunnings, Kogan, Petbarn and The Iconic. The specification is published under the Apache 2.0 licence, so no single company owns it.

That breadth is the point. Our guide to Shopify agentic commerce covered UCP as one of Shopify's three building blocks. This article looks at the protocol itself, and at what it means for a store that is not on Shopify.

How does UCP work?

A business publishes a profile that lists what it supports. An AI platform reads the profile, works out which capabilities the two sides share and uses only those. The agent then builds the cart and requests checkout. If anything needs the buyer, the business returns a link and the person finishes on the merchant's own page.

In practice there are four steps, all described in the UCP specification:

1. Discovery. The store serves a JSON profile at /.well-known/ucp. It carries the protocol version, the services on offer, the capabilities supported and the payment handlers accepted.
2. Negotiation. The business computes the overlap between its capabilities and the platform's. Anything only one side supports is dropped, so an agent never attempts a step the store cannot perform.
3. Checkout. The agent creates a checkout with the items, the buyer's details and a payment credential. On Google that credential comes from Google Pay, using the card and address saved in Google Wallet.
4. Handover. When a step cannot be completed by the agent, such as a bank challenge, the checkout returns a status of requires_escalation and a continue_url. The specification says the platform must open that link for the person to finish. The same link is the fallback when negotiation fails.

The fourth step is the one to remember. UCP does not assume the agent always finishes. It writes the route back to your website into the standard.

Where is UCP checkout live, and is Australia included?

UCP checkout on Google is live for selected merchants in the United States and, since 4 November 2026, Canada. Google's Merchant Center help lists Australia as an eligible market alongside them, with the feature limited to participating merchants. The United Kingdom has been named as the next market, without a date.

Three details sit behind that table.

Access is by selection. Google's help page says the checkout feature is "available for select merchants at this time". A retailer completes the technical work, submits an interest form and waits to be chosen. Listings show a Buy button only when the product carries the native_commerce attribute in the feed, and the retailer needs a Google Pay and Wallet Console account.

Australia was announced in June. Trade press reported Australia as the first Asia-Pacific market for UCP, with five launch retailers and single-item purchases in Search, AI Mode and the Gemini app (RetailBiz). ChannelNews described the checkout at the time as something that "will soon launch". We could not confirm at source which of the five are selling this way today, so treat Australia as open to a few large retailers, not to the market.

Self-service comes later. Google Canada says a simplified UCP integration inside Merchant Center starts "next year". Google's onboarding page says the Merchant Center integration is opening gradually in the US, with Australia and Canada to follow. Neither gives a date. For a store on someone else's platform, Google's advice is to ask the platform provider about its UCP plans.

Which ecommerce platforms already support UCP?

Shopify, BigCommerce and Wix stores mostly do, because the platform publishes the profile for them. Stores on WooCommerce, Magento, Squarespace, PrestaShop and Salesforce Commerce Cloud mostly do not. A probe of 19,044 storefronts on 7 November 2026 found the gap between the two groups is more than 60 percentage points.

Read the chart with its limits. TechnologyChecker sells technology data, so this is a vendor study, not an independent audit. It checked whether a profile exists, not whether an agent can complete a purchase. Stores that blocked the request were left out of the percentages. And the low numbers are even lower than they look: 21 of the 38 WooCommerce hits, and all 28 of the Salesforce Commerce Cloud hits, were domains that also run Shopify.

The pattern still holds. Where the platform switches UCP on, most stores have it without doing anything. Where the merchant has to build it, almost nobody has.

WooCommerce is the clearest case. Its own agentic commerce page lists UCP as not live yet, and points merchants to its Google extension, which syncs the catalogue to Merchant Center. Third-party UCP plugins have appeared in the WordPress plugin directory, but they are young and WooCommerce does not endorse them. On WooCommerce the work is a build, not a setting: a clean Merchant Center feed, policies in the right fields and, later, a profile that matches what the checkout can really do. That is the kind of job a WordPress specialist such as WP Creative scopes as one project, and WP Creative's comparison of WooCommerce and Shopify is a useful read if this changes how you weigh the two platforms.

Does UCP mean customers stop visiting your website?

No. UCP moves some checkouts onto an assistant's screen, but it keeps the merchant as the seller, the merchant's policies in force and a link back to the merchant's site whenever the agent cannot finish. Fewer visits will reach your checkout page. The visits that do arrive will be further along and less forgiving.

Compare it with OpenAI's approach. As our piece on Businesses in ChatGPT explains, a ChatGPT Business Agent cannot take an order and sends the customer to the website. Google has gone a step further and takes the payment on its own surface. Both still depend on what the business publishes: accurate products, prices, stock, delivery and returns.

Our view: UCP changes three things for a website, and none of them is "you no longer need one".

• The handover page becomes the checkout that matters. When an agent escalates, the person lands mid-purchase with a cart already built. That page has one job, which is to confirm. A forced account, a surprise delivery fee or a broken mobile layout loses a sale that was nearly finished.
• Your product data becomes your shop window. An agent reads the feed and the structured data, not the design. A price in the feed that differs from the price on the page is now a failed transaction, not a small inconsistency.
• Your measurement gets a blind spot. A sale completed on Google's surface never loads your product page, so page-based tracking has nothing to record. Ask your platform how those orders are reported before you compare channels.

Agents are already heading for the checkout. Microsoft Clarity's study, covered in our piece on AI agent analytics, found agent sessions reach checkout far more often than human ones. UCP gives them a formal door to use.

Where is this heading?

These are forecasts, not facts.

• UCP will become a platform default, not a merchant project. The adoption figures show it. We expect WooCommerce and the other open platforms to ship it in core or in an official extension during 2027, and the stores with clean feeds will be ready on the day.
• Agentic checkout will spread beyond retail. The protocol's site already shows hotel booking and food ordering flows. Google has said hotel booking in AI Mode and food delivery in Maps are coming. Service businesses that take bookings should expect the same question within two years.
• Lead generation gets its own version. UCP is built for carts. For enquiries, the equivalent is a form an agent can read and complete, which is what our guide to WebMCP covers. The principle is the same: publish what an agent can do, and keep a human path for the rest.
• Selection will narrow, then open. Today Google chooses its merchants. Once Merchant Center offers self-service, the constraint moves from access to quality: complete feeds, clear policies and a checkout that does not fail.

The risk for most businesses is not being left out of UCP this year. It is arriving late with product data nobody has looked at since the last replatform.

What to do next

1. Find out where your platform stands. Open yourstore.com/.well-known/ucp in a browser. A JSON file means your platform already publishes a profile. A 404 on Shopify or BigCommerce is worth a support ticket. A 404 on WooCommerce is normal today.
2. Get Merchant Center in order. UCP checkout on Google runs on your product feed. Fix disapprovals, keep prices and stock in step with the site, and complete the returns and shipping settings.
3. Check your structured data. Run the free schema markup checker on a product page and confirm Product and Offer data match what a shopper sees.
4. Make key pages readable without scripts. Run the agent readiness check on a product page and your cart. An agent that cannot read the page cannot recommend the product.
5. Test your handover page as a stranger. Open a cart link on a phone, signed out. Count the steps to pay. Remove the forced account, show delivery costs early and make sure the page loads quickly on mobile data.
6. Ask before you build. If you are a larger Australian retailer, complete Google's interest form through Merchant Center. If you are on WooCommerce, ask your developer for a feed audit now and hold the UCP build until the platform's own support lands.
7. Decide how you will count agent orders. Agree with your platform or agency where orders placed on Google will show up, so they are not lost between channels.

Frequently asked questions

Is the Universal Commerce Protocol only for Shopify stores?

No. Shopify co-developed UCP and switches it on for eligible stores, but the standard is open and published under the Apache 2.0 licence. In a November 2026 probe, most BigCommerce and Wix stores published UCP profiles too. WooCommerce has announced UCP support but has not shipped it, and any retailer with a developer can implement the specification directly and apply to Google through Merchant Center.

Is UCP checkout available in Australia?

Partly. Google's Merchant Center help lists Australia with the United States and Canada as eligible markets, and five Australian retailers were named in June 2026. The feature is limited to merchants Google selects. Google has not published a date for self-service access in Australia, so smaller stores should prepare their product feed and wait for their platform.

Does Google become the seller when a customer checks out with UCP?

No. Google states that retailers remain the seller of record. The shopper pays with Google Pay on Google's surface, and the order, the customer relationship, delivery and returns stay with the retailer. The protocol's own site makes the same commitment: businesses remain the merchant of record.

What is the difference between UCP and ACP?

They are two standards for the same job. WooCommerce describes UCP as Google's protocol for AI-powered shopping and ACP, the Agentic Commerce Protocol, as connecting a product catalogue to AI agents through Stripe's Agentic Commerce Suite. It has announced support for both, so a WooCommerce merchant should not have to choose between them.

Do I need UCP if my website generates enquiries, not sales?

Not today. UCP is built for carts, bookings and orders. A lead generation site has a different task: making sure an AI agent can read its pages and complete its contact form on a person's behalf. The preparation is similar, though. Clear content in the HTML, accurate structured data and a form that works without a mouse.