How to Make Your Store Buyable in Google AI Mode (UCP Setup Guide)

Being named in an AI shopping answer and having a Buy button next to your product are two different outcomes. Google can recommend a retailer in text and still leave the shopper to finish the purchase on your site. Or, for eligible merchants, it can complete checkout on AI Mode or Gemini while you stay the seller of record.

That second path runs on the Universal Commerce Protocol (UCP). On November 4, 2026, Google Canada said UCP-powered direct checkout started rolling out to Canadian shoppers on AI Mode in Google Search and the Gemini app, with early partners including lululemon, Shoppers Drug Mart, Simons and select Shopify merchants. Merchant Center Help says the feature applies to products with eligibility in the United States, Canada and Australia for participating merchants and partners, and that checkout is available for select merchants at this time.

This guide is the setup view: what UCP is, what Google says you need before a Buy button can appear, and how that differs from simply showing up when someone asks where to buy yoga pants in Canada.

What UCP is (and what it is not)

Google's Merchant UCP guide describes UCP as an open standard for agentic commerce: agents and merchant systems exchange product and checkout information so shoppers can buy inside AI Mode and Gemini without bouncing through a separate cart flow. You remain the merchant of record. UCP is designed to work with related industry protocols such as Agent Payments Protocol (AP2), Agent2Agent (A2A) and Model Context Protocol (MCP).

Merchant Center Help draws a useful line between two Google features:

• UCP-powered checkout on Google's surfaces. Checkout happens on AI Mode or Gemini. You stay the seller of record. Shoppers can pay with Google Pay using payment methods and shipping details already saved in Google Wallet.
• Agentic checkout that buys on the merchant's website. That is a different path: the agent completes the purchase on your site at the customer's direction. UCP is the protocol that standardizes the exchange (via API, MCP or A2A) between the agent and your backend for discovery and checkout journeys.

This post focuses on the first path: becoming eligible so a Buy button can appear on Google's AI surfaces.

UCP is not a guarantee that AI Mode will name you. Being buyable and being recommended are separate. Our Canada retailer study measured which retailers ChatGPT, Perplexity and Google AI Overview named for unbranded shopping questions the day after the Canada launch. That audit did not measure AI Mode or Gemini Buy buttons.

Current status (as of November 2026)

Fact	Status	Source
Eligible markets	United States, Canada, Australia (participating merchants/partners)	Merchant Center Help
Surfaces	AI Mode in Google Search and Gemini (Help also says you may see checkout soon on those surfaces)	Merchant Center Help; Google Canada blog
Who can use it today	Select merchants; early access via interest form and technical implementation	Merchant Center Help
Broader Merchant Center self-serve	Google Canada said simplified UCP integration in Merchant Center begins next year	Google Canada blog, Nov 4, 2026
Buy button trigger	Only listings with the native_commerce(checkout_eligibility) product attribute show the Buy button for this experience	Merchant Center Help
Seller of record	You remain the seller of record	Merchant Center Help; Google Canada blog
Payments today	Standard Funding Primary Account Numbers (FPANs) stored in Google Wallet; more methods may come later	Merchant Center Help

If a third-party article claims every Shopify store in Canada already has a Buy button, treat that as unverified. Google's own wording is select merchants, early access, and a later Merchant Center path.

Before you start: prerequisites checklist

Work through these before you invest engineering time. Google's Help article is the source of truth; re-read it when you start, because onboarding details move.

1. Confirm you sell in an eligible market. Help currently lists the United States, Canada and Australia for participating merchants and partners.
2. Have a Merchant Center account with solid product data. Google says Merchant Center stays the hub for feeds and brand assets, and that robust, up-to-date product data is the best preparation.
3. Create a Google Pay & Wallet Console account. Help says you do not need a Google Pay button on your own checkout pages to participate, but you do need that console account. If your payment service provider is not integrated with the Google Pay API, the provider has to onboard. Direct (non-PSP) payment processing needs encryption setup and PCI documentation.
4. Plan for a UCP technical integration. Google describes native checkout as the default path into AI Mode and Gemini, with an optional embedded (iframe) path for approved merchants with complex branding. The open standard also expects merchants to expose capabilities agents can discover (Google's developer guide and the UCP docs describe profiles and transports such as REST and MCP).
5. Expect an interest form, not an instant toggle. Help says the protocol rolls out in phases: meet requirements, submit the interest form, then complete the required technical implementation.

Step 1: Separate discovery from checkout

Shoppers still have to find you before they can buy. UCP checkout does not replace product feeds, titles, prices, availability or the pages AI systems cite when someone asks "best winter boots in Canada."

Practical split:

• Discovery work is feed quality, on-site product facts in HTML, and whether AI answers name you. Beket AI's free 25-prompt audit across ChatGPT, Perplexity and Google AI Overview is built for that second question.
• Checkout work is UCP eligibility, the native_commerce attribute, payment setup and the merchant endpoints Google's agents call.

Our explainer on AI Mode vs AI Overviews is useful background if your team still treats every Google AI surface as one feature. Checkout described here is tied to AI Mode and Gemini in Google's announcements, not to AI Overviews.

Step 2: Get into the early access path

1. Open About the Universal Commerce Protocol (UCP) and UCP-powered checkout in Merchant Center Help.
2. Confirm the eligibility notes still match your market and catalog.
3. Submit Google's interest form from that Help article (the form link lives on the Help page; use Google's page, not a third-party copy).
4. Follow the onboarding guide Help links for Merchant Center UCP implementation. Do not invent steps that are not on Google's docs.

Until Google opens the simplified Merchant Center path it described for next year, treat access as application plus engineering, not a self-serve checkbox.

Step 3: Mark eligible products with native_commerce

Merchant Center Help is explicit: only product listings using the native_commerce(checkout_eligibility) product attribute will display the Buy button for this checkout experience.

That means:

• A UCP integration without the attribute on the listing is not enough for the Buy button Google describes.
• Feed hygiene matters: the products you want to be buyable inside AI Mode need the attribute set correctly, alongside accurate price, availability and shipping data.
• Re-check Google's product data implementation docs from the Help article when you wire the attribute; attribute names and enums can be updated in Merchant Center documentation.

Step 4: Stand up the merchant side of UCP

Google's developer guide says UCP maps to standard retail operations such as checkout, supports REST API and MCP binding, and lets you choose capabilities and extensions. In practice, plan for:

• A discovery profile agents can read (UCP documentation describes a standard profile location such as /.well-known/ucp on compliant merchants).
• Checkout session create / update / complete behavior that returns authoritative cart state (items, tax, shipping, totals).
• Order lifecycle updates so Google's surfaces stay aligned with fulfillment.
• Payment handling on your rails, using Google Pay credentials as described in Help for this feature.

If you already sell through Shopify, ask your Shopify and payments contacts which UCP or agent-checkout paths they support for your shop. Google Canada's launch post named Shopify as a collaborator and mentioned select Shopify merchants; that is not the same as every Shopify store being live.

For a wider view of how Google is opening AI Mode to third-party apps (separate from UCP checkout), see our note on Google's Connected Apps Platform.

Step 5: Test what shoppers actually see

Once Google confirms you are in the program:

1. Search AI Mode (and Gemini, where available) for your own products and close substitutes.
2. Record whether you are named, whether a Buy control appears, and which listing it points at.
3. Complete a low-risk test purchase if your launch plan allows it, then confirm the order lands in your system with the right totals and shipping.
4. Watch for missing attributes: a product that is named in text but has no Buy button often means feed or eligibility gaps, not a ranking failure.

Do not use a ChatGPT or Perplexity screenshot as proof of Google UCP readiness. Those engines are useful for recommendation checks; they are not Google's UCP checkout surface.

Step 6: Keep naming and buyability on separate dashboards

Retailers that already appear in AI answers still need a UCP path to become buyable inside Google's AI surfaces. Retailers that get UCP access still need to be named, or shoppers never reach the Buy button.

A simple weekly scorecard:

Question	Where to check	What "good" looks like
Do AI answers name us for category questions?	ChatGPT, Perplexity, Google AI Overview (and AI Mode separately)	Your brand appears on the unbranded prompts that matter
Do eligible listings show Buy in AI Mode / Gemini?	AI Mode and Gemini in eligible markets	Buy appears on the SKUs you marked with native_commerce
Do completed UCP orders match our OMS?	Your order system	Totals, SKUs and shipping match what the shopper saw

Beket AI can help with the naming side through the homepage audit. It does not enroll you in UCP, set Merchant Center attributes, or process payments.

Common mistakes

• Treating the Canada launch as automatic coverage for every store. Google's wording is select merchants and early access, with broader Merchant Center access described for next year.
• Confusing AI Overview citations with AI Mode checkout. Different surfaces. See AI Mode vs AI Overviews.
• Skipping the native_commerce attribute after building endpoints. Help says the Buy button depends on it.
• Assuming Google Pay on your site is required. Help says the opposite for participation, while still requiring a Google Pay & Wallet Console account.
• Using recommendation share as a checkout KPI. A mention without Buy is still only a mention.

What remains unclear

Google's public materials we checked do not spell out how UCP checkout sales appear in standard retailer analytics, how Buy eligibility interacts with organic ranking inside AI Mode, or the exact timeline for every Shopify app or PSP. If your finance or analytics team needs attribution rules, get them in writing from Google or your platform partner rather than from a blog post.

Checklist: are you actually buyable?

• [ ] Selling into US, Canada or Australia as a participating merchant path
• [ ] Merchant Center feed is complete and current
• [ ] Google Pay & Wallet Console account exists
• [ ] Interest form submitted from Google's Help article
• [ ] UCP merchant endpoints / profile implemented per Google's onboarding docs
• [ ] native_commerce(checkout_eligibility) set on the listings that should show Buy
• [ ] Test searches in AI Mode / Gemini show Buy where expected
• [ ] Test order (if allowed) lands correctly in your order system
• [ ] Separate tracking for "named in answers" vs "Buy available"

If you only need the naming half today, start with Beket AI's free 25-prompt audit on the homepage. If you need a quick technical crawl pass (robots.txt, llms.txt, structured data and related signals), use the free 9-point /ai-check. Neither tool replaces Merchant Center UCP onboarding.