Google agentic checkout: how to sell in AI Mode and Gemini

Google's agentic checkout is the most concrete form of AI shopping available to merchants in late 2026: a shopper asks AI Mode or Gemini for a product, sees yours, and buys it without visiting your site, while the order, payment and customer relationship stay with you.

It is also the most procedural. Eligibility comes down to account settings, feed attributes and a checkout integration that follows the Universal Commerce Protocol. This guide walks through each step with Google's requirements, and the checks that catch the problems Merchant Center will not.

What is Google's agentic checkout?#

A way for shoppers to complete a purchase from an eligible product listing inside AI Mode in Google Search or the Gemini app, using the Universal Commerce Protocol. Google calls the default integration native checkout: your checkout logic is connected directly to AI Mode and Gemini, and the shopper confirms the purchase there.

Three points define it:

• You stay the merchant of record. Google's guidance is explicit: you keep your customer data and relationships, and own the post-purchase experience.
• Payments use your existing integrations. UCP supports tokenised payments and lets merchants keep their payment providers through what it calls payment handlers.
• It builds on your Merchant Center feeds. Products come from the feeds you already use for Shopping. Eligibility is an additional attribute, not a new catalogue.

For brands with complex or heavily customised checkouts, Google also offers embedded checkout, an optional path for approved merchants that renders the merchant's own checkout UI.

Which stores and products are eligible?#

Stores with a Merchant Center account in good standing and products approved for free listings, joining through Google's waitlist, for products outside the excluded categories.

Google's preparation guide excludes products that need anything beyond a simple purchase. Mark these ineligible:

Availability started in the US and Google describes it as rolling out; access is through a Merchant Center interest form. Check Google's current documentation for your market before planning around a date.

How do you set up Google agentic checkout?#

Prepare the account, mark eligible products in a supplemental feed, and connect a checkout that speaks UCP. Step through the setup below; the feed rows are illustrative.

1id               native_commerce(checkout_eligibility)  merchant_item_id2RL-TRAIL-WP-10   TRUE                                    ridgeline-trail-wp-103RL-TRAIL-WP-11   TRUE                                    ridgeline-trail-wp-114GIFT-CARD-50     FALSE5SOCKS-MONTHLY    FALSE6TRAIL-PREORDER   FALSE7 8Merchant Center: return policy ✓  customer support ✓  free listings approved ✓9UCP profile:     https://shop.example/.well-known/ucp  →  live checkout endpoints

A few details from Google's guide that are easy to miss:

• Consumer notices. Products that need a legal disclaimer, safety warning or California Proposition 65 notice carry it in the consumer_notice attribute group, with notice_type and a notice_message of up to 1,000 characters.
• Return policies on advanced accounts must be set on each sub-account. A return_policy_label limits a policy to a subset of products.
• Merchant API, not Content API. Attributes can be sent as custom attributes through the Merchant API; Google marks the Content API path as deprecated.

How does UCP fit in?#

UCP is the protocol between Google's agent and your checkout. Merchant Center decides which products may be bought; UCP is how the purchase is carried out.

A store that supports UCP publishes a profile describing its capabilities, starting with checkout, and the endpoints that implement them. In outline, Google's agent reads the profile and uses your checkout capability to carry out the purchase with your system, with payment passed as a token through your existing payment integration. UCP was co-developed by Google and Shopify and is published as an open standard; our protocol comparison explains how it relates to ACP, AP2 and MCP.

Most merchants will not write UCP themselves. Shopify generates the profile for its merchants, and other platforms are adding support. What remains yours is making sure the profile exists, points to live endpoints, and describes the same products, prices and stock as your feed.

What should you check before you go live?#

That the feed, the profile and the website all agree, and that each piece answers when an agent calls it.

1. Feed and page agree. Price, availability and title in Merchant Center match the product page. A disagreement is a policy problem in Merchant Center and a trust problem for any agent (feed and page disagree on price).
2. Eligible products are the ones you meant. Export the supplemental source and confirm no excluded category is marked TRUE (feed items cannot be bought in Google's agent checkout).
3. Ids line up. Spot-check that the id sent for a product is the one your checkout accepts, especially for variants (feed items have no merchant item id).
4. The UCP profile resolves. Fetch it, follow its endpoints, and check they respond.
5. Policies are complete. Return policy and support contact set, so the checkout screen and order confirmation have what they need.

What changes in day-to-day operations?#

Less than you might expect: orders arrive in your system as orders, and customers contact you as customers. But a few things are worth preparing.

• Order handling. Agentic orders are your orders, processed through your checkout integration. Fulfilment, confirmation emails and order status work as they do today; check that your order source or channel tagging distinguishes them so you can report on them.
• Customer service. The order confirmation in AI Mode or Gemini links to the support contact you set in Merchant Center. Make sure that address is monitored, and that agents answering it know orders can come from this channel.
• Returns. Your return policy is shown at checkout. Shoppers will hold you to it, so the policy in Merchant Center must match the one on your site and the one your team applies.
• Payments and fraud. Payment comes through your existing provider as a token. Your fraud rules still apply; review whether any of them treat orders without a browser session as suspicious and would cancel legitimate agentic orders.
• Reporting. Track agentic orders as a channel: volume, average order value, return rate. Early data will tell you which products and categories sell well this way.

Why might products not become eligible?#

Usually because of an account requirement, an excluded category, or data that does not line up. If products you marked TRUE are not appearing for checkout, work through these in order:

1. Account standing and free listings. Products must be approved for free listings, and the account must be in good standing.
2. Return policy and support contact. Both are required; a missing return policy is a common blocker, and advanced accounts need it on every sub-account.
3. Excluded category. A product classed as personalised, pre-order, subscription or age-restricted will not be eligible, whatever the attribute says.
4. Identifier mismatch. If the id Google sends is not one your checkout recognises, the purchase cannot complete. Use merchant_item_id where they differ.
5. Waitlist and rollout. Access is granted through Google's interest form and is rolling out by market. Confirm your account has been admitted.

Does Google agentic checkout replace your own checkout?#

No. It adds a way to buy without leaving AI Mode or Gemini; your site's checkout still serves everyone else, including other agents.

Shoppers will keep arriving at your store from search, from links in other assistants, and through browser agents acting on their behalf. Those paths depend on your own checkout working for agents: no bot rule refusing them at the basket, no CAPTCHA on the purchase path, and product data they can read. Google's integration is one surface. The rest of the work in what is agentic commerce still applies.

Written by the tragent team and checked against the sources listed above on October 19, 2026. See how we write and correct posts in our editorial policy.