What Is Google UCP? A Merchant's Guide to Universal Commerce Protocol

Google UCP, short for Universal Commerce Protocol, is an open standard that enables AI agents operating in Google Search AI Mode and Gemini to complete purchases directly on behalf of users, without redirecting to a merchant's website for checkout. Merchants remain the Merchant of Record and retain all customer data. UCP uses existing Merchant Center product feeds as the discovery layer and offers two integration paths: native checkout and embedded checkout.

Introduction to Agentic Commerce

Agentic commerce refers to shopping experiences where AI systems assist, influence, or autonomously participate in the purchasing journey on behalf of a user. An AI agent operating through UCP does not browse product pages in the traditional sense. It queries structured product data, validates pricing and availability, builds a cart session, and triggers checkout through an API. The quality of product feed data and the completeness of checkout infrastructure determine whether the agent can complete a purchase at all.

For eCommerce merchants, agentic commerce raises a practical question: when a user asks an AI agent "buy me the best standing desk under $800 with same-day delivery in Melbourne," is your store visible to the agent? And if it is visible, can the agent complete the purchase? UCP is Google's answer to the second question. The first is answered by Merchant Center feed quality and structured data.

How a UCP Transaction Works

A UCP-enabled transaction flows through five stages. The AI agent interprets a user's shopping intent and queries Merchant Center feeds to identify relevant products. The UCP protocol calls the merchant's checkout API to build a cart session. Control then passes to a Google-hosted checkout UI where the user enters fulfilment and payment details directly. The agent is excluded from this step by design to preserve security and determinism. When payment is complete, the merchant receives the order on their own systems as Merchant of Record.

Native Checkout

Native checkout is the default and recommended UCP integration path. It requires the merchant to build a RESTful API that Google can call to create and manage checkout sessions. The native checkout flow: the user and optionally an AI agent add items to a checkout session via the API. Once the user decides to checkout, the agent passes control to a Google-hosted UI with the checkout session data. The user fills in address and payment details in Google's interface. The agent is not involved in this payment step. Google shows a confirmation page and the order is passed to the merchant. Native checkout is the path that will unlock full agentic potential as UCP expands.

Embedded Checkout

Embedded checkout is an optional integration path for specific approved merchants whose checkout flows are too complex for the native API path. The merchant's existing web-based checkout is embedded inside Google surfaces using an iframe. Unlike a simple redirect, this enables bi-directional communication between Google's interface and the merchant's checkout. Google can delegate tasks such as selecting a saved address or applying a stored payment credential. The merchant remains the Merchant of Record and handles order creation on their own systems. Embedded checkout requires separate Google approval and is not the default path.

Google Universal Cart

The Universal Cart allows shoppers to add products from multiple UCP-enabled merchants into a single cart on Google surfaces and complete one checkout session across all items. Before Universal Cart, a shopper wanting items from several retailers had to visit each website separately. Universal Cart aggregates products from multiple UCP-participating merchants into a single Google-managed cart. The shopper pays once through Google Pay and each merchant receives their portion as a separate Merchant of Record transaction. Merchants not participating in UCP are invisible to Universal Cart behaviour regardless of traditional search rankings.

What Merchants Need to Do

Implementation follows five steps: (1) Prepare Merchant Center with complete product feeds, shipping, and returns configured. (2) Set up Google Pay integration. (3) Publish a UCP profile at the well-known endpoint declaring what commerce capabilities the store supports. (4) Build and test the checkout integration, native or embedded. (5) Apply for the waitlist and receive Google's approval before going live on AI Mode and Gemini.

SEO and AI Search Implications

For UCP-based discovery, Merchant Center feeds are what AI agents query. Feed completeness, title clarity, attribute specificity, and availability accuracy matter more than page keyword density for agentic commerce. Merchants should treat Merchant Center feeds as their primary AI search ranking signal, add conversational attributes where they answer real pre-purchase questions, structure product schema on PDPs to support entity relationships, and configure shipping and returns with precision as these are used to validate purchase conditions before agent recommendations.