Universal Commerce Protocol (UCP): definition

In detail

Per the published spec at ucp.dev and Google's merchant documentation, a UCP-ready merchant publishes a JSON profile at /.well-known/ucp (public, with declared signing keys) and exposes five checkout REST endpoints under a declared base URL — create, read, update, complete, and cancel checkout sessions. Order-status webhooks (created, shipped, delivered) flow from the merchant to Google. The service-level targets are checkout-grade: roughly one-second median response on session creation, which is why most Shopify storefronts reach UCP through Shopify's integration rather than a hand-rolled backend.

One naming note worth stating plainly: UCP is the Universal Commerce Protocol, not "Unified Content Protocol." Several publications used the wrong expansion in the week after the January 2026 announcement, and the error still circulates.

On the catalog side, UCP adds attributes to the Merchant Center product feed — most importantly native_commerce, a SKU-level boolean opt-in. A SKU without it is ineligible for UCP checkout even if the merchant is otherwise ready. This is where agent-readiness becomes per-SKU work rather than a one-time backend project.

Why it matters for ecommerce

UCP answers the question Shopify brands keep asking about Google's AI surfaces: how do you take an order from AI Mode or Gemini without rebuilding checkout or handing the customer relationship to Google? The merchant stays Merchant of Record; the AI surface drafts the cart and drives the protocol exchange; the order lands in the normal pipeline.

The strategic point is that the groundwork is shared across protocols. The same complete Product schema, machine-readable price and availability, and discoverable policies that win citations today are what make a SKU draftable under UCP, ACP, or whatever wins. Brands do not have to bet on a protocol to start the per-SKU preparation.

Example

A Shopify brand selling carry-on luggage enables Shopify's agentic channel and opts its eligible SKUs into native_commerce via a supplemental feed. A shopper in Google AI Mode asks for "carry-on under 7 pounds," the answer cites the brand's SKU, the shopper says "buy it," and the protocol exchange completes the order — which arrives in Shopify Admin as a regular order with an attribution flag. The brand's work was feed hygiene and PDP data quality, not protocol engineering.

How eCommerce Insights relates to it

eCommerce Insights does not implement UCP checkout — it scores readiness for it. Each SKU's agent-readability score checks the groundwork agents read upstream of any protocol: Product JSON-LD completeness, crawler admittance, machine-readable price and availability, and discoverable policies. The free Agentic Readiness Grader runs the same checks on any store in about a minute; the agentic commerce solution page covers the strategy.

Related terms

ACP (Agentic Commerce Protocol) — the OpenAI/Stripe counterpart behind ChatGPT Instant Checkout.
Shopify Agentic Storefronts — Shopify's wrapper for both stacks.
AP2 (Agent Payments Protocol) — the payments-layer sibling.
Agentic commerce — the umbrella term.
MCP (Model Context Protocol) — one of the transports UCP supports.

Ask AI about UCP

Have your favorite AI engine apply this definition to your store.

Frequently asked questions

Does UCP stand for Unified Content Protocol?

No — UCP is the Universal Commerce Protocol. Several third-party publications used the wrong expansion in the week after Google's January 2026 announcement and the mistaken name still circulates in vendor decks. The canonical name on ucp.dev and Google's developer documentation is Universal Commerce Protocol.

How is UCP different from ACP?

UCP is Google's protocol, serving AI Mode and Gemini; ACP is the OpenAI/Stripe protocol behind ChatGPT Instant Checkout. They solve the same problem — agent-completed purchases against merchant endpoints — with different specs and ecosystems. A Shopify brand does not have to pick: Shopify Agentic Storefronts wraps both, and the PDP groundwork underneath is shared.

What does a merchant implement to be UCP-ready?

Per the published spec: a public JSON profile at /.well-known/ucp, five native checkout REST endpoints under a declared base URL (create, get, update, complete, and cancel checkout sessions), order-status webhooks back to Google, and the native_commerce opt-in attribute on the Merchant Center product feed. Most Shopify brands get all of this through Shopify's integration rather than building it.

Who takes the order — Google or the merchant?

The merchant remains the Merchant of Record. The AI surface assembles the cart and initiates checkout through the protocol, but the order, the payment relationship, and fulfillment stay with the merchant — the order lands in the normal order pipeline with an attribution flag.

Is UCP live for everyone?

No. UCP is in pilot as of mid-2026, with eligibility limited to the US, Canada, and Australia per Google's documentation, and several product categories excluded (subscriptions, pre-orders, age-restricted goods, and others). Describe readiness work as preparation, not as flipping a switch that is available today for every store.

Go deeper

Check whether your SKUs are agent-ready before any protocol asks. Run the free Agentic Readiness Grader.