The Universal Commerce Protocol has published an updated specification — its fourth release overall and the first since April. It adds grocery features, lays groundwork for food and lodging, and includes breaking changes that require schema updates.
Key facts
- Effective: Released now; earlier versions can still be supported, but new features require schema changes
- Who's affected: Merchants and platforms already implementing UCP for checkout inside AI Mode and Gemini. If you haven't adopted it, nothing changes today
- What to do: Adopters: read the breaking changes section today, focusing on fulfillment, buyer consent and signing keys. Everyone else: no action
What happened
Per Search Engine Journal's breakdown, the release covers three areas. Structurally, the spec is reorganised into Shopping, Payment and Common sections, with payment features positioned to apply across verticals rather than retail checkout alone. On grocery, agents gain location tools for finding physical stores — addresses, operating hours, map coordinates — plus a standardised store hours format and the ability to order by weight. On payments, the update adds vendor-neutral 3D Secure 2 authentication, payment schedules with deposits and installments, and splitting a single order across multiple payment methods. Four breaking changes: fulfillment schemas move to a new structure; buyer consent moves from fixed fields into a flexible map; profile signing keys consolidate into a single JWK Set; and versions are now labelled by date instead of number. Google introduced UCP at NRF in January; the Governing Council's permanent members are Google and Shopify, with Stripe added in April. A Food Technical Council formed in July (Block/Square, DoorDash, Google, Toast, Uber Eats) and a Lodging Technical Council on August 11 (Amadeus, Booking.com, Expedia, Google, Hilton, Marriott, Trip.com). On retail, Google I/O revealed UCP-powered checkout is expanding to Canada and Australia, with the UK later.
What it means for independent store owners
If you haven't adopted UCP, there is nothing to do today — but put it on the calendar. UCP is the contract behind checkout completed inside an AI interface: the shopper picks a product in AI Mode or Gemini and pays without ever landing on your store. Current adopters do need to move. The breaking changes land on fulfillment and buyer consent, and those two failing rarely looks like an error — it looks like orders silently not arriving or consent state drifting, which is far harder to diagnose than a crash. Read the breaking changes section against the features you actually use; the spec lets you keep supporting older versions, so anything you don't touch can wait. For merchants still deciding, the signal to watch is geography, not the feature list: wait until UCP checkout is genuinely live in your main markets — beyond the US that currently means Canada and Australia, with the UK unscheduled — before pricing an integration. Food and lodging are foundations only. Nothing in the release says you can order groceries or book a hotel through an AI interface today, so don't plan as if you can.