Universal Commerce Protocol (UCP)

Definition

The Universal Commerce Protocol (UCP) is an open standard for agentic commerce led by Google, designed to let AI agents transact across the full shopping journey — discovery, purchase, and post-purchase support — on Google’s AI surfaces, including AI Mode in Search and Gemini.

Merchant integration runs through Google Merchant Center, with payment handling available through Google Pay. The specification, documentation and reference implementations are published publicly.

Scope: wider than ACP

The most useful distinction between the two standards is scope rather than capability.

The Agentic Commerce Protocol is tightly scoped around discovery, checkout and payment. UCP deliberately extends past the transaction into post-purchase — order status, modifications, returns — which is the territory where a large share of customer contacts actually live.

That breadth is a real advantage and a real cost. It means UCP touches more of your systems: not only the catalog and checkout, but order management and support workflows.

What a merchant has to do

• Merchant Center hygiene. UCP builds on the feed infrastructure many retailers already maintain for Shopping. If your feed is healthy, you start from a better position than you would with ACP.
• Structured attributes. Same requirement as everywhere else in agentic commerce: agents compare on attributes, not adjectives.
• Checkout surface. The UCP-powered checkout feature, with Google Pay as the documented payment path.
• Post-purchase endpoints. The part teams underestimate. Exposing order status and modification capability to an agent is an authorization problem before it is an integration one.

When not to prioritise it

If your buyers are not arriving through Google AI surfaces in meaningful numbers, this can wait. The signal to watch is the share of your organic traffic already being intercepted by AI Overviews and AI Mode — if that number is climbing while clicks fall, UCP moves up the list.

As with ACP, the catalog work underneath should not wait. It is required by both standards and improves conventional Shopping performance regardless.

The honest position

Two competing standards backed by the two companies that own most of the demand is not a stable end state, and anyone claiming certainty about which prevails is guessing. Our recommendation: treat the protocol surface as a channel decision you can defer, and the catalog and identifier work as a foundation you should start now. The second is what determines whether an agent shortlists your product under either standard.

See the full side-by-side in ACP vs UCP.

Related terms

Agentic commerce · Agentic Commerce Protocol · Product feed · Generative engine optimization · Agent checkout