UCP Explained: Google's Universal Commerce Protocol

If ACP is the protocol everyone heard about first, UCP is the one quietly doing the checkout. It is Google and Shopify's answer to the same question — how does an agent buy from a store? — and its approach is different enough to be worth understanding on its own.

Let me explain UCP in plain terms: how it works, who runs it, what has actually shipped, and how it sits next to ACP.

The one idea behind UCP

Here is the whole thing in a sentence: a store publishes a file that says what it sells and how it takes payment, and any agent can read that file.

The file lives at a fixed address — /.well-known/ucp — on the store's own domain. (That /.well-known/ path is a long-standing web convention, RFC 8615, so this is built on old, boring, reliable plumbing.) An agent fetches it and immediately knows three things:

• ucp.version — which version of the protocol this store speaks.
• ucp.services — what the store can do (browse, cart, checkout, and so on).
• ucp.payment_handlers — how the store accepts payment.

Those three parts are mandatory. Everything else builds on them.

Why this design matters

The clever bit is what UCP does not require: there is no sign-up, no review board, no middleman deciding which merchants are allowed in. The spec calls this "permissionless onboarding." You publish the file, and you are discoverable. That is a very different philosophy from a managed, centrally controlled surface.

It is also decentralised and free to implement. The store hosts its own profile. No one takes a cut just for listing you.

For the services themselves, UCP does not force one transport. A service can use REST, MCP, A2A, or an embedded binding — and in practice MCP is the most common choice. This is the quiet reason I keep telling people to get their MCP layer right: it shows up everywhere, including inside UCP.

Who governs it

UCP is backed by a serious coalition, which matters for whether a standard survives.

• Google and Shopify are permanent governing members.
• Stripe joined the governing council in April 2026.
• The wider tech council expanded to 16 seats in April 2026, with members including Amazon, Meta, Microsoft, Salesforce and Stripe.
• Co-developers include Etsy, Wayfair, Target and Walmart; endorsers include Best Buy, Visa, Mastercard and The Home Depot.

That is a lot of weight behind one standard. It does not guarantee success, but it is not a side project either.

What has actually shipped

This is where I try to keep everyone honest. UCP is not a plan — real checkout is live. The dated milestones:

• 11 January 2026 — Google announces UCP at NRF with the first spec.
• 11 February 2026 — checkout goes live in Google's AI Mode and Gemini, with Etsy and Wayfair, in the US.
• 5 May 2026 — a Buy button appears in main Google Search results (US).
• Mid-June 2026 — UCP launches in Australia, with Bunnings, THE ICONIC, Kogan, Adore Beauty and Petbarn trialling checkout. (As an Australian, I admit I enjoyed seeing local names on that list first.)
• 22 September 2026 — eligible US Shopify products are opted into Google's native checkout automatically.

So: live, mostly US, with Australia as the first market beyond it.

A reality check on adoption

A healthy habit: "announced" and "widely working" are not the same. When people have gone and actually checked storefronts for a valid /.well-known/ucp profile, the results are mixed — some careful checks in October 2026 found well over half of a small sample serving a valid profile, while broader censuses report anywhere from around 13% to 80%, depending on who they sampled. Some big names returned errors or no profile at all.

The takeaway is not "UCP is failing." It is that a standard being live is the start of adoption, not the finish. The plumbing works; the rollout is uneven. That is normal this early.

How UCP relates to ACP

People treat ACP and UCP as rivals. In practice they have drifted into different jobs:

• ACP (OpenAI and Stripe, 29 September 2025) began as the ChatGPT checkout standard. After March 2026 it leaned toward product discovery — it carries your product feed into ChatGPT, while checkout happens elsewhere.
• UCP runs Google's own checkout across Search, AI Mode and Gemini.

So a common pattern is: ACP to be found inside ChatGPT, UCP to actually sell inside Google. Not either/or — both. (I go deeper on this in the protocol stack.)

Key takeaway

UCP is the open, decentralised checkout standard for agentic shopping: publish a profile at /.well-known/ucp, and agents can find and buy from you with no gatekeeper. It is backed by a heavy coalition, it is genuinely live in Google's surfaces (US first, Australia next), and its rollout is real but uneven. If you sell online, UCP is one of the two profiles worth publishing — and MCP is likely how its services will run.

For the full map of protocols, see the agentic commerce protocol stack; for the companies behind each, see the landscape.

Sources and further reading

• Google Developers Blog, "Under the Hood: Universal Commerce Protocol" (2026-01-11): https://developers.googleblog.com
• Google, "New UCP features and tools for retailers" (2026-05-20): https://blog.google
• Google Merchant Center Help, About UCP and UCP-powered checkout: https://support.google.com/merchants
• RFC 8615, Well-Known URIs: https://www.rfc-editor.org/rfc/rfc8615
• Agentic Commerce Protocol (ACP), OpenAI + Stripe: https://www.agenticcommerce.dev

Note: UCP's spec version and live markets change often (the profile release seen in the wild moved to 25 August 2026). Please check Google's own docs above before relying on a specific date or market.