Google Universal Cart: How It Works and What Retailers Still Own

Google's Universal Cart launched in the U.S. on October 15, 2026, in Google Search and the Gemini app. A shopper can save products from different retailers in one cart, get alerts on price drops and restocks, then pay with Google Pay on Google or move the items to the retailer's own cart.

The easy reading is that Google is becoming the store. The documentation supports a narrower one: Universal Cart separates ownership of the shopping state from ownership of the transaction. Google holds the list of what a shopper is considering. The retailer still sells the product.

What Google Universal Cart is

Google's launch post describes four things the cart does:

• saves products from multiple retailers in one place, across Google's shopping surfaces;
• sends notifications about price drops and restocks, drawing on the Shopping Graph's more than 60 billion product listings;
• shows relevant promo codes and, because it is built on Google Wallet, suggests which of the shopper's cards to use;
• lets the shopper check out with Google Pay or transfer items to the merchant's site.

Google frames it as a shopping tool, not an agent acting for the shopper. The shopper adds items and decides when to buy.

Where Universal Cart is available

At launch, Universal Cart is U.S. only, in Google Search, including AI Mode, and the Gemini app. Google's help page on managing the cart notes that Gemini and AI Mode have limited access to it, so they may not list its contents or order updates inside a chat.

When Google announced the cart at I/O in May, it said YouTube and Gmail would follow. The October launch post does not mention either, so neither should be treated as live.

Can it hold items from different retailers?

Yes, and products in the cart are grouped by merchant. But "universal" describes the cart, not the payment. A native checkout session is created with one merchant's system and can hold several of that merchant's items. Google documents no payment covering several retailers, so a cart with items from three stores means up to three separate purchases.

Google does not say which products can be saved, or what checkout looks like for a merchant that supports neither path.

How checkout works: two paths

Checkout on Google. For participating merchants, the shopper pays with Google Pay inside Google's interface. This is native checkout through the Universal Commerce Protocol: Google opens a checkout session with the merchant's system, and the merchant returns prices, taxes and shipping, then charges the payment through its own payment provider. It is limited to select merchants in an early access program, and only products marked eligible in the feed show the Buy button. Google's Merchant Center requirements exclude subscriptions, personalized goods, pre-orders, final-sale items and age-restricted products.

Transfer to the merchant's cart. For other merchants, Google fills a cart on the merchant's own site and the shopper finishes there. The Cart API overview explains the mechanics. Google holds items as the shopper adds them, without calling the merchant. When the shopper clicks to transfer, Google sends one request with every item, and the merchant returns a link to a prefilled cart. The transfer is one-way: updating, deleting or syncing the cart is not supported in this first release. Merchants can offer transfer without building native checkout.

What is UCP, and how is it different from Universal Cart?

UCP is the plumbing and Universal Cart is the product. The Universal Commerce Protocol is an open standard Google co-developed with retailers that defines how Google's surfaces talk to a merchant's systems: opening a checkout, transferring a cart, linking an account, reporting an order. A merchant integrates with UCP. A shopper uses Universal Cart.

Many merchants may already be connected. Google lists many Shopify merchants among participants, and Shopify turns on direct checkout for Google's AI surfaces by default for eligible stores, as I covered when agentic commerce became a platform default.

Does Google become the Merchant of Record?

No. Google's launch post says the merchant remains the seller of record on both paths, and that confirmations and customer support come from the merchant. The UCP FAQ for developers states it directly: "you remain the Merchant of Record."

In checkout on Google, the merchant's terms of sale apply. It checks inventory in real time, validates shipping addresses, and must publish a return policy and support contacts in Merchant Center.

Does the retailer keep customer data?

For a completed purchase, yes. In native checkout, Google passes the buyer's name, email, phone and shipping details to the merchant, and Google's FAQ says the merchant owns the transaction data and the customer relationship. After a cart transfer, the merchant collects data at its own checkout as usual.

Two qualifications matter. Checkout on Google is guest checkout unless the merchant builds identity linking, so loyalty accounts do not connect by default. And an option for shoppers to opt in to marketing during checkout is, per the FAQ, still planned.

What the merchant does not get is the cart. Saved items live in the shopper's Google Wallet, and Google's UCP reporting counts checkout activity and cart transfers, not products saved. A retailer cannot see that its jacket has sat in a shopper's cart for two weeks next to a competitor's.

How order tracking works

After a purchase, shoppers can follow orders in a My Orders tab, but only when the merchant shares order data. For native checkout, the order lifecycle guide requires merchants to send order created, shipped and delivered updates, with tracking, to Google. For purchases finished on a merchant's site, Google says some merchants do not share data back.

Google keeps My Orders data until the user deletes it, and the merchant's retention policies govern its copy. After the purchase, both hold a record of the order.

What Google does not disclose

Google's launch post, help page and the developer documentation I reviewed do not mention merchant fees, commissions or a revenue model. Google's FAQ says choosing native checkout does not change how offers rank, but Google has not said whether saved items affect ads or ranking, or given dates for YouTube, Gmail or two-way cart sync.

What Universal Cart means for ecommerce brands

A meaningful part of late-stage consideration used to become visible only after the shopper reached the retailer's own cart or wish list. For Universal Cart shoppers, it sits in Google Wallet, where Google tracks price changes, surfaces relevant promo codes, and can suggest which saved card to use. The retailer receives the cart at the end.

That is not a takeover. The merchant still sets prices, holds inventory, takes the payment and owns the order, the division of labor I described in what the retailer still owns when checkout moves. What moves is the early signal: what a shopper is weighing, how long they hesitate and which promotion finally moved them.

A few practical steps follow:

• Decide whether you want native checkout, cart transfer or both. AI Commerce 2027 treats these as separate postures with different tradeoffs.
• If you offer transfer, make the landing cart fast and complete. Google recommends answering the transfer request in under a second.
• Reconcile transfers against completed orders on your site, because Google's UCP reporting counts transfers, not the purchases that follow.
• Keep prices and availability in Merchant Center accurate, since changes now trigger alerts in someone else's interface.

If a shopper's cart lives with Google until the moment they buy, what does your site need to do in the minute after the transfer arrives?