Google's Sundar Pichai took the stage at the National Retail Federation with a message that wasn't soft. E-commerce distribution is changing fundamentally. Not in five years. Now.
The protocol he presented is called UCP — the Universal Commerce Protocol.
The restaurant that had to register everywhere
Imagine you own a restaurant and want to appear on food delivery apps. You register on Uber Eats with your menu and prices. You register on Foodora with the same information. Bolt Food. Wolt. Same menu, four formats, four places to keep updated. If you change a price, you go to four places. If you add a dish, you register it four times.
That's exactly what e-commerce looks like today. A product page on your website, a product feed to Google Shopping, separate integrations to Klarna, to Meta, to Amazon. Same product, ten formats.
UCP is the idea of registering once in a format all agents and search engines can read.
Why AI agents need it
The old search indexing system — a crawler reading text on your web page — works well enough to display a link. It's not sufficient to recommend a product.
An AI agent answering "which bike tyre suits my commuting bike?" needs information about specifications, real-time stock, accurate price, and delivery options. It needs that in a format it can reason about, not just index.
Without UCP-structured data, the agent can't recommend your product with confidence. That's not an intelligence problem. It's a data problem.
Not a clean slate
What makes UCP achievable is that it builds on standards most e-commerce operators already work with. Schema.org product data, Google Shopping feeds, JSON-LD structured data — UCP is a layer on top of what you're probably already doing, not a restart.
Google developed the protocol jointly with Shopify, Walmart, Etsy, Target, and Wayfair. It's not a Google product that can be taken back. It's an open standard the industry owns collectively, the same way HTML is an open format.
It's no longer optional
There's a pattern in Google's history of technical requirements. Mobile optimisation was introduced as a recommendation. Then as a ranking factor. Then as a requirement. HTTPS. Core Web Vitals. Structured Data. Every time, the question "should we prioritise this?" was already decided by Google's timeline, not yours.
Those who understand how AI agents find, understand, and buy products today are the ones still visible when that's the only purchase flow in three years.
The documentation is at ucp.dev. That's a reasonable place to start.
