Google Is Auto-Enabling Native Checkout on Products

On 22 September 2026 Google started emailing merchants whose ecommerce platform supports the Universal Commerce Protocol, and the wording of that email is the story. Search Engine Roundtable published the message the same day. It reads: “Your products are now eligible for native checkout.” Then, a line later: “Eligible products are automatically included. There’s nothing for you to set up.”

What the email actually says

The mechanism is inheritance, not application. If your platform supports the Universal Commerce Protocol and your store is matched to a Merchant Center account, eligibility follows without any action by you. The reported message describes exactly that chain — “your Shopify store was matched to your Merchant Center, enabling native checkout on Google AI Mode and Gemini” — and then tells the merchant where to turn it off, “in your Shopify admin under Sales channels > Agentic”.

Worth stating plainly: the automatic-inclusion wording comes from merchant emails reported in the trade press, not from Google’s published documentation. Google’s own merchant UCP pages describe native checkout as the default integration path but do not set out the automatic eligibility or the opt-out. If you are making a decision on this, the email in your inbox is currently better evidence than the documentation, which is an uncomfortable position to be in.

What changes for the buyer

The purchase completes inside AI Mode or Gemini. The buyer sees your product, your price and your availability, and pays without arriving on your domain. Everything you have built downstream of the add-to-cart click — the cart upsell, the shipping threshold nudge, the post-purchase sequence that runs off your thank-you page — is not in that flow, because that flow does not touch your site.

This is the concrete version of the shift described in when AI clicks instead of you. The difference is that this one is not a demo or an origin trial. It is switched on, on live catalogues, by default.

What you keep

More than the framing suggests. Google’s merchant UCP documentation is direct on the commercial position: “You remain the Merchant of Record” and “Keep all of your customer data and relationships.” It goes on to say you “retain full ownership of your customer relationships, data, and the post-purchase experience”. The discovery side is fed by infrastructure you already run — the documentation points merchants at their existing Merchant Center shopping feeds rather than a new integration.

Merchant of record is not a small thing. It means tax, refunds, chargebacks and the customer relationship sit with you, which is a materially different arrangement from a marketplace listing. It also means the accuracy of your feed is now the accuracy of a live checkout rather than of an advert.

What you lose, and it is not nothing

Three things, in rough order of how much they will hurt:

• The post-click experience. Bundles, cross-sells, free-shipping thresholds and anything else that depends on the buyer being on your page do not run.
• Attribution clarity. A conversion that never touches your site does not pass through your analytics the way an on-site order does, so your channel reporting will need reconciling against platform-side data rather than your own.
• Presentation control. Your product is rendered by Google’s surface from your feed. Photography, copy and layout that you tuned on your product template are not what the buyer sees.

Against that, an eligible product that opts out is a product that cannot be bought in a surface where someone is already asking to buy it. That is a real cost too, and it is the one people underweight because it is invisible in reporting.

The checks worth running in the next two weeks

Start with whether this applies to you at all: confirm whether your platform declares UCP support, and whether your store is matched to a Merchant Center account. Both are factual questions with fast answers, and a surprising number of stores are matched through an integration nobody currently on the team set up.

Then audit the feed as though it were a live checkout, because it is one now. Price, availability, variant-level stock, shipping and returns data all need to be correct at the moment an agent reads them, not correct on a nightly sync that lags a flash sale by six hours. The product-page fundamentals that feed most of this are covered in WooCommerce product pages, and the feed-side requirements in Google Shopping and product-feed SEO.

Finally, locate the opt-out before you have a reason to use it. Find the control in your platform admin, confirm who has permission to change it, and write down where it is. A setting you have found and deliberately left on is a decision; the same setting left on because nobody knew it existed is not.