UCP: Universal Commerce Protocol
Google's open commerce protocol, announced January 11, 2026 with Shopify, Etsy, Wayfair, Target, Walmart, and roughly twenty partners. Often misidentified as "Unified Content Protocol" in early third-party coverage.
The naming confusion
UCP stands for Universal Commerce Protocol, not Unified Content Protocol. Several third-party publications used the wrong expansion in the week after Google's January 11, 2026 announcement, and the mistaken name has cycled through some vendor decks. The canonical name on ucp.dev and developers.google.com/merchant/ucp is Universal Commerce Protocol.
In detail
A UCP-ready merchant publishes a JSON profile at /.well-known/ucp (no auth, minimum 60-second cache TTL, includes ucp and signing_keys objects) and exposes five native checkout REST endpoints at a merchant-declared base, conventionally /ucp/v1: POST /checkout-sessions, GET /checkout-sessions/{id}, PUT /checkout-sessions/{id}, POST /checkout-sessions/{id}/complete, POST /checkout-sessions/{id}/cancel.
The SLOs are aggressive. POST /checkout-sessions must hit ≥95% availability, P50 ≤1s, P95 ≤4s. POST /complete must hit P50 ≤6s, P95 ≤10s. Most Shopify storefronts need an edge layer to clear those targets reliably.
Webhooks flow from the merchant TO Google at shoppingdataintegration.googleapis.com (not the reverse). Three events are mandatory: Order Created (status: processing, fired immediately), Order Shipped, and Order Delivered. Webhook signing uses RFC 9421 in 2026-04-08, or HMAC/detached-JWT per RFC 7797 in 2026-01-23. Identity linking uses OAuth 2.0 with PKCE-S256 recommended; Google Streamlined Linking is optional for in-Google account-link UI. Compatible transports include REST, MCP, A2A, and Embedded Protocol (EP). The Google Pay handler is com.google.pay at v2026-01-23.
The three new product-feed attributes
UCP introduces three attributes on the Merchant Center product feed:
native_commerce— a SKU-level boolean opt-in. Recommended via a supplemental feed rather than modifying the primary feed. Without it the SKU is not eligible for UCP checkout, even if the merchant is otherwise UCP-ready.consumer_notice— required for regulated products. Contains anotice_typeenum value and anotice_messagestring.merchant_item_id— optional. Maps a GMC product ID to a merchant's internal UCP ID.
Ineligible categories per Google's documentation: subscriptions, installments, personalized goods, pre-order, bundled, age-restricted, services, rentals, virtual items, and software-dependent goods.
Why it matters
UCP is the answer to a question Shopify brands have been asking: how do you participate in Google AI Mode and Gemini commerce without rebuilding checkout? UCP defines the contract; Shopify ships the integration through Shopify Agentic Storefronts. Pilot eligibility as of 2026-06-03 is US, Canada, and Australia.
Related terms
- ACP (Agentic Commerce Protocol) — the OpenAI/Stripe/Meta counterpart that powers ChatGPT Instant Checkout.
- Shopify Agentic Storefronts — Shopify's channel for AI-driven commerce; wraps UCP for Shopify merchants.
- AP2 (Agent Payments Protocol) — Google's sister protocol for secure agent-led payments.
- Agentic commerce — the umbrella term.
- Product schema — the structured data UCP attaches to.
Ask AI about UCP
Have your favorite AI engine summarize this for your specific use case.
Frequently asked questions
What is the difference between UCP and Unified Content Protocol?
Who maintains UCP?
Where does AP2 fit in?
Related guides
- Universal Commerce Protocol (UCP) for Shopify: a 2026 guide
- What is the Agentic Commerce Protocol
- How to make my Shopify store agent-ready
Score your store's UCP and ACP readiness in 60 seconds with the free Agentic Readiness Grader.