What is Google UCP? The Universal Commerce Protocol, explained for merchants

UCP describes how compatible shopping applications and merchants exchange commerce information. This guide explains the capabilities, Google's participation requirements and the tests that separate a published profile from a working checkout.

Reviewed October 1, 2026 · 6 min read

The Universal Commerce Protocol (UCP) is an open specification for commerce interactions between businesses and compatible applications. Google introduced it with commerce partners in January 2026. It can support catalog, cart, checkout and post-purchase workflows, depending on the capabilities each side implements.

In Google's UCP merchant integration, the retailer remains the merchant of record. That preserves the retailer's role in fulfillment and customer support; it does not mean every existing loyalty feature or checkout customization automatically carries over. Confirm the supported behavior in the integration you choose.

This guide covers capabilities, onboarding and verification. The protocol comparison explains how UCP differs from ACP and MCP.

The capabilities to understand#

UCP is modular. A business profile advertises supported services, capabilities and payment handlers. Clients must use compatible versions and supported combinations. Consult the current UCP specification rather than treating every capability as mandatory or universally available.

A catalog API can provide fresher information than a periodic file, but only if its backend and cache are current. Revalidate price and availability before commitment. A recent response timestamp alone does not prove that an item can still be fulfilled.

Read the protocol and platform requirements together#

The protocol describes possible interactions. Google's implementation defines what a participating merchant must support and which experiences are available. Keep these four references in your implementation plan:

• The specification version your client and server support.
• The platform's current merchant eligibility and account requirements.
• The chosen checkout or cart-transfer experience and its payment requirements.
• The test evidence and operational owner for each advertised capability.

For a service or booking business, check whether the actual integration supports your offer's scope, timing and fulfillment. A protocol extension or roadmap announcement is not confirmation that your business category is accepted today.

How you actually get on it#

Start with your commerce provider if it offers a supported integration. For a direct Google connection, use the Merchant Center integration guide. It describes the available integration choices and the UCP profile location.

1. Confirm eligibility and account access. A product feed or platform subscription alone does not establish UCP participation.
2. Choose the supported experience, such as native checkout or transfer to a merchant cart, based on your operational needs.
3. Publish the profile and endpoints required by that experience, using the accepted specification version.
4. Connect catalog, pricing, inventory, order and payment systems with clear ownership for updates.
5. Complete the platform's tests and inspect the customer journey before enabling live traffic.

Payment methods and authorization requirements depend on the selected experience. Follow the platform and payment provider documentation, and test the final authorization and settlement behavior. Do not assume that mentioning AP2 or another payment standard makes an integration secure or universally supported.

Verify behavior, not just a profile file#

A public profile shows what a merchant advertises. It does not establish whether a particular customer can complete a purchase, whether a private payment configuration is active or whether the merchant is enrolled with a platform.

Treat ecosystem counts with the same care. A crawler can count reachable profiles and declared capabilities at known paths. It cannot infer all private integrations or prove a complete purchase from those declarations alone.

For your own store, collect stronger evidence: the request, the selected item, the quote, the authorized action and the resulting order. Use a supported test environment for transactions and compare the result with your order system.

Also test the handoff to customer support. A shopper needs a durable order reference and a clear route to delivery information, cancellation or returns. The automation is incomplete if your team cannot identify the order it created.

Should you prioritize UCP?#

Prioritize UCP when you have a confirmed platform route, suitable offers and the capacity to maintain the integration. Existing Merchant Center data can help prepare the catalog, but it does not eliminate checkout engineering or operational work.

For appointment businesses, a reliable booking flow may be the nearer-term need. Compare the supported UCP route with your existing booking system and any connected tools. The service booking guide explains the requirements without assuming a particular protocol is best.

Keep your product pages, structured data and operational catalog aligned. Useful public information supports customer decisions even when a shopper does not use a protocol-based checkout.

A shared catalog reduces duplicate editing, while separate adapters handle destination-specific formats. Version those adapters and test them after changes. A protocol upgrade may require more than regenerating a file, especially when payment or order behavior changes.