Your Google commerce problem this week is not another buy button.
On September 22, 2026, Barry Schwartz at Search Engine Roundtable reported that Google is emailing Merchant Center users whose platforms support the Universal Commerce Protocol. The subject line lands soft: your products are now eligible for native checkout. The body is harder. If your Shopify store was matched to Merchant Center, eligible products are automatically included for native checkout on AI Mode in Google Search and on Gemini. There is nothing for you to set up. If you want buyers to finish on your online store instead, you turn native checkout off in Shopify admin under Sales channels > Agentic.
That is not a feature celebration. That is a default channel decision made for you while your catalog looked fine.
Catalog sync is not checkout policy. The control surface is who owns the customer and order path, plus the feed attribute that actually gates eligibility.
What the email actually said
Keep the operational facts tight.
Fact one: auto-match, auto-include. Schwartz quotes the email Menachem Ani posted: your Shopify store was matched to your Merchant Center, enabling native checkout on Google AI Mode and Gemini. Customers can buy in AI Mode on Google Search, Gemini, and more. The seamless checkout is powered by UCP. Eligible products must be published on the Shopify storefront and available in Merchant Center. Eligible products are automatically included.
Fact two: opt-out lives in Agentic, not in a Merchant Center checkbox. Google’s own wording in the email, per Schwartz: you manage and retain full ownership of your customer relationships, data, and sales. If you would rather have buyers complete purchases on your online store, turn off native checkout in Shopify admin under Sales channels > Agentic. The switch is a sales-channel control, not a feed upload ritual and not a Google Ads campaign setting.
Fact three: this is a broader push of something that already existed for limited merchants. Schwartz notes UCP-powered checkout launched in February, with a wider retailer push referenced as the prior Friday. Google Pay sits in the payment path. Nic McDonough posted seeing it live the morning of Schwartz’s piece. Limited availability turning into matched Shopify defaults is the news, not the invention of buy-in-chat.
Fact four: Shopify already positioned Agentic Storefronts as the admin home. Shopify’s January 11, 2026 newsroom post announced UCP co-developed with Google and said native shopping on Google surfaces would be managed from Shopify Admin through Agentic Storefronts. Shopify’s June 18, 2026 how-it-works guide restates the merchant-of-record claim, AI-channel attribution into admin, and direct-checkout toggles for Microsoft Copilot and for AI Mode / Gemini. ChatGPT checkout still completes on the merchant store via in-app browser in that guide. Google’s email is the moment the default flipped from “you can” to “you are, unless you turn it off.”
Bright line against last month’s tickets
This essay is not a rematch of Vault’s recent commerce and media stack. Say the fences once.
Not The catalog is the campaign: Shopify ChatGPT Ads catalog craft. Not The country is not the playbook: ChatGPT Ads geo open. Not bill-is-not-the-click (oCPM). Not click-is-the-conversation (Sponsored Agents). Not pipe-is-not-the-placement (Amazon DSP). Not search-term-is-not-the-journey or upgrade-is-not-a-toggle (AI Max). Not the-ad-is-the-associate (Business Agent). Not mix-model-is-not-a-report-card, crm-is-the-ads-console, or visual-search-is-the-auction.
Today’s ticket is checkout policy on an agent surface: default inclusion, eligibility attributes, ineligible SKUs, and who remains merchant of record when the buy button lives inside Google.
If your working group is still arguing ChatGPT Ads feed quality under a “Google checkout” subject line, you are in the wrong thread.
The Merchant Center control surface
Google’s UCP Merchant Center guide (updated August 25, 2026) is where operators should live this week, not the email screenshot.
Returns and support are Merchant of Record work. You must define return policies in Merchant Center. Return cost, return speed window, and a link to the full policy are required. Advanced accounts need policies at each sub-account. Customer support info must exist so Google can show a Contact Merchant link on the order confirmation page: at least one of website URL, email, or phone. If your return policy and support block are stale because free listings never forced the issue, native checkout will surface that debt on the confirmation screen.
Eligibility is a boolean, and missing means no. The feed attribute is native_commerce(checkout_eligibility). A single boolean. Set to FALSE or missing, and the product is not eligible. The guide is explicit that the default is FALSE. The older native_commerce attribute remains supported as an alias to checkout eligibility. Google recommends a supplemental feed so you do not break primary product ingestion while you flip SKUs.
Hold that against the email. The email says eligible products are automatically included for matched Shopify stores. The docs say the attribute defaults to FALSE when missing. Operators need to reconcile which layer is winning for their account: Shopify Agentic matching, Merchant Center free-listing approval, and the feed boolean. Do not assume “we sync the catalog” equals “every SKU can check out inside Gemini.”
Whole categories are ineligible on purpose. The guide lists financial products and recurring billing (subscriptions, installments), personalized goods, refurbished or final-sale items, pre-orders, bundled services, special shipping, gifting with split invoices, in-store activation, age-restricted goods, prohibited content, digital goods and services, rentals, virtual items, and software-dependent goods. Those should keep native_commerce(checkout_eligibility) empty or FALSE. If your catalog mixes subscription replenishment with one-shot hard goods, a blanket “turn on agentic” is how you create support tickets Google cannot fulfill inside the chat UI.
Consumer notices and ID mapping matter. Regulatory warnings (Prop 65 and peers) ride in consumer_notice with typed notice messages. Product id in the feed must match what your Checkout API expects, or you map with merchant_item_id. Wrong IDs are not a reporting nuisance. They break session creation when Google posts line items your API does not recognize.
What the checkout API commits you to
The native checkout REST guide for version 2026-04-08 (updated September 11, 2026) is the contract behind the button.
Google creates a checkout session with line items and limited address context. You return totals, taxes, fulfillment options, required privacy and terms links, and Google Pay handler config. Address updates force tax and shipping recalculation. Full hydration arrives before Pay with GPay. Complete is where you process payment with the token and return an order id plus permalink URL. Cancel exists. Unrecoverable stock failures return ucp.status error without a session id.
That flow assumes you are ready to be merchant of record inside Google’s UI: accurate tax, honest shipping options, fraud checks on Google’s signals, and a buyer-facing order permalink that is yours. Catalog sync alone does not implement /checkout-sessions. Shopify’s UCP integration is why matched Shopify merchants got the email without building those endpoints by hand. Custom stacks still owe the API work. Agentic-plan brands using Shopify as a sidecar still owe a clear answer on which system owns complete and which system owns fulfillment exceptions.
What operators get wrong
Mistake one: celebrating the buy button. Native checkout on AI Mode and Gemini is a distribution change. It is not proof your offer, margin, or post-purchase path survive an agent-mediated trip. Teams that screenshot the email for leadership without checking Agentic toggles and ineligible SKUs are performing launch theater.
Mistake two: treating catalog sync as checkout consent. Feed freshness, title quality, and image completeness decide discovery. They do not decide whether a SKU should settle inside Google. Eligibility is a policy attribute. Channel ownership is a toggle. Confusing the three is how a gift card, a subscription box, and a freight sofa all look “live” until session create fails or support explodes.
Mistake three: ignoring the opt-out path until the first angry order. The email is explicit: turn it off under Sales channels > Agentic if you want purchase on your store. Waiting for a blended ROAS readout before you decide channel ownership means Google already settled orders into a path you never briefed CX on.
Mistake four: assuming merchant-of-record language equals CRM control. Google and Shopify both say you retain customer relationships and data. The practical question is whether your lifecycle stack sees the order with the same identity keys, discount logic, and loyalty hooks you use on-site. If the agent checkout strips a loyalty credential your on-site checkout always asked for, you did not keep the relationship. You kept the refund liability.
Mistake five: running one policy for ChatGPT, Copilot, and Google. Shopify’s how-it-works guide draws different checkout shapes by surface. ChatGPT still points at your store via in-app browser in that documentation. Copilot and Google can embed direct checkout. A single “AI commerce on” slide hides three different ownership models. Brief each surface separately.
Mistake six: skipping return and support readiness. Confirmation screens will show your return policy and Contact Merchant path. If those Merchant Center fields were never maintained for free listings, native checkout makes the gap public at the exact moment the buyer paid.
Mistake seven: measuring the channel like a Shopping ad. Attribution into Shopify admin by AI channel is useful. It is not the same as Search query reporting. Decision work this week is eligibility coverage, opt-in intentionality, and post-purchase parity, not another ROAS chase on day one of a default match.
Second-order effects for commerce and marketing
Agency and in-house commerce pods get a new RACI. Who owns Agentic toggles? Who owns the supplemental eligibility feed? Who owns CX macros for “I bought this in Gemini”? If those names are blank, the email already assigned Google a role your org chart did not.
Margin math changes when shipping, tax, and fee lines are calculated in session rather than on a theme you A/B tested for years. The API allows fees, multi-tier tax lines, and tax-inclusive market display rules. Finance needs to see a sample complete payload before marketing promises “seamless.”
Brand and lifecycle feel the cut. If native checkout cannot carry your loyalty prompt or gift-message flow, you either accept a thinner relationship on that surface or you keep discovery on and checkout off. That is a brand decision disguised as a sales-channel checkbox.
Legal and risk sit closer to merchandising. Ineligible categories are not suggestions. Age-restricted, final sale, pre-order, and subscription SKUs that slip through become compliance and CX debt. Treat the ineligible list as a merchandising QA checklist this week.
What to do this week
Run this as a channel-ownership and eligibility sprint, not a launch party.
- Open Sales channels > Agentic before you open a celebration doc. Confirm whether native checkout for Google surfaces is on. Decide on purpose: keep embedded checkout, keep discovery with store checkout, or pause. Document the owner and the date.
- Reconcile eligibility layers. For a sample of hero SKUs, check Merchant Center free-listing status, Shopify publish state, and
native_commerce(checkout_eligibility)in feed or supplemental feed. Resolve conflicts in writing. Do not stop at “the catalog syncs.”
- Fence ineligible products explicitly. Map subscriptions, personalized goods, freight, final sale, pre-order, and age-restricted SKUs to FALSE or empty eligibility. Spot-check that none of them can create a Google checkout session.
- Audit Merchant of Record basics. Return policy completeness, support contact methods, privacy and terms URLs your checkout responses must return. Fix anything you would be embarrassed to show on a Google confirmation screen.
- Brief CX and lifecycle on the path. Give support the channel name, how refunds work, and whether loyalty or discount codes apply. Confirm order permalinks and identity matching into your CRM or ESP.
- Separate surface policies. Write one paragraph each for ChatGPT, Copilot, and Google AI Mode / Gemini: discovery only vs embedded checkout, and who owns the toggle. Stop using “AI commerce” as one switch.
- Pilot measurement without pretending it is Shopping. Track AI-channel orders in admin, refund rate, and ticket themes for two weeks. Refuse a blended AI ROAS claim until eligibility coverage and CX macros are intentional.
The email made checkout look like a storefront upgrade. It is not. The storefront is still yours to design. The checkout is a policy surface Google just defaulted for matched Shopify merchants. Own the toggle, own the attribute, own the order path, or someone else’s default will own your week.
