Universal Commerce Protocol (UCP)

The Universal Commerce Protocol is an open standard developed by Google and Shopify that lets AI agents handle the full commerce journey, from discovery through checkout to post-purchase, on any compatible platform. It is one of the core protocols behind agentic commerce.

Google announced UCP at the National Retail Federation conference on January 11, 2026. It is the broadest agentic commerce protocol so far, covering the whole lifecycle rather than checkout alone: discovery, browsing, cart, payment, order tracking, returns and customer service.

The protocol defines interactions between four actors: platforms (AI agents and applications), merchants, credential providers (identity) and payment service providers. One design principle matters most to retailers: the merchant stays merchant of record. You keep the customer relationship, the data and the post-purchase experience (Google Developers, January 2026).

UCP was co-developed with Shopify and is endorsed by over 20 major partners including Stripe, Visa, Mastercard, Adyen, American Express, Best Buy, Macy's, Home Depot, Target, Walmart, Wayfair, Etsy, and Zalando (Google Blog, Jan 2026).

UCP matters because it standardizes the whole shopping journey rather than one piece of it. Where ACP handles checkout and MCP handles data connectivity, UCP is designed to be the end-to-end framework.

Google's Shopping Graph indexes more than 50 billion product listings, with 2 billion updated every hour (Google, January 2026). UCP is the standard interface agents use to work with that index and complete transactions for shoppers.

It is built to interoperate. UCP works with the Agent Payments Protocol (AP2) for payment, Agent-to-Agent (A2A) for coordination between agents, and MCP for structured data access. Merchants can integrate through REST APIs, A2A or MCP, whichever fits their stack (Google Developers, January 2026).

Early participants in Google AI Mode agentic checkout include Wayfair, Chewy, Etsy and Quince (Google, February 2026). For most other merchants the practical path is through their commerce platform, with Shopify leading.

UCP is modular and extensible. Merchants implement capabilities based on what their systems support:

Discovery. Merchants publish a UCP profile at /.well-known/ucp. It advertises services, endpoints, versions and capabilities. It is not the catalog. Google uses Merchant Center data for product discovery, so the feed still does that job.

Browsing and selection. Agents query the catalog, filter by the shopper's preferences and present options. UCP carries rich attributes: images, variants, availability, price tiers, shipping options.

Cart and checkout. The agent manages the cart and starts checkout. Payment runs through AP2-compatible providers and the shopper's credentials are never exposed to the agent.

Post-purchase. Order tracking, returns and customer service routing. This is what separates UCP from checkout-only protocols.

Shopify Engineering described the co-development process: "We co-developed UCP with Google to create an open standard for AI agents to connect and transact with any merchant" (Shopify Engineering, Jan 2026).

The three are complementary. A retailer might use MCP to make catalog data reachable, ACP for ChatGPT checkout and UCP for the Google journey. Whichever protocols your platform supports, they all read the same product information, and that is the part a retailer controls directly. Paz handles that work: a Paz expert keeps the catalog and Merchant Center feed complete and accurate so products are eligible and well described wherever the protocol takes them. See how the product feeds service works. For an engineering walkthrough, see Paz.ai's UCP technical guide for retailers.