A lodging booking draft
An initial lodging capability enters the repository as a draft.
Protocol · draft, not a rollout
The agentic web · A living reference
Track the Universal Commerce Protocol from its January 2026 announcement through specification changes, Google rollouts and country-specific developments.
The latest release checked is dated 25 August 2026. Selected retail deployments are documented, while lodging remains a draft capability. A specification release does not establish availability in every product or country.
UCP stands for Universal Commerce Protocol, announced on 11 January 2026. Google’s launch announcement.
The protocol and Google’s shopping products have different histories. A specification can define a capability before a retailer or consumer app makes it available. This reference tracks both, with separate labels.
The founding participants are listed above. Google also named a wider group of endorsers. Launch participants.
The timeline records subsequent changes to the governing and technical councils. Those are distinct bodies with different roles; council membership is not a checkout rollout.
A business describes its supported services and capabilities in a discoverable profile. An agent can read that profile, identify compatible functions and interact with the business through the supported interfaces. Google’s launch walkthrough uses a JSON document at a well-known path. Google’s technical introduction.
For example, the discovery step is an HTTP request of this form:
GET /.well-known/ucp HTTP/1.1
Host: shop.example
shop.example is a placeholder. This is an illustration of discovery from the January 2026 design, not a complete integration or a live retailer test. The response identifies versions, services, capabilities and payment configuration. Later versions change the schema, so production work must use the documentation for the version being implemented.
Google’s March update added optional capabilities for carts, catalog queries and identity linking. These address different parts of shopping: choosing several items, retrieving product information and connecting an existing customer account. A merchant can support some capabilities without implementing every part of the protocol. March capability update.
Google’s merchant guidance describes a separate onboarding process for its checkout experience. Technical compatibility and eligibility to appear in a consumer product should therefore be checked separately. Google merchant guidance.
The timeline distinguishes announcements, specification releases, governance changes, documentation and reported rollouts. Each answers a different question about maturity.
For a business assessing UCP, the useful evidence becomes more specific: which products can a customer buy, in which country, with which payment method, and what happens when something goes wrong? The Australian watch section keeps local evidence visible as the wider protocol evolves.
Latest developments
Newest first. Work backwards through the developments and their original dates.
UCP was announced in January 2026. Google’s 2025 shopping experiments predate this protocol.
Share this view using the address in your browser.
Country tags identify the markets named in the evidence. Global updates have no country-specific scope.
19 milestones · newest to oldest
An initial lodging capability enters the repository as a draft.
Protocol · draft, not a rollout
Google reports a gradual US rollout of cart transfer and enhanced checkout testing through its UCP integration hub. Analytics remains forthcoming.
US · Merchant Center integration-hub features
The same update plans these new integration-hub capabilities for Australia and Canada in early 2027. This does not date the first availability of UCP checkout in either country.
Australia and Canada · hub features planned for 2027
Tapestry reports single-item purchasing through Google Search and Gemini, with customer approval before payment.
US · Coach and Kate Spade
Shopify updates its advertised UCP version while saying its supported capabilities remain unchanged.
Shopify · implementation
UCP establishes a dedicated payments council.
Protocol · payments
The August release adds structural changes for more commerce categories, payment security and independent capability versioning.
Protocol
A dedicated council begins work on lodging.
Protocol · lodging
A dedicated council begins work on food commerce.
Protocol · food
The retailer describes selected own-label products, single-item purchases, linked accounts and Google Pay.
Australia · limited retailer integration
Documentation dated 9 July. The stated start, “Thursday, 10 July 2026”, has a weekday/date mismatch. An exact launch day is not confirmed.
Read the SignalAt Marketing Live, Google reiterates plans for Australia and Canada in the coming months, followed later by the UK. These are expansion plans, not confirmation of local availability.
Australia, Canada and UK · planned
Google announces UCP checkout expansion to Canada and Australia in the coming months, with the UK later. It also announces US plans for Universal Cart and UCP on YouTube.
Google surfaces · planned expansion
Stripe joins Google and Shopify on the governing council.
UCP · governing council
Amazon, Meta, Microsoft, Stripe and Salesforce representatives join.
UCP · technical council
UCP publishes version 2026-04-08.
Protocol
Google announces optional capabilities covering multi-item carts, catalog access and linked customer identities.
Protocol · optional capabilities
Google reports US checkout for Etsy and Wayfair in AI Mode and Gemini. Shopify, Target and Walmart are still described as coming soon.
US · Etsy and Wayfair
Read the SignalUCP publishes version 2026-01-23.
Protocol
UCP is introduced as an open commerce standard. Google describes eligible US checkout in AI Mode and Gemini as coming soon.
Protocol · initial US product plans
Read the SignalNo matching milestones are recorded here. An empty result is an evidence gap. Try another selection or reset the filters.
Evidence checked through 7 Oct 2026.
Dates follow the source’s calendar date. Version dates identify specification snapshots; they do not prove the exact day a release first became public.
“Reported rollout” means a platform or retailer reports availability in the stated scope. These entries are source research, not purchase tests conducted by Paul. Announcements, specifications and council membership are recorded separately from adoption.
Country tags follow explicit market statements in the cited sources, including announced plans. They do not follow a company’s headquarters, a translated website or the general availability of ChatGPT, Gemini or AI Mode. Eligibility documentation is recorded in Country watch using the research check date when an original rollout date is unknown.
New findings keep their historical dates and appear newest first. Corrections and substantive reviews update the research date above.