Full commerce journey · Google and Shopify · NRF January 2026
Universal Commerce Protocol
Enables AI agents to interact with merchant catalogs, shopping carts, and checkout flows through a single open standard. The full-journey protocol.
Abbreviation: UCPThe Universal Commerce Protocol is the full-journey protocol of the agentic commerce stack. Announced at NRF in January 2026 by Google and Shopify, UCP defines how AI agents discover products, interact with merchant catalogs, manage shopping carts, and complete checkout - all through structured REST endpoints without browser rendering.
UCP is not a discovery protocol alone. It covers the entire commerce journey from initial product query through payment execution. This distinguishes it from ACP, which focuses specifically on checkout and payment execution inside conversational AI surfaces. In a mature deployment, UCP handles the broader commerce journey while ACP handles transaction execution within ChatGPT and similar surfaces.
The protocol is built on OAuth 2.0 and REST APIs, integrating with existing commerce infrastructure without requiring merchants to replatform. Shopify Plus merchants receive native UCP support through Shopify Agentic Storefronts. Merchants on custom platforms must build UCP endpoints directly or use an aggregation layer.
As of April 2026, UCP supports AI-mode exclusive discounts, branded Business Agents in Google Search, and multi-item cart management. The Shoptalk Spring 2026 announcements expanded UCP with multi-item carts, loyalty programme linking, Google Pay integration, and the Gap partnership as the first major non-Shopify enterprise deployment.
How does an agent discover, evaluate, and purchase from a merchant catalog?
What UCP provides
Standardised product discovery: agents query merchant catalogs via structured REST endpoints
Cart and checkout sessions: agents initiate, modify, and complete purchases without browser rendering
Payment handler integration: supports Shop Pay, Google Pay, and configurable payment options
AI-mode exclusive discounts and branded Business Agents in Google Search
Built on OAuth 2.0 and REST APIs; integrates with existing commerce infrastructure without replatforming
Before you begin
The following must be in place before starting UCP integration. Missing prerequisites are the most common cause of delayed or failed protocol deployments.
Commerce platform with REST API capability (Shopify Plus native; custom platforms require endpoint build)
OAuth 2.0 authentication infrastructure
Structured product catalog with complete JSON-LD schema markup
Real-time inventory API with sub-second response time
Google Merchant Center account in good standing
What goes wrong
These are the failure modes the AXD Institute has observed across early UCP implementations. Each includes the root cause and the recommended mitigation.
Schema incompleteness
products with missing required fields are not discoverable by agents. Run the schema validator on a random 10% sample of your catalog before sandbox testing.
Inventory latency
UCP agents check real-time availability before completing checkout. APIs with response times above 500ms cause checkout abandonment. Cache inventory data with a maximum 60-second TTL.
Authentication timeout
OAuth token refresh must be handled gracefully in agent checkout sessions. Sessions that expire mid-checkout result in abandoned transactions without user notification.
Category taxonomy mismatch
products categorised outside Google's taxonomy are excluded from category-level agent queries. Map your internal taxonomy to Google's before registration.
Step-by-step walkthrough
A sequenced implementation guide for UCP. Each step includes the action, the rationale, and the validation criteria for completion.
Product data audit and schema completion
Before registering for UCP, audit your product catalog against UCP's data requirements. Products with incomplete data will not appear in agent recommendations regardless of technical integration quality.
- •Run the AXD Data Maturity Audit (/tools/data-audit) to score your current catalog completeness.
- •Implement or remediate JSON-LD schema markup across your product catalog. Target 90%+ required field completeness.
- •Map your internal product taxonomy to Google's product category taxonomy. Products categorised outside Google's taxonomy are excluded from category-level agent queries.
- •Verify real-time inventory API response times are below 500ms. Cache inventory data with a maximum 60-second TTL.
- •Validation: randomly sample 10% of your catalog and verify all required UCP fields are present and correctly formatted.
UCP sandbox registration and OAuth configuration
Submit your UCP registration through Google Merchant Center. Begin sandbox integration in parallel with registration review.
- •Ensure your Google Merchant Center account is in good standing with no active policy violations.
- •Configure OAuth 2.0 authentication infrastructure for agent session management.
- •Implement token refresh handling that works gracefully during active checkout sessions. Sessions that expire mid-checkout result in abandoned transactions without user notification.
- •Set up sandbox environment that mirrors your production catalog and inventory systems.
Build discovery, cart, and checkout endpoints
Implement the three core UCP endpoint categories: product discovery, cart management, and checkout session handling.
- •Product discovery endpoints: agents query your catalog via structured REST endpoints. Implement filtering, sorting, and pagination that matches UCP specification requirements.
- •Cart session endpoints: agents initiate, modify, and complete shopping carts. Implement idempotent cart operations to handle agent retry behaviour.
- •Checkout session endpoints: support Shop Pay, Google Pay, and your configured payment options. Implement the full checkout flow including shipping calculation, tax computation, and payment authorisation.
- •All endpoints must return structured JSON responses conforming to UCP schema definitions.
Complete UCP sandbox test scenarios
UCP requires completion of five mandatory sandbox test scenarios before production activation. Each scenario validates a different aspect of the integration.
- •Scenario 1: Product discovery - agent queries return correct, complete product data with all required fields.
- •Scenario 2: Cart creation and modification - agent can add items, update quantities, remove items, and apply discount codes.
- •Scenario 3: Checkout completion - full checkout flow from cart to payment authorisation to order confirmation.
- •Scenario 4: Error handling - graceful handling of out-of-stock items, price changes during session, and payment failures.
- •Scenario 5: Inventory accuracy - real-time inventory checks during checkout match actual availability.
Production activation and measurement
Activate UCP in production and implement measurement infrastructure from Day 1.
- •Activate UCP in production through Google Merchant Center.
- •Implement AIR (Assistant Inclusion Rate) measurement for UCP-attributed traffic immediately. Establish your discovery baseline.
- •Implement AACR (Agent-Assisted Conversion Rate) tracking for UCP checkout sessions.
- •Set up server-side event collection with UCP-specific UTM parameters for cross-surface attribution.
- •Schedule a 30-day review to assess AIR improvement from pre-integration baseline and identify optimisation priorities.
Related metrics, frameworks, and essays
AXD Metrics Standard KPIs
AXD Practice Frameworks