What Google launched on October 15
Google started rolling out Universal Cart in the US on October 15, 2026, across Google Search and the Gemini app, according to Google’s announcement. Shoppers can save products from many retailers into one cart, and the items stay there as they move between Search and Gemini. Google first showed the tool at Google I/O in May, as TechCrunch reported.
The cart watches what shoppers save. Google says it sends alerts when a price drops or an out-of-stock item comes back, using its Shopping Graph of “60+ billion continually refreshed product listings.” It also shows promo codes and suggests which card to pay with based on card perks. The cart is built on Google Wallet.
How checkout works for the retailer
Universal Cart is powered by the Universal Commerce Protocol (UCP), the open standard Google introduced earlier this year for AI agents and retailers. Google describes two ways to finish a purchase. The shopper can pay with Google Pay inside the cart, or move the items to the retailer’s own cart and finish on the retailer’s site. Google names Nike, Sephora, Target, Ulta Beauty, Walmart and Wayfair among the merchants offering these paths.
In both cases the retailer stays the seller of record, and Google says buyers get “direct confirmations and customer support from the merchant.” In practice your order pipeline has to accept these orders the same way it accepts web orders, and your support team will hear from buyers who never saw your checkout page.
What Merchant Center requires
Google’s Merchant Center help article on UCP-powered checkout describes a Buy button on product listings in AI Mode in Search and in Gemini, with the checkout happening on Google’s surface. It applies to products eligible in the United States, Canada and Australia, and is limited to select merchants for now. Google says the protocol “will be available in phases.”
- Only listings with the native_commerce(checkout_eligibility) product attribute show the Buy button.
- Payment uses card numbers stored in Google Wallet, so you need a Google Pay and Wallet Console account.
- If your payment service provider is not integrated with the Google Pay API, the provider has to onboard. Processing without a PSP requires encryption setup and PCI compliance documentation.
- To join, you confirm the requirements, submit an interest form, complete the technical implementation and then set up product data.
The UCP integration hub guide says the Merchant Center hub is gradually rolling out in the US, with Australia and Canada to follow. It lets you test in sandbox and production and validate each checkout operation: creating a checkout, updating shipping, completing a transaction and transferring items to your own cart. Merchants who work with a platform or service provider are told to ask that provider about its UCP plans.
The developer work behind the Buy button
The UCP developer overview lists the parts. Merchant Center needs shipping, returns and a product feed configured, and Google must approve the integration before it goes live in AI Mode and Gemini. You publish a UCP profile, which Google reads to find your payment handlers and the public keys it uses for signature verification. Native checkout also needs the Google Pay payment handler and an order lifecycle integration that pushes order updates back to Google.
Identity linking through OAuth 2.0 is optional. Without it, purchases run as guest checkout. Promo codes and discounts are an optional extension, which matters if your margins depend on coupon rules that live in your cart.
On a custom or headless build, such as Adobe Commerce with a separate storefront or a B2B ordering portal, this means new endpoints that call your existing cart, tax, shipping and order services. In our view it is closer to adding a sales channel than adding a payment method, and it should be estimated that way.
What we would check before applying
Start with the feed. If Merchant Center disapprovals, missing shipping settings or stale prices are already a problem, a Buy button puts them in front of buyers who never visit your site. Then ask your PSP whether it accepts Google Pay today and what onboarding it needs.
- Can your tax and shipping calculations be called by API for a cart that was never created on your site?
- How will orders from Google be tagged in your order management system or ERP so finance can reconcile them?
- Which products should be eligible? The attribute is set per listing, so you can start with simple stock items and leave out made-to-order or freight products.
- Does your platform vendor or agency have a UCP integration planned? Google sends platform merchants there first.
Once those answers are written down, submit the interest form linked from Google’s help article and book the sandbox testing in the Merchant Center hub when your account gets access.





