Google Universal Cart for retailers: how carts reach your store and what to check first

Direct answer: Google's Universal Cart went live in the US on 15 October 2026 in Search (including AI Mode) and the Gemini app. Shoppers save products from several retailers into one cart, and when they are ready to buy they either pay inside the cart with Google Pay or transfer the items to the retailer's own cart. Both routes run on the Universal Commerce Protocol (UCP). Cart transfer is the lighter build: one endpoint, POST /carts, that creates a cart on your side and sends the shopper back to your site. You stay the seller of record either way. Universal Cart is US-only today; Google has said UCP checkout comes to Canada and Australia first and the UK later, with no date for the EU.

This guide is for ecommerce directors, heads of digital and engineering leads at mid-market retailers. It explains how a cart gets from Google to your store, what each integration path needs, where it is available, what we found when we read the UCP profiles of the 225 retailers in our Agent Commerce Index, and what to fix first.

Last verified: 26 October 2026 against Google's launch posts, Merchant Center Help, Google's UCP developer guides and Shopify's Help Center. These pages change often, and Google rolls features out in stages, so check the current versions before you plan work.

What Universal Cart does

Google announced Universal Cart at Google I/O on 19 May 2026 and launched it in the US on 15 October 2026, across Google Search and the Gemini app. Google's launch post lists four things it does for the shopper:

• One cart across retailers. Products saved in AI Mode, Search or the Gemini app stay in the same cart.
• Price and stock alerts. The cart is built on Google's Shopping Graph, which Google describes as more than 60 billion "continually refreshed" product listings, and sends notifications when a saved item drops in price or comes back in stock.
• Payment and promo suggestions. It is built on Google Wallet, suggests which of the shopper's cards to use, and shows relevant promo codes.
• Two ways to buy. Check out with Google Pay inside the cart at participating stores, or "transfer your items directly to the merchant's cart to finish buying on their site". Google says the shopper receives confirmations and support from the merchant, who remains the seller of record.

Google named Nike, Sephora, Target, Ulta Beauty, Walmart, Wayfair and "many Shopify merchants" for these checkout options at launch. The May announcement also said YouTube and Gmail would follow; the October post does not mention them.

For a retailer, the practical point is that the shopper's basket now lives in Google's account, not in your session cookie. Your products reach that basket through your Merchant Center data. The cart reaches you only through UCP.

Two integration paths: cart transfer and native checkout

Google's Merchant Center integration guide lets a retailer choose cart transfer, native checkout or both.

Google describes cart transfer as the option that "minimizes implementation effort to accelerate UCP integration". Identity linking, for loyalty and signed-in checkout, is listed as coming soon and only works with native checkout.

Google's Merchant Center Help also describes a third, separate thing: an "agentic checkout feature" that "buys things on the customer's behalf directly on a merchant's website at the customer's direction". That one does not use your cart API. It uses your website, so it only works if an agent can reach your product, cart and checkout pages without a block or a challenge.

Where Universal Cart and UCP checkout are available

Two things follow for a retailer outside the US. First, eligibility is about where your customers are, not where you are based. Shopify's Google AI Mode and Gemini help page says a store "can be based in any country" if it sells to customers in the US, Canada or Australia. Second, a UK or EU retailer cannot use Universal Cart with its home market today. If you sell to US shoppers, the US route is open now; if you do not, the work that pays off later is the same feed, product-page and checkout groundwork described below.

Building cart transfer: what your developers need

Google's Cart API guide and implementation reference set out the work.

1. Support UCP version 2026-04-08. Google says the Cart API is only available from that version.
2. Publish a UCP profile at /.well-known/ucp that declares the dev.ucp.shopping.cart capability. The endpoint in the profile is the base URL Google calls. In the integration hub, the capabilities in your profile must "exactly match" the ones you select.
3. Implement POST /carts. Google adds items to the cart on its side and fires no API calls while the shopper is adding. When the shopper clicks the transfer button, Google sends one request with every line item. You create the cart and return its ID, line items, currency, totals, a continue_url that opens the pre-filled cart on your site, and optionally an expires_at time.
4. Match product IDs. Google's Merchant Center preparation page says the id in your product feed must match the product ID your API expects, or be mapped with the merchant_item_id attribute.
5. Secure the endpoint. Google's authentication guide covers API keys, OAuth 2.0 and mutual TLS. In the integration hub you provide separate keys for sandbox and production.
6. Plan for latency and peaks. Google does not enforce service levels on POST /carts but recommends responding "ideally in under one second", planning capacity for peak campaigns, and returning HTTP 429 when you need to throttle.
7. Test, then apply. Google's onboarding page says to complete the technical implementation first, then fill in the interest form. Selected merchants get the integration hub, with a sandbox for the profile, cart transfer and checkout APIs.

The request Google documents is short. The item.id is the product ID that has to match your feed:

{
  "line_items": [
    { "item": { "id": "item_123" }, "quantity": 2 }
  ]
}

The response must include the cart and the URL to send the shopper to. This is Google's example, trimmed:

{
  "ucp": { "version": "2026-04-08", "capabilities": { "dev.ucp.shopping.cart": [{ "version": "2026-04-08" }] } },
  "id": "cart_abc123",
  "currency": "USD",
  "totals": [{ "type": "total", "amount": 5000, "display_text": "Estimated total (taxes calculated at checkout)" }],
  "continue_url": "https://business.example.com/checkout?cart=cart_abc123",
  "expires_at": "2026-01-16T12:00:00Z"
}

The first release is one-way. Google says "updating, deleting, or synchronizing cart contents between Google and your system are not supported". Once the cart is on your site, Google has no further control over it. The integration hub can also simulate optional Get, Update and Cancel cart calls.

What the cart transfer hands you

The shopper arrives at your continue_url with a cart you built. Everything after that is your normal cart and checkout. A transferred cart can still be lost to a forced account creation, a missing guest checkout, a price that differs from the one Google showed, or a delivery charge that only appears at the last step. Google gives you the shopper's intent; your checkout still has to convert it.

Native checkout: the extra work

Native checkout puts a Buy button on eligible listings in AI Mode and Gemini. Google's Merchant Center Help says it is available "for select merchants at this time", that you remain the seller of record, and that it currently uses standard card numbers stored in Google Wallet. You need a Google Pay & Wallet Console account but do not need a Google Pay button on your own checkout.

Google's preparation page lists what must be in place before you build:

• Return policy in Merchant Center, with return cost, return window and a link to the full policy. Google calls this a merchant-of-record requirement shown on the checkout screen.
• Customer support details, used for the "Contact Merchant" link on the order confirmation.
• The native_commerce(checkout_eligibility) attribute set to TRUE on each product you opt in. If it is missing or FALSE, the product is not eligible. Google recommends a supplemental feed so your primary feed is not affected.
• Consumer notices such as California Proposition 65 warnings, through the consumer_notice attribute.

Some products cannot use native checkout at all. Google's list includes subscriptions, instalment plans, personalised goods, refurbished, used and final-sale items, pre-orders, items needing freight or other special shipping, age-restricted items, and digital goods and services. If much of your range falls into these groups, cart transfer is the realistic route.

Shopify and other platforms

Shopify. Shopify's Google AI Mode and Gemini help page says direct checkout is "activated by default for eligible stores" and still rolling out. The requirements are: sell to customers in the US, Canada or Australia; a Merchant Center account that meets Google's requirements; products in Merchant Center (through the Google & YouTube channel or a feed provider); products eligible for Shopify Catalog; agreement to the Shopify Agentic Storefronts Supplemental Terms; and completed terms, privacy and refund policies. Subscriptions, bundles, customisable and B2B-only products are not supported, nor are local delivery and pickup, and customers cannot be required to sign in. To switch direct checkout off, go to Sales channels > Agentic, turn off "Allow Shopify to manage for me", open Google AI Mode and Gemini and deactivate Direct checkout. Products stay discoverable and shoppers are sent to your store. We found no Shopify help page that describes Universal Cart transfer specifically.

Other platforms. Google's advice is that merchants using "a third-party service provider or platform" should ask that provider about its UCP plans. If you are on Adobe Commerce, Salesforce Commerce Cloud, BigCommerce, WooCommerce or a custom stack, ask whether it can serve a cart-capable UCP profile on your domain, which UCP version it supports, and whether it implements POST /carts.

If you are building agent features yourself, our guide to WebMCP for ecommerce covers the browser-side equivalent, where the shopper's own browser agent fills a cart on your site.

What we found in the Agent Commerce Index

On 26 October 2026 (08:05 CET) we requested /.well-known/ucp from the 225 UK and US retailers scored in the Agent Commerce Index Q4 2026, with one request per site from a standard browser user agent.

Three things stand out:

• Most of the coverage comes from Shopify. 115 of the 129 Shopify stores in the Index served a profile, against 6 of the 96 retailers on other or unidentified platforms.
• A declared capability is not a live integration. The Shopify profiles we read advertise MCP and embedded transports. Google's Cart API guide documents a REST endpoint and requires selection and validation in Merchant Center. Shopify connects its stores to Google through its own channel. A profile shows what the platform can do; whether Google transfers carts to a given store depends on Google's onboarding.
• Off Shopify, it is a build. Only 3 non-Shopify retailers declared the cart capability over REST. For a mid-market retailer on another platform, cart transfer is still something you or your platform provider has to build and get approved.

We publish these figures in aggregate only, without naming retailers. Our earlier scan with Cloudflare's agent readiness checker found a similar picture.

Measurement: what you will and won't see

• No signal before transfer. Google keeps items in the cart on its side and calls POST /carts only when the shopper transfers. You will not see an add-to-cart event for a product saved in Universal Cart.
• Merchant Center analytics. The UCP analytics dashboard shows clicks to Buy, purchases, purchase rate, average order value, cancellations, account linking and top-selling UCP products.
• Cart transfers via the Merchant API. The alpha Merchant Reports API views add cart_transfers, average_cart_product_count and average_cart_value by date and customer country. Product-level data covers buy button clicks only. Neither lists a metric for items saved to a cart.
• Your own analytics. The continue_url is a URL you build, so you can tag it in a way your analytics recognises and count transferred carts and their conversion yourself.
• Native checkout bypasses your pixels. Shopify says Google Analytics and custom pixels do not fire in Google AI Mode and Gemini's direct checkout; only server-to-server events do. Plan reporting from orders and Merchant Center.

What to check first

1. Decide your market position. If you sell to US customers, Universal Cart is live for your shoppers now. If you sell only in the UK or EU, prepare, but do not expect it in your home market yet.
2. Fix your Merchant Center data. Products reach the cart through the Shopping Graph, so price, availability, shipping and returns must match your site. Price-drop and restock alerts can only be as accurate as the data Google holds. Our product structured data guide covers the page-side facts.
3. Choose cart transfer, native checkout or both. Cart transfer keeps payment, upsell and checkout on your site and has the shorter validation path. Native checkout removes the last click but excludes several product types.
4. Publish and validate a UCP profile. Check that /.well-known/ucp returns valid JSON and declares exactly the capabilities you will support. Our score specification checks this as TRX-04, and the free score runs it on your store.
5. Make the landing cart convert. Test the continue_url journey as a guest, on mobile, with the same price Google showed and every charge visible early. TRX-01 (guest checkout), TRX-03 (no captcha on cart or checkout) and TRX-10 (an agent can reach checkout) cover the agent side.
6. Keep agents unblocked. Google's agentic checkout acts on your website directly, so bot management that challenges agents on cart or checkout pages costs you orders. See whether you are blocking AI shopping agents.
7. Set up measurement before launch. Tag continue_url, pull cart transfers from the Merchant API or dashboard, and agree how Google-originated orders will be reported.

If you want to see where an agent drops out of your cart and checkout, the Simulated Agent Buyer runs browser agents through your purchase flow and records each step. For merchants whose platform cannot serve UCP, the Hosted Agent Layer is on a waitlist, piloting on WooCommerce and BigCommerce. Our overview of agentic commerce for retailers puts Google's channel alongside ChatGPT, Copilot and the rest.

Sources

• Google, Introducing the Universal Cart and more ways to help you shop, 19 May 2026
• Google, How we're helping retailers thrive with new Universal Commerce Protocol features and AI tools on Google, 20 May 2026
• Google, Google's new Universal Cart launches today in the U.S., 15 October 2026
• Google for Developers, Cart API overview and Cart API implementation (2026-04-08), last updated 16 and 9 October 2026
• Google for Developers, How to start UCP integration in Merchant Center, About the UCP integration hub and Monitor and optimize your integration, last updated 19 October 2026
• Google for Developers, Prepare your Merchant Center account, last updated 2 October 2026
• Google for Developers, Analyze UCP agentic performance (Alpha), last updated 21 October 2026
• Google Merchant Center Help, About the Universal Commerce Protocol (UCP) and UCP-powered checkout feature on Google and How to onboard to the UCP integration hub in Merchant Center, read 26 October 2026
• Shopify Help Center, Selling on Google AI Mode and Gemini, read 26 October 2026
• Search Engine Journal, Google's Universal Cart Is Live: How Carts Get To Your Store, 15 October 2026
• ConversionVector, /.well-known/ucp check of the 225 scored Index retailers, 26 October 2026; Agent Commerce Index Q4 2026 (CC BY 4.0) and Agent Conversion Score specification v0.6