# Google Universal Cart explained: UCP checkout

Google’s Universal Cart saves products from many stores across Search and Gemini, then checks out with Google Pay or hands the cart to the store. Its status in Google’s own words, and what a merchant has to set up.

By Valerii Checha, 17 Nov 2026

"Today, Universal Cart is rolling out in the U.S. across Google Search and in the Gemini app." That is Google's own line from 15 October 2026, and it is about shoppers. For merchants the wording is more careful: Google's help page says the checkout feature behind it "is available for select merchants at this time."

Universal Cart is Google's shopping cart across Search and Gemini. It saves products from many retailers in one place, watches their prices and stock, and lets the shopper either pay with Google Pay inside the cart, through Google's UCP checkout, or move the items to the store's own cart to finish there. Checkout on Google is an early access programme; cart transfer needs a cart capability in the store's UCP profile. In both cases, Google says, the store "will remain the seller of record."

Google's own pages do not always agree with each other, so every status label below is quoted word for word from the page that states it.

## What is Google Universal Cart?

Google calls it "an intelligent shopping cart and your new hub for shopping on Google", previewed earlier in 2026 and launched in the US on 15 October. Its launch post lists four things it does:

- It saves "products from multiple retailers, wherever you're shopping on Google", so a handbag saved in AI Mode and a sweater saved in Gemini end up in one cart.
- It watches them. "The cart is built on the 60+ billion continually refreshed product listings in Google's Shopping Graph", and it sends "notifications about price drops or when an item comes back in stock".
- It looks for savings: it "is built on Google Wallet so it understands your card perks", and it shows "relevant promo codes right from the cart".
- It checks out, in one of two ways, covered below.

The third point concerns stores most. A cart that surfaces promo codes and compares a shopper's card perks is a cart that shops around on the shopper's behalf. Your discount codes may get more use than you planned, which is either a growth channel or a margin problem depending on how you set them up.

The cart runs on the Universal Commerce Protocol. Google's May post says it was shown at Google I/O with UCP and AP2, as part of its "vision for the future of agentic commerce". What UCP itself defines is in [UCP explained](https://storewalk.ai/blog/ucp-explained), and the glossary entry for [Universal Cart](https://storewalk.ai/blog/agentic-commerce-glossary#universal-cart) has the short version.

## Is Universal Cart available to every store?

Not yet, and the answer depends on which Google page you read. Each one has its own status words, so here they are page by page:

Universal Cart’s status, in the words of each Google page.

Announced (20 May 2026). Google’s words: “Our new Universal Cart is a truly intelligent shopping cart that works across retailers and across services like Search, Gemini and more.” “Shoppers can try these select checkout features soon”. And: “UCP-powered checkout will roll out across Canada and Australia in the coming months, and later to the U.K.” Our reading: An announcement with “soon” in it. The cart itself came later.

Source: [Google: New UCP features and AI tools for retailers (20 May 2026)](https://blog.google/products-and-platforms/products/shopping/shopping-updates-google-marketing-live/).

Launched for shoppers (15 Oct 2026). Google’s words: “Universal Cart launches in the U.S. today.” “Today, Universal Cart is rolling out in the U.S. across Google Search and in the Gemini app.” Our reading: For shoppers in the US, it is rolling out. Google’s word is “rolling out”, not “available to everyone”.

Source: [Google: Universal Cart launches in the U.S. (15 Oct 2026)](https://blog.google/products-and-platforms/products/shopping/universal-cart-launch/).

Checkout, for merchants (Merchant Center Help). Google’s words: “The checkout feature enabled by UCP is available for select merchants at this time.” “The protocol will be available in phases.” It applies to “products with eligibility in the United States, Canada, and Australia, and for participating merchants and partners.” Our reading: Checkout on Google is an early access programme with an interest form, not a switch every store can flip.

Source: [Google Merchant Center Help: UCP-powered checkout](https://support.google.com/merchants/answer/16837055?hl=en).

The Merchant Center hub (updated 19 Oct 2026). Google’s words: “the UCP integration hub is gradually rolling out in the United States, with Australia and Canada to follow early next year.” The onboarding help says “with Australia and Canada to follow next year.” Our reading: The tool for setting it up is itself rolling out, so some merchants will not see it yet.

Sources: [Google for Developers: UCP integration hub in Merchant Center](https://developers.google.com/merchant/ucp/guides/merchant-center/overview) and [Google Merchant Center Help: Onboard to the UCP integration hub](https://support.google.com/merchants/answer/16992327?hl=en).

The developer page (undated). Google’s words: “UCP unlocks access to users on surfaces like AI Mode in Google Search and Gemini web (app coming soon).” Its roadmap lists “upcoming features like multi-item carts, account linking for loyalty programs, and post-purchase support for tracking and returns.” Our reading: This page says the Gemini app is “coming soon” while the October post says the cart is rolling out “in the Gemini app”. We quote both and do not pick one.

Sources: [Google for Developers: UCP on Google](https://developers.google.com/merchant/ucp) and [Google: Universal Cart launches in the U.S. (15 Oct 2026)](https://blog.google/products-and-platforms/products/shopping/universal-cart-launch/).

Three statuses run side by side. For shoppers, the cart is "rolling out in the U.S." For merchants, checkout through UCP is "available for select merchants at this time", by interest form, and the help page covers "products with eligibility in the United States, Canada, and Australia". The Merchant Center hub that sets it up is "gradually rolling out in the United States, with Australia and Canada to follow early next year." In May, Google added that UCP-powered checkout would come to the U.K. "later".

One detail does not line up. The October post says the cart is rolling out "in the Gemini app", while Google's developer page lists "Gemini web (app coming soon)". We have not tested either, so we quote both. If you plan around Gemini, check the page you will rely on before you rely on it.

## How does a shopper check out from Universal Cart?

Two ways, and they ask very different things of a store:

Two ways out of Universal Cart, and what each needs from a store.

Check out with Google Pay. For the shopper: “You can securely check out with Google Pay in just a few taps with many of your favorite stores right in the cart”. The help page: the feature “uses standard Funding Primary Account Numbers (FPANs) that users have stored on their Google Wallet.” What you need: A UCP checkout integration, a Google Pay & Wallet Console account, early access, and products marked with native_commerce(checkout_eligibility) TRUE: “If set to FALSE or missing, the product won’t be eligible for checkout”. Our reading: The harder path, and the one where the whole purchase happens on Google’s surface while you stay the seller.

Sources: [Google: Universal Cart launches in the U.S. (15 Oct 2026)](https://blog.google/products-and-platforms/products/shopping/universal-cart-launch/), [Google Merchant Center Help: UCP-powered checkout](https://support.google.com/merchants/answer/16837055?hl=en) and [Google for Developers: Prepare your Merchant Center account](https://developers.google.com/merchant/ucp/guides/overview/merchant-center).

Move the cart to your site. For the shopper: “or you can transfer your items directly to the merchant’s cart to finish buying on their site.” What you need: “products approved for free listings in Google Merchant Center are automatically eligible for cart transfer once dev.ucp.shopping.cart is declared in your UCP profile.” It is opt-out: “eligible products are included by default unless explicitly excluded.” Our reading: The lighter path: a cart capability in your UCP profile, and the shopper pays in your own checkout. Our DISC-021 reports whether your profile declares the cart family.

Sources: [Google: Universal Cart launches in the U.S. (15 Oct 2026)](https://blog.google/products-and-platforms/products/shopping/universal-cart-launch/), [Google for Developers: Prepare your Merchant Center account](https://developers.google.com/merchant/ucp/guides/overview/merchant-center) and [Storewalk: DISC-021, UCP capability families declared](https://storewalk.ai/checks/DISC-021).

Paying in the cart is the full agentic path: the shopper never visits your site, Google Pay supplies a card "stored on their Google Wallet", and your systems take the order through UCP. It needs the early access programme, a Google Pay & Wallet Console account and a UCP checkout integration. Google's developer page offers it as "Native checkout", with an "Embedded checkout" option reserved for "specific, approved merchants".

Moving the cart to your site is lighter. Products approved for free listings become eligible "once dev.ucp.shopping.cart is declared in your UCP profile", and from then on they are included unless you opt them out. The shopper lands in your checkout with the items already in the cart, which is how a cart is supposed to behave anyway. [Publishing a UCP profile](https://storewalk.ai/guides/publish-a-ucp-profile) covers the profile side, and our [DISC-021](https://storewalk.ai/checks/DISC-021) reports which capability families yours declares, cart among them.

## How does a product get a Buy button in Universal Cart?

It takes a product attribute in Merchant Center. Google's help page is precise: "Only product listings using the native_commerce(checkout_eligibility) product attribute will display the "Buy" button for this checkout experience." The developer page adds that a missing value means no: "If set to FALSE or missing, the product won't be eligible for checkout (defaults to FALSE )."

Some products cannot be bought this way at all. Google lists categories "ineligible for checkout", among them subscriptions, personalised goods, used and "Final Sale" items, pre-orders, freight and premium delivery, age-restricted items and virtual goods. Pick a product and the features you use, and the builder writes the value:

A native_commerce builder: the feed value for one product.

On the page, you pick the product’s category, whether you are in Google’s checkout programme, whether your UCP profile declares dev.ucp.shopping.cart, and whether this product may move to your cart, and copy the feed value. Some cases:

A new item, checkout and cart transfer both on. Checkout on Google: Eligible: set checkout_eligibility to TRUE. Missing means FALSE. Cart transfer: Included by default (opt-out model).

```
native_commerce(checkout_eligibility:cart_eligibility)
TRUE:TRUE
```

```xml
<g:native_commerce>
  <g:checkout_eligibility>TRUE</g:checkout_eligibility>
  <g:cart_eligibility>TRUE</g:cart_eligibility>
</g:native_commerce>
```

A personalised item, both on. Checkout on Google: Not eligible. Google lists the category: “Personalized goods: items requiring custom design decisions (e.g., engravings, monograms).” Set checkout_eligibility to FALSE. Cart transfer: Included by default (opt-out model). Google’s list covers checkout and does not say whether it also excludes cart transfer.

```
native_commerce(checkout_eligibility:cart_eligibility)
FALSE:TRUE
```

```xml
<g:native_commerce>
  <g:checkout_eligibility>FALSE</g:checkout_eligibility>
  <g:cart_eligibility>TRUE</g:cart_eligibility>
</g:native_commerce>
```

A new item, checkout only (no cart capability declared). Checkout on Google: Eligible: set checkout_eligibility to TRUE. Missing means FALSE. Cart transfer: Off: cart transfer starts only “once dev.ucp.shopping.cart is declared in your UCP profile”.

```
native_commerce(checkout_eligibility)
TRUE
```

```xml
<g:native_commerce>
  <g:checkout_eligibility>TRUE</g:checkout_eligibility>
</g:native_commerce>
```

A new item, cart transfer only, opted out. Checkout on Google: Not offered: you are not in the checkout programme, so the product shows no Buy button. Cart transfer: Opted out with cart_eligibility FALSE.

```
native_commerce(cart_eligibility)
FALSE
```

```xml
<g:native_commerce>
  <g:cart_eligibility>FALSE</g:cart_eligibility>
</g:native_commerce>
```

The categories Google lists as ineligible for checkout, in its words: “Subscriptions: products requiring recurring billing cycles.” “Personalized goods: items requiring custom design decisions (e.g., engravings, monograms).” “Non-new or final sale items: refurbished goods, used items, and items marked as “Final Sale” (no returns).” “Pre-order items: products with future release dates and deferred fulfillment.” “Special shipping: items requiring non-standard delivery fees (e.g., freight, premium delivery).” “Age restricted: items requiring ID verification (e.g., Alcohol, Tobacco).” “Virtual items: in-game currency, MMORPG goods, or skins.”

Google: “The native_commerce attribute group is fully overwritten with each upload and does not support incremental updates”, so every upload must carry every flag, and it suggests a supplemental feed. Our scan does not read your Merchant Center feed.

Source: [Google for Developers: Prepare your Merchant Center account](https://developers.google.com/merchant/ucp/guides/overview/merchant-center).

Two rules on that page are easy to miss. If you use both checkout and cart transfer, you "must use the composite format", one value of two booleans joined by a colon, such as `TRUE:FALSE`. And "The native_commerce attribute group is fully overwritten with each upload and does not support incremental updates", so a feed that sends only one flag erases the other. Google suggests a supplemental feed, which keeps these flags away from your main product data.

If you sell on a platform, Google's onboarding help says to ask the platform first: "please connect directly with them to learn more about their plans for Universal Commerce Protocol integration." Google's launch post mentions "many Shopify merchants" among the stores you can check out with.

## Who is the seller of record in Universal Cart?

The store, whichever way the shopper pays. The launch post: "Either way, you will receive direct confirmations and customer support from the merchant, and they will remain the seller of record." For US checkout, Google's Checkout Addendum spells out what that means for tax, payments, fulfilment and support, and our [merchant of record article](https://storewalk.ai/blog/merchant-of-record-agentic-commerce) quotes it line by line.

One practical consequence: your return policy and support details travel into Google's checkout. Google's product data page says return policies are "a Merchant of Record requirement and will be referenced on the checkout screen". A shopper who never saw your site will still read your returns window, so make sure it is the one you honour.

## How should a store prepare for Universal Cart?

Begin with the part that needs no application. Publish a valid UCP profile that declares the cart capability, keep Merchant Center's free listings approved, and set `native_commerce(cart_eligibility)` to `FALSE` on anything you do not want moved into your cart. Google's Merchant Center hub then asks you to test your cart endpoints in its sandbox, and the hub is still rolling out.

Then decide on checkout. If you want shoppers to pay inside the cart, the route is Google's interest form, a UCP checkout integration and a Google Pay & Wallet Console account, or your platform's own plan if it has one. Products in Google's excluded categories stay out either way.

Our scan covers the profile side: [DISC-018](https://storewalk.ai/checks/DISC-018) validates your UCP profile against its schema, DISC-021 reports the capabilities it declares, and [DISC-023](https://storewalk.ai/checks/DISC-023) checks that robots.txt lets agents read it. It does not read your Merchant Center feed. A cart is only one stop on the way, and [the other reasons an agent leaves without buying](https://storewalk.ai/blog/why-agents-cant-buy) are covered separately.

## Frequently asked questions

### What is Google Universal Cart?

A shopping cart across Google Search and Gemini that saves products from many retailers, tracks prices and stock, and checks out with Google Pay or by moving the items to the store's own cart. Google launched it in the US on 15 October 2026.

### Is Universal Cart available outside the US?

For shoppers, Google says it "is rolling out in the U.S." For merchants, Google's help page covers products eligible "in the United States, Canada, and Australia", and its Merchant Center hub says "Australia and Canada to follow early next year". Google said in May that UCP checkout would reach the U.K. "later".

### How do I get my products into Universal Cart?

Have products approved for free listings in Merchant Center, and declare `dev.ucp.shopping.cart` in your UCP profile for cart transfer. For checkout on Google, join the early access programme and mark products with `native_commerce(checkout_eligibility)` set to `TRUE`.

### Does Google become the seller when shoppers use Universal Cart?

No. Google says merchants "will remain the seller of record", whether the shopper pays in the cart or on the merchant's site.

### Can every product be bought through Universal Cart checkout?

No. Google lists categories that are ineligible for checkout, including subscriptions, personalised goods, used or final sale items, pre-orders, freight and age-restricted products.

If you do one thing this month, make it the profile Universal Cart reads. Run our [agent readiness checker](https://storewalk.ai/), and DISC-018 says whether your UCP profile is valid against its schema before Google's sandbox gets a go at it.

The sources below were last checked on the date shown.

## Sources

- [Google: Universal Cart launches in the U.S. (15 Oct 2026)](https://blog.google/products-and-platforms/products/shopping/universal-cart-launch/)
- [Google: New UCP features and AI tools for retailers (20 May 2026)](https://blog.google/products-and-platforms/products/shopping/shopping-updates-google-marketing-live/)
- [Google Merchant Center Help: UCP-powered checkout](https://support.google.com/merchants/answer/16837055?hl=en)
- [Google for Developers: UCP on Google](https://developers.google.com/merchant/ucp)
- [Google for Developers: UCP integration hub in Merchant Center](https://developers.google.com/merchant/ucp/guides/merchant-center/overview)
- [Google Merchant Center Help: Onboard to the UCP integration hub](https://support.google.com/merchants/answer/16992327?hl=en)
- [Google for Developers: Prepare your Merchant Center account](https://developers.google.com/merchant/ucp/guides/overview/merchant-center)

Last checked 4 Nov 2026
