What Is UCP (Universal Commerce Protocol)? — Google's Open Standard for Agentic Commerce

What Is UCP (Universal Commerce Protocol)?

On January 11, 2026, Google CEO Sundar Pichai took the stage at the National Retail Federation (NRF) annual conference and introduced a new open standard for agentic commerce: the Universal Commerce Protocol (UCP).

The problem it addresses is straightforward. AI agents need a common language to transact with ecommerce businesses. Google Search, Gemini, Shopify agents, third-party AI assistants — each new agent requires merchants to build custom API integrations, and each new merchant requires agents to do the same in reverse. Google's engineering team calls this the "N x N integration bottleneck."

UCP collapses that bottleneck. According to Google's technical deep-dive, the protocol "collapses N x N complexity into a single integration point for all consumer surfaces." It covers the entire purchase flow: product discovery, cart building, checkout, order management, and payments — all under one standard.

What makes UCP notable is its coalition. Shopify, Etsy, Wayfair, Target, and Walmart co-developed the protocol, with over 20 additional endorsers including Adyen, American Express, Best Buy, Flipkart, Macy's, Mastercard, Stripe, The Home Depot, Visa, and Zalando. The specification is published at ucp.dev and developed as open source on GitHub.

.well-known/ucp — Bringing Web Standards to Commerce

The design philosophy behind UCP is best captured by its .well-known/ucp manifest.

robots.txt tells crawlers what they can access. sitemap.xml tells search engines how a site is structured. In the same spirit, UCP has merchants publish a JSON profile at /.well-known/ucp on their own domain. This profile declares supported services (e.g., shopping), available capabilities (checkout, catalog, etc.), and payment handler configurations.

According to the UCP specification, the manifest includes version information, a service registry with REST endpoints and OpenAPI schema references, a capabilities list, and payment handler definitions. Namespacing uses a reverse-domain convention (dev.ucp.shopping.checkout for official capabilities), clearly distinguishing protocol-native features from third-party extensions.

The key benefit: no registration or platform approval is required. Once a merchant publishes their manifest, any AI agent can discover it and initiate transactions based on shared capabilities. Shopify's engineering blog likens this to HTTP content negotiation — agents and merchants compute the intersection of their supported capabilities and communicate on common ground.

Why a decentralized approach rather than a centralized marketplace? The Web succeeded because publishing a website never required Google's permission. UCP applies the same principle to commerce. Merchants retain data control on their own servers, free from platform dependency. This "merchant-first" design is also what fundamentally differentiates UCP from ACP.

Technical Architecture — Four Layers

UCP is not a monolithic system. As Google's technical blog details, it separates into four layers — Discovery, Communication, Execution, and Payment — each evolving independently through well-defined interfaces.

Discovery Layer

The .well-known/ucp manifest is the core of this layer. Agents fetch the manifest to understand what a merchant sells and which capabilities are supported. The specification defines a "server-selects" algorithm that computes the intersection of capabilities supported by both parties.

Communication Layer

What sets UCP apart from other commerce protocols is multi-transport support. The primary transport is RESTful HTTP/1.1+ with JSON, but UCP also provides bindings for MCP (Model Context Protocol) and A2A (Agent2Agent).

REST uses OpenAPI 3.x, MCP uses OpenRPC, and A2A follows the Agent Card Specification. Additionally, Shopify developed the Embedded Protocol (EP), a JSON-RPC 2.0-based bidirectional communication layer that enables agents to embed merchant checkout UIs directly.

Execution Layer

This is where actual commerce happens. Capabilities like Checkout, Cart, Catalog, Order Management, Discount, and Identity Linking are each independently versioned. Capabilities support extension via the extends field — for instance, Discount extends Checkout.

Payment Layer

Payments separate "Payment Instruments" (what consumers use) from "Payment Handlers" (processing providers). The UCP specification defines a "Trust Triangle" model among business, credential provider, and platform. Credentials flow unidirectionally (platform to business only), and agents never touch raw card numbers.

Capability Evolution — January to March 2026

UCP launched with three capabilities: Checkout, Identity Linking, and Order Management. The March 19, 2026 update significantly expanded the protocol's scope.

Cart API — Beyond One-Product Sessions

The initial version treated each product interaction as a discrete event. According to SearchEngineJournal, the March update introduced a persistent, stateful cart session object.

Agents can add multiple items to a cart at once, modify quantities, apply discount codes, and then transition to checkout. The everyday act of "buying shampoo and conditioner together" is now standardized at the protocol level.

Catalog API — From Feeds to Live Queries

Traditional ecommerce integrations require merchants to submit product data as pre-built feeds. The Catalog API inverts this model. Agents query merchant servers directly for variants, inventory counts, and real-time pricing — a pull-based approach.

This matters in practice. Feed-based models introduce lag when prices change or items sell out. With the Catalog API, agents receive data at the exact moment of purchase consideration, structurally preventing "added to cart but out of stock" experiences.

Identity Linking — Connecting Loyalty Programs

Purchasing through an agent but losing member discounts or free shipping would drive consumers away from agent-based shopping. Identity Linking connects merchant loyalty systems to agents via OAuth 2.0, ensuring agent-driven purchases receive the same benefits as logged-in sessions.

Checkout Flow — How an Agent Completes a Purchase

Here is how a purchase flows through UCP.

The agent fetches the merchant's /.well-known/ucp manifest to identify supported capabilities and payment handlers. It then queries the Catalog API for product information and selects items matching the user's requirements.

Once products are selected, the agent creates a checkout session via POST request. The merchant returns a session ID with line item details (product name, price, tax). If a discount code applies, the agent sends a PUT request and the merchant recalculates totals.

The checkout session follows a state machine. Shopify's implementation defines three statuses: incomplete (missing information), requires_escalation (human input needed via continue_url browser handoff), and ready_for_complete (fully autonomous completion).

The requires_escalation state is a critical design choice. Address verification, 3D Secure authentication, age verification — when human judgment is required, the agent opens a browser to the merchant's checkout UI. Supporting hybrid human-agent flows as a first-class protocol feature is one of UCP's most pragmatic strengths.

AP2 Integration — Securing Payment Authorization

Where UCP standardizes the commerce flow from discovery to checkout, AP2 (Agent Payments Protocol) standardizes the payment authorization flow. The two protocols work together.

The UCP specification defines a dev.ucp.shopping.ap2_mandate extension that integrates AP2's Mandates — cryptographically signed digital contracts — into the checkout flow. Verifiable Digital Credentials (VDCs) proving the user authorized the agent's purchase are attached to checkout sessions.

This integration lets merchants cryptographically verify that an agent genuinely has user authorization for a purchase. Payments use a tokenized model based on Google Pay, with support for PayPal and other methods planned by design.

Cost-wise, UCP transactions incur processor fees only at approximately 3.2%. No platform fee. For a merchant doing $1M monthly, the difference versus ACP's additional 4% platform fee amounts to roughly $40,000 per month.

The Partner Ecosystem

UCP's ecosystem operates in three tiers: co-development partners, endorsement partners, and onboarding partners.

Shopify's involvement is the most impactful. Beyond supporting UCP, Shopify co-developed the protocol and designed the Embedded Protocol (EP). With millions of Shopify stores becoming UCP-enabled, smaller merchants need not implement the protocol themselves — platform-level support handles it.

From retail, Walmart participated as a co-developer. According to NRF, Walmart is advancing UCP adoption through its Sparky AI agent, and Target joined as an early implementation partner. By February 2026, Etsy and Wayfair launched UCP-powered checkout in Google Search AI Mode and the Gemini app.

On the payments side, Visa, Mastercard, American Express, Stripe, Adyen, and PayPal have endorsed UCP. Stripe holds a unique position as both a UCP onboarding partner and ACP co-developer.

The March 2026 update announced simplified Merchant Center onboarding with six launch partners: Shopify, Salesforce, Stripe, BigCommerce, Adobe, and Commerce Inc.

UCP vs Traditional EC Integration

The most critical difference is structural scalability. Traditional integration requires custom API work for every new sales channel — Amazon, Rakuten, Google Shopping, Instagram Shopping. Costs grow linearly with channel count.

UCP solves this "N x N problem" at the root. A merchant publishes a UCP manifest, and any agent that reads it can initiate transactions. Agents beyond Google's ecosystem can transact with any UCP-compliant merchant. As SearchEngineLand reported, UCP avoids platform lock-in and enables an open agent ecosystem.

Structured product data is the entry point. If a merchant's existing backend (product catalog, inventory, payments) is already API-enabled, adding UCP endpoints takes approximately 8-16 hours.

UCP and ACP — Complementary, Not Competing

Understanding UCP requires addressing its relationship with ACP (Agentic Commerce Protocol), co-developed by OpenAI and Stripe. A detailed comparison is covered separately, but here are the essentials.

UCP is decentralized and merchant-hosted. ACP is centralized and platform-mediated, with merchants submitting product data to OpenAI's index for discovery and purchase on ChatGPT.

The design philosophies are polar opposites, but the protocols coexist because they capture different demand. UCP operates in Google Search and Gemini's intent-driven channels. ACP generates purchase opportunities from ChatGPT's more ambiguous conversational contexts. Google itself states that UCP is "designed to coexist alongside" ACP.

Implementation Guide for Ecommerce Businesses

How should ecommerce businesses approach UCP adoption? Here is the most practical path, broken down by stage.

Step 1: Make Product Data Machine-Readable

Structured product data is a prerequisite. Schema.org Product markup and Google Merchant Center feed registration come first. UCP's Catalog API can leverage existing Merchant Center feeds, so this investment carries forward.

Step 2: Platform Integration vs Self-Implementation

Merchants on Shopify, BigCommerce, Salesforce Commerce Cloud, or Adobe should wait for their platform's UCP support — the most efficient path. The March 2026 onboarding partner announcement means these platforms are building simplified Merchant Center-based UCP integration.

For merchants with custom backends, start with the ucp.dev specification and GitHub repository. The minimum requirement is Checkout capability implementation along with the /.well-known/ucp manifest.

Step 3: Configure Payment Handlers

Check whether your PSP (Payment Service Provider) has an AP2 roadmap. Stripe, Adyen, and PayPal are already in the UCP ecosystem. As PSP-side AP2 support matures, merchant integration overhead will decrease significantly.

Step 4: Plan for Dual Protocol

Medium-term, a dual UCP + ACP strategy is becoming standard. Build a shared backend API layer (product catalog, inventory, payments), then implement endpoints for both protocols.

Future Outlook

UCP is still early in its evolution. In three months since launch, capabilities expanded from 3 to 6+, and onboarding has been simplified. Live checkout is operational on Etsy and Wayfair, with Shopify, Target, Walmart, Best Buy, and Home Depot integrations forthcoming.

The protocol's design anticipates expansion beyond shopping into travel, service booking, and B2B procurement. The namespace system makes this possible — dev.ucp.travel or dev.ucp.b2b can be added without disrupting existing infrastructure.

If agentic commerce is the era where AI agents handle purchasing, UCP aims to be its HTTP — open, decentralized, and preserving merchant data sovereignty. The fact that 20+ companies have endorsed this vision speaks to the direction's soundness.

Summary

UCP is the Google-led, industry-backed open standard for agentic commerce. Decentralized discovery via .well-known/ucp manifests, multi-transport support across REST, MCP, and A2A, and payment integration through AP2 — these design choices reflect a clear vision: merchant-controlled, platform-independent agent readiness. The first step for ecommerce businesses is structuring product data and checking their platform's UCP support. Preparing for the age of agent-driven commerce is worth starting now.