Universal Cart is the interface the consumer sees. UCP — Universal Commerce Protocol — is the layer underneath, and it is the reason Google's move carries more strategic weight than just a universal cart.
What UCP is
UCP is an open-source standard designed to let three different actors speak the same language: AI agents, merchant platforms and payment systems. The protocol defines common primitives for describing products, managing a cart, applying promotions, completing checkouts and handling post-sale flows. Without a shared protocol, every agent would have to write a custom connector for every e-commerce; with UCP the same action works wherever it has been implemented.
Google co-developed UCP with a first wave of partners: Shopify, Etsy, Wayfair and Target on the consumer commerce side, Amazon, Walmart and Meta for marketplace scale. On the payments side, UCP integrates with AP2 (Agent Payments Protocol), also updated at I/O 2026, which handles authorization and traceability for agent-initiated transactions.
Why it matters for e-commerce builders
Until now, merchants had to chase every new agent (Gemini, ChatGPT with Operator, Perplexity Shopping, Claude). UCP reduces that fragmentation to a single server-side implementation: a merchant adopting the protocol opens its catalog to every compatible agent without redoing the work multiple times. For platforms it is a promise of interoperability; for aggregators it is a disintermediation risk, because the consumer may never visit the merchant's website before purchase.
Geographic and category expansion
UCP-powered checkout, already available in the United States, expands to Canada and Australia. The United Kingdom is announced for the following months. On categories, Google confirmed an expansion beyond physical goods: hotel bookings and local food delivery are in the first wave.
What to watch with skepticism
A protocol is a promise of neutrality, but in practice whoever controls it sets the standard. UCP is born inside Google, and it is reasonable to expect the first reference implementation will favor the internal flow (Search → Cart → Pay → Wallet). The fact that the initiative launches with competitors like Amazon and Meta at the table is the strongest signal of openness, but the history of web standards (from AMP to Web Components) shows that real governance plays out in the three years after launch, not at the keynote. The full UCP documentation lives at developers.google.com/merchant/ucp and in a dedicated technical post on the Google Developers Blog: worth reading before signing road maps.