Agentforce
Commerce Cloud checkout inside Google Search: what UCP changes for merchants in October
From October, a Commerce Cloud merchant can let a shopper find a product in Google's AI Mode or the Gemini app and buy it there, with the merchant still the merchant of record. The protocol underneath is Google's Universal Commerce Protocol. This is what it does, how it differs from the OpenAI checkout spec, what stays yours, and what to fix in your catalog before the button goes live.
A shopper asks Google’s AI Mode a question, sees your product in the answer, and buys it right there. The order lands in your Commerce Cloud instance. You fulfil it, you handle the return, you own the customer. Google took the click.
That flow is what Salesforce and Google put a date on at Dreamforce. The product feed from Commerce Cloud into Google Merchant Center is generally available now, and checkout through Google’s Universal Commerce Protocol reaches general availability in October 2026, per the September 15 announcement. The protocol itself was announced in January and Salesforce committed to supporting it the same week. October is when it stops being a roadmap slide.
Whether it is good news depends on what you sell and how clean your catalog is. This post covers what UCP does, how it sits next to the OpenAI checkout spec that most merchants already looked at, what you still own when the checkout is on someone else’s page, and the list of things to fix before you switch it on.
What UCP is
The Universal Commerce Protocol is Google’s open standard for connecting consumer AI, Gemini in particular, to a merchant’s backend. Google’s own framing is that it gives models a common way to check inventory, apply loyalty, and complete a purchase against the merchant’s systems rather than scraping a storefront.
The Merchant Center documentation describes the shopper-facing result: a checkout button on eligible product listings in AI Mode in Search and in the Gemini app, with the transaction completed on Google’s surface while the merchant stays the merchant of record.
For a Commerce Cloud merchant, Salesforce’s part is the native implementation. You do not build the UCP endpoints. Commerce Cloud exposes catalog, inventory, pricing and order creation through the protocol, with Google Pay support on the checkout, and the order flows into your existing order management.
Merchandising, fulfilment and customer service stay with you. That is the arrangement Nitin Mangtani, who runs Commerce and Retail at Salesforce, and Google’s Ashish Gupta described in January, and it has not changed.
SharkNinja is the named early merchant. Its CIO, Velia Carboni, put the pitch in one line in the September announcement: with products surfaced across Google and UCP checkout on the results page, the path from discovery to purchase gets shorter.
UCP next to ACP
Most merchants I talk to have already looked at agentic checkout once, because of OpenAI. The Agentic Commerce Protocol, which OpenAI and Stripe published, is what lets a product be bought inside ChatGPT. I wrote about what a Salesforce merchant should build for it in July, and the feed spec and checkout flow there are different from Google’s.
The two are not competing standards for the same thing so much as two doors into two different audiences. ACP puts your products in front of ChatGPT users. UCP puts them in front of Google Search and Gemini users.
A merchant of any size will end up wanting both, and the encouraging part of the Salesforce position is that Commerce Cloud is doing the protocol work on each side. Your job is the catalog and the operations underneath, which are the same for both.
Where they differ operationally is worth knowing. ACP’s product feed is a file you push to a provided endpoint on a schedule. UCP’s discovery runs from the Merchant Center feed you already maintain for Shopping ads, fed from Commerce Cloud’s Business Manager. If your Merchant Center feed has been neglected because you stopped running Shopping campaigns, UCP inherits every gap in it.
What you still own when the checkout is not on your site
The phrase “merchant of record” does a lot of work in these announcements, and it is worth unpacking what it means in practice.
You own the price. The price Google shows must be the price Commerce Cloud returns, and a shopper who sees one number in AI Mode and another in your order confirmation is a chargeback waiting to happen. If you run price books that vary by customer group, decide which one an anonymous Google shopper gets before you enable the feed.
You own inventory truth. UCP checks stock in real time against your backend. If your inventory in Commerce Cloud lags your warehouse by an hour, you will sell things you do not have, and the customer service call comes to you, not Google.
You own returns, refunds and the customer record. The order arrives with a Google-side identity that may or may not match a customer you already have. Whether that shopper becomes a known customer in your CRM, with their history and their consent, depends on identity linking you configure, not on Google. This is the same identity resolution problem Data 360 exists to solve, with one more source.
You do not own the session. The discovery, the comparison and the moment of decision happened on Google. Your analytics will see an order appear with a referrer and little else. Attribution models built on site sessions will undercount this channel from day one, and anyone whose bonus depends on conversion rate should know that before October.
What to fix before you switch it on
The good news is that everything on this list improves your existing storefront too.
Start with the Merchant Center feed. Titles, attributes, GTINs, availability and image quality decide whether a product is eligible to show in AI Mode at all. Run the feed diagnostics in Merchant Center, and fix the disapprovals before you think about checkout.
Then test inventory latency end to end. Place a test order through your own storefront, and measure how long the stock decrement takes to reach the value Commerce Cloud returns through the API. That number is your exposure window on every UCP sale.
Decide the anonymous price book and the promotions that apply. A promotion that needs a code will not apply on Google’s checkout unless the protocol carries it, so assume list price plus whatever Commerce Cloud applies automatically.
Map the order path. A UCP order should land in the same order management flow as a storefront order, with the same fraud screening. If your fraud rules key on session behaviour, they have nothing to key on here, so check what your provider does with an order that arrives with no session.
Then decide the analytics question. Tag UCP orders as their own channel in whatever you use for reporting, and agree with marketing how the channel is attributed before the first order arrives, not after.
If you are running the Shopper agent on your own storefront, the two are complementary rather than redundant. The Shopper agent guides a customer who came to you. UCP catches the customer who never would have.
Who this is for, and who should wait
UCP is for merchants whose products are searched for by name or by need, in categories where Google is the starting point. Consumer electronics, home goods, apparel, anything with a GTIN and a comparison shopper. SharkNinja is a good example of the shape.
It is a smaller win for merchants whose catalog is configurable, quoted or B2B. A product that needs a conversation to price does not belong on a one-tap checkout, and the B2B Buyer agent is the right tool there.
Wait if your Merchant Center feed is a mess, if your inventory sync is nightly, or if legal has not signed off on a checkout that happens off your domain. October is a date, not a deadline.
Understanding the basics
What is the Universal Commerce Protocol?
UCP is an open standard from Google that connects consumer AI, including Gemini and AI Mode in Search, to a merchant’s backend for inventory checks, loyalty and checkout. A shopper can find a product in Google’s AI answers and buy it there, with the merchant remaining the merchant of record.
When can Commerce Cloud merchants use UCP checkout?
The product feed from Commerce Cloud into Google Merchant Center is generally available now. UCP checkout inside Google Search and the Gemini app is dated for general availability in October 2026, per Salesforce’s September 15 announcement with Google Cloud.
Do I need to build the UCP integration myself?
No. Salesforce implements UCP natively in Commerce Cloud, so catalog, inventory, pricing and order creation are exposed through the protocol without custom endpoints. Your work is the Merchant Center feed, price and inventory accuracy, and the order and analytics path on your side.
How is UCP different from the OpenAI Agentic Commerce Protocol?
They serve different audiences. ACP, from OpenAI and Stripe, enables purchases inside ChatGPT and uses its own product feed. UCP enables purchases in Google Search and Gemini and runs off your Merchant Center feed. Commerce Cloud supports both, so a merchant can be present in each without separate builds.
The catalog was always the product
Every agentic checkout announcement, Google’s or OpenAI’s, ends up at the same place. The protocol is the vendor’s problem. The catalog, the inventory truth and the price consistency are yours, and they were yours before any of this existed.
October gives you a reason to fix them with a date attached. Take it.
If you sell on Commerce Cloud and want the feed, the price book and the order path checked before UCP checkout goes live, talk to us, or size the wider agent case first with the Agentforce ROI calculator.
