Google has begun a staged US rollout of a Universal Commerce Protocol (UCP) hub inside Merchant Center, and merchants will choose which capabilities to switch on. Search Engine Land reported the change on October 6. The decision matters because it determines where a purchase that starts on Google actually ends.
Three capabilities are on the menu. A merchant can send shoppers to its own website with their cart intact, offer native checkout on Google, or set up identity linking between a shopper’s Google account and the merchant’s own customer system. Each capability can be selected separately, so the hub replaces a one-size-fits-all checkout with a configurable set of options.
The geography is also moving. The US comes first, and Search Engine Land reports that Australia and Canada are now expected next year, a shift from the earlier timeline for those markets. Google’s documentation changed alongside the launch: the relevant help page was renamed to reflect the hub, and an older FAQ about UCP-powered checkout for select US merchants was removed. Search Engine Land did not report eligibility criteria, specific rollout dates, or fees, so merchants should check their own Merchant Center accounts before assuming access.
The more useful question is what each choice costs and returns. These are considerations for merchants to weigh, not claims about how Google handles any of them.
Start with attribution. When a sale closes on a merchant’s own site, the merchant’s analytics and ad tags see the whole path from click to order. When a sale closes inside Google’s native checkout, the merchant should confirm which conversion data it receives and how that data reconciles with its existing reporting.
Customer data is the second consideration. A merchant that owns the checkout page captures the email address, consent choices, and order history directly. With native checkout, the merchant should verify what customer information is passed back and on what terms. Identity linking exists partly to narrow that gap, since it connects the shopper’s Google identity to the merchant’s own account system.
Landing-page traffic is the third. Cart transfer sends shoppers to a merchant’s site, which preserves a chance to show related products, loyalty prompts, and content that a shorter Google-hosted flow would skip. Native checkout may convert more shoppers who would abandon a redirect, though Google has not published evidence on that, and the source reports no conversion figures for either path.
None of these trade-offs is settled in advance. A merchant with strong repeat-purchase economics and a mature email program has more to lose from giving up the checkout page. A merchant whose site converts poorly on mobile may reasonably weigh the opposite.
The hub also fits a pattern. Google has said it plans to adopt a draft UCP lodging spec so AI Mode, its conversational search experience, can handle hotel bookings, as we covered here. Shopify has also built WebMCP checkout tools through UCP so browser-based AI agents can finish purchases, as covered here. Both items appeared on September 29. Taken together with the Merchant Center hub, UCP now touches hotels, platform checkout, and merchant configuration in a matter of days.
The announcement as reported does not include any independent measurement of how the options perform. Everything about conversion, margin, and data access remains for merchants to test.
US merchants who see the hub in Merchant Center over the coming weeks should decide per capability, not all at once, and set up a clean comparison of orders, customer records, and returning-shopper rates before expanding any option beyond a pilot.
Based on reporting by Anu Adegbola for Search Engine Land, published October 6, 2026.
