E-commerce
August 19, 2026
This sheet describes a Google Assistant with a "Buy for me" agentic checkout funnel on Search AI Mode and Gemini. It tags automatic purchase, all merchants, USA, buyer's card, price alerts, Shopping Graph. No Gross Merchandise Volume (GMV), no accuracy rate, no list of eligible stores. This article does not have them either. It separates three business lines that the directory lumps under one logo: being discoverable in Google listings, cashing in via UCP if Google approves you, and not confusing this with Amazon Buy for Me. Lumping them together means budgeting a purchase in the chat in the US that you do not have, or a Merchant Center feed you already have.
Google launched the Universal Commerce Protocol (UCP) on January 11, 2026 as an open standard for the entire journey (discovery, purchase, after-sales), compatible with A2A, AP2, and MCP. First public deliverable: a checkout funnel on eligible Google product sheets, in AI Mode Search and the Gemini app, eligible US stores, Google Pay and Wallet, PayPal announced, with the store remaining the merchant of record. The Google Merchant UCP Developer Guide: Merchant Center (feeds, port, returns), waiting list, Google approval before being visible on AI Mode and Gemini, Google Pay manager, UCP profile, three REST access points (create, update, terminate a session), guest by default or OAuth for a linked account, status webhooks. Two texts. One logo. Not "all merchants".
If the idea of a software buyer is new: what agentic commerce is. The 2026 timeline: what has been delivered. Other sheets: AI buying agents. Official totals remain human purchasing journeys: 2026 e-commerce statistics.
Summary
Three professions under one Gemini logo
Three Google artifacts under "Gemini shopping." They are not configured in the same place.
Role | What the directory describes | What Google documents |
|---|---|---|
Discovery | Prompt, Shopping Graph, price, reviews, availability, alerts | Merchant Center feed, listings, discovery attributes. Not a "Shopping Graph" specification in our two URLs |
UCP checkout funnel | Gemini collects payment for you, Google Pay, cart and automatic shipping | Eligible US listings, waitlist, 3 access points, merchant of record, Wallet |
Other Google products | Absent from the map (Business Agent, Direct Offers) | Brand chat in Search; "Sponsored deal" Ads pilot. Different contract |
Lumping AI Mode and Gemini together makes sense: the post and the guide talk about both interfaces. Reading "Buy for me" as the Amazon product, or "all merchants" as an indexing of the open web, does not. UCP, at launch, means eligible Google listings, eligible US brands, and an approval. Not Nordstrom just because the directory has a Nordstrom badge elsewhere.
Automatic purchase plus "buyer's card": two badges, two stories. Google talks about payment credentials already in Wallet, via a Google Pay manager. It is not Operator typing into your theme's card field. Nor is it, in these texts, a Stripe ACP token.
A merchant who "chooses Gemini" like a payment provider has read the title, not the waitlist. You do not install Gemini. You run a Merchant Center, you apply for UCP, Google approves or not. That is the entire collection channel.
The directory's filters by task (search, price, deals, checkout funnel) are use cases, not four integrations: shopping agents by task.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
The UCP: one track, one waiting list, three access points
UCP is not a conversational agent. It is a language for agents and merchant backends to talk about discovery, cart, checkout, and after-sales. Google calls it open, across all sectors. The first concrete example is Google itself: buying from AI Mode and Gemini.
On January 11, 2026, the "soon" checkout pipeline targets eligible listings, buyers in the US, Google Pay, info already in Wallet, with PayPal later. Customizing the integration is announced. Global expansion and extras (related products, loyalty, personalized experiences): in the coming months, not this week. Co-developed with Shopify, Etsy, Wayfair, Target, Walmart, and a list of partners who have endorsed it. These are protocol partners. This is not your "Gemini is already selling at Target" slide.
The Merchant guide is drier, and therefore more useful. Active Merchant Center account, products eligible for checkout, shipping and returns configured. Then waitlist, contact Google, approval before being visible. Then Google Pay. Then an UCP profile (capabilities, payment processors, public keys). Then three REST: create, update, complete. Guest by default. Linked account: OAuth 2.0. Order status: webhooks to Google.
Implementing UCP "somewhere" and appearing in Gemini are two separate requests. The guide states: the integration must be approved before being visible on AI Mode and Gemini. A missing /.well-known profile does not process payments. The axes where the tracks diverge: how protocols differ. Platform framework: what platforms need to change.
MCP appears as a compatible protocol, not as the checkout pipeline. Do not pay for a "Gemini shopping MCP server" instead of a feed and a waitlist. Vocabulary (merchant of record, session, listing): agentic commerce glossary.
Not all merchants are eligible for a listing
The directory aligns "all merchants". Google, in both texts, aligns eligible Google product listings and eligible American brands. A Magento store without Merchant Center is not in this tunnel. A product reference without a feed is not compared. Discovery work: what a machine needs to compare.
"Shopping Graph" is the directory's term for the Google shopping index. Our two URLs talk about Merchant Center, listings, and tunnel eligibility. We do not source a magic graph beyond that. Being in the graph, for you, starts with a real feed: price, stock, identifier, shipping.
Alerts and target price (step 2 of the directory): absent from the UCP post and the checkout tunnel guide. Treat them as a directory user guide, not a 2026 specification. Same goes for review summaries and bargain hunting on the map: buyer behaviors, not UCP access points. Google bargains are more like Direct Offers (advertising), not a coupon bot: bargain hunting.
Discovery can work without the UCP tunnel. A Merchant Center listing informs AI Mode. The checkout tunnel waiting list is a second request. Merging them means requiring a mandate just to be findable. Reverse it: feed first, session second.
Product search (Q&A, variants) and price comparison (ISO 4217, parity) remain catalog work, Gemini or not: product search, price comparison.
The funnel: Google Pay is the merchant of record, not your theme
Step 3 of the directory: "Gemini completes the purchase on your behalf" with Google Pay, cart, port, automatic payment. This is the buyer journey. The merchant journey, in the guide, is a REST session plus a Pay handler.
Eligibility: US at launch of the post. Eligible listings and brands. Not "global". The directory itself says US: on this point, it is more honest than "all merchants".
Approval: waitlist then OK Google. Without this, no AI Mode or Gemini visibility, says the guide. A local access point is not enough.
Guest or account: guest by default. Linked account: OAuth to sync profiles. Two depths. A checkout word.
After purchase: status webhooks to Google. The directory says to track the order via Google. Your order system must still deliver and refund.
Merchant of record: the brand, the post repeats. This is not a legal opinion of this site. Chargebacks, 3-D Secure, Strong Customer Authentication (SCA): ask the acquirer how a Wallet purchase in AI Mode is coded. Reason codes do not say "Gemini misread the size". Breakages: where agentic commerce still breaks.
Your site's pixel will not see a CPU session in the chat. You will have an order, a webhook, maybe a Merchant line. If you judge Gemini by the last click on the site, the funnel disappears. Decide attribution before the waitlist, not after the first internal disagreement.
The checkout category of the directory mixes Gemini and Honey. Mechanisms: agents for the checkout. Here, the mechanism is a Google session, not a JavaScript coupon.
Buy for me, ACP, Claude: other contracts
The Gemini listing says "Buy for me agentic checkout". Amazon has a separate product. Two names. Two stacks. Do not merge them into one slide.
Product | Where it cashes out | What you control |
|---|---|---|
Gemini via CPU | Google surface (AI Mode, Gemini app), eligible listings | Merchant Center, waitlist, access points, feeds |
Amazon Buy for Me | Consent in the Amazon app, then agent on your checkout funnel | Theme, web application firewall, 3-D Secure, Amazon eligibility |
ChatGPT via APC | Agent session if integrated, other specification | OpenAI application or Stripe blocks, not CPU |
ChatGPT has APC. Copilot has a US Checkout documented by Microsoft, plus an MMC feed. Claude clicks your theme in Chrome. Three contracts. One word "agent" in a presentation. Gemini is not a headless browser on your product page for the CPU funnel. It is the opposite: the buyer stays on Google.
Business Agent (brand chat in Search, US pilot, Merchant Center) is not the Gemini listing. Direct Offers is not a Gemini bargain-hunting capability: it is advertising. A pitch "we put you in Gemini" can sell all three, plus CPU, plus a directory listing. Five deliverables. Ask which one.
Shopify, cited among the co-developers of the CPU, can already syndicate a catalog to Google surfaces. This is not, in our two URLs, proof that your Shopify store is already cashing out in Gemini. Read the Agentic admin interface and eligibility, not the directory.
What this sheet does not measure
This sheet does not measure anything that matters after "Pay".
Volume: no Gemini gross merchandise volume (GMV) or AI Mode in the post or the guide. "Soon" and waitlist are not a cost-per-acquisition channel.
Coverage: all merchants is a label. Eligibility is a Google process. We do not invent a list of brands in production.
Alerts: target price: directory instructions. Not in either source.
After-sales service: tracking via Google plus delivery to your home. Two doors. No after-sales service protocol in these pages.
Do not budget this sheet as a channel for Europe. The post places the funnel in the United States first, expansion later. An EU merchant copying the guide word-for-word is copying a product that, today, does not target them. They are left with feed and discovery.
A Verified listing on this site does not buy an endorsement from the UCP. Editorial and waitlist remain separate.
Funnel automation and auto-purchase, on the map, are labels. It is not an order volume. We do not recycle them as metrics.
Three requests, not seven capacities
This week, by request, not by logo.
Discovery: Merchant Center: price, stock, identifier, shipping, returns. Product detail page parity. Discovery attributes if you have them. Useful even without a waitlist.
Checkout tunnel: read the guide: waitlist, Pay, UCP profile, three RESTs, guest or OAuth. Do not code before having a Google contact, unless you accept the research and development risks.
Internal naming: ban the "Buy for me" slide without saying Google or Amazon. Label UCP orders outside of the last-click site.
The unique test: would this work still be useful if Gemini closed the tunnel tomorrow and only kept AI Discovery Mode? A true feed, yes. An exclusive "Gemini session only" connector, no.
Name the owners: merchandising or Merchant Center for the feed, payments for Google Pay and disputes, engineering for the three access points, measurement for attribution. A single "Gemini owner" stops at the first waitlist.
If you only have one hour: open Merchant Center, five references (price, stock, shipping). Ask who has a Google Pay business account. Read the waitlist. Do not read the seven capabilities of the directory like a specification sheet.
You don't turn on Gemini like a channel
You don’t turn on Gemini like a Shopify Agentic channel you already have. Buyers open Gemini and AI Mode. You maintain a feed and, optionally, an approved session. The card badges are not buttons.
If a seller promises to place you "in Gemini," ask: Merchant Center feed, UCP waitlist, Business Agent, Direct Offers, theme, or directory listing. Six deliverables. One word.
UCP is chosen when the checkout mechanism is truly a Google session. To merely be findable, the protocol is already the feed. Reporting the three RESTs is not the same as reporting a lying [price].
After confirmation, it’s your dispute, your package, your return. Google is no longer the sole customer service because tracking is displayed with them. The directory has collected nothing.
A Google surfaces index, not a ranking
Gemini shopping is splitting into discovery and payment funnel. The logo has not "replaced" Merchant Center. UCP has not "replaced" Amazon Buy for Me. This sheet is a starting point: Google surfaces, US eligibility, waitlist, not all merchants. The only card you hold: the feed and, later, the session.
Treat it like an index: are you findable, are you eligible to collect payment, have you named the product (Google or Amazon). Three questions. Not a ranking of assistants.
You can ignore UCP and still sell via a Search listing. You can refuse Gemini and keep ACP. You can be outside the United States. The directory does not decide. Your Merchant Center and your geography, however, do decide.
Next, open the UCP guide and a neighboring sheet (ChatGPT or Amazon Buy for Me). Ask each time: where the payment takes place, who approves the integration, which artifact you control.
Flow first, session second
The owner is not "Gemini growth". It is Merchant Center plus, if applicable, payments and session engineering. A single owner stops at the first incomplete flow.
After the waiting list, buyers come according to Google, not according to the directory. You do not turn on a "7 capabilities" button. You deliver a readable catalog and a checkout funnel that Google has accepted, or you remain in discovery.
If the committee wants a figure: there is none here. "Soon", "eligible", "waiting list" are launch words. A channel is budgeted on attributed orders, not on an automatic purchase badge.
Frequently Asked Questions
Is Gemini already collecting payments for everyone?
No. The post from January 11, 2026, describes a payment tunnel soon to be available on eligible US profiles, AI Mode, and the Gemini app. The guide requires a waitlist and Google approval. The automatic purchase badge in the directory is not this eligibility.
Does "All merchants" mean my Magento?
Not in the two cited texts. This means, at best, that the buyer can talk about any brand. The documented tunnel is Merchant Center plus eligible profiles. Without a feed, you are not in the Google comparison.
Is Gemini Amazon Buy for Me?
No. The Gemini sheet borrows "Buy for me." Amazon Buy for Me is an agent on your tunnel after an Amazon checkout page. The UCP keeps the buyer on a Google surface. Two contracts.
Are ChatGPT and Gemini on the same track?
No. Stripe and OpenAI document the ACP. Google documents the UCP. Two integrations, two specifications, two waitlists. Neither do Copilot and Claude.
Is Google Pay required?
For Google's implementation of the UCP tunnel, the guide requires a Google Pay manager and Wallet credentials. PayPal is announced in the post, but not as a button we can date here. The guest tunnel is the default identification, not the absence of Pay.
What to do this week?
Merchant Center parity. Read the waitlist. Do not budget Europe for a US tunnel. Do not merge Business Agent, Direct Offers, and the UCP. Postpone the three RESTs as long as approval does not exist, except for research and development.
Are price alerts documented?
In the directory, yes. In the post on the UCP and the payment tunnel guide, no. We do not source them. Do not sell them as a feature you configure.
Sources
Enzo
August 19, 2026
