UCP (Universal Commerce Protocol) is Google's open-source standard for the whole agentic shopping journey — how an AI agent discovers products, builds a cart, checks out, and tracks fulfilment across a merchant. Google announced it on 11 January 2026 with retailers including Shopify, Etsy, Wayfair, Target, and Walmart, and endorsement from more than 20 partners such as Visa, Mastercard, Stripe, and American Express. Where AP2 proves an agent's payment was authorised, UCP orchestrates everything around that payment.
This piece explains what UCP is, the six things it standardises, how it relates to AP2 and the Agentic Commerce Protocol (ACP), and what it asks of a merchant. Volatile specifics — partners, surfaces, rollout geography — are dated; the durable idea is a shared language for agent-driven commerce that no single company owns.
What problem does UCP solve?
UCP solves the fragmentation that appears once AI agents start buying across many merchants. Every retailer already has its own checkout, its own cart format, its own order-status API. A human clicks through those one at a time without noticing. A shopper agent transacting across dozens of stores hits a different integration at each one, and that friction is what stops agentic commerce from scaling.
The protocol's answer is a common vocabulary: one agreed way to describe a product, add it to a cart, apply a discount, complete checkout, and report that an order shipped — so an agent learns the pattern once and reuses it everywhere. That is the same reason the web needed HTTP and email needed SMTP: shared primitives beat one-off integrations.
What does UCP actually standardise?
UCP defines a set of functional primitives — the repeatable actions any agentic purchase needs — so a merchant exposes them once and any compliant agent can use them. As of its January 2026 specification, it standardises six:
| UCP primitive | What it covers |
|---|---|
| Product discovery | Surfacing catalog items and attributes an agent can shortlist from |
| Checkout | Initiating and completing a purchase on the shopper's behalf |
| Discount handling | Applying promotions, codes, and offers within the agent flow |
| Fulfilment | Shipping, delivery, and pickup options and status |
| Order management | Post-purchase state — confirmations, changes, returns |
| Identity linking | Connecting the shopper's identity to their account with the merchant |
Source: Google's Universal Commerce Protocol announcement and developer documentation, January 2026. The point of the table is that UCP is not just "agent checkout" — it spans the full lifecycle from finding a product to managing the order after it ships.
UCP is the shared grammar of agentic commerce: describe a product, build a cart, pay, and track the order the same way everywhere, so an agent integrates once instead of once per store.
How does UCP relate to AP2, ACP, and MCP?
UCP is the commerce-orchestration layer; it leans on other protocols for the pieces it deliberately does not own. Google states UCP is compatible with AP2 for the payment step, and that merchants can implement UCP over ordinary APIs, the Agent2Agent (A2A) protocol, or the Model Context Protocol (MCP). In plain terms: UCP runs the shopping journey, and when it reaches "pay," it hands off to AP2 to prove the human authorised the charge.
That makes UCP the closest Google counterpart to the Agentic Commerce Protocol (ACP) from OpenAI and Stripe. Both orchestrate an agent-driven purchase; they are parallel bets from different ecosystems rather than layers stacked on each other. A useful way to hold it: UCP and ACP compete at the journey layer, while AP2 and x402 operate a layer down, at payment authorisation and payment request.
Where does UCP sit in the agentic-commerce stack?
At the commerce-orchestration layer — above the payment protocols and the settlement rails, below the discovery decision of whether an agent picks you at all. Separating the layers keeps the growing protocol zoo legible:
| Layer | Example | Job |
|---|---|---|
| Discovery / being chosen | Answer-engine optimisation | Whether an agent surfaces and selects your product |
| Commerce orchestration | UCP (Google) · ACP (OpenAI + Stripe) | Running the journey: discover, cart, checkout, fulfil, manage |
| Payment authorisation | AP2 (Google) | Proving a human authorised what the agent pays for |
| Payment request | x402 | The HTTP handshake that asks for and confirms payment |
| Settlement rail | Cards or stablecoins | Actually moving the money |
These are complementary layers, not competitors — except at the orchestration row, where UCP and ACP are genuine alternatives. A single purchase could be discovered through an answer engine, orchestrated by UCP, authorised by AP2, and settled on a card. As of mid-2026 no orchestration standard has won, so a merchant does not have to pick one; the durable work feeds all of them.
What is the Universal Cart, and where does it run?
The Universal Cart is Google's first product built on UCP: a single cart a shopper fills across Google surfaces — Search, the Gemini app, and later YouTube and Gmail — and checks out once. Google reported the U.S. rollout beginning in the summer of 2026, starting with Search and the Gemini app, with expansion to Canada, Australia, and then the U.K., plus new verticals like hotel booking and local food delivery.
Crucially, the brand stays the merchant of record. A shopper can either check out natively with Google Pay in a few taps or transfer the cart to the merchant's own site to complete the purchase — either way the merchant keeps the customer relationship. Google also said it would introduce AP2-backed agent payments to these surfaces "in the coming months," starting with Gemini. These specifics are dated to mid-2026 and will move; the durable shape is a shared cart with the merchant, not Google, as seller.
What does UCP mean if you sell online?
Mostly it is infrastructure you adopt rather than build, but it changes where a purchase can complete. If your catalog is exposed through UCP, an agent can discover, buy, and track an order from your store inside a surface like Gemini — without the shopper ever loading your site. Google's baseline for the Universal Cart is an active Merchant Center account and checkout-eligible products; the readiness and catalog-enrichment work you would do anyway is what feeds it.
But UCP settles how an agent transacts with you — not whether it chooses you. That decision happens a layer up, at discovery, and it turns on whether an answer engine surfaces and recommends your product in the first place. That is exactly what Buffy Intel measures, snapshot over snapshot. Questions: [email protected].