UCP Updates Spec: New Schema Changes Released
▼ Summary
– The Universal Commerce Protocol (UCP) released its fourth specification update, introducing features tailored for grocery shopping and expanding beyond traditional retail.
– This version includes breaking changes to schemas, such as modified fulfillment structures and consolidated profile signing keys, requiring adopters to update their implementations.
– Payment capabilities have been enhanced with vendor-neutral 3D Secure 2 authentication, support for split payments, and flexible scheduling options like deposits and installments.
– Grocery-specific tools now allow agents to locate physical stores via addresses and maps, access standardized operating hours, and place orders by weight.
– Governance expansions include new technical councils for food and lodging sectors, involving major industry players like DoorDash, Booking.com, and Hilton to develop future specifications.
The Universal Commerce Protocol (UCP) has unveiled a significant update to its specification, marking a strategic pivot toward grocery shopping and setting the stage for expansion into food and lodging commerce. This release serves as a critical complement to existing retail capabilities, introducing structural changes that facilitate multi-vertical growth while enhancing payment security and specialized grocery features.
This marks the fourth overall release of the protocol since its introduction by Google at NRF in January. It is the first major update since March, when initial Cart and Catalog features were detailed. The announcement was published on both the project’s website and GitHub, coinciding with an expansion of UCP’s Governing Council. In April, Stripe joined permanent members Google and Shopify, signaling strong industry backing for the standardization effort.
Structural Shifts and Grocery Enhancements
The latest specification introduces breaking changes designed to support broader industry adoption. For grocery commerce, the update adds robust location tools that allow agents to identify physical stores, retrieve addresses, operating hours, and map coordinates. A standardized format for store hours has been implemented, and the protocol now supports ordering by weight, addressing specific needs of produce and bulk goods.
Payment infrastructure has also undergone substantial revision. The specification now includes vendor-neutral 3D Secure 2 authentication, enabling more flexible payment schedules with deposits and installments. Orders can be split across various payment methods, increasing consumer choice. To improve clarity and reusability, the specification has been reorganized into three distinct sections: Shopping, Payment, and Common. Payment features are no longer confined to retail checkout but are positioned as relevant across all categories.
Breaking Changes for Adopters
Developers integrating UCP must address several schema modifications. Fulfillment schemas have been restructured, and buyer consent data has moved from fixed fields to a flexible map structure. Additionally, profile signing keys are now consolidated into a single JWK Set, streamlining key management.
UCP versions are identified by date rather than numerical labels, helping platforms align on compatible releases. Businesses retain the ability to support earlier versions while adopting the latest updates, ensuring backward compatibility during transition periods.
Expansion Beyond Retail
Governance changes earlier this summer paved the way for sector-specific development. In July, the Governing Council established a Food Technical Council with initial members including Block (Square), DoorDash, Google, Toast, and Uber Eats. On August 11, a Lodging Technical Council was formed, featuring Amadeus, Booking.com, Expedia, Google, Hilton, Marriott, and Trip.com.
According to the project roadmap, new specifications are being developed in collaboration with these industry leaders. Food-related developments will cover restaurant discovery, menu selection, and checkout processes involving tipping and delivery notes. Lodging efforts focus on hotel searches, room selection, and reservation management. Shared components like token binding are being redesigned to support these verticals effectively.
Strategic Implications
Companies that have already implemented UCP should review the breaking changes section to determine necessary schema updates based on their current feature usage. While the protocol aims to power checkout in AI Mode and Gemini across food, grocery, and travel sectors, the current release does not enable actual grocery ordering or hotel booking through any AI interface. These features represent foundational steps for future updates still in development.
No specific timeline has been announced for the release of food or lodging specifications. However, on the retail front, news from Google I/O revealed that UCP-powered checkout is expanding to Canada and Australia, with the U. K. planned for later implementation.
(Source: Search Engine Journal)