Google’s checkout in AI Mode and Gemini, built on the Universal Commerce Protocol (UCP), is an early access program for select merchants. Before a Buy button can appear, you have to be selected, finish a technical integration, and flag each eligible product in your feed. The flag defaults to “no”.
Market availability is where Google’s own pages disagree. As of October 27, 2026, one Merchant Center help page names the United States, Canada and Australia. Google’s two onboarding pages say the rollout is US first, with Australia and Canada to follow “next year”. The checkout terms are labelled US only. Our reading: the US is the documented market. Canada is unconfirmed until Google tells you otherwise.
Whole product types can never qualify, including subscriptions, engraved and personalized goods, final-sale and used items, pre-orders and age-restricted products. The preflight below helps you find out which of your products and markets are even candidates before you spend on integration.
Checked on October 27, 2026. This program is moving fast, so re-check before acting.
The rollout conflict table
Every Google and Shopify statement we found on market and rollout, with the date each page shows.
| Source | What it says about markets and rollout | Page date | Status |
|---|---|---|---|
| Merchant Center Help: About UCP-powered checkout | “Only applies to products with eligibility in the United States, Canada, and Australia, and for participating merchants and partners.” Checkout “available for select merchants” | None shown | Documented, broadest |
| Merchant Center Help: Onboard to the UCP integration hub | Integration “gradually rolling out in the U.S., with Australia and Canada to follow next year.” Access after selection | None shown | Documented, US now |
| UCP developer guide: integration hub overview | Rolling out in the US, “Australia and Canada to follow early next year.” Scope: “only to products sold within the United States.” Without hub access, use the Direct API path | 2026-10-19 | Documented, US only |
| Merchant Center Help: Checkout Terms of Service | The Checkout Addendum “applies to the United States only” | None shown | Documented, US only |
| UCP developer landing page | Reaches AI Mode and “Gemini web (app coming soon)”. Its own FAQ mentions the Gemini app | None shown | Marketing page, internally inconsistent |
| Shopify Help: agentic storefronts | Google AI Mode and Gemini “rolling out to eligible stores”; direct checkout “might not yet be available in your store” | None shown | Documented for Shopify, no market stated |
How to read it
| Your situation | What the documents support | What’s unknown |
|---|---|---|
| US merchant selling to US shoppers | A documented path exists: interest form, selection, integration | Whether and when you’ll be selected |
| Canadian merchant | One page lists Canada. Three others put Canada after the US, or exclude it | Whether Canadian products can go live now. Confirm with Google before building |
| Shopify store, any market | Shopify says direct checkout is rolling out and may not be in your store yet. Google tells third-party platform merchants to ask their platform | How Shopify’s rollout maps to Google’s selection |
| Direct API path (no hub access) | Google points merchants there if they lack hub access | No market statement for this path in what we read |
We don’t try to pick a winner. The terms page and the developer guide (dated October 19, 2026) are the most specific, and both say US. The broader help page may describe where the feature is headed, or it may just be older. Google hasn’t said.
The preflight
Run this before you fill in the interest form. Every gate comes from Google’s pages; leave the last column for your own answers.
Account and policy gates
| Gate | Google’s requirement | Where documented | Your status |
|---|---|---|---|
| 1. Market | See the conflict table. The US is the consistently documented market | All rollout pages | |
| 2. Merchant Center standing | Account in good standing, with approved products for free listings | Developer guide: Prepare your Merchant Center account | |
| 3. Return policy | Defined in Merchant Center, with return cost, return window and a link to the full policy. Advanced accounts set it per sub-account. A product-level returns attribute is allowed |
Same | |
| 4. Customer support | At least one of: support URL, email or phone. It powers the “Contact Merchant” link on the order confirmation | Same | |
| 5. Payments | A Google Pay & Wallet Console account. Your payment provider must be integrated with the Google Pay API, or follow Google’s onboarding steps. Direct processing needs encryption setup and PCI documentation | Help: About UCP-powered checkout, FAQ | |
| 6. Platform | On a third-party platform, ask the platform about its UCP plans | Help: Onboard to the hub, FAQ | |
| 7. Program entry | Complete the technical implementation, submit the interest form, wait for selection | Help: Onboard to the hub |
Product data gates
| Attribute | What it does | Google’s rule |
|---|---|---|
native_commerce(checkout_eligibility) |
Opts the product into checkout on Google | A single boolean. Missing or FALSE means not eligible; it defaults to FALSE. native_commerce still works as an alias |
consumer_notice |
Shows a legal or safety warning at checkout | Mandatory for items with regulatory warnings, such as California Proposition 65. notice_type is one of legal_disclaimer, safety_warning or prop_65; the message is up to 1,000 characters |
merchant_item_id |
Maps the feed ID to your checkout API’s product ID | Needed only if the two IDs differ. It takes precedence over id in agentic requests |
variant_option with item_group_id and item_group_title |
Builds the variant selector | Newest page version only: strongly recommended, up to 30 per item, and incomplete variant data can suppress the checkout button. An older version seen the same day didn’t list it, so confirm the live page first |
Google recommends sending these through a supplemental feed so a formatting mistake doesn’t break your main product data. For freshness, it recommends the Merchant API, or real-time price and availability updates if you use scheduled feeds, “to prevent checkout price mismatches.”
Products that can never qualify
Google lists these as ineligible for checkout, and says they must have the eligibility attribute empty or FALSE. This is where most small catalogs lose products.
| Group | Excluded | Common in small stores? |
|---|---|---|
| Billing | Subscriptions; merchant-mandated installments or financing | Yes: subscribe-and-save, refill clubs |
| Customized and fulfillment | Personalized goods (engraving, monograms); refurbished, used and final-sale items; pre-orders; items needing contracts like warranties or installation; special shipping such as freight; gifting with split invoices or hidden prices; in-store activation | Yes: engraving, clearance, launches |
| Policy and safety | Age-restricted items needing ID (alcohol, tobacco); anything blocked by Google Shopping policy, including weapons, adult content and healthcare or pharmaceuticals | Depends on category |
| Digital and services | Services such as lessons and classes; rentals; virtual items; goods that need software installed before purchase | Rare for physical-goods stores |
Two notes. Final sale counts as “no returns”, so a clearance section with a no-returns policy is out. And the attribute is per product, so one store can have eligible and ineligible items side by side.
A different flag with a similar name
Shopify’s agent catalog has its own native-checkout field. In our unpersonalized Shopify Catalog snapshot of October 26, 2026, it was false on the returned variant of all 1,620 results. That’s a Shopify field in Shopify’s catalog. It isn’t Google’s native_commerce attribute, and it tells you nothing about your Google eligibility. Don’t use one to check the other.
Worked case: a hypothetical store
Hypothetical store, for illustration only. An Ontario-based Shopify store sells to the US and Canada. It has 40 products in Merchant Center, all approved for free listings:
- 28 new, in-stock products with standard shipping
- 6 engraved versions of those products
- 4 clearance items marked final sale
- 2 pre-order items for a spring launch
Step 1: market. US-sold products have a documented path. For Canadian shoppers, one help page says yes and three pages say later or US only. The store records Canada as “unconfirmed: ask Google” and doesn’t plan Canadian revenue around it.
Step 2: platform. It’s on Shopify. Google tells third-party platform merchants to ask the platform, and Shopify says direct checkout for Google users is rolling out and may not be in the store yet. Before building a direct integration, the store checks whether Shopify’s route covers it. We can’t see that from public docs.
Step 3: exclusions.
| Products | Count | Eligible? | Why |
|---|---|---|---|
| Standard new items | 28 | Candidates | No exclusion applies |
| Engraved versions | 6 | No | Personalized goods |
| Final-sale clearance | 4 | No | Final sale, no returns |
| Pre-orders | 2 | No | Future release date |
| Total | 40 | 28 candidates, 12 excluded |
Step 4: data. The 28 candidates get native_commerce(checkout_eligibility) set to TRUE in a supplemental feed. The 12 others get FALSE, so the intent is explicit even though missing already means no. Three of the 28 come in sizes. The store keeps its ordinary Merchant Center variant fields (item_group_id, size, color) accurate. Before adding variant_option, it checks that the current Prepare page still recommends it. None needs a Proposition 65 notice; if any did, consumer_notice would be mandatory.
Step 5: account. The return policy in Merchant Center states cost, window and a link. Support email is set. The store opens a Google Pay & Wallet Console account and confirms its payment provider supports the Google Pay API.
The store ends up knowing more than “we want checkout”. It has 28 candidate products in one documented market and an open question on Canada. Its platform route depends on Shopify’s rollout, and it has a feed change ready to ship once it’s selected.
What checkout doesn’t do
No Google page we read says checkout eligibility helps a product get found or recommended. Google says the Buy button appears “on eligible product listings”, which means the listing has to be there first. Discovery in AI Mode and Gemini runs on your indexed pages and Merchant Center data. Our AI Mode route guide maps those routes, and the free listings checklist covers the approval that checkout requires.
For the protocol itself, see our UCP guide. For how it compares with OpenAI’s protocol, see UCP vs ACP. For the Shopify side of distribution, see Shopify’s agentic storefronts.
What this preflight can’t tell you
It can’t tell you whether Google will select your store. It can’t settle which market statement is current; only Google can. It stops before the technical integration: we didn’t read the cart, payment-handler or order-lifecycle guides in detail, or the full terms addendum. We didn’t see Merchant Center’s integration hub. Checked on October 27, 2026; re-check before acting.
Your next step
Export your Merchant Center product list and add one column: “checkout candidate?”. Mark every subscription, personalized, final-sale, used, pre-order and age-restricted item No, then count what’s left. If the remaining products are a meaningful share of your US sales, fill in the preflight’s “Your status” column. If they aren’t, keep improving your discovery data first; checkout can wait.