Google's AI Checkout Starts in Your Feed

Google is rolling out a checkout button that lives on Google’s own surfaces — AI Mode in Search and the Gemini app — and the thing that decides which products get it is not a ranking algorithm. It is a single boolean attribute in your Merchant Center product feed.

The feature runs on the Universal Commerce Protocol (UCP), an open standard for agentic commerce co-governed by Google and Shopify. Google’s Merchant Center documentation states the rule in one sentence: only product listings using the native_commerce(checkout_eligibility) attribute display the Buy button for this checkout experience. If the attribute is missing, the product is not eligible. The default is FALSE.

That makes this a listing-data story, not an ads story. The shopper stays on Google’s surface, but you remain the merchant of record, the checkout runs through Google Pay with payment methods the shopper already has stored, and every input Google needs to decide eligibility and render the transaction — eligibility flag, returns, warnings, identifiers — comes from the product data you control. If you sell on Shopify, most of that data starts life in your Shopify admin and reaches Google through your Merchant Center feed.

What shipped, and when

Three pieces are moving at once, and they are at different stages.

The checkout experience itself is live for select merchants. Google’s help documentation says the UCP-powered checkout button can appear on eligible product listings in AI Mode in Search and on Gemini, currently applying to products with eligibility in the United States, Canada, and Australia. Participation is by interest form, and Google describes the merchant set as “select merchants at this time.”

The onboarding path is what is new and rolling out now. Google has opened a UCP integration hub inside Merchant Center, described as rolling out gradually in the US, with Australia and Canada to follow next year. The hub gives accepted merchants a sandbox to validate their UCP profile, test cart transfer to their own site, and exercise the native checkout APIs — and Merchant Center flags feed, returns, or account configuration gaps it finds along the way.

The documentation is fresh. Google’s developer guide for preparing Merchant Center for UCP was last updated October 2, 2026 — the operating detail below reflects that version.

The one-attribute gate

Everything Google published about eligibility reduces to three feed attributes and one account requirement.

native_commerce(checkout_eligibility) is a boolean. TRUE makes the product eligible for the checkout experience; FALSE or missing keeps it out. Google notes that an older native_commerce value still works as an alias, so a feed that already carried it does not need restructuring.

consumer_notice is required where regulations demand a warning — California Proposition 65 is Google’s own example. It carries a notice type (legal disclaimer, safety warning, or Prop 65) and a message capped at 1,000 characters, and Google renders it prominently on the checkout screen. If you sell apparel with chemical dyes, hardware with Prop 65 exposures, or anything carrying a mandatory warning, this attribute is how the warning travels.

merchant_item_id exists for identifier mismatches: the product ID in your feed must match the ID your checkout API expects, and where they differ, this custom attribute maps one to the other. It takes precedence in agentic requests when defined.

Google recommends deploying all of these through a supplemental data source rather than editing your primary feed — the same pattern the conversational attributes use. Your primary feed, synced from Shopify through the Google & YouTube app or your feed tool, stays untouched; the eligibility table is joined to it by product ID. Not every feed app supports custom attributes or supplemental feeds, so check yours before planning a manual upload.

What the checkout reads besides the flag

Two account-level requirements in Google’s guide are really listing infrastructure in disguise.

Return policies are mandatory. Google requires return cost, a return window, and a link to the full policy — configured in Merchant Center, submitted per product through the returns attribute, or scoped with a return_policy_label. The reason is physical: the policy is referenced on the checkout screen Google renders. A blank policy is not a style problem anymore; it is missing checkout input. We covered why return rules became a trust signal for apparel listings — with UCP, the same data became transaction plumbing.

Customer support information is required too: at least one of a support URL, email, or phone number, because it generates the contact link on the order confirmation page.

The exclusion list is a catalog audit

Google publishes the product categories that are ineligible for checkout, and it reads like a description of the Shopify stores that get silently disqualified: subscriptions and installment plans, personalized goods like engravings and monograms, refurbished and final-sale items, pre-orders, bundled services such as warranties and installation, age-restricted products, and digital goods.

If that list feels familiar, it should. When Muse gained agentic checkout through Shop Pay, the exclusions were nearly identical: subscriptions, bundles, customizable products built on line-item properties. Two independent checkout programs, run by different companies, converged on the same catalog boundaries. The practical consequence for a Shopify seller: if you restructured your catalog for Muse eligibility last month — turning a bundle into a standard variant product, splitting a subscription into one-time purchases — that work transfers. Agent checkout eligibility is converging into one catalog hygiene checklist, which is the core of Shopify Product GEO.

For ineligible items, set the attribute to FALSE or leave it empty and move on. Nothing else changes: the products keep serving in ads and free listings exactly as today. Eligibility is a transaction gate, not a visibility gate.

Why Shopify sellers are already halfway there

The protocol Google runs this on is not something Shopify joined last week — it helped found it.

Shopify and Google are the permanent members of the UCP Governing Council, with Stripe joining in April 2026. In September 2026 the protocol formed its Payments Technical Council — eight members including Shopify, Google, PayPal, Adyen, and Stripe — to govern how agents pay across the ecosystem. And on September 4, 2026, Shopify announced that every Shopify storefront now advertises support for UCP version 2026-08-25 in a discovery profile at /.well-known/ucp, a machine-readable file agents read to negotiate what a store can do. Shopify’s changelog describes it as requiring no merchant action — platform plumbing, shipped platform-wide.

Read that trajectory as a Shopify seller: the rails your storefront speaks and the rails Google’s checkout runs on are the same rails. The GEO for marketplace sellers job — making products visible and recommended to AI — now has a transactional twin, and both are fed by the same structured listing data: titles, options, policies, and now an explicit commerce flag.

One honest boundary: full UCP integration includes developer work — a UCP profile, authentication, and checkout API endpoints that Google’s sandbox validates. Google’s own FAQ tells merchants on third-party platforms to ask their platform about integration plans. The Merchant Center half, though — eligibility attributes, return data, support info, identifier hygiene — is feed and settings work you can start now, which is exactly what the waitlist review will look for.

What to inspect this week

Work in this order, in Merchant Center and your Shopify admin — not in Search Console.

1. Audit which SKUs could qualify. Walk your catalog against the exclusion list. Standard variant products — a tee in three colors, four sizes — qualify. Subscription boxes, engraved goods, final-sale clearance, pre-orders: flag them ineligible now so the decision is deliberate.
2. Check your return policy completeness. Return cost, window, and policy link — in Merchant Center settings, in your Shopify Settings > Policies page that feeds it, or per product through the returns attribute. Advanced accounts need this per sub-account.
3. Verify customer support info. At least one contact method in Merchant Center. If your Shopify theme’s contact page is the only place it lives, surface it where the feed can read it.
4. Stage the supplemental feed. A three-column table — ID, native_commerce(checkout_eligibility), consumer_notice — covers most catalogs. If any product carries a mandatory warning, draft the 1,000-character message now; Google’s own formatting example includes the HTML it accepts.
5. Map your identifiers. Compare the product IDs in your feed with what your checkout integration would use. Mismatches are what merchant_item_id exists for, and discovering them in Google’s sandbox is cheaper than discovering them in production.
6. Submit the interest form. The hub is rolling out gradually in the US; the form is how Google knows to look at your account.

None of this is schema markup. None of it is Search Console. It is listing and feed hygiene, which is the pattern across everything agents now read — the same fields we walked through for Google’s conversational attributes and for Muse eligibility.

What this does not guarantee

Setting the eligibility flag does not promise a sale, a rank, or even a button. Google shows the checkout experience on surfaces and to merchant cohorts it selects; eligibility is a precondition, not a placement. Google does not claim UCP participation affects AI Mode rankings or Shopping placement, and FirstShelf does not claim it does either. What the flag changes is narrower and more durable: when Google does render a checkout on one of its AI surfaces, your product’s data is ready to be the one that can be bought.

The limitation cuts the same way as every agent surface we have covered: a checkout that reads your feed can only transact on what your feed says. A return window that exists in your store but not in your feed is a return window Google cannot quote. An ID that differs between systems is an order that cannot route. The fix is a listing audit, not more integration configuration.

How FirstShelf can help

FirstShelf audits the exact surfaces this checkout reads: the structured fields in your Merchant Center feed, the policy pages behind them, the variant and option names agents match on, and the identifier consistency a checkout depends on. We score them the way AI shopping systems do and return a prioritized fix list — which products should carry eligibility, which listing models disqualify themselves, which return and warning data is missing before Google’s sandbox looks for it. That is the work that decides whether an agent can finish what it recommends.