On 14 January, Salesforce announced native support for the Universal Commerce Protocol in its commerce line, letting merchants "enable native checkout and direct buying experiences on Google AI commerce surfaces." What the announcement did not carry was a date. Its own small print said that any unreleased features referenced "are not currently available."

Eight months later there is a date. In the Salesforce and Google Cloud announcement published on 15 September during Dreamforce, the availability list is explicit: the product catalog feed into Google Merchant Center is generally available now, and the integration with the Universal Commerce Protocol is generally available in October 2026. The shopper-facing version of the same sentence reads: "Starting this Fall, shoppers can seamlessly discover and purchase products directly within Google Search, including AI Mode, and the Gemini app, powered by Commerce Cloud."

That makes this a good moment to write down what Salesforce Commerce Cloud storefronts declare before the integration ships, so there is something to compare against afterwards.

#Two different paths, one announcement

The availability list is worth reading closely, because it describes two mechanisms that are easy to collapse into one.

The feed path sends catalog data to Google Merchant Center through a native integration in Business Manager. That is a snapshot: product data is exported, ingested, and served from Google's side. It is generally available today.

The protocol path is the one that arrives in October. UCP is how a storefront describes, in a machine-readable manifest at a known location, which commerce capabilities an agent can actually call against it — search the catalogue, build a cart, complete a checkout — and then serves those calls live. Salesforce's framing keeps the merchant in place behind it: purchasing happens inside Google surfaces "while keeping payments, compliance, and order management securely on their existing commerce infrastructure."

The distinction matters for anyone measuring adoption. A merchant can be visible in Google's shopping surfaces through the feed while declaring nothing over the protocol. The two milestones are three weeks and a category apart.

It is the same split the Bulk Product Discovery working group has been working through since its kickoff: a feed is a point-in-time snapshot, and the real-time interfaces stay authoritative for the last mile.

#What the storefronts declare today

Zero.

We added Salesforce Commerce Cloud as a tracked platform this week, and the platform page currently reports no verified storefronts. Across roughly 21,400 storefronts we recrawl every 24 hours, not one site we can identify as Commerce Cloud publishes a valid UCP manifest.

Given that the integration is generally available in October, zero is the expected number. Nothing has shipped yet for a merchant to turn on. The useful part is not the count but the shape of the baseline, and there are two details in it worth recording now.

The first is that Commerce Cloud storefronts are unusually hard to see from the outside. A large share of the ones we know about sit behind an edge security layer that answers our manifest request with a 403 and no body at all. A fetch that returns nothing cannot be attributed to a platform, so any count of Commerce Cloud storefronts we publish is a floor rather than a census. We would rather say that plainly than imply our sample is the market.

The second is what those storefronts return at the manifest path. Requests to /.well-known/ucp on Commerce Cloud sites do not come back as a clean 404. They come back as a 200 carrying the storefront's own HTML — the standard catch-all behaviour of a storefront that routes unknown paths to a page rather than declining them.

To a person that difference is invisible. To an agent it is not. A 404 is a clear answer: this site does not speak the protocol, move on. A 200 with HTML in it is a site that appears to have answered, and the agent has to parse the response before it can conclude the same thing. Every storefront on a platform that behaves this way makes the same demand of every agent that visits it. It is a small thing, and it is worth platforms deciding deliberately rather than inheriting.

#What we will be watching in October

Four things, all of which the baseline above makes measurable:

• The first valid manifest. Which storefront declares first, and how long after general availability.
• Where the manifest lives. Whether Commerce Cloud merchants declare on their own domains at /.well-known/ucp, or whether Salesforce serves declarations on their behalf from platform-hosted endpoints. The protocol has more to say about what a manifest contains than about who is allowed to host it for whom, and a platform of this size answering that question in practice is informative.
• Which version they declare. The current release is v2026-08-25. Platforms arriving now can start there or land on the April release, and that choice determines which capabilities their merchants can negotiate on day one.
• Whether the catch-all goes away. A storefront that starts serving a real manifest at the manifest path has, by definition, stopped serving the catch-all there. Whether that change reaches storefronts that have not enabled the integration is a separate question, and a visible one.

None of that requires taking a position on whether the integration is good. It requires only that somebody wrote down what was true beforehand. That is what the page above is for, and we will publish the after picture once October has run.

UCP Checker recrawls roughly 21,400 storefronts every 24 hours and publishes what each one declares. The Salesforce Commerce Cloud platform page updates as that changes, alongside the Shopify, WooCommerce and other platform pages.

#About UCP Checker

UCP Checker is the independent validation and observability layer for the Universal Commerce Protocol. We crawl, validate and grade every public UCP manifest we can find, run the merchant directory, the UCP Score, live adoption stats, the vertical guides and the authority-bound vendor map, and track the spec as it evolves so you don't have to — measured from two vantages (what a business declares, and what actually happens when an agent transacts), the same way for everyone, without picking winners.

#Sources

• Salesforce and Google Cloud Unify Infrastructure and Agents for One Connected AI Stack (15 September 2026)
• Salesforce Announces Support for Google's Universal Commerce Protocol (14 January 2026)
• Salesforce — How Agentforce Commerce and Google UCP power the future of agentic shopping
• Salesforce — Agentforce Commerce release announcement
• UCP specification v2026-08-25
• UCP Checker — Salesforce Commerce Cloud platform page
• Related coverage: UCP's first working group is meeting · Shopify's Storefront MCP after August 31 · The v2026-08-25 spec update · Agentic commerce adoption, measured · What shopping agents do when the store misbehaves · Connect any agent to every verified UCP store · Product discovery