Google Opens Its UCP Checkout Hub in Merchant Center

Affiliate disclosure: This post contains affiliate links. If you buy through them, I may earn a commission at no extra cost to you. Full disclosure

Google began rolling out a Universal Commerce Protocol hub in Merchant Center on October 6, letting selected US merchants test checkout buttons for AI Mode and Gemini.

If you run a high-ticket store, as most Ecommerce Paradise readers do, this is Google’s front door for AI-driven buying. Merchants pick from three capabilities, according to Search Engine Land: cart transfer to their own site, native checkout on Google, and identity linking. That choice decides who owns the checkout page, the customer data and the phone call on a $3,000 order.

Below: what Google published, how the protocol got here since January, what I’d do with each option, and five moves for this week. I covered the order-submission side of agent buying in Shopify lets AI agents submit orders on your store, and this is the Google half of the same story.

Before you sell through Google’s AI surfaces, put the store inside a clean LLC, and form it with Northwest Registered Agent, the best LLC formation service for ecommerce owners. Cheap formation sites upsell you every year, while Northwest keeps the renewal price the same as year one with no upsell ladder. Form your LLC with Northwest →

Google Merchant Center Opens a UCP Hub to US Merchants

Anu Adegbola, Paid Media News Editor at Search Engine Land, reported on October 6 that Google is gradually rolling out the integration hub to eligible US merchants. Google also renamed its Merchant Center help page to match and removed an earlier FAQ about UCP-powered checkout for select US merchants, per the same report.

Google’s help page calls UCP “a new open standard for agentic commerce.” According to the Merchant Center help page, integrating lets a merchant show a checkout button on eligible product listings in AI Mode in Google Search and on Gemini.

The hub offers three capabilities. Cart transfer moves a shopper’s cart to the merchant’s site. Native checkout lets shoppers pay on Google’s surfaces. Identity linking connects the shopper’s identity to the merchant. Merchants choose which to support rather than adopting one checkout model.

Access is not open enrollment. The help page lists three steps: complete the technical implementation in Google’s UCP developer guide, submit an interest form, and wait for Google to select you. The page does not state selection criteria or a timeline. Merchants on a third-party platform are told to contact that provider about its UCP plans.

Google’s developer documentation, last updated October 2 according to the page, describes the hub as tools for an early access program. It supports testing in sandbox and production, including creating a checkout, updating shipping and completing a transaction. Only listings carrying the native_commerce(checkout_eligibility) product attribute show the Buy now button, and the program applies only to products sold within the United States.

Luís Rijo of PPC Land filled in more technical detail on October 7. Per his report, merchants must publish a UCP profile at /.well-known/ucp that includes the dev.ucp.shopping.cart capability, and the Cart API requires UCP version 2026-04-08 or later. The initial cart release supports only creating and transferring carts, with no updates, deletions or sync. Google’s own Cart API guide, quoted by PPC Land, says the capability is “designed for basket building before the user has expressed explicit intent to check out.”

Geography is narrow. Australia and Canada are expected “early next year,” per Google’s documentation. PPC Land notes that an earlier version of the help page described a US, Canada and Australia rollout “in the coming months,” so the dates slid. No UK date has been given.

Barry Schwartz of Search Engine Roundtable published the hub’s own banner text on October 7: “Start selling across AI surfaces by implementing Universal Commerce Protocol.”

How UCP Got From a January Launch to a Merchant Center Hub

PPC Land dates the protocol’s launch to January 11, 2026, with Shopify, Etsy, Wayfair, Target and Walmart as co-developers and more than 20 endorsers including Adyen, Mastercard, Stripe and Visa. On March 2, Google published a Merchant Center help page for UCP checkout covering the native_commerce attribute, Google Wallet payments and a payment service provider requirement, applying to selected US merchants.

Ashish Gupta, VP and GM of Merchant Shopping at Google, wrote on March 19 that UCP adds optional Cart, Catalog and Identity Linking capabilities and that a simplified onboarding process in Merchant Center would roll out “over the coming months.” Per Google’s post, Commerce Inc, Salesforce and Stripe planned to implement UCP on their platforms.

On May 5, PPC Land reports, UCP checkout showed up in main Search results with a Wayfair Buy button. At Google Marketing Live on May 20, Google added multi-item carts and cart transfer, citing more than 60 billion Shopping Graph listings and more than 1 billion monthly AI Mode users, figures PPC Land attributes to Google.

On September 16, Matt G. Southern of Search Engine Journal reported that cart transfer was reaching the hub, and that final checkout stays on the merchant’s site. The same report says Google announced a UCP analytics dashboard that tracks the funnel from Buy-button clicks to completed purchases, plus average order value and cancellations, for merchants with UCP enabled and the Performance role. The data is not yet in the Merchant API, and Search Engine Journal says it is unclear whether the dashboard is live for everyone.

There is a counterpoint. According to Search Engine Journal, retailers raised concerns in January that transactions completed on Google mean lost customer contact and fewer brand connections. Cart transfer is meant to address that concern. Native checkout is where the concern still applies, and Google’s pages do not say how much order and customer data a merchant receives in that mode.

The commentary is also not uniform. PPC Land quotes Zhao Hanbo, co-founder of Nile, calling cart transfer “the lighter of the integrations.” He also claimed checkout is on by default for Shopify merchants, but PPC Land points out Google’s help page never mentions Shopify, so treat that as his claim alone. PPC Land lists open questions: how many merchants get selected, the criteria, and whether validation results affect AI Mode eligibility. I have covered the cart side before. My July piece on Google’s Universal Cart entering your funnel shows the direction has not changed since May.

What the UCP Hub Means for High-Ticket Store Owners

My read is that Merchant Center is turning into the control panel for AI buying, and the default I’d pick for a high-ticket store is cart transfer. That is my opinion, not Google’s recommendation.

High-ticket orders carry steps that a one-tap checkout skips. You verify the order, check supplier stock, quote freight on bulky goods and, often, call the buyer. My guide to high-ticket sales follow-up exists because those calls close sales. With cart transfer the shopper lands on your checkout with the cart filled, so every one of those steps still happens on your terms.

Run hypothetical math. Take a $2,400 sofa at a 22% gross margin. That is $528 of margin per order. One lost dispute costs the $2,400 sale plus fees, so you need roughly four to five clean orders to cover a single loss. The numbers are invented for illustration, but the ratio holds for any store with margins in the teens and twenties. My breakdown of chargeback prevention for high-ticket stores covers how those disputes start.

Native checkout is the option I’d approach with questions. Google’s pages do not say whether you can hold a payment for manual review, run your own fraud screen before capture, or confirm supplier stock before the charge. Until Google answers, I’d treat those as open. If you do enable it, a fraud screen such as ClearSale matters more, not less, on four-figure orders.

Identity linking carries a different risk. Google’s March post says it lets shoppers get the member benefits they would get logged in on your site, such as pricing or free shipping. If your supplier agreement has minimum advertised pricing, member pricing can collide with it. Read the MAP policy before you switch anything on.

Here is the threshold I’d use, labeled as my rule of thumb and not reported data. Under about $500 per order, native checkout’s convenience can outweigh the lost control. Between $500 and $1,500, test it on a handful of SKUs. Above $1,500, start with cart transfer and keep your own checkout in the loop.

Timing matters too. The hub is selection-based, and PPC Land’s open questions include the lead time between the interest form and access. I would not plan holiday revenue on being selected. I’d plan on being ready, because the technical work is the same whenever the invite arrives.

That work is where most store owners stall. The developer guide assumes someone who can publish a profile at a well-known path and test endpoints in a sandbox, and Google tells platform-hosted merchants to ask their provider. If you are on Shopify, ask Shopify’s support what its UCP status is for your store, because Google’s help page does not name it. My earlier post on Meta’s Muse checking out with Shop Pay shows how fast platforms are adding agent paths.

The bigger pattern is who gets picked. A study I covered found AI shopping picks big retailers nine times in ten, and a small store gains little from a checkout button nobody sees. Feed quality and product data decide visibility first. I’d put feed work ahead of checkout work. If your catalog comes through Spocket, check that its stock and pricing data match what your feed advertises.

If you would rather not run feeds, supplier onboarding and store operations yourself while Google’s rules keep moving, that is what my team handles in the turnkey done-for-you service.

Feed quality and store operations decide whether any Google checkout button helps you, and that is the work my team does for stores that are already live. See the scaling service →

Your UCP Hub Checklist: Five Moves Before Holiday Traffic

Five actions, in the order I’d do them. None require being selected by Google first.

  1. Open Merchant Center and look for Settings, then UCP integration. Google says the hub is rolling out gradually, so it may not show yet, and the help page says the contact form is only for merchants who already have access. Screenshot what you see so you can date it later.
  2. Ask your platform in writing whether it supports UCP and on what timeline. If you run Shopify, the answer determines whether you need a developer at all. If you have a developer, give them Google’s developer guide and the interest form on the help page.
  3. Audit your product feed before anything else. Check price, availability, brand, GTINs, shipping and return data on your top 20 products. If your feed comes from suppliers through Inventory Source, confirm the supplier data refreshes often enough to match what you promise. My walkthrough on turning Google Shopping clicks into sales has the product page side.
  4. Set a baseline before AI checkout exists on your account. Record weekly Shopping impressions, clicks and orders for your top products, and use SEMRush to track where those products rank. If a Buy button later changes your numbers, you will know by how much. Keep your Performance Max setup honest too, as I laid out in feed-only PMax exclusions.
  5. Write your checkout policy now. Decide your price floor for native checkout, who reviews orders before fulfillment, and which supplier MAP rules limit member pricing. If you want a second set of eyes on that policy, book a discovery call and bring the numbers.

Two housekeeping items ride along. Test whether a transferred cart shows up as a started checkout in your email platform, such as Klaviyo, because abandoned-cart flows depend on that event. And update your privacy policy if identity linking will ever touch shopper data, which a generator like Termly can help with.

Frequently Asked Questions

Can any merchant use the UCP hub right now?
No. Per Google’s help page, you must complete the technical implementation, submit an interest form and be selected, and the rollout is gradual in the US only.

Does the hub apply to stores outside the United States?
Not yet. Google’s documentation says it applies only to products sold within the US, with Australia and Canada expected early next year and no UK date.

What is the difference between cart transfer and native checkout?
With cart transfer the shopper’s cart moves to your site and checkout stays there, per Search Engine Journal. With native checkout the shopper pays on Google’s surfaces.

Do I need a developer?
Almost certainly, unless your platform handles it. Google’s guide requires a UCP profile and tested endpoints, and platform-hosted merchants are told to ask their provider. My launch guide for high-ticket stores covers setting up the base store first.

Is this still worth caring about if I am just starting out?
Yes, as a feed and product-data exercise. Start with what high-ticket dropshipping is. Grab the free niches list if you are still choosing a category.

Will Buy now buttons raise my chargeback risk?
Google has not published data on it, so nobody can say. High-ticket stores already face disputes, and my guide on building a payment processor backup plan is the safety net I’d set up first.

Want 1-on-1 coaching to decide how your store handles Google’s AI checkout? Get the coaching details →

I’ll keep tracking how Google’s hub rolls out and what selected merchants report. Subscribe to the YouTube channel for daily breakdowns. More breaking news coming through the day.

Related Articles

If this was useful, these go deeper:

Free 1,000+ high-ticket niches list

Still deciding what to sell?

Grab the free list of 1,000+ niches that work for high-ticket dropshipping, sorted by category.

Free. Unsubscribe any time.