UCP Explained: The Universal Commerce Protocol

The Universal Commerce Protocol (UCP) is Google’s open standard for agentic commerce. Where ACP began as a checkout handshake, UCP is broader: it aims to standardize the entire shopping journey, from discovery and buying through to post-purchase support. It is the one genuine rival to ACP at the commerce layer, and it is live today inside Google’s own surfaces.

Who is behind it

UCP was announced on 11 January 2026 at the NRF retail show during Sundar Pichai’s keynote. It was co-developed with Shopify, Etsy, Wayfair, Target, and Walmart, and endorsed at launch by more than twenty other companies including Adyen, American Express, Best Buy, Macy’s, Mastercard, Stripe, The Home Depot, Visa, and Zalando. It is licensed under Apache 2.0, with the specification at ucp.dev and code under a dedicated GitHub organization.

The standard is steered by a UCP Tech Council, which reviews contribution proposals and stewards the open-source protocol. Its founding members are Google, Shopify, Etsy, Target, and Wayfair. On 24 April 2026 the council doubled in size when Amazon, Meta, Microsoft, Salesforce, and Stripe joined it, a notable convergence that brought several companies with previously rival positions under one open-standard governance body. Stripe and Meta now sit formally on the UCP council while also being tied to the rival ACP, a sign the big platforms are hedging across both commerce standards.

What UCP actually does

What distinguishes UCP is scope. Its initial capabilities include catalog search, cart building, checkout, identity linking via OAuth 2.0, an order lifecycle (shipped, delivered, returned), and a payment-token exchange. In other words, UCP tries to standardize the whole sequence, with payment as one composable piece rather than something baked in.

That payment piece is where AP2 comes in. Google designed the two to fit together: as AP2’s own documentation puts it, UCP orchestrates the broader purchase lifecycle while AP2 is the specialized layer that authorizes and signs the transaction. UCP is also designed to be compatible with the agent-to-agent protocol A2A and with MCP, and businesses can expose UCP capabilities over plain REST, MCP, or A2A.

What is actually live

As of mid-2026, the specification, SDKs, samples, and a conformance suite are published, and Google built the first reference implementation to power checkout inside AI Mode in Search and the Gemini app for eligible US retailers, paying through Google Pay. In March 2026 Google added new optional UCP capabilities: a Cart option that lets agents add multiple items at once, a Catalog capability for retrieving real-time product details like variants, inventory, and pricing, and Identity Linking so shoppers keep loyalty and member benefits on UCP-integrated surfaces, plus a simplified onboarding path in Merchant Center. At Google Marketing Live on 20 May 2026, Google extended Universal Cart, which lets shoppers save products across retailers and check out via Google Pay or a retailer’s own flow, to named brands including Nike, Sephora, Target, Walmart, Wayfair, and Shopify merchants, and pushed UCP into new verticals beyond retail: hotel booking (with Booking.com, Expedia, Hilton, Marriott, IHG, and Accor) and food delivery (with DoorDash, Square, Toast, and Uber Eats), rolling out in the US first. So UCP is real and shipping in Google’s own surfaces and expanding past retail, though broad third-party adoption is still early.

A common point of confusion

“UCP” the acronym is overloaded in the wider tech world, and the generic phrase “unified commerce platform” is a different, older retail concept. In agentic commerce, UCP means this Google-led protocol. The live confusion to avoid is UCP versus ACP: two parallel standards launched by rivals, not two names for the same thing. For a side-by-side, see ACP vs UCP, and for where UCP sits among the other standards, see the protocol stack.

FAQ

What is UCP? Google’s open standard for agentic commerce, launched January 2026, covering the full shopping journey from discovery to post-purchase, with payment as a composable piece.

Is UCP the same as ACP? No. They are rival commerce-layer standards: UCP is Google’s whole-journey protocol; ACP is OpenAI and Stripe’s checkout protocol. Both are Apache 2.0, and several companies back both.

How do UCP and AP2 fit together? Google pairs them: UCP orchestrates the purchase lifecycle and AP2 authorizes the payment, with AP2 integrated as an extension within UCP.