If you sell online and want shoppers to buy your products inside Google’s AI experiences, the Universal Commerce Protocol is the route Google documents today. Before you start the technical work, check three things: that your product data agrees everywhere it appears, that your policies are clear enough for a shopper who never visits your site, and that your order handling can cope with a sale that starts somewhere else.
UCP itself is a technical integration. The harder questions are often about the business: which products should be sold this way, what the shopper sees before paying, and who handles the order afterwards.
What UCP is, and where it stands
Google describes the Universal Commerce Protocol as an open standard for agentic commerce: a common way for AI agents, businesses, and payment providers to work together. On Google, it powers a checkout on eligible product listings in AI Mode in Search and in Gemini. The merchant remains the seller of record. See Google’s UCP overview for merchants. Google’s developer page adds that merchants keep their customer data and relationships (Google’s UCP guide for developers).
Availability is still limited, so plan around the current rules rather than the announcement headlines:
- Early access. Google says the UCP-powered checkout is available to select merchants for now and that the protocol will be available in phases.
- Implementation comes first. You complete the technical integration described in Google’s developer guide, then submit an interest form. Selected merchants get access to onboarding in Merchant Center, including a sandbox for validating the integration, and Merchant Center flags feed attributes, returns or account settings that need updating. Read Google’s onboarding steps.
- Region. The Merchant Center onboarding is rolling out gradually in the United States, with Australia and Canada to follow next year, according to Google’s help page.
- Eligible listings only. Google says the “Buy” button appears only on product listings that use the
native_commerceproduct attribute with checkout eligibility. - Payment. When we checked on October 18, 2026, Google said the feature uses standard card numbers that shoppers have stored in Google Wallet, and that more payment forms may follow.
If your shop runs on a third-party platform, Google’s advice is to ask that provider about its UCP plans. Do not assume your platform has already enabled it; confirm it with them and then test it.
Readiness check
The table below is the work to do before and alongside the technical integration. The example notes come from a fictional online shop selling outdoor gear. Every product, policy, and finding in it is invented.
| Area | What to check | Why it matters here | Fictional finding |
|---|---|---|---|
| Product data | Price, availability, variants, and shipping agree across your site, your Merchant Center feed, and checkout | The shopper may never see your product page before paying | Two jacket colors show “in stock” in the feed but are back-ordered on the site |
| Product selection | Which products should be bought without a site visit | Some purchases need sizing advice, configuration, or a conversation | Made-to-measure tents excluded; standard sizes included |
| Policies | Returns, delivery times, and fees are stated plainly and consistently | The shopper relies on what the listing and checkout show | Returns window says 30 days on the site, 14 days in the feed |
| Order handling | Orders started on Google flow into your order, stock, and support systems | You remain the seller and own the post-purchase experience | Support team has no way to tell where an order started |
| Customer accounts | Whether you will link shopper accounts, and what that changes for loyalty or saved details | Identity linking is among the capabilities Google lets merchants select in the UCP integration hub; Google’s UCP updates announcement ties it to loyalty and member benefits | Loyalty points not yet available for externally started orders |
| Payments | Your payment setup matches what Google currently supports | Supported forms are limited during early access | Payment provider confirmed; testing booked |
| Testing | Sandbox runs for a normal order, a stock change mid-checkout, a cancellation, and a return | Errors here are seen by a customer, not a reviewer | Cancellation webhook not yet handled |
| Ownership | One named person for the feed, one for policies, one for orders | Inconsistencies come back when nobody owns the fix | Owners assigned; monthly feed check scheduled |
The first three rows matter even if you never implement UCP. A shopper comparing products in an AI answer sees what the system was given. A price or returns policy that differs between your feed and your site is a problem in any channel.
Decide which products belong in agent checkout
Not every product should be bought inside an AI answer without a visit to your site. A replacement filter or a standard-size jacket usually needs little explanation. A product that needs measurements, compatibility checks, or professional advice may lead to returns or support tickets if bought without them.
Write the decision down for each product category, with a reason. It keeps the feed attribute and the business decision aligned, and it gives the next person a basis for changing it.
Keep the source of truth current
An agent completing a purchase relies on structured data you supplied, not on a person reading your product page carefully. That raises the stakes on accuracy. Our guide to building a product page that answers buyers’ proof questions shows how to record an owner, a source, and a checked date for each claim that affects a purchase. The same discipline applies to the feed.
When something changes, such as a price, a delivery time, or a returns rule, update the site, the feed, and the checkout terms together. Then check that they match.
Watch what AI answers say about your products
Checkout is the last step. Before it, the shopper asks questions: which jacket suits wet weather, which tent fits two people, which brand has easier returns. Whether your products appear in those answers is a separate question from whether they can be bought there.
Seenvero collects answers to the buying questions you choose from engines including Google AI Mode and Gemini. It stores each answer with its citations and shows whether your brand is recommended, listed, mentioned in passing, or cautioned against. That shows which of your pages are cited on buying questions and where competitors are named instead. It does not test UCP eligibility or checkout. Treat it as the view of the conversation before the purchase.
Explore Seenvero’s sample report to see how answers, citations, and brand roles are presented, using a fictional brand.
Common questions
Is UCP the same as a Merchant Center product feed?
No. The feed describes your products. UCP is the protocol that lets a purchase be completed on Google’s AI surfaces. Google requires the product attribute for checkout eligibility in addition to the integration itself.
Can we use UCP outside the United States?
Not yet through Merchant Center onboarding, according to Google’s current help page. Google says Australia and Canada will follow next year. Check the page again before you plan a launch.
Do we lose the customer if they buy inside Gemini?
Google says the merchant remains the seller of record, and its developer page says merchants keep their customer data and relationships. Make sure your systems record where the order started so your team can support it.