Google's Universal Cart tells the retailer nothing until the shopper clicks transfer

Google launched Universal Cart in the U.S. on October 15, 2026, one cart in AI Mode and the Gemini app that holds products from many retailers.¹ Google’s developer guide says the retailer hears nothing while a shopper fills it, because Google keeps the items and calls the retailer once, at transfer.⁴ Until then, the save-to-cart moment your abandoned-cart emails depend on stays with Google.

Google sends a retailer one cart request per Universal Cart, at the moment the shopper clicks transfer, and none while the shopper is adding items.

What did Google launch with Universal Cart?

Universal Cart is a shopping cart that Google hosts across AI Mode in Search and the Gemini app, launched in the U.S. on October 15, 2026. It saves products from several retailers in one place, alerts the shopper to price drops and restocks, and suggests a payment card and promo codes. It then checks out with Google Pay or sends the items to the retailer’s own cart.¹

Google’s post names Nike, Sephora, Target, Ulta Beauty, Walmart, Wayfair “and many Shopify merchants” as checkout partners. Whichever path the shopper takes, confirmations and customer support come from the retailer, which remains “the seller of record.”¹

Two Google systems sit underneath. The Shopping Graph, the product index Google describes as “60+ billion continually refreshed product listings,” runs the alerts, and Google Wallet, which “understands your card perks,” runs the payment suggestions.¹

Is Google’s Universal Cart an agentic commerce product?

Google files Universal Cart outside its agentic commerce work. The October 15 launch post splits Google’s commerce efforts into two fronts, “agentic capabilities that act on your behalf” and “practical tools that give shoppers confidence and control,” and says Universal Cart “is built for that second track.”¹ The shopper adds every item and approves every purchase.

That framing changed between May and October. Google introduced the cart at its I/O conference on May 19, 2026, under the line “We’re building the foundation for agentic commerce,” and called it “the next step that brings this all together.”² I compared the two posts line by line on October 16. The launch came about a season later than promised, and four features the preview described are absent from the launch post.

What the May 19 preview said	What the October 15 launch post says
Works in Search, Gemini, YouTube and Gmail, with “YouTube and Gmail to follow”	Search and the Gemini app
“Rolling out across Search and the Gemini app in the U.S. this summer”	Launched October 15
Gives “insights on price history”	Price-drop and restock alerts, with no price history named
Flags incompatible products, such as computer parts that will not fit together	Not mentioned
Wallet knows “payment method perks, loyalty information and merchant offers”	Wallet knows card perks; loyalty is not named

Sources for the table: the preview² and the launch post.¹

Google’s developer guide for native checkout, the path where the purchase happens on Google instead of the retailer’s site, is consistent with that framing. “Initially, Google will render the user interface for the buyer, with future plans to support more agentic experiences,” it says. Once payment starts, “The Agent is not involved in this part, ensuring determinism.”⁸

My read: absence from a launch post does not prove a feature is missing. What the two posts do confirm is the framing. The May preview called this agentic, while the product that shipped is a cart a person fills by hand on Google’s surface. So the levers a retailer has are the ones it already owns, its feed and its checkout integration.

What does a merchant see when a shopper adds a product to Universal Cart?

A merchant sees nothing when a shopper adds its product to Google’s Universal Cart. Google’s Cart API reference says that “Google accumulates those items locally” and “does not fire multiple API calls as items are added.”⁴ The merchant’s cart endpoint, the address on its server that takes Google’s request, receives one request, carrying all the saved items at once, and only “when the user clicks the transfer button.”⁴

The guide also limits what that request can do. “This initial release is limited to cart creation and transfer,” the overview says, and “updating, deleting, or synchronizing cart contents between Google and your system are not supported.”³ So the data flows one way. Your system answers with a link, which Google calls the continue_url, pointing to a cart on your site already filled with those items.⁴

One page disagrees at the edges. Merchant Center’s test environment lists optional tests for reading, updating and canceling a cart beside the test for creating one.⁵ My read: the test tooling is ahead of the shipped feature, because the overview rules out updates in this release.

Google’s reporting starts at the transfer. Merchant Center’s dashboard for the Universal Commerce Protocol (UCP), the open standard Google’s cart and checkout use to call a retailer’s systems, lists seven metrics, and the first is “Clicks to Buy.”⁶ The Merchant API’s alpha report for the same data adds cart_transfers, average cart value and average items per cart.¹¹ Neither report counts a product saved to the cart.

A shopper who saves your product on Monday and transfers on Friday reaches your analytics as a Friday visitor who arrived with a full cart. A shopper who saves it and never transfers appears in no report you can open. The API reference confirms that nothing reaches your server before transfer, and neither report Google documents has a metric for saves.

Where do Universal Cart’s price alerts and promo codes come from?

Universal Cart’s price alerts run on Google’s Shopping Graph, and Google’s checkout guide names Merchant Center feeds as a source of the promotions it applies on its own. The Shopping Graph works “in the background, sending notifications about price drops or when an item comes back in stock.”¹ For a retailer, that means every price drop or restock Google records can become a message to each shopper who saved the item.

Google has not said what size of drop triggers an alert, so treat any threshold as unknown. Suspected, not confirmed: a sale price that has ended in your store but still sits in Google’s copy of your data could trigger a price-drop alert, and the shopper then lands on a higher price.

Google’s guide to promo codes in UCP checkout names two sources of promotions. “Auto-applied promotions” are “Offers ingested directly from your Google Merchant Center feeds,” which Google “automatically applies,” while “user-applied promotions” are codes the shopper types in.⁷ The checkout accepts up to 10 typed codes per session.⁷

That guide covers checkout sessions, and the cart is a step earlier. The launch post says the cart shows “relevant promo codes right from the cart” and does not say where those codes come from.¹ Unconfirmed: whether a code you never gave Merchant Center can appear there. Wallet’s card suggestion is the one part of the cart a retailer has no input into at all.

Which Universal Cart checkout path should a merchant choose?

Merchant Center’s UCP integration hub gives a merchant two checkout paths for Universal Cart. Transfer to merchant cart sends the items to the retailer’s own site and needs only the cart endpoint. Native checkout on Google keeps the purchase on Google with Google Pay, and needs three checkout endpoints, order-status updates and an accepted program addendum.⁵ The hub is rolling out gradually in the U.S.

The two paths differ in what they ask of your feed as much as your code.

	Transfer to merchant cart	Native checkout on Google
Where the purchase happens	Your own site	Google, with Google Pay
What you build	One cart endpoint	Three checkout endpoints, plus order-status updates sent to Google
What the feed needs	Matching product identifiers; Google says this path “doesn’t require full product feed setup, product warnings, or customer support information”	A native_commerce(checkout_eligibility) attribute set to true on each product, plus return policy and support contact in Merchant Center
Products left out	None listed	Subscriptions, personalized goods, final-sale and pre-order items, age-restricted goods and others
Who renders the checkout	You	Google

Sources for the table: the Merchant Center integration guide⁵ and the account preparation guide.⁹

Google describes cart transfer as the path that “Minimizes implementation effort to accelerate UCP integration,”⁵ and it keeps your checkout tracking on your own pages. A product you never flag stays out of native checkout, because the eligibility attribute “defaults to FALSE.”⁹

I checked which path some launch merchants declare. A store’s UCP profile is a public file at /.well-known/ucp listing what it supports. On October 16 I fetched it for eight of the merchants Google named across its two posts. Two returned a profile.¹⁰

Steve Madden and Fenty Beauty, both Shopify stores, publish the same list of 11 capabilities, the features a store tells Google it supports. The list includes the cart capability, the checkout capability and a Google Pay payment handler, so both stores declare support for both paths. Two stores cannot show what every Shopify store publishes, though the identical lists suggest Shopify generates the file.

The other six, Nike, Target, Ulta Beauty, Walmart, Wayfair and Quince, returned 404 (not found) at that path. Merchant Center asks each merchant where its profile lives, so a 404 at the standard path says the file is elsewhere, absent or blocked from my connection, and nothing about whether the retailer is integrated.⁵ Google’s cart guide does tell merchants to publish the profile at that path, which makes the six misses worth a second look from a different connection.³

The Steve Madden and Fenty Beauty profiles both list the August release (2026-08-25) first and still support the April one (2026-04-08). The April release is the version Google’s Cart API guide tells merchants to handle.³ The August release rewrote fulfillment, consent and signing fields, covered in the UCP release that breaks the schema you integrated. A merchant building to Google’s guide in October 2026 builds to the older shape.

What should a merchant do before the holiday season?

A merchant preparing for Google’s Universal Cart this holiday season has five jobs, and three of them sit in Merchant Center. Choose a checkout path, keep feed prices and availability current, load promotions where Google reads them, mark the cart transfer in your own analytics, and size the cart endpoint for peak traffic.

1. Choose a path in Merchant Center’s UCP hub. If you sell subscriptions, personalized goods or final-sale items, cart transfer is the only path those products can take.
2. Audit how fast feed price and availability changes reach Merchant Center. They may drive alerts to shoppers who saved the product, so a lag could turn into a wrong notification.
3. Load your holiday promotions into Merchant Center. That is the source Google’s checkout guide names for offers it applies on its own.⁷
4. Tag the continue_url. Your server writes that link, so add a parameter that marks the session as a Universal Cart transfer. Without one, a shopper arriving from Google with a full cart lands in your reports as ordinary Google or direct traffic, the same blind spot ChatGPT’s untagged citation links created.
5. Size the cart endpoint for peak traffic. Google recommends answering “ideally in under one second” and returning a 429 (too many requests) response when traffic exceeds your limits.³ What happens when a transfer is retried is covered in whether agentic checkout protocols require idempotency keys.

The tag is the cheapest item on that list, and it decides whether you can measure anything later. Add the parameter the day you switch the capability on, because a transfer that arrives untagged cannot be told apart afterward.