Google is now letting shoppers fill a single cart across multiple retailers and check out with Google Pay without ever landing on your product page. If your store is not in Merchant Center with checkout-eligible products, you are not in that cart. That is the whole story, and it is worth ten minutes of your attention this week.
Google announced the Universal Cart and a batch of new Universal Commerce Protocol features at Google Marketing Live on May 20, 2026. The company said shoppers will be able to check out with Google Pay in a few taps across retailers including Nike, Sephora, Target, Ulta Beauty, Walmart, Wayfair and Shopify merchants such as Fenty and Steve Madden.
The names on that list matter less than the mechanism. A standard now exists for an AI surface to read your catalog, build a cart, apply your discount codes, and complete a purchase, while you stay the merchant of record.
What the Universal Commerce Protocol actually is
UCP is an open-source standard that gives AI agents and merchant backends a shared language. Google published the technical breakdown on the Google Developers Blog on January 11, 2026, written by Amit Handa, Director of Engineering for Google Commerce, and Ashish Gupta, VP and GM of Merchant Shopping.
According to that post, UCP was co-developed with Shopify, Etsy, Wayfair, Target and Walmart, and endorsed by more than 20 partners including Adyen, American Express, Best Buy, Flipkart, Macy’s, Mastercard, Stripe, The Home Depot, Visa and Zalando.
The problem it solves is the N x N integration mess. Every new AI shopping surface used to mean another bespoke build. UCP collapses that into one integration point. Businesses publish a JSON manifest at /.well-known/ucp listing the services and capabilities they support. Agents read it and discover what your store can do without any hardcoded setup.
Three things in the spec are worth knowing:
- Capabilities are the building blocks: checkout, discount, fulfillment, product discovery, order management.
- Payments are modular. UCP separates what a consumer pays with from who processes it, so it works with your existing processor. Google’s post states every authorization is backed by cryptographic proof of user consent.
- Transport is flexible. UCP supports REST APIs, Agent2Agent (A2A) and the Model Context Protocol (MCP), so you are not locked into one plumbing choice.
What to do: read the spec on the UCP GitHub repository before your platform vendor tells you what it means. Ten minutes with the manifest example will tell you more than any vendor deck.
You do not have to give up your checkout
This is the part most merchants get wrong when they first hear about agentic checkout.
Google’s developer post is explicit: with UCP you own your business logic and you remain the merchant of record. There is also an embedded option that lets you keep a fully customized checkout experience from day one. The Google Marketing Live announcement made the same point twice, noting shoppers can either buy through Google Pay or transfer items to the merchant’s site to finish, and that the retailer always remains the merchant of record either way.
OpenAI’s Agentic Commerce Protocol takes a similar position. Its developer documentation states plainly that OpenAI is not the merchant of record, that merchants bring their own payment service provider, and that the merchant validates, calculates tax, runs risk analysis and accepts or declines the order on their own systems.
So the fear that these protocols hand your customer relationship to a platform is not what the specs describe. What you do lose is control of the browsing experience. The comparison, the upsell, the merchandising, the trust signals you spent years tuning on your product page: an agent may skip all of it and read your feed instead.
What to do: stop treating your product detail page as the only place your value gets communicated. If your differentiation lives in page design and copy that never enters your feed, an agent cannot see it. And before any of this, make sure your existing payment flow is clean. Our breakdown of the PCI rules quietly breaking modern checkout pages covers the compliance gaps that agentic flows will only make more visible.
Your product feed is now your storefront
To take part in Google’s UCP implementation, the developer guide states you need an active Merchant Center account and products that are eligible for checkout. No feed, no cart placement. It is that blunt.
Google also shipped two things at Marketing Live aimed squarely at feed quality. Retailers globally can now use conversational attributes to write product descriptions that match how people actually phrase questions. And a new AI performance insights tool in Merchant Center shows how your brand performs on AI surfaces compared with similar brands, rolling out in Australia, Canada, India, New Zealand and the United States in the coming months.
Share of voice against competitors on AI surfaces is a metric that did not exist eighteen months ago. It will be in someone’s board deck by Q4.
What to do this week:
- Audit your Merchant Center feed for checkout eligibility, not just listing eligibility. They are different bars.
- Rewrite your top 50 product descriptions the way a customer would ask for the product out loud, not the way a category manager would file it.
- Get your structured data in order. Feeds and schema are two views of the same catalog truth, and our guide to writing Schema.org markup that AI systems actually parse walks through the markup that carries weight now.
- Check that inventory and pricing sync in near real time. Agents transact on live data. A stale feed becomes a cancelled order, and cancelled orders are how you get deprioritized.
Where this is going next
Google said UCP-powered checkout will roll out in Canada and Australia in the coming months and later in the United Kingdom. It is also expanding beyond retail into hotel booking and local food delivery, with hotel bookings coming to AI Mode in Search and food delivery to conversations in Google Maps.
On the ads side, brands with UCP integrated will be able to attach instant buying to Direct Offers promotions and to Shopping ads on YouTube through Demand Gen campaigns. Affirm and Klarna buy now, pay later options are being embedded directly into Google Pay.
That last detail is the one to watch. When checkout moves into the ad unit, the gap between impression and order collapses. Attribution models built around session-based journeys will start returning numbers that do not make sense.
The honest caveats
A few things nobody can tell you yet.
There is no public data on what share of retail revenue actually flows through agentic checkout today. Announcements describe availability, not volume. Anyone quoting you a conversion lift from agentic commerce right now is extrapolating, not measuring.
Two competing standards also means two integration paths, and the industry has not settled on one. Google’s UCP and OpenAI’s ACP overlap heavily in intent but differ in implementation. If you build for one, budget for the second.
And “in the coming months” is doing a lot of work in these announcements. Several features described above were not fully live at the time of Google’s May post.
The takeaway
Agentic commerce is not going to kill your store. It is going to demote your storefront from the main stage to a backend. The retailers who win the next two years are the ones whose catalog data is clean enough to be read by a machine that never sees their homepage.
Fix the feed. Keep the merchant of record. Watch the share of voice number when it lands in Merchant Center. That is the entire playbook for now, and most stores are not doing the first one.
Sources
- Google, “How we’re helping retailers thrive with new Universal Commerce Protocol features and AI tools on Google,” The Keyword, May 20, 2026 — blog.google
- Amit Handa and Ashish Gupta, “Under the Hood: Universal Commerce Protocol (UCP),” Google Developers Blog, January 11, 2026 — developers.googleblog.com
- OpenAI, “Key concepts — Agentic Commerce,” OpenAI Developers documentation — developers.openai.com
- Universal Commerce Protocol specification and samples, GitHub — github.com/universal-commerce-protocol
- Google Merchant Center UCP integration guide — developers.google.com/merchant/ucp
Last reviewed: July 27, 2026
Related guides
- How to Prepare Your Store for AI Shopping Agents
- Stores Running Their Own AI Agents Grew 59% Faster
- Schema.org for LLMs: Structured Data That Trains AI
- Your Checkout Page May Be Breaking PCI Rules Right Now
Affiliate disclosure: this site may earn commissions from some links on this page, at no extra cost to you. It does not influence which tools or platforms we cover.
