Google quietly updated the Universal Commerce Protocol last week. Three new capabilities. Most coverage missed what each one actually names.

Here’s what changed and the specific infrastructure problem each capability exposes.

Capability 1: Cart

Agents can now add multiple items to a shopping cart simultaneously from a single store.

Before this, agent-mediated UCP transactions were single-item. That’s a significant limitation: you can’t run a grocery replenishment workflow, an apparel outfit assembly, or a household essentials standing order on a single-item protocol. The basket is the fundamental unit of commerce for most retail categories.

The infrastructure gap is named: basket assembly requires that every item in that cart is queryable, comparable, and available in real time, not just the hero product. A brand whose product catalog is partially structured, or whose inventory data is accurate for in-demand SKUs but stale for everything else, will see agent-assembled carts fail or degrade at the edges. Cart capability makes catalog completeness a transaction-critical requirement, not a data quality nice-to-have.

Capability 2: Catalog

Agents can now retrieve real-time product details, variants, inventory, and pricing directly from a retailer’s catalog at the moment of query.

This is the live retrieval layer. Before this, agents were largely dependent on what they had trained on or last crawled. That data is often stale. New products, live pricing changes, promotional pricing, and real-time stock status weren’t reliably accessible at transaction time.

The infrastructure gap is named: there is a measurable difference between a brand that trains AI well and a brand that is queryable in real time. Training data determines whether agents know you exist. Catalog integration determines whether agents can verify you’re relevant right now. A brand with well-structured product data but no Catalog endpoint is discoverable but not transactable at the current state. That gap between discovery and real-time transaction readiness is what the Catalog capability makes concrete and testable.

Capability 3: Identity Linking

Shopper loyalty accounts can now be recognized across integrated platforms when transacting through agents.

This is the least-discussed of the three and arguably the most commercially significant near-term. The primary reason consumers delegate shopping tasks to agents is time savings and better outcomes. Loyalty redemption applying points, accessing member pricing, and earning towards status is a core part of what “better outcome” means for a large portion of the buying population. Without identity linking, agents either skip loyalty entirely or require the consumer to intervene at the point where loyalty would apply, which defeats the purpose of delegation.

The infrastructure gap is named: loyalty program architecture was not designed for agent-mediated transactions. Most loyalty systems authenticate against a human session a browser cookie, a logged-in account, or a physical card scan. Agents don’t have sessions in the human sense. They carry delegated authorization. Identity linking is the mechanism that maps authorization to a loyalty account. Brands whose loyalty infrastructure can’t support this will see agents either ignore their loyalty programs entirely or generate exceptions that force human intervention at the worst possible moment in the transaction flow.

The fourth thing: Merchant Center onboarding

Google also simplified UCP onboarding through Merchant Center. Less technically interesting but strategically significant.

Shopify gave its merchants a one-click path to agent discovery through Agentic Storefronts in January. Google is now making UCP integration simpler for Merchant Center retailers in March. Two on-ramps, advancing in parallel.

The brands outside both WooCommerce and Magento, headless architectures, and custom stacks, have neither. The gap is widening from two sides simultaneously, and it is widening faster than most teams are moving.

The three new UCP capabilities are not features. They are a diagnostic instrument.

Can your agent-assembled cart handle incomplete catalog coverage at the edges? Can your product data be queried in real time for variants, inventory, and pricing, not just crawled periodically? Can your loyalty infrastructure recognize a delegated agent identity and execute redemption without requiring human intervention?

Three questions. The answers determine whether the protocol advancement Google shipped last week translates into commercial advantage for your brand or commercial advantage for a competitor whose infrastructure is already positioned to use it.