Google Universal Cart: what merchants actually need to do, and what UCP asks of your store
Google Universal Cart for merchants: what is confirmed, what Shopify stores should check, and what cart transfer and native checkout need from your store.
By Rokibul Hasan8 min read
- E-commerce

Google Universal Cart launched in the US on 15 October 2026, across Google Search and the Gemini app. It holds a shopper's items from several retailers in one place, and at the end they pay with Google Pay or move the items to the merchant's own cart. Google says checkout is "powered by the Universal Commerce Protocol (UCP)". Its announcement does not say what a merchant has to do.
This guide answers that for store owners and the developers who work with them, using Google's Merchant Center help pages, its UCP developer guides and Shopify's help centre. The answer depends on your platform. A Shopify store may already be live, while a custom store has API work and a selection step ahead of it. Everything here is as of 4 November 2026, and I say where Google's own pages disagree.
I build e-commerce automation and integrations on official APIs. For the wider picture of AI shopping, read agentic commerce for online stores.
Google Universal Cart: what is confirmed
From Google's launch post:
- Where: the US, in Google Search and the Gemini app. Items saved in AI Mode can reappear in Gemini.
- For shoppers: one list across retailers, alerts on price drops and restocks, a suggested payment method from Google Wallet, and promo codes.
- For you: the shopper gets confirmations and support from you, and you "remain the seller of record".
- Named retailers: Nike, Sephora, Target, Ulta Beauty, Walmart, Wayfair and "many Shopify merchants".
Keep two names apart. Universal Cart is the shopper's feature. UCP is the open standard your systems use to talk to Google, and nearly all your work sits there.
Find your situation first
| Your store | Where you stand | Next step |
|---|---|---|
| Shopify, products in Merchant Center | Direct checkout in AI Mode and Gemini is on by default for eligible stores | Review it and decide whether to keep it |
| Another hosted platform | It depends on the platform; Google's help page tells you to ask them | Email your provider about UCP plans |
| Custom store selling in the US | UCP endpoints to build, then an interest form and selection by Google | Choose cart transfer, native checkout or both |
| Selling outside the US | Google says hub onboarding reaches Australia and Canada next year; PPC Land reports no UK date | Keep feeds clean and wait |
| Not in Merchant Center | None of this applies yet | Start with a product feed |
If you are on Shopify, check what is already on
PPC Land reports that Google's broader native checkout rollout began on 18 September 2026, with Shopify merchants matched to their Merchant Center accounts and switched on automatically, and notification emails sent on 22 September. Shopify's help page confirms the default: direct checkout is "activated by default for eligible stores", with no extra fee beyond your standard payment processing.
That page does not mention Universal Cart by name, and Google's post says only "many Shopify merchants". So I cannot tell you whether a particular store appears in the cart. Check your own admin rather than assume.
What Shopify's page lists:
- Requirements: you sell to customers in the US, Canada or Australia; products are in Merchant Center and eligible for Shopify Catalog; your terms, privacy and refund policies are filled in.
- Unsupported products: subscription-only, bundles, customisable and B2B-only.
- Delivery: no local delivery, in-store pickup or pickup points.
- Checkout: you cannot require sign-in, and upsells, custom fields and some validations may not appear.
- Tracking: Google Analytics and custom pixels do not fire. Only server-to-server started and completed events are sent.
The last two deserve the most thought: a custom field such as a gift message may be missing, and in pixel-based reports these orders can look as if they came from nowhere.
To turn it off: go to Sales channels > Agentic, deactivate "Allow Shopify to manage for me", open Google AI Mode and Gemini, and turn off Direct checkout. Shoppers can still find your products and are sent to your store to buy.
Cart transfer or native checkout on a custom store
Google's hub guide offers two main paths, and you can choose both.
| Transfer to merchant cart | Native checkout on Google | |
|---|---|---|
| Where the shopper pays | Your site | On Google, with Google Pay |
| What you build | Cart API: dev.ucp.shopping.cart |
Checkout endpoints to create, update and complete a session |
| Payment work | None new | A com.google.pay handler, and a provider that can process Google's token |
| Merchant Center setup | Fast track, including matching product IDs | All configurations: returns, support contact, warnings, feed attributes |
| After the sale | Your normal process | Order webhooks to Google |
| Legal step | None listed in the guide | Agree to the UCP Program Addendum |
Both need a UCP profile at /.well-known/ucp, and the capabilities it declares must match what you select in Merchant Center. Google's guides are written against UCP version 2026-04-08, the first with the Cart API. The examples on ucp.dev now show 2026-08-25, so check which version Google accepts before you build.
Cart transfer is the smaller job. Google says it sends a single POST /carts request only when the shopper clicks the transfer button, with every item at once, and you return a cart with a continue_url back to your site. This first release supports creation and transfer only, with no updating or syncing.
For most custom stores I would start there: the shopper pays on your checkout, your tracking still works, and you learn whether the channel matters before taking on order webhooks.
The Merchant Center details that catch people out
Google's preparation guide has several rules that are easy to get wrong in an automated feed:
native_commerceis overwritten whole. The group holdscheckout_eligibilityandcart_eligibility, and Google says it "is fully overwritten with each upload and does not support incremental updates". Send both every time, or the one you omit is cleared.- The defaults differ. Checkout eligibility defaults to false, so you opt in. Cart eligibility is opt-out.
- Use a supplemental feed, so these attributes do not disturb your primary product data.
- IDs have to line up. Line item IDs must match the feed. If your feed
idis not what your API expects, map it withmerchant_item_id, which takes precedence. - Some products must stay out of checkout, including subscriptions and instalment plans, personalised goods, non-new or final sale items, pre-orders, freight, age-restricted items and digital goods.
- Warnings need their own attribute. Items with regulatory warnings, such as California Prop 65, need
consumer_notice. - Returns and contact details must be complete: return cost, return window and a policy link, plus at least one contact method.
How onboarding works, and where Google's pages disagree
The order, from Google's help page and the hub guide:
- Complete the technical implementation from the UCP developer guide.
- Submit the interest form.
- If selected, Google opens onboarding under Settings > UCP integration, with a sandbox for your profile and APIs.
- In production, select capabilities, publish your profile and pass the checklist.
- Google Support reviews it and tells you whether you are live.
PPC Land reports that Google published the hub on 6 October. Merchants without hub access have a direct API path, which still needs Google's approval.
Two inconsistencies are worth knowing:
- How open it is. The help page describes selection and says you may not see the hub yet. A Google "Accelerate" announcement page calls it "Generally available for US selling merchants". Assume selection applies until the hub appears in your account.
- Identity linking. The hub guide marks it "coming soon", though PPC Land describes it as one of three options. Do not plan around it yet.
What native checkout changes in your own systems
On Shopify the platform carries this. On a custom store it falls to you.
Order updates. Google's order lifecycle guide requires you to post the full order on creation, on shipping with tracking, and on delivery, and says a progression from shipped to delivered is mandatory. Cancellations, returns and refunds go in an adjustments array. If your system never records a delivered event, that may be the first gap you hit.
Stock. Google's UCP FAQ says you run the real-time stock check and return out_of_stock. If your counts lag, the failure lands in someone else's interface, so multichannel inventory sync comes first.
Retries. Use a 10-second client timeout and reuse one Idempotency-Key for every retry of an event.
Security. Google recommends mutual TLS and verifying its signatures. Do not authenticate on the UCP-Agent or User-Agent headers alone, because Google notes they can be spoofed.
This is custom work, quoted from a brief. Feed and stock work beforehand is the kind of automation my marketplace plans cover.
What Google has not said
- Fees outside Shopify. Google's public pages give none. The commercial terms sit in a Checkout Addendum, so read it before you agree.
- Attribution. The hub has an Analytics tab, but PPC Land lists attribution for cart transfers as undisclosed.
- Adoption. PPC Land notes Google has published no merchant count. Third-party trackers conflict, so I am leaving their numbers out.
FAQ
Do merchants have to sign up for Google Universal Cart?
Google's documents describe no separate sign-up under that name. What they describe is UCP: Shopify stores can be switched on through their Merchant Center match, and custom stores implement UCP, submit an interest form and wait for selection. Cart eligibility in the product feed is opt-out, but a store still needs an approved integration.
Will UCP checkout improve where my products rank on Google?
No. Google's UCP FAQ says offers with UCP get a direct purchase option but that ranking is unchanged. Treat it as a way of removing steps for a shopper who has already found you, and judge it on orders and on what you give up, such as pixels and custom checkout fields. Product data, price and availability still decide whether you appear in the first place.
Can I keep shoppers on my own checkout instead of Google's?
Yes. On Shopify, turn off Direct checkout under Sales channels > Agentic, and shoppers who find your products in AI Mode or Gemini are sent to your store to buy. On a custom store, implement transfer to merchant cart and leave checkout_eligibility false or empty, so the Buy button does not appear. You remain the seller of record either way, and you keep your own tracking and checkout rules.
If you want to work out what Universal Cart needs from your store, send me a short brief: your platform, whether you are in Merchant Center, how your feed is built, and which of cart transfer or native checkout you are leaning towards. You can send it through the contact page, see the custom automation I build for online stores, or check what to do before the peak in the Black Friday ecommerce checklist.


