Universal Commerce Protocol (UCP)
The Universal Commerce Protocol (UCP) is an open standard by Google and Shopify that standardizes the entire commerce lifecycle for AI agents. While ACP focuses on checkout and payment, UCP covers everything — from product discovery to returns management.
What Is UCP?
The Universal Commerce Protocol (UCP) defines an open standard for the entire lifecycle of a commerce transaction between AI agents and merchants: product discovery, identity linking, checkout, payment, and post-purchase management.
UCP positions itself as a holistic solution. It answers not only the question "How does an agent make a purchase?" but also "How does an agent find products?", "How does it link customer accounts?", and "How are returns handled?"
Google and Shopify as Driving Forces
Google brings its enormous reach: Google Search, Google Shopping, Google Maps, and the new Business Agent reach billions of users. UCP defines how AI-powered commerce interactions work across these products.
Shopify brings the merchant network: over 2 million active stores worldwide. Shopify has already deployed an MCP server that gives agents access to product catalogs and checkout — an early implementation of the UCP vision.
Additional partners include Adobe Commerce, BigCommerce, and PayPal. Google positions UCP as the standard around which a broad ecosystem is forming.
The Commerce Lifecycle in Four Phases
Phase 1: Discovery
The agent finds products. UCP standardizes how product catalogs are provided and searched — comparable to the Product Feed Spec in ACP, but broader. Discovery also encompasses categorization, filtering, and semantic search.
Phase 2: Identity Linking
A feature ACP does not have: the agent can link an existing customer account with the merchant. This enables personalized pricing, loyalty points, saved addresses, and order history — information that improves the purchase decision.
Phase 3: Checkout
Create a cart, select shipping options, pay. Functionally similar to the ACP Checkout API, but embedded in the broader UCP lifecycle. UCP is compatible with AP2 for the payment layer.
Phase 4: Order Management
After the purchase: check order status, retrieve tracking information, initiate returns, contact customer service. This phase is entirely absent from ACP — UCP defines how an agent can act on behalf of the user even after the purchase.
Participant Roles
UCP defines three roles in the commerce process:
- Buyer: The user who instructs the agent. Sets goals, confirms purchases, receives the goods.
- Agent: The AI system acting on behalf of the buyer. Searches products, compares, executes checkout.
- Seller: The merchant offering products. Provides product data, processes orders, handles fulfillment.
In the long term, a fourth participant may emerge: the Seller Agent — an AI agent operating on the merchant side that negotiates with the buyer agent.
Compatibility with Other Protocols
UCP was deliberately designed as an "umbrella" that works together with other protocols:
- A2A (Agent-to-Agent): Google's protocol for communication between AI agents. UCP uses A2A when multiple specialized agents collaborate.
- AP2: For the payment layer. UCP delegates payments to AP2-compatible systems.
- MCP: For tool communication. Stores can expose UCP-compatible endpoints as MCP servers.
Business Agent and Merchant Center
Alongside UCP, Google introduced the Business Agent — an AI system that allows customers to interact directly with brands and merchants in Google Search. The Business Agent is the first Google-side implementation of UCP.
In Google Merchant Center, new data attributes are being introduced that specifically target conversational commerce: extended product descriptions, return policies in structured format, and agent-compatible checkout information.
UCP vs. ACP
| Aspect | ACP | UCP |
|---|---|---|
| Scope | Checkout + Payment | Full Commerce Lifecycle |
| Discovery | Product Feed Spec | Comprehensive Discovery Phase |
| Identity | Not included | Identity Linking |
| Post-Purchase | Not included | Order Management, Returns |
| Payment | SharedPaymentToken | AP2-compatible |
| First Impl. | ChatGPT | Google Search / Business Agent |
The protocols do not directly compete — they solve problems of different breadth. A merchant supporting both reaches both ChatGPT and Google users. More details: ACP vs. UCP vs. AP2.
Frequently Asked Questions
What is the difference between UCP and ACP?
UCP covers the entire commerce lifecycle (discovery through post-purchase), while ACP focuses on checkout and payment. UCP is broader, ACP goes deeper in the checkout area. Both can coexist.
Do I need UCP as a Shopify merchant?
Shopify is actively working on UCP integration. As a Shopify merchant, you will likely benefit automatically — through the Shopify MCP server and native platform updates.
Is UCP only relevant for Google products?
No. UCP is designed as an open standard. The first implementations run in Google products (Search, Shopping, Business Agent), but the protocol can be used by any agent.