Google's April UCP Update: Multi-Item Carts, Live Catalog, and Loyalty Are Now in the Spec
Google expanded the Universal Commerce Protocol this month with three major additions: multi-item cart support, real-time catalog access, and loyalty/identity linking. Here is what changed and what it means for developers and merchants.
What Google Just Shipped
Two weeks ago, Google quietly dropped a significant UCP expansion. The official post went up on the Google Shopping blog and the engineering announcement landed in the UCP GitHub org. If you blinked, you missed it.
Three new capabilities joined the spec:
Multi-item cart support. The original UCP checkout flow handled single-item transactions. The April update adds a cart primitive, letting agents build multi-item orders in a single checkout session. For shopping agents trying to bundle items from the same merchant, this is a fundamental unlock. You no longer have to chain single-item purchases together and hope the merchant applies the right combined shipping.
Real-time catalog access. Merchants with UCP enabled can now expose live inventory and pricing through the Catalog capability. When an agent queries a product, it can get current variants, stock levels, and pricing in real time, not cached data from Google's crawl. For high-velocity products where inventory changes by the hour, this is the difference between a reliable purchase and a failed checkout.
Identity linking and loyalty benefits. This one is underrated. UCP now supports Identity Linking, which lets agents surface the same member benefits a shopper would get on the merchant's own site when they're logged in. Free shipping thresholds, loyalty pricing, rewards redemption. The shopper's relationship with the merchant travels with them across platforms.
Why This Matters for Developers
The multi-item cart is the most developer-relevant change if you're building shopping agents. Previously, building an agent that could buy multiple items from a single merchant meant:
- Identify all desired items
- Check if UCP single-item checkout works for each
- Initiate separate checkout flows per item
- Hope the merchant's backend handles them as related orders
With the cart primitive, you can do this properly. One cart session, one checkout, one order confirmation. The spec now includes endpoints for adding items to a cart, modifying quantities, applying identity tokens to get member pricing, and completing checkout in a single flow.
The Catalog capability is important for agent reliability. Cold-start agents fetching product data from Google's index could encounter stale inventory or pricing. Merchants who implement the Catalog endpoint let agents request live data on demand. The request/response format is in the updated spec.
What the Identity Linking Update Actually Does
Loyalty programs are complicated. A shopper logged into their Target account gets different pricing than a guest. Their REDcard membership changes the checkout total. Their rewards balance can offset the purchase.
UCP's Identity Linking lets agents carry that context into UCP-powered checkout. The shopper pre-authorizes their identity through a UCP-compliant provider. The agent presents that authorization during checkout. The merchant's system looks up the shopper's account, applies the relevant benefits, and returns the updated order total.
This is not magic. It requires the merchant to implement Identity Linking on their end. But for merchants who do implement it, agents become first-class shoppers rather than anonymous guests.
Microsoft is doing something adjacent here. Their announcement with Target last week covers UCP-based loyalty integration specifically, using Target Circle member benefits in agent-initiated checkout. Real implementation, major retailer, production deployment.
Updated Entries in the Directory
We've updated the UCPList directory to reflect these new capabilities:
- Google Shopping now shows multi-item cart and catalog capability support
- Target now shows identity linking / loyalty support (pending full verification)
- Payment handlers that have indicated Catalog capability support have been updated
If you're building against the updated spec and notice anything wrong in the directory, open a PR to Full-Vibe/ucp-ecosystem or use the submit page.
The Broader Pattern
Look at UCP's trajectory this year. The protocol launched in January with basic checkout and identity primitives. Q1 added payment token exchange improvements and a merchant onboarding flow in Merchant Center. Now Q2 starts with multi-item cart, live catalog, and loyalty.
This is a protocol growing up fast. The cadence of additions suggests Google has a roadmap here that's moving quickly. Commerce Inc, Salesforce, and Stripe have all announced implementation plans. Shopify's native support already gives UCP access to a massive merchant long tail.
The directory is growing with it. If you want to track what's live, what's announced, and what's in the ecosystem, start here.
Read next
A data-driven look at the Universal Commerce Protocol ecosystem in March 2026: 81 listings, 51 live endpoints, and what the adoption curve looks like.
An overview of the developer tools, agent frameworks, and automation platforms that have emerged around the Universal Commerce Protocol in 2026. What exists, what is coming, and what to build on.
Platform announcements, payment handler maturity, and agent framework integrations. Here is where the UCP ecosystem stands at mid-Q2 2026.