UCP 1.2 Release: What Changed and Why It Matters for Agent Commerce

The UCP 1.2 specification release addresses feedback from enterprise deployments that identified gaps in multi-agent coordination, spend control granularity, and fulfillment event coverage. This post covers the changes that affect production deployments and what implementation work they require. See also: How to Identify AI Agent Traffic in Google Analytics 4. See also: 2026 UCP Compliance and Risk Checklist for Merchants. See also: UCP vs ACP vs MCP. For related reading, see WebMCP Is Here. For related reading, see The Invisible Middlemen Getting Disrupted First by Agentic Commerce. For related reading, see The Trust Problem Is Not Technical. It Is Institutional..

Multi-Agent Coordination: The Authorization Delegation Model

One of the most significant changes in 1.2 is formal support for authorization delegation. In complex enterprise agent deployments, a primary orchestrator agent may spin up sub-agents to handle specific tasks — one agent for price discovery, one for checkout, one for post-purchase tracking. Under UCP 1.0 and 1.1, each of these sub-agents required separate authorization scopes, creating management overhead. UCP 1.2 introduces a delegation model: the primary agent can delegate a subset of its authorization scope to a sub-agent without requiring human re-authorization for each delegation, as long as the delegated scope is strictly narrower than the primary scope.

Spend Control Granularity Improvements

UCP 1.1 supported spend limits at the agent level and category level. Deployments running complex procurement workflows needed finer granularity — per-merchant limits, per-order limits, and time-bounded limits (daily, weekly, monthly). UCP 1.2 adds all three, giving finance teams the precise control they need to deploy agents across procurement workflows without creating open-ended spending exposure.

New Fulfillment Event Types

Based on merchant feedback, UCP 1.2 adds three new fulfillment event types to the webhook schema: FULFILLMENT_DELAYED (with estimated new delivery date), ITEM_SUBSTITUTED (when a merchant substitutes an equivalent item due to availability), and PARTIAL_SHIPMENT_CREATED (for orders split across multiple shipments). These events were previously handled as custom extensions by merchants that needed them; standardizing them enables consistent handling across all UCP-certified agents.

Migration Path from 1.1 to 1.2

UCP 1.1 implementations are backward compatible with 1.2 in all cases. The new features require explicit opt-in at the merchant and agent configuration level. Merchants that do not need delegation or the new spend control granularity can continue using their 1.1 configuration without any changes. The new fulfillment event types will simply not be emitted by 1.1-configured merchants.

Frequently Asked Questions

Is there a deadline for migrating to UCP 1.2?

There is no forced migration deadline. UCP maintains N-1 backward compatibility — 1.1 integrations will continue to work with 1.2-certified counterparts indefinitely. However, enterprise features like authorization delegation require both sides of the transaction to be on 1.2.

Frequently Asked Questions