Google’s UCP, decoded for merchants

If you sell online and you’ve read anything about AI agents buying products on a shopper’s behalf, you’ve probably seen the acronym UCP: Universal Commerce Protocol, from Google. It is not one thing. It’s a bundle of decisions about how AI surfaces discover merchants, when they can complete a purchase, and how payment gets authorized. Most merchant confusion about UCP comes from treating it as a single on/off switch. It isn’t. Here is what it actually is, what’s live today, and what a store owner should do right now versus simply watch.

What UCP actually is

UCP is Google’s approach to letting AI surfaces (Gemini, AI Mode in Search) find merchants and, in some cases, transact with them. It was co-developed with Shopify: not a Google-only spec, but one with a major commerce platform’s fingerprints from the start.

UCP covers two separate jobs that are easy to conflate: discovery, helping an AI surface find your products and decide whether to recommend them, and checkout, letting an AI surface complete a transaction on a shopper’s behalf inside the surface itself. These two jobs have very different rollout status, and that difference is the most important thing to understand.

Discovery is open. Checkout is gated.

Google auto-surfaces eligible merchants in its AI surfaces. The word “eligible” is doing real work there. Eligibility and checkout are gated to select markets and merchants. This is not global, and not automatic for everyone selling online today.

In practice: discovery has a lower bar and wider reach. Checkout stays restricted to a smaller set of markets and merchants while Google works through the trust and operational requirements of letting agents move money. If you’re wondering why your store isn’t transacting inside Gemini yet, this is why. Checkout access is a gate, not a feature flag you flip yourself.

Much of the reporting about Google’s agentic commerce rollout describes intent, not shipped behavior. When you read that “AI agents can now buy from any store,” treat it as roadmap language until you can point to eligibility terms that apply to your market.

The gating input: your Merchant Center feed

Here is the part merchants can act on. Structured product feeds are the gating input for discovery. Google Merchant Center still runs on structured feeds, the same ones that have powered Shopping ads and free listings for years. Feed quality (complete attributes, correct categories, images meeting Google’s minimums) determines what surfaces.

UCP doesn’t replace Merchant Center, it sits on top of it. An AI surface deciding whether to recommend your product reads the same structured signal Google has always used to decide whether to show it in Shopping results. If that feed is thin (missing GTINs, vague categories, sparse attributes) an AI agent has the same problem a human shopper comparing listings has: not enough to go on.

Where AP2 fits

The other acronym folded into UCP conversations is AP2, the Agent Payments Protocol: a separate Google specification. UCP is about commerce orchestration and discovery, finding the merchant, understanding the product. AP2 is about payments: how an agent gets authorization to spend money on a shopper’s behalf, and how that’s verified.

Conflating the two leads to bad assumptions. A UCP-ready feed doesn’t mean checkout is close behind: checkout also depends on AP2’s payment-authorization layer being live for your market. Feed quality is the input to discovery, not to payments.

Where MCP fits

One more acronym worth separating out. MCP, the Model Context Protocol, is an open standard that Google consumes among other AI providers. MCP governs how an AI agent accesses tools, not commerce discovery or checkout specifically. A merchant might expose an MCP endpoint so agents can query live inventory or place orders. It’s a related but distinct layer: UCP is Google’s commerce-specific framework, MCP is general-purpose, and commerce is just one use case for it.

What to do now versus what to watch

Here is the honest, practical split for a store owner.

Do now

• Get your Merchant Center feed in order. The one lever you control today, and the same one that’s always mattered for Shopping ads and free listings: complete attributes, correct categories, GTINs where applicable, images meeting Google’s minimums.
• Fix data-quality warnings, don’t just clear them. A disapproved item isn’t only an ads problem anymore. If discovery eligibility reads the same structured data, a thin listing is invisible twice over.
• Treat descriptions and attributes as agent-facing, not just human-facing. An AI surface deciding whether to recommend your product parses the same fields a shopper would skim.

Watch, don’t chase

• Checkout eligibility for your specific market and account. This expands on Google’s timeline, not something a merchant integration can unlock early.
• AP2 rollout. Its availability in your market determines when checkout-in-agent becomes possible, independent of how good your feed is.
• Claims that agentic checkout is “live everywhere.” Verify against Google’s actual eligibility terms for your market before changing strategy off a headline.

The through-line: everything you can do to prepare for UCP today is good Merchant Center hygiene. There’s no separate “UCP integration” checklist. Clean feeds and real product data are the same homework it’s always been. UCP just raises the stakes, since the reader on the other end might now be an agent deciding whether to recommend you at all.

The bottom line

UCP is real, it has serious backing from Google and Shopify, and it’s worth understanding now. But it isn’t a switch you flip, and it isn’t one thing. Discovery is opening faster than checkout, and checkout depends on both market eligibility and AP2’s payment layer, neither of which a merchant integration can unlock early. The lever in your hands today is the one you’ve always had: a clean, accurate Merchant Center feed. Get that right and you’re positioned for whatever UCP looks like once it reaches your market.