TL;DR
- Google published a Merchant Center Help page on the UCP integration hub, reported by Search Engine Roundtable on 7 October 2026, covering checkout buttons on eligible listings in AI Mode and Gemini.
- The hub is rolling out gradually in the United States, with Australia and Canada to follow next year; Google gave no Thailand timing.
- Merchants must finish the UCP developer guide implementation first, then submit an interest form; only selected merchants get the Merchant Center onboarding flow.
- The sandbox validates the UCP profile, cart transfer and native checkout APIs, and Merchant Center flags needed changes to feed attributes, returns or account configuration.
Google has added a UCP integration hub to Merchant Center, an onboarding path inside the product for merchants who want a checkout button on eligible product listings in AI Mode in Google Search and in Gemini. According to a Google Merchant Center Help page that Search Engine Roundtable reported on 7 October 2026, the hub is rolling out gradually in the United States, with Australia and Canada to follow next year. Merchants cannot simply switch it on: they must finish the technical implementation in the UCP developer guide first, then submit an interest form and wait to be selected.
What Google published about the Merchant Center UCP integration hub
The page is titled "How to onboard to the UCP integration hub in Merchant Center" and is published on Google Merchant Center Help. It describes the Universal Commerce Protocol (UCP) as a new open standard for agentic commerce, meaning a standard that lets agents and systems work together across the commerce ecosystem. In practical terms, a merchant that integrates with UCP can implement a checkout button on eligible product listings in AI Mode and in Gemini.
Search Engine Roundtable's Barry Schwartz reported the page on 7 October 2026 and credited Hana Kobzova with spotting it on PPC News. He quoted the text shown inside the hub itself, which tells merchants to "Start selling across AI surfaces by implementing Universal Commerce Protocol." Google's help page says the Merchant Center integration lets a merchant onboard to the program from its own account and enable capabilities such as cart transfer to a merchant site and enhanced checkout flow testing.
How onboarding works, step by step
The help page lays out a sequence, and the order matters because Merchant Center is the last step, not the first.
- Complete the technical implementation described in the UCP developer guide. Google states this is necessary before onboarding begins.
- Fill out the interest form that Google links from the help page.
- Wait for notification. Google says that as soon as a merchant is selected to participate, it will notify them, and only then do they get access to the onboarding experience in Merchant Center.
- Use the onboarding experience, which includes a sandbox environment. In the sandbox a merchant can validate the integration, including the UCP profile, cart transfer to a merchant site and the native checkout APIs.
- Act on the alerts. Besides those validations, Merchant Center will alert the merchant if any action is needed to update feed attributes, returns or account configuration.
Google adds a note that a merchant may see the UCP integration hub appear in its Merchant Center account as the onboarding experience rolls out gradually. Seeing the hub is therefore not the same as being selected; the selection step comes from the interest form.
Which UCP capabilities a merchant can select
With the hub, merchants can select UCP capabilities. Google's page names three: cart transfer to a merchant site, native checkout on Google, and identity linking. The page does not define each capability in detail, so the descriptions below stay close to the names and to what the page says about the sandbox.
- Cart transfer to a merchant site: listed as a selectable capability. The sandbox covers testing this flow.
- Native checkout on Google: listed as a selectable capability. The sandbox covers the native checkout APIs.
- Identity linking: listed as a selectable capability. The help page gives no further detail on how it works, so any assumption about account matching would go beyond the source.
What is new compared with RA's earlier UCP coverage
Relevant Audience reported on UCP updates in September, including cart transfer, UCP analytics and Business Agent in mid-September, and a UCP lodging draft at the end of the month. Those stories described individual features. This one is different in kind: it is the formal front door. Google now has a documented path inside Merchant Center that runs from interest form to selection to sandbox testing, and it ties that path to the data a merchant already maintains in the product, namely feed attributes, returns and account configuration.
The help page also reframes Merchant Center's role. It says Merchant Center will continue to be the central hub for preparing product data to show ads and listings on Google surfaces, and that the best preparation is to make sure all data in Merchant Center, from product feeds to brand assets, is as robust and up to date as possible. For UCP, the product feed is not a side issue. It is one of the items Google says Merchant Center will flag.
Availability and what Google did not say
The table below collects the facts the help page and the Search Engine Roundtable report state directly.
| Item | What the sources say |
|---|---|
| Where it is rolling out | Gradually in the United States now |
| Later markets | Australia and Canada, next year |
| Prerequisite | Technical implementation per the UCP developer guide, then an interest form |
| Selectable capabilities | Cart transfer to merchant site, native checkout on Google, identity linking |
| Sandbox validates | UCP profile, cart transfer to a merchant site, native checkout APIs |
| Merchant Center alerts on | Feed attributes, returns, account configuration |
Several things are missing from the page. Google gave no date for broader availability beyond "next year" for Australia and Canada. It gave no timing for Thailand or any other Asian market. It did not say how many merchants will be selected, what criteria it uses, or how long selection takes. It did not publish the specific feed attribute or returns changes that Merchant Center might request, and it did not say whether shoppers will see a checkout button on every eligible listing or only some. Those gaps are worth stating plainly, because a plan built on guesses about them would be a plan built on nothing.
What third-party platform merchants are told
Many online stores run on a hosted platform rather than custom code. Google's FAQ on the page addresses this directly: a merchant that works with a third-party service provider or platform should connect with that provider to learn about its plans for UCP integration. The page does not name any platforms and does not promise that any platform will support the developer-guide implementation. For a store on a hosted platform, the first practical action is therefore a support ticket or account-manager question to the platform, not a Merchant Center setting.
A practical checklist before applying
The following steps are analysis based on what the help page says Merchant Center will check; Google did not publish a checklist of its own.
- Read the UCP developer guide that the help page links to, and assign an owner. Google says implementation must be complete before onboarding, so the developer work is the long pole, not the Merchant Center form.
- Audit feed attributes. The page says Merchant Center will alert merchants to feed attribute changes, so find products with missing or thin attributes now and fix them in the feed source.
- Review the returns configuration in the account. Returns appears by name in the list of alerts, so confirm that policy information is complete and matches the policy shown on the website.
- Check account configuration and brand assets. Google's FAQ says the best preparation is robust, up to date data in Merchant Center, from product feeds to brand assets.
- If a platform runs the store, send the platform a written question about its UCP plans and keep the reply, since the page tells merchants to ask the provider directly.
- Decide which of the three capabilities matter commercially. Cart transfer keeps the sale on the merchant site; native checkout on Google moves the purchase onto Google. Those choices affect customer data, payment handling and support workflows, so the business side should weigh in before the developer side builds.
None of these steps needs an invitation from Google.
What this means for Thai marketers and ecommerce teams
The source does not say anything about Thailand. The hub is rolling out in the United States first, and the only other markets Google named are Australia and Canada. No source names Thailand as a rollout market, so a store that sells only to Thai shoppers has no announced access today. Merchants can treat the page as a preview of what Google will check before it lets a product take part in checkout inside AI Mode and Gemini.
Because the page names feed attributes, returns and account configuration as the things Merchant Center will flag, a sensible low-cost step is to review those now. This is analysis rather than something the source says, but it follows from the alerts Google describes: complete product attributes, a clear returns policy configured in the account, and brand assets that are accurate are all things a team can inspect without waiting for any invitation. Teams working on ecommerce marketing can fold this into an existing feed audit rather than starting a separate project.
There is also a visibility angle. When a checkout button sits on a listing inside an AI answer, the shopper may never visit the merchant's site before buying, so how a product is described in the feed and on the page matters in a new place. Brands that want to be recommended in those answers should keep their product data consistent with their site content; our generative engine optimization service covers that kind of consistency work for AI search surfaces.
FAQ
Is the Merchant Center UCP integration hub available in Thailand?
No source says it is. Google's help page names the United States as the current rollout market and Australia and Canada as later markets next year, and it gives no Thailand timing. Check the Merchant Center account for the hub if you sell into the US.
Can any merchant turn on UCP checkout from Merchant Center?
No. Google requires the technical implementation from the UCP developer guide first, then an interest form, and only selected merchants are notified and given access to the onboarding experience. The hub may appear in an account during the gradual rollout, but selection is a separate step.
What does the sandbox test?
It lets a merchant validate its UCP profile, cart transfer to a merchant site and the native checkout APIs. Google adds that Merchant Center will also alert the merchant to needed updates to feed attributes, returns or account configuration.
What if my store runs on a third-party platform?
Google tells those merchants to contact the platform directly to learn about its UCP integration plans. The page does not say which platforms will support UCP or when.
Which UCP capabilities can merchants choose?
The hub lists cart transfer to a merchant site, native checkout on Google and identity linking. Google's page does not describe identity linking in further detail.
Next step
If your team is unsure whether your product feed, returns setup and platform are ready for agentic checkout, Relevant Audience can review them with you as part of an AI SEO and ecommerce audit. We will update this post when Google publishes timing for markets beyond the United States, Australia and Canada.
