# Google UCP Checkout in AI Mode: What Merchants Should Do

> Google UCP checkout in AI Mode lets shoppers buy inside Google. See the feed attributes, eligibility limits and a test to check your products get named.

- Author: Simran Rawat, Growth Executive, Nurdd
- Published: 2026-11-09
- Publisher: Noma by Nurdd (https://nomahq.app)
- Original page: https://nomahq.app/blog/google-ucp-checkout-ai-mode

Google UCP checkout in AI Mode is a buy button on eligible product listings that lets a shopper pay with Google Pay without leaving Google. The Universal Commerce Protocol (UCP) is the open standard behind it. The merchant stays seller of record, and only products flagged in the feed with native_commerce(checkout_eligibility) get the button.

## Key takeaways

- The checkout button is a feed decision: products show it only when the `native_commerce(checkout_eligibility)` attribute is TRUE, and a missing value means FALSE.
- Access is limited. Google's help page says the feature is for select merchants in the United States, Canada and Australia, and you apply through an interest form.
- Being named in an AI answer and being buyable in it are two separate problems. Feed quality and page content decide the first; UCP eligibility decides the second.
- Fix the data checkout depends on now: price, availability, returns, support contact and variant attributes. Google says mismatches can suppress the button.
- Measure with a fixed prompt set, repeated runs and a written log, not one screenshot of AI Mode.

## What is Google UCP checkout in AI Mode?

Google describes the [Universal Commerce Protocol](http://ucp.dev) as an open standard for agentic commerce that lets agents and systems work together across discovery, buying and post-purchase support. It is compatible with the Agent2Agent, Agent Payments and Model Context protocols, according to [Google Merchant Center Help, 2026](https://support.google.com/merchants/answer/16837055).

The checkout feature built on it puts a Buy button on eligible listings in AI Mode in Google Search and in Gemini. The shopper pays with Google Pay, using cards and shipping details already saved in Google Wallet. Google states the merchant remains the seller of record.

Google Merchant Center Help page describing UCP-powered checkout, its eligible countries and the select-merchant note. Source: Google Merchant Center Help.

The latest news is the Canadian rollout. [Search Engine Journal, November 2026](https://www.searchenginejournal.com/google-brings-ucp-direct-checkout-to-ai-mode-in-canada/595882/) reports that Google announced direct checkout in AI Mode and the Gemini app for Canadian shoppers on 4 November 2026, starting with four partners and merchant groups: lululemon, select Shopify merchants, Shoppers Drug Mart and Simons. Simplified UCP integration inside Merchant Center is planned for next year, with no date given.

### How it differs from the old checkout button

Google's help page separates this from the existing Merchant Center checkout button. With the old button the transaction happens on your site. With the UCP experience, checkout happens on Google's surfaces while you stay merchant of record. That changes what you need to prepare: your site's cart matters less at that moment, and your feed and checkout API matter more.

| Question | Existing checkout button | UCP-powered checkout |
| --- | --- | --- |
| Where the transaction happens | On your site | On Google's surface (AI Mode, Gemini) |
| Seller of record | You | You |
| Payment | Your checkout | Google Pay, cards saved in Google Wallet |
| Feed signal | Existing checkout setup | native_commerce(checkout_eligibility) |

Source for all rows: Google Merchant Center Help, as checked on 2026-11-08.

## Who can use UCP checkout today?

Not every merchant. The Google help page says the feature is available for select merchants in the United States, Canada and Australia, and points to a requirements page and an interest form. The Merchant Center onboarding page says the UCP integration hub is [rolling out gradually in the U.S., with Australia and Canada to follow next year](https://support.google.com/merchants/answer/16992327). Use the table to place yourself.

| Your situation | What to do this month |
| --- | --- |
| US merchant with a developer team | Check the UCP requirements, build to the developer guide and submit the interest form. Merchant Center onboarding includes a sandbox to test your UCP profile and checkout APIs. |
| Canadian or Australian merchant | Clean the feed and returns data now. Submit the interest form. Expect the Merchant Center route next year. |
| Shopify store selling into Canada | Google says the initial launch covers select Shopify merchants. Test how your products appear; do not assume eligibility. |
| Store on another platform or agency stack | Google's guidance is to ask your platform provider about its UCP plans. |
| Outside the three countries | Nothing to enable. Feed quality still affects whether products appear in AI responses. |

## How do I get my products into Google AI Mode shopping?

There are two layers, and teams often mix them up. The first is appearing at all. [Google Search Central's AI optimisation guide](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) says generative AI responses can include product listings and product information, and that Merchant Center feeds can help products be visible in AI responses and other Google Search results. There is no separate submission for this layer.

The second layer is being buyable inside the answer, which needs UCP. Google's Merchant Center page states that only product listings using the `native_commerce(checkout_eligibility)` attribute display the Buy button.

Google's own guidance on the first layer is short, so the work is mostly basics done well: approved products in free listings, accurate titles, descriptions, prices and stock, and pages that match the feed. For the page side, see how to [optimise content for AI Mode](https://nomahq.app/blog/optimise-content-for-ai-mode) and how [product pages win AI Overviews](https://nomahq.app/blog/win-ai-overviews-for-product-pages).

## What feed and account data does UCP checkout need?

Google's [UCP guide for Merchant Center](https://developers.google.com/merchant/ucp/guides/merchant-center) (last updated 29 October 2026 at the time of checking) lists the requirements. Treat it as your checklist.

### Account settings

- **Return policy:** required as a merchant-of-record condition and shown at checkout. It must include return cost, return speed and a link to the full policy. You can scope it with `return_policy_label` or set it per product with the `returns` attribute.
- **Customer support:** at least one of a support URL, email or phone number. It feeds the "Contact Merchant" link on the order confirmation.
- **Account standing:** a Merchant Center account in good standing with products approved for free listings.

### Product attributes

| Attribute | What it does | Rule from Google's guide |
| --- | --- | --- |
| native_commerce(checkout_eligibility) | Opts a product into checkout | Single boolean; FALSE or missing means not eligible |
| native_commerce(cart_eligibility) | Controls cart transfer to your site | Opt-out model; included by default once the cart capability is declared in your UCP profile |
| consumer_notice | Shows legal or safety warnings at checkout | Mandatory for items with regulatory warnings; message up to 1,000 characters |
| variant_option | Builds the size and colour selector | Strongly recommended with item_group_id; repeatable up to 30 times per item; name and value up to 250 characters each |
| merchant_item_id | Maps feed ID to checkout API ID | Needed only if your feed id differs; takes precedence over id in agentic requests |

Source: Google Developers, as checked on 2026-11-08.

### Worked example: the overwrite trap

Google's guide shows a sample feed with three rows. Product 11111 carries `TRUE:TRUE` (checkout and cart), product 22222 carries `TRUE:FALSE`, and product 33333 carries `FALSE:TRUE`. If you use both features, the composite format is mandatory, with values separated by a colon.

Now the trap. Google states the native_commerce group is fully overwritten with each upload and does not support incremental updates. Suppose a merchant later uploads a supplemental file containing only `TRUE` for checkout on 22222. Per the guide, the omitted cart flag is erased and set to blank. Always send every flag in every upload, and put these attributes in a supplemental data source so a formatting error does not disturb your primary feed, as Google recommends.

### Products Google excludes from checkout

Google lists categories that are ineligible and tells you to leave the attribute empty or FALSE for them. Audit your catalogue against these before you flip flags in bulk.

- Subscriptions and instalment or financed purchases.
- Personalised goods, refurbished or used items, and final-sale items.
- Pre-orders, bundled services such as installation, and items needing non-standard delivery fees.
- Age-restricted items, and prohibited content including healthcare and pharmaceuticals.
- Services, rentals, virtual items and goods that require software installed first.

## Which product data keeps the Buy button from disappearing?

Google's recommendations are specific. Use the Merchant API for catalogue updates so price, availability and details stay synchronised. If you run scheduled feeds, send supplemental real-time price and availability updates to prevent checkout price mismatches. Submit `variant_option` with `item_group_id` for multi-variant items: the guide says complete variant data prevents automated transactability discrepancies that can suppress the checkout button.

Google names price and availability mismatches as one cause. If your feed says $48 and your checkout API says $52, the product fails a check you cannot see in your own analytics. Compare feed and API values weekly for your top 50 products by revenue.

## How do I check whether my products are named in AI Mode answers?

Checkout eligibility tells Google you can sell in the answer. It does not tell you whether the answer names you. Run a repeatable test.

1. **Write 20 prompts** a buyer would ask, mixing categories ("best trail running shoes under $150"), attributes ("waterproof, wide fit") and comparisons. Keep brand names out of most of them. The [free AI Prompt Finder](https://nomahq.app/tools/ai-prompt-finder) can suggest the questions.
2. **Run each prompt in AI Mode three times** on different days, signed out, from your target country. Answers vary, and Noma's [published count of 2,545 answers](https://nomahq.app/blog/ai-citation-half-life) found two in three cited URLs appeared in one run only.
3. **Log five fields:** prompt, date, whether your brand is named, whether a specific product is named, and which sources are cited.
4. **Record the Buy button separately.** Note whether a listing shows it. That is a presentation detail, not visibility.
5. **Compare with classic rank.** Use the [free Google Rank vs AI Mode Checker](https://nomahq.app/tools/google-rank-vs-ai-mode), which shows your Google rank next to what AI Overviews and AI Mode cite for the same query and who is cited instead.

Count a product as named only if it appears in at least two of three runs. Report the rate as named answers divided by total answers, with both numbers shown. For method detail, read [AI Mode rank tracking](https://nomahq.app/blog/ai-mode-rank-tracking) and [how to measure AI share of voice](https://nomahq.app/blog/measure-ai-share-of-voice).

## Which failure points should merchants plan for?

These are the failure points Google's documentation and the launch coverage spell out:

- **The overwrite behaviour** of native_commerce flags, which can silently turn off cart transfer.
- **The exclusion list**, which removes subscriptions, pre-orders, final-sale and personalised items from checkout. A catalogue heavy in those gets little from UCP.
- **What is unknown.** Search Engine Journal notes Google has not said how UCP orders are reported or attributed in Merchant Center and Google Ads, or how direct checkout interacts with Shopping and Performance Max campaigns. Plan for thin attribution and keep your own order-source field.

> "UCP handles the complexity of agentic commerce underneath," said Mani Fazeli, VP of Product at Shopify, in Google's Canadian announcement, as quoted by [Search Engine Journal, November 2026](https://www.searchenginejournal.com/google-brings-ucp-direct-checkout-to-ai-mode-in-canada/595882/).

Note the gap between that quote and Google's wording: the launch covers select Shopify merchants, not every Shopify store.

## Where does Noma fit?

Noma by Nurdd is an AEO and AI visibility platform that asks 13 AI engines, including ChatGPT, Gemini, Perplexity and Claude, the questions your buyers ask every day. It shows where your brand is named, where competitors are named instead, and which pages the answers draw on. It measures naming and citation, not whether a Buy button appears.

See it on your own brand: [book a demo](https://nomahq.app/demo) or [start the 3-day free trial](https://platform.nomahq.app/signup). A card is taken at signup so billing can start on day 3; cancel before then and nothing is charged.

## What should a merchant do this week?

1. Confirm your country and platform against the eligibility table above, and submit Google's interest form if you are in the US, Canada or Australia.
2. Export your top 50 products and compare feed price and stock with the live checkout values.
3. Set return policy and customer support details in Merchant Center.
4. Add `variant_option`, `item_group_id` and `item_group_title` to multi-variant products.
5. Remove ineligible categories from any bulk checkout flag change.
6. Run the 20-prompt test and save the baseline before any change, so you can see an effect.

If you also sell through ChatGPT, the feed work differs. See the [ChatGPT Shopping checklist](https://nomahq.app/blog/chatgpt-shopping-black-friday-checklist) and the comparison of [AI shopping visibility tools](https://nomahq.app/blog/ai-shopping-visibility-tools).

## How we researched this

We read Google's Merchant Center Help pages, the Google Developers UCP documentation, Google Search Central's AI optimisation guide and Search Engine Journal's report on the Canadian rollout. We did not test UCP checkout on a live merchant account. Facts, attribute rules and availability were checked on 2026-11-08, and Google says rollout is phased, so recheck before acting.

## Next step

Baseline first, then fix. [Book a demo](https://nomahq.app/demo) to see your products and competitors across AI engines, or [start the free trial](https://platform.nomahq.app/signup) and track your first prompts today.