---
title: "Google Universal Cart: A Shopping Cart in Search and AI Mode"
description: "Google launched Universal Cart in the US: one cart across Search, AI Mode and Gemini. How it works, what UCP is, what a store needs and what changes for SEO."
date: 2026-10-27
category: SEO
tags: ["Universal Cart", "UCP", "Google Shopping", "Merchant Center", "AI Mode", "E-commerce"]
url: https://uper.pl/en/blog/google-universal-cart-shopping-cart-in-search/
---

# Universal Cart: Google now has its own shopping cart in Search How it works, what UCP is, what a store needs, and what it means for SEO, in the US and beyond

**On 15 October 2026 Google launched Universal Cart in the United States: one shopping cart that works in Search (including AI Mode) and in the Gemini app.** Shoppers add products from different stores to a single place, get alerts when prices or stock change, and at the end either pay with Google Pay or move the whole cart to the retailer's site. A week after launch, the cart icon was sitting in the top right corner of the results page for most US users. If you sell outside the US you will not see it yet, but it moves the place where the buying journey ends, so here is what exactly shipped, what it runs on and what I would do about it as a store.

## What exactly shipped on 15 October

Google described Universal Cart on its blog as "an intelligent shopping cart" and "your new hub for shopping on Google". It was previewed in May at Google I/O and Google Marketing Live, with a promise of a launch "this summer". Summer passed, and the cart arrived in mid-October, just ahead of the holiday season. Google's announcement lists four things the cart does:

- **It gathers products from many stores in one place.** A handbag added in AI Mode and a sweater added in Gemini land in the same cart, and your progress is remembered across Google products.
- **It watches prices and stock.** The cart runs on the Shopping Graph, Google's product database, which the company describes as "60+ billion continually refreshed product listings". When a price drops or an item is back in stock, the shopper gets a notification.
- **It suggests how to pay.** The cart is built on Google Wallet, so it knows the perks of your saved cards, recommends a payment method and surfaces matching promo codes.
- **It lets you buy.** In many stores you pay with Google Pay without leaving Google; in the others you transfer the items to the store's own cart and finish the order there.

Barry Schwartz at Search Engine Roundtable showed on 23 October how it looks in practice: a cart icon next to the account avatar, "Add to cart" buttons on product listings in the results, a cart view and a "My orders" tab next to it. Glenn Gabe, who got the feature on 17 October, described adding a product with size and variant selection, paying through Google Pay with a saved card, and seeing a preview of the credit card points he would earn. His comment sums up the mood in the industry: the feature has a lot of potential, but we have yet to see how many people will use it and trust it.

Among the stores where the cart works from day one, Google names Nike, Sephora, Target, Ulta Beauty, Walmart, Wayfair and "many Shopify merchants". In both purchase variants, on Google and on the store's site, the store stays the seller: Google uses the term "seller of record" and says the merchant sends the order confirmation and handles customer support.

## How Google got here: from UCP in January to the cart in October

Universal Cart is the last link in a chain of announcements Google made throughout 2026. Without that sequence it is hard to see why the cart works with such large retailers right from launch.

| Date | What happened |
|---|---|
| 11 January 2026 | At the NRF conference, Google announces the Universal Commerce Protocol (UCP), an open standard for shopping done by AI agents. It is co-developed with Shopify, Etsy, Wayfair, Target and Walmart, and endorsed by more than 20 companies including Visa, Mastercard, Stripe, Adyen, Best Buy, The Home Depot and Zalando. |
| February 2026 | The first purchases through UCP in AI Mode and Gemini, starting with Etsy and Wayfair listings. |
| 20 May 2026 | At Google I/O and Google Marketing Live, Google demos Universal Cart and promises a US launch "this summer", with YouTube and Gmail to follow. It also announces UCP for Canada and Australia "in the coming months", then the UK, plus Affirm and Klarna instalments inside Google Pay. |
| September 2026 | US Shopify stores receive a Merchant Center notice that their products "are now eligible for native checkout" with nothing to set up. Shopify handles the integration on the store's side through Agentic Storefronts. |
| 6 October 2026 | The UCP integration hub opens in Merchant Center, where a store picks which protocol capabilities it supports. US only for now. |
| 15 October 2026 | Universal Cart launches in Search and Gemini in the US. |
| 17-23 October 2026 | The cart appears for more and more users, and the industry publishes the first recordings and screenshots. |

Two things in this table stand out. First, the big chains had their integrations ready on launch day because they had been working on the protocol since January. Second, "this summer" slipped by a few months, and the October announcement no longer mentions YouTube or Gmail at all.

## What UCP is

The **Universal Commerce Protocol** is an open standard in which a store describes its commerce capabilities as a standardised API, so that an AI agent, an app or a search engine can use them without a separate integration for every store. The specification is published on ucp.dev under the Apache 2.0 licence, and Google says it is compatible with the other agent protocols: A2A, AP2 (agent payments) and MCP.

The protocol is split into capabilities a store can implement separately:

- **Catalog**: searching and browsing the product catalogue,
- **Cart**: building and managing a multi-item cart,
- **Checkout**: a purchase session from creation to completion,
- **Identity Linking**: linking the shopper's account to the store through OAuth 2.0,
- **Order**: order status, shipment tracking and returns.

The store publishes a UCP profile at an address like `https://yourstore.com/.well-known/ucp`. Google reads from it which capabilities the store supports and at which endpoints. The mechanism works much like `robots.txt` or `security.txt`: one well-known address where a machine learns what it can do with the site.

## How a store gets into the cart

The Merchant Center documentation describes two paths that can be implemented separately or together. A third, Identity Linking, is marked "coming soon".

| | Cart transfer | Native checkout on Google |
|---|---|---|
| What the shopper sees | Adds products on Google, finishes the order in the cart on your site | Buys without leaving Google, pays with Google Pay |
| What you implement | The Cart API | Three REST endpoints: session creation, update and completion, plus webhooks with order status updates |
| What you sign | Nothing beyond the standard Merchant Center terms | The UCP Program Addendum |
| What you need in Merchant Center | Matching product IDs | A full feed, return policies, customer support contact details, consumer notices on products that need them |
| Tests | Create Cart is required; Get, Update and Cancel Cart are optional | Create, Update and Complete Checkout |

Google says plainly that the cart transfer path "doesn't require full product feed setup, product warnings, or customer support information". It is the starting option for a store that does not want to hand the whole payment process to Google.

In both paths, the UCP profile at `/.well-known/ucp` must declare exactly the capabilities the store selected in Merchant Center. The process goes like this: implement according to the developer documentation, submit the interest form, get access to the sandbox (API keys for testing are exchanged by email with a Google contact), run the tests, and finally pass a review by the Google Support team, which tells you whether the account is live or what needs fixing. As of today the UCP integration hub is "gradually rolling out in the United States", and Australia and Canada are to follow "early next year".

### What you need in Merchant Center

A separate Google guide explains how to prepare an account for native checkout. The entry condition is an account in good standing with products approved for free listings. Then:

- **A return policy** with the return cost, the return window and a link to the full text, because it is shown on the checkout screen. In advanced accounts it must be set on every sub-account.
- **Customer support details**, at least one of three: a website URL, an email address or a phone number. They power the "Contact Merchant" link on the order confirmation.
- **The `native_commerce(checkout_eligibility)` attribute** set to TRUE for every product that should be buyable on Google. It defaults to FALSE, so without it the product never reaches the cart. Google recommends delivering it through a supplemental feed or the Merchant API.
- **Product identifiers.** The `id` in the feed must match the identifier your Checkout API expects. If it differs, the `merchant_item_id` attribute saves the day, because it takes precedence in agentic requests.
- **Consumer notices** (`legal_disclaimer`, `safety_warning`, `prop_65`) wherever the law requires them.

Excluded from checkout are, among others, subscriptions and instalment plans, personalised, used, final-sale and pre-order items, age-restricted goods, digital services, rentals and anything that requires installing software. For those products the attribute stays FALSE.

### How cart transfer works

Here the Cart API documentation (UCP version 2026-04-08) clears up a doubt that had been circulating online. Google does not call the store every time a product is added. It accumulates the items on its side and sends the store a single `POST /carts` request only when the shopper clicks the transfer button, for example "Checkout on merchant". The request carries the complete list of line items with identifiers and quantities. The store responds with a cart session: the items with prices, totals, the session expiry time and a `continue_url` that "must direct the user back to a page on your site where they can continue managing the cart", typically the cart with the session preloaded.

For SEO the most interesting part is what happens at the end. The shopper does land on your site, but not through an organic result, a category page or a product page. They arrive straight at the cart stage, with the order already decided. The product page, where stores put the most SEO effort, plays no part in this path at all.

## What this changes for stores and SEO

What follows are my conclusions, not Google announcements, so read them as interpretation.

**The product feed starts to weigh more than the product page.** The cart runs on the Shopping Graph, and matching identifiers are the entry condition for UCP. If the Merchant Center feed has errors in prices, stock or variants, Universal Cart will show them to the shopper as your offer before they ever see your site. Structured data on product pages, which I covered in the piece on [Schema.org for e-commerce](/en/blog/schema-org-ecommerce/), remains a complement, because Google still reads it, but schema alone will not get you into the cart.

**Part of the buying journey leaves your site and your analytics.** With native checkout the shopper never visits the store, so GA4 shows neither the session nor the funnel. With cart transfer the session starts on the cart page, which breaks landing page reports and conversion rates measured from the product page. Orders from Google will have to be counted in the backend, by the cart session identifier, rather than in an analytics tool. There is also no Search Console report for the cart yet. Google is only now testing [AI Search reports in Search Console](/en/blog/search-console-ai-search-reports/), so I would not expect Universal Cart data before next year at the earliest.

**The cart compares on the shopper's behalf.** Back in May, Google said the cart "gets to work in the background" the moment a product is added: it looks for a better price elsewhere, applies promotions and watches for price drops. A store that wins the click from the results today thanks to a good page competes in the cart on price and availability with everyone who has the same product in the Shopping Graph. Google has not published the rules by which the cart orders and proposes offers.

**A paid layer already exists.** Direct Offers in Google Ads lets stores with a UCP integration show exclusive promotions in AI Mode that can be bought on the spot. Google has not named any fees for UCP as a protocol, but the ecosystem around the cart already has a slot where budget can go.

**Shopify gets it without an IT project, but also without being asked.** US Shopify stores were enrolled in native checkout by default: Shopify handles the protocol on its side, and a store that prefers shoppers to finish the purchase on its own site has to turn the feature off itself, in the Agentic section under sales channels in the admin. Stores on other platforms (WooCommerce, PrestaShop, Magento and the regional SaaS platforms) will wait for plugins from their vendors or implement the API themselves. I expect that when UCP reaches Europe, SaaS platforms will repeat Shopify's move, so the decision "do I want to sell in Google's cart" will land on stores as switched on by default.

## What is not known

- **Fees.** Neither the announcement nor the documentation says whether Google takes anything on sales through Universal Cart. Payment in native checkout goes through the store's own payment provider, so its fees stay. Claims of "zero fees" I have only seen on third-party blogs.
- **Offer ranking.** There is no documentation on how the cart selects and orders products, or how it decides which store to show when several sell the same item.
- **Usage.** There is no data on how often shoppers use the cart. The first numbers will probably come after the US holiday season.
- **Markets.** Google talks about Australia and Canada in early 2027, and in May it mentioned the UK. There is not a word about the EU, and I would not be surprised if DMA regulation delayed that market more than others.
- **Documentation version.** UCP is versioned, and I am describing version 2026-04-08. Before you build anything, check the current specification, because details such as the moment `POST /carts` is sent have already changed once in the descriptions circulating online.

## What I would do today as a store outside the US

Universal Cart does not work outside the US, and in most markets it will not for the next year, so writing a UCP integration is a waste of time right now. Three things on this list pay off regardless of the cart, though, and when UCP arrives, a store without them will not get in at all:

1. **Clean up the Merchant Center feed.** Prices, stock, variants and identifiers consistent with what the shopper sees on the site and what your backend knows. If the `id` in the feed differs from the identifier in your store, add `merchant_item_id` now.
2. **Fill in the return policy and contact details in Merchant Center.** It is an entry condition for UCP, but also something Google already shows next to free listings today.
3. **Prepare backend measurement.** Orders that start outside your site will have to be recognised by the source of the cart session, not by a GA4 cookie. It is worth knowing how to do that before the first channel of this kind shows up.

If you sell on Shopify, add a fourth point: decide now whether you want to sell in Google's cart, because in the US Shopify switched the feature on for stores by default and you have to turn it off yourself.

## Summary

Universal Cart is Google's step towards owning the whole buying journey, from inspiration in AI Mode, through comparing offers and watching prices, to payment. It runs on UCP, a protocol developed since January 2026 with Shopify, Etsy, Wayfair, Target and Walmart, which is why the big chains were ready on launch day. A store enters the cart through Merchant Center, and the simplest path, cart transfer, needs only the Cart API and matching product identifiers. For stores outside the US this is a signal, not a task, because the feature works only in the US. The fundamentals stay the same, though: a clean feed, return policies and contact details in Merchant Center, and measurement that does not depend on whether the shopper ever visited your site.

## Sources