Universal Commerce Protocol Explained for Retailers 2026

The Universal Commerce Protocol (UCP) is an open standard that lets AI agents and stores exchange product, cart and checkout information. For Australian retailers, the next action depends on your platform’s implementation and the countries supported by the sales channel.

Google announced UCP with retail and platform partners in 2026. Supporting the protocol and being eligible for Google’s direct checkout are separate requirements.

What the Universal Commerce Protocol Does

UCP gives an AI shopping agent and a store a shared way to describe commerce operations. They use agreed information formats to find products, update a cart and complete an eligible checkout.

Google’s developer announcement names Shopify, Etsy, Wayfair, Target and Walmart as co-developers. It also names endorsers including Adyen, American Express, Best Buy, Flipkart, Macy’s, Mastercard, Stripe, The Home Depot, Visa and Zalando. Co-development and endorsement describe participation in the standard. They don’t establish that every merchant on a partner’s platform has an active UCP connection.

A store publishes the capabilities it supports, and the agent identifies which ones it can use. The pair agrees on compatible versions before carrying out a request. The UCP specification describes this exchange.

The retailer still supplies its commercial rules and fulfils the order. Google’s implementation keeps the retailer as the merchant of record, responsible for the sale and the customer relationship.

How Google UCP Works Between an Agent and Your Store

UCP separates the agent’s requests from the store’s decisions about what can be sold and on what terms. A platform can run the store’s side of the connection.

1. The agent discovers the store’s supported capabilities. The store publishes a profile that identifies its services and connection methods. Product discovery supplies the items and variants available for the request. In Google’s implementation, Merchant Center supplies product information.
2. The agent builds or changes the cart. It requests the chosen variant and quantity, while the store returns valid prices and stock. The store applies its delivery options, discounts and tax rules. The agent must use the returned information when presenting the purchase.
3. The agent requests checkout completion with the required buyer information and payment authorisation. The store checks the request and processes payment through the supported payment arrangement. It then returns the order result. If a step needs the customer’s intervention, the store can return a link to continue checkout.

For example, imagine an agent requests two navy shirts in medium. Your store decides whether that variant is available and calculates the order total. The agent conveys the result to the customer and requests the next permitted action. UCP doesn’t give the agent permission to invent stock or override a delivery restriction.

These are protocol responsibilities. Each sales channel decides which capabilities it exposes and which merchants it accepts. Read the guide to Google AI shopping for the channel itself.

How UCP Relates to ACP, AP2 and MCP

UCP describes commerce operations, while other protocols cover overlapping checkout tasks or the connections and authorisation those tasks need.

Protocol	What it defines	Relationship to UCP
Universal Commerce Protocol (UCP)	Commerce capabilities and the information exchanged between a business and an agent platform	The store and agent agree on supported capabilities before transacting
Agentic Commerce Protocol (ACP)	Programmatic commerce and checkout flows, developed by OpenAI and Stripe	An alternative commerce specification with overlapping checkout responsibilities
Agent Payments Protocol (AP2)	Verifiable mandates for agent-led payment authorisation	UCP can use its AP2 extension to bind approval to the checkout terms
Model Context Protocol (MCP)	Connections between AI applications and external tools or data	UCP can expose its commerce operations through an MCP connection

A mandate is a recorded authorisation that defines what an agent may do. The AP2 explainer covers that payment layer, while the ACP explainer covers the alternative checkout specification.

An MCP connection alone doesn’t establish UCP support. The commerce operations and their agreed information still need implementation. Equally, a retailer can meet several standards through one platform or connector. You don’t necessarily need a separate development project for each protocol. The commerce protocols guide explains the wider set.

Do Australian Retailers Need to Act on UCP

For an Australian store, technical UCP support and eligibility for a particular checkout channel require separate decisions. Your platform may provide the connection while the channel still limits which countries can participate.

Shopify’s help documentation describes Google AI Mode and Gemini direct checkout through its agentic storefronts. Its eligibility rules require a store based in the United States that sells to United States customers. An Australian-based Shopify store therefore doesn’t meet that stated location requirement. For eligible stores, Shopify handles the checkout infrastructure and exposes channel controls in the admin. Product discovery uses Merchant Center.

BigCommerce’s Catalyst documentation describes UCP endpoints served by the BigCommerce platform through the storefront’s own domain. A customised Catalyst proxy needs the documented UCP proxy changes. That establishes an implementation path, but it doesn’t make every BigCommerce merchant eligible for Google checkout. Ask your BigCommerce implementation partner whether your storefront includes that path and which channel onboarding it supports.

Other platforms need their own implementation assessment. Wix’s App Market lists an ooasis UCP Adapter, which is a third-party app. The listing limits the app to the United States. Its presence doesn’t establish native UCP support across Wix stores. For WooCommerce or another self-managed platform, identify the actual connector or custom implementation before treating the store as UCP-enabled.

For a custom store, ask your developer to map the connection to your existing checkout:

• Identify the UCP capabilities your store will publish and how an agent will discover them.
• Name the source of product availability and variant information.
• Demonstrate that existing discounts, tax calculations and delivery restrictions still run.
• Describe the handling of payment authorisation, failed payments and duplicate requests.
• Show how orders and later status changes reach your existing fulfilment system.
• Identify an agent platform that accepts this implementation and your market.

A useful proposal identifies those responsibilities and demonstrates a complete order in a test environment. Publishing a profile alone doesn’t prove checkout works.

What to Watch in 2026

Watch protocol changes and channel rollout separately, because a published capability can arrive before a sales channel supports it.

The UCP announcements describe a 2026 release with independent capability versioning and structured request constraints. The release also adds payment security changes, including support for cardholder authentication. Those changes affect how implementations agree on supported operations and handle payment steps.

The UCP roadmap names loyalty benefits, product recommendations and local shopping journeys as priorities. It also describes phased expansion into global markets, including Asia Pacific. These are stated priorities, so they don’t establish an Australian launch commitment.

Google posts implementation guidance on its UCP developer site. The shared standard records releases and governance changes on its announcements page. Platform documentation supplies the merchant requirements that determine whether your store can use each connection.

For an Australian store, the actionable milestone is support for your market and checkout requirements in a channel you intend to use. Give your platform provider those requirements now, then budget development against its documented implementation path.