Google’s Universal Cart is live: how a shopper’s saved cart reaches your store, and what you control

Google’s Universal Cart went live in the US on 15 October, in Search and the Gemini app. Shoppers can now save products from different stores into one cart that sits in Google Wallet, get price-drop and back-in-stock alerts on them, and check out later. You don’t sign up for the cart itself. What you do control is how a saved cart ends up at your store. There are three ways. Selected merchants let shoppers pay with Google Pay inside the cart. Selected merchants can also receive the cart pre-filled on their own site. For everyone else, Google says it “helps you populate your cart on the merchant’s website,” and doesn’t say how. Here’s what Google has published, what I found when I checked real stores, and what to do before the holiday rush.

What Google launched

Google’s launch post, An intelligent new shopping cart (15 October 2026), says: “Today, Universal Cart is rolling out in the U.S. across Google Search and in the Gemini app.” YouTube and Gmail, named when Google previewed the cart in May, aren’t part of this launch.

For a merchant, three lines in the post matter:

• Where the data comes from: “The cart is built on the 60+ billion continually refreshed product listings in Google’s Shopping Graph.” Your Merchant Center feed is the main way your products get into the Shopping Graph, so the price and stock a shopper gets alerted about come largely from your feed. That’s my inference. Google doesn’t spell it out for the cart.
• How it ends: “You can securely check out with Google Pay in just a few taps with many of your favorite stores right in the cart, or you can transfer your items directly to the merchant’s cart to finish buying on their site.”
• Who owns the sale: shoppers “will receive direct confirmations and customer support from the merchant, and they will remain the seller of record.”

The merchants Google names are Nike, Sephora, Target, Ulta Beauty, Walmart, Wayfair “and many Shopify merchants.”

The three ways a cart ends

Google’s consumer help page, Manage your universal cart, spells out the split. “Check out with Google Pay: For participating merchants, you can complete your transaction on Google using your saved payment methods. Check out on the merchant site: For other merchants, Google helps you populate your cart on the merchant’s website so you can complete the purchase there.”

A. Pay on Google. This is the native checkout that runs on Google’s Universal Commerce Protocol (UCP). Google’s Merchant Center page on UCP says it is “available for select merchants at this time,” and “Only product listings using the native_commerce(checkout_eligibility) product attribute will display the ‘Buy’ button.” Payment happens on Google, but “the checkout happens directly on Google’s surfaces while keeping you the merchant of record.” If you’re on Shopify, this is probably the route you’re already on. Shopify switched direct checkout on Google on by default for eligible US stores in September, as I covered in the four-channel map. That’s my reading of why Google says “many Shopify merchants”. Google doesn’t say it.

B. Cart transfer. This one is new, and it’s the one built for this cart. Google’s Cart API guide describes it as “a one-way population of the cart on your system, primarily through the CreateCart endpoint.” When a shopper chooses to move their items to your site, Google sends you the line items, and you send back a link to a cart that’s already filled in. The shopper pays on your own checkout. Two details stand out. “Native checkout is a distinct API and is not required for implementing Cart transfer,” so you can offer this without letting Google take payment. And you need “UCP version 2026-04-08” with a profile at /.well-known/ucp that declares the dev.ucp.shopping.cart capability.

Building it isn’t enough on its own. Google’s onboarding page for the UCP hub in Merchant Center lists three steps: do the technical work first, fill in the interest form, and then wait: “As soon as you’re selected to participate, we’ll notify you.” The hub is “gradually rolling out in the U.S., with Australia and Canada to follow next year.”

C. Everyone else. If you’re in neither group, Google’s help page still promises the shopper a route to your site. It doesn’t say what that route is. I couldn’t find a Google page that explains it, so I won’t guess. The safe assumption is that a shopper who saved your product arrives on your site and has to add it to the cart again. That’s one more step than for the merchants in groups A and B.

What I found when I checked real stores

A UCP profile is a public file, so you can check whether a store has the technical half of cart transfer in place. On 16 October I requested /.well-known/ucp from 18 stores, using an ordinary browser user agent. Three of them (Coach, Kate Spade and Bombas) blocked or rate-limited the request, so they aren’t in the table.

Every standard Shopify store I tried returned a profile, and every one declared the cart capability. That includes Steve Madden, the one Shopify brand Google named in its launch post. Each profile also lists the 2026-04-08 version that Google’s Cart API asks for. Shopify publishes it for them. The two headless Shopify stores I tried, Gymshark and Ruggable, returned “not found”, which matches what I saw earlier this month when headless stores got none of Shopify’s WebMCP tools.

None of the big non-Shopify retailers Google named (Nike, Target, Walmart, Wayfair, Ulta and Quince) served a profile at that address. That doesn’t mean they’re not connected. Large retailers can integrate with Google directly, and Sephora’s address redirected me to its German site, so I couldn’t test it. The point for a smaller store is simpler. On Shopify, the technical prerequisite is already done. A profile still doesn’t tell you whether Google has switched cart transfer on for that store. Only Merchant Center can tell you that.

WooCommerce is behind. WooCommerce’s own agentic commerce page, as I read it on 16 October, lists Google’s Universal Commerce Protocol as “Coming soon,” adding: “If you already sync to Google Merchant Center or use structured data, you have the foundation.” Some third-party plugins on WordPress.org say they add UCP endpoints, including a cart. I haven’t tested any of them, and Google still needs to select you, so a plugin alone won’t get you into groups A or B. Google’s own advice if you sell through a platform: “please connect directly with them to learn more about their plans for Universal Commerce Protocol integration.” I mapped the other doors that are open to Woo stores here.

What to do this week

• Check your own profile. Open https://yourstore.com/.well-known/ucp in a browser. If you see JSON with dev.ucp.shopping.cart in it, the technical half of cart transfer exists. If you get a 404, you’re in group C for now.
• Keep price and stock exact in your feed. The cart’s alerts come from Shopping Graph listings. If your feed shows a price drop that your site doesn’t, or “in stock” when you’re sold out, the shopper hears about it from Google and finds out it’s wrong on your site.
• Make your cart and checkout easy to land on. Shoppers from groups B and C arrive mid-purchase. A cart page that loads fast and doesn’t force sign-in matters more now.
• Expect support questions about orders you didn’t see begin. Google is clear that order problems go to you: “To fix these issues, contact the merchant you made the purchase from.” It also says “Some merchants do not share data back to Google so these orders do not appear in the ‘My orders’ tab.” If you take payment on Google, make sure your team knows those orders exist.
• If you want cart transfer and you’re not on Shopify: it’s a build-then-apply process. Read the Cart API guide, publish the profile, then use the interest form in the UCP hub page.

The cart puts Google between the moment someone decides they want your product and the moment they pay. Google didn’t take the sale: you’re still the seller of record. What it now holds is the list of things people meant to buy from you. I’ll update this when Google documents what happens to stores in group C.