Google has started rolling out a UCP integration hub inside Merchant Center accounts in the United States, giving merchants a direct path to add agentic checkout buttons to product listings in AI Mode in Google Search and on Gemini.

The hub's pitch to merchants is blunt: "Start selling across AI surfaces by implementing Universal Commerce Protocol." Google describes the protocol as an open standard built for the next phase of commerce — one where AI sessions convert directly into transactions rather than sending users through a traditional purchase funnel.

What is the Universal Commerce Protocol?

According to Google's new help document, UCP is an open standard for agentic commerce that lets agents and systems interoperate across the commerce ecosystem. By integrating with UCP, a merchant can implement a checkout button on eligible product listings shown in AI Mode in Search and in Gemini.

Google's own framing in the hub reads: "The Universal Commerce Protocol (UP) is an open standard designed for the future of commerce, empowering you to turn customer AI interactions into instant sales. Adopt UP to enable agentic actions on AI Mode, Gemini, and Search, starting with checkout directly on Google."

In practice, that means an AI-surfaced product result can carry merchant-branded checkout rather than functioning as a referral link to a store. That is the structural change merchants are being asked to prepare for.

Who gets access, and when?

The rollout is staged:

• United States: the Merchant Center integration hub is rolling out gradually right now.
• Australia and Canada: Google says merchants there get the hub next year.

Google has not published a completion date for the US phase, and there is no confirmed timeline beyond the two named follow-on markets. The gradual rollout means some US Merchant Center accounts will see the hub before others do.

What does the hub actually do?

Onboarding is the core function. The hub lets a merchant join the UCP program directly from within Merchant Center, rather than working through a separate enrollment path. Google says the integration also enables:

• Cart transfer to a merchant site — carrying an AI-initiated cart over to the merchant's own checkout environment.
• Enhanced checkout flow testing — validating that the agentic checkout path works correctly before it serves to users.

Those two capabilities matter for merchants weighing how much of the purchase experience they cede to Google-hosted checkout versus retaining on their own domains. Cart transfer in particular suggests Google is building for a hybrid model, not only closed on-platform checkout.

Who spotted it, and what is confirmed versus early signal?

Hana Kobzova surfaced the change on PPC News, sharing the new Google help document that describes the UCP integration hub. A screenshot of the hub appearing inside Merchant Center accompanied the report.

Here the record is straightforward to separate:

• Confirmed by Google: the hub exists, it is rolling out gradually in the US, Australia and Canada follow next year, and the stated capabilities are UCP onboarding, cart transfer, and enhanced checkout flow testing. All of this comes from Google's own help documentation.
• Not yet established: adoption rates, traffic or conversion impact on merchants, and how prominently checkout buttons will appear in AI Mode results. No performance data exists yet because the program is in its rollout phase.

Why this matters for merchants and search practitioners

Merchant Center has been accumulating UCP-related features in recent weeks, and this hub represents the most direct self-serve entry point so far. For e-commerce teams, the significance is architectural: Google is formalizing a protocol under which AI agents can complete purchases, starting with checkout hosted directly on Google.

That shifts the question for retailers from "how do I rank in AI answers" to "what happens to my customer relationship, data, and margin when checkout happens on Google rather than my site." Merchants with heavy reliance on direct site transactions have the most to evaluate. Those already invested in Merchant Center feed quality and Google-hosted shopping surfaces will find the technical bar to entry lower, since the hub lives inside an account they already operate.

The open-standard framing is also worth noting. By calling UCP an open protocol rather than a proprietary Google feature, Google positions it as something the broader commerce ecosystem — payment providers, platforms, agents — can build against. Whether that openness translates into genuine multi-platform adoption is unproven at this stage.

What to watch next

Monitor three things as the rollout progresses: whether the hub appears in your US Merchant Center account and what onboarding steps it requests; how Google documents the cart-transfer mechanics, since they determine how much of the transaction stays on merchant infrastructure; and any announcement fixing dates for the Australia and Canada expansion next year. Google's help document on the UCP integration hub is the authoritative reference as details are added.