Guide · Protocol · Updated June 2026
The Universal Commerce Protocol, explained for merchants
UCP is Google's open protocol for agent-led commerce: a buyer asks Gemini or Google AI Mode for a product and completes the purchase inside Google's surface, with the merchant staying merchant of record. Announced January 2026 with Shopify, Etsy, Wayfair, Target, and Walmart among the launch partners, and in pilot as of mid-2026. This guide covers the merchant profile, the endpoints, the three new feed attributes, the SLOs, and the Shopify wrapper that means most brands never touch the wire format.
eCommerce Insights team · 12 min read
A note on the name
UCP stands for Universal Commerce Protocol. Several third-party publications in the days after Google's announcement expanded it as "Unified Content Protocol," and that wrong expansion still circulates in vendor decks. The canonical name on developers.google.com/merchant/ucp and ucp.dev is Universal Commerce Protocol.
Who built UCP
Google leads. The announcement on the Google Developers Blog, dated January 11, 2026, names launch partners including Shopify, Etsy, Wayfair, Target, and Walmart, plus roughly twenty additional commerce platforms and brands. The current spec version is 2026-04-08, with 2026-01-23 still supported through the early-access window. Like ACP, everything below describes a published spec in pilot — not mainstream consumer behavior.
What UCP solves
UCP turns AI Mode and Gemini interactions into transactions while keeping the merchant as merchant of record. Without it, an agent-led flow either redirects the buyer to the storefront — breaking the agentic experience — or holds the buyer inside Google with the merchant demoted to a back-end vendor. With it, the buyer completes the purchase in Google's surface and the merchant fulfills the order and owns the customer relationship. For the commercial stakes of the buyer-never-lands pattern, see the agentic commerce solution page.
What a merchant exposes
- A JSON profile at
/.well-known/ucp— required, unauthenticated, minimum 60-second cache TTL. Contains aucpobject (capabilities, base URL, supported versions) andsigning_keysfor webhook verification. - Five REST endpoints at a merchant-declared base URL, conventionally
/ucp/v1. - A Google Pay handler against the published pay.google.com UCP spec.
- Identity linking via OAuth 2.0 with PKCE (S256 recommended).
- Signed webhooks to Google's shopping-data endpoint — three events mandatory: Order Created, Order Shipped, Order Delivered.
POST /ucp/v1/checkout-sessions # create a session
GET /ucp/v1/checkout-sessions/{id} # read state
PUT /ucp/v1/checkout-sessions/{id} # update items, shipping, buyer
POST /ucp/v1/checkout-sessions/{id}/complete # capture and complete
POST /ucp/v1/checkout-sessions/{id}/cancel # releaseCompatible transports include REST, MCP, A2A, and Embedded Protocol — a hint that Google expects agent frameworks, not just browsers, on the other end.
The three new feed attributes
UCP's SKU-level control surface lives in the Google Merchant Center product feed:
| Attribute | What it does | Status |
|---|---|---|
| native_commerce | Boolean opt-in per SKU; without true, the SKU is not eligible for UCP checkout | master switch |
| consumer_notice | Required disclosures for regulated products (notice_type + notice_message) | conditional |
| merchant_item_id | Maps the GMC product ID to the merchant's internal UCP ID | optional |
The recommended pattern pushes native_commerce through a supplemental feed, which lets a merchant opt in a known-good slice of the catalog without touching the primary feed. That per-SKU gating is worth pausing on: eligibility for agent checkout is decided SKU by SKU, which makes per-SKU data quality — the core of SKU-level AEO — the prerequisite, not an optimization.
The aggressive SLOs
P50 ≤ 1s on session creation is the demanding target. A storefront that proxies through a cold-starting serverless function, or round-trips to a platform admin API, will miss it under load. Direct implementers typically front the endpoint with an edge worker that caches the merchant profile and rate-limits abusive callers. Merchants going through Shopify inherit Shopify's infrastructure instead.
Shopify Agentic Storefronts: the wrapper
Shopify ships the UCP integration so its merchants do not stand up the protocol themselves. The merchant-visible surface is Shopify Agentic Storefronts, documented at shopify.dev — components include Global Catalog, Storefront Catalog, and the Cart, Checkout, and Order MCP servers. For a Shopify brand the practical work is therefore not endpoints; it is catalog quality: accurate variant availability, complete identifiers, fresh prices, and clean feeds. That is the same groundwork measured by the agent-readability score, and the same fixes covered in schema for AI search.
UCP vs ACP, and where AP2 fits
UCP and the OpenAI/Stripe-led ACP are parallel answers to the same question from two camps. UCP's distribution runs through Google surfaces and the GMC feed; ACP's runs through ChatGPT and a PSP-delegated payment flow. Shopify backs UCP; ACP's first named PSP is Stripe. Neither has consumer volume that forces a choice as of mid-2026 — and a brand does not have to choose, because the catalog groundwork is shared. The Agent Payments Protocol (AP2), Google-initiated with multiple partners, sits on the payments layer and is designed to work alongside both. Full side-by-side in the ACP guide; category framing in what is ACO.
What to do about it
- Clean the Merchant Center feed now — identifier gaps and stale availability disqualify SKUs before any opt-in flag matters.
- Decide the opt-in slice: which SKUs you would trust an agent to sell unattended, and gate via supplemental feed when eligible.
- Keep PDPs citation-ready — agents recommend from the same answer surfaces measured in the product AI visibility pillar.
- Score agent-readability per SKU with the free readiness grader and fix the failures.
- Watch Shopify's Agentic Storefronts rollout rather than building endpoints yourself.
Questions merchants ask
What is the Universal Commerce Protocol?
UCP is Google's open protocol for agent-led commerce: it lets a buyer complete a purchase inside Google AI Mode or Gemini while the merchant remains the merchant of record. Google announced it in January 2026 with Shopify, Etsy, Wayfair, Target, Walmart, and roughly twenty other partners. It is in pilot as of mid-2026.
Is UCP the same as the "Unified Content Protocol"?
No — that expansion is a common third-party misnaming that circulated after the announcement. The canonical name on ucp.dev and Google's merchant documentation is Universal Commerce Protocol. If a vendor deck says Unified Content Protocol, it is almost certainly UCP under the wrong name.
How does a Shopify store get UCP checkout?
Through Shopify, not by self-implementing. Shopify is a UCP launch partner and ships the integration as Shopify Agentic Storefronts — the merchant-visible surface documented at shopify.dev. Most Shopify brands should prepare the catalog (feed quality, schema, availability accuracy) and opt in through the platform rather than standing up the five REST endpoints themselves.
What controls which SKUs are eligible for UCP checkout?
A boolean native_commerce attribute on the Google Merchant Center product feed, best pushed via a supplemental feed. A SKU without native_commerce: true is not eligible. Two more attributes matter: consumer_notice, required for regulated products, and merchant_item_id for mapping GMC IDs to internal catalog IDs.
Why do UCP's SLOs matter to a merchant?
The spec sets tight latency targets — P50 of one second or less on checkout-session creation, P95 of four seconds — that most storefronts cannot hit through slow serverless proxies or round-trips to platform admin APIs. Merchants implementing directly typically need an edge layer; Shopify-wrapped merchants inherit Shopify's infrastructure.
Eligibility starts with data
UCP gates checkout SKU by SKU. So should your audit.
Score every SKU on agent-readability before the opt-in flag ever matters.