Shopify UCP: Catalog MCP Audit Guide

What Is UCP?

UCP (Universal Commerce Protocol) is an open protocol that standardizes how an AI agent discovers a merchant catalog, builds a cart, and triggers a purchase. The specification is published on ucp.dev and on GitHub under the Apache 2.0 license.

Update as of July 23, 2026: three things have changed since the January 2026 launch.

1. The spec has a dated current version: 2026-04-08, released on April 9, 2026. It is the third and latest release to date.
2. On Shopify, there is nothing left to enable. Since the Spring ‘26 Edition of June 17, 2026, merchants are UCP-enabled by default and pre-approval has been removed (Shopify, June 17, 2026).
3. On Google’s side, UCP-powered checkout is still limited to three markets: Australia, Canada and the United States (Google Merchant Center Help).

For a Shopify store, the thing to audit is therefore not a switch to flip, but a surface to verify: the Storefront Catalog MCP exposed at https://{storedomain}/api/ucp/mcp. This endpoint implements the UCP Catalog capability through MCP and exposes the canonical tools search_catalog, lookup_catalog and get_product.

A store is not “UCP ready” just because an endpoint exists or a tool name appears. The audit must verify that the endpoint accepts a UCP agent profile, that the tools are current, and that a read-only search_catalog call returns usable products: title, URL, price, availability, variants, media, and data consistent with the page and JSON-LD.

In Verity, UCP is treated as evidence of agentic catalog discovery, not as a guarantee of checkout, returns, or presence in Google’s AI surfaces.

Where the Specification Stands

The specification has had three releases, and none after July 23, 2026 (GitHub releases):

Version 2026-04-08 adds five things:

• The cart capability: an agent can assemble a cart at the merchant.
• Catalog search and lookup: product discovery and retrieval of a specific record.
• First-class errors: failures are typed in the protocol instead of being guessed by the agent.
• Identity linking through OAuth 2.0: connecting a shopper to an existing merchant account (loyalty, history).
• Multi-parent schema resolution: an object can inherit from several parent schemas.

The /.well-known/ucp manifest declares the supported version, which is 2026-04-08 for the current release, with independent versioning per service and per capability (ucp.dev overview). In other words, a merchant can support one capability at one version and another capability at a different version. That is exactly why behavioral auditing is required: the presence of a manifest does not tell you what actually works.

Why UCP Matters for E-Commerce

Before UCP

Each AI platform built its own merchant integrations:

• Google Shopping had its proprietary product feeds
• ChatGPT had its ACP with Stripe
• Perplexity had its custom PayPal integrations
• Each new AI engine had to negotiate individual agreements with each merchant

Result: fragmentation. A merchant wanting visibility across all AI platforms had to implement 4 or 5 different integrations. Only large retailers had the resources to do so.

After UCP

One protocol, potentially all agents. The merchant exposes the surface once, and any compliant AI agent can query the catalog. This is the shift from bilateral to multilateral, much like the web moving from proprietary networks (AOL, CompuServe) to the open HTTP protocol.

Worth stating plainly: that promise is structural, not yet measured. No official adoption figures have been published (number of transacting merchants, volume, GMV). The only official number available remains “more than 20 partners” at the January 2026 announcement. Be skeptical of content quoting precise volumes.

UCP Capabilities

UCP structures merchant-agent interactions around distinct capabilities. Each one is optional: a merchant can expose only some of them, and each carries its own version.

Checkout (Payment)

The Checkout capability allows AI agents to complete a purchase on behalf of the user. On Google surfaces, payment runs through Google Pay and the merchant remains merchant of record.

Concrete example: a user asks Google AI Mode “order me 2 HP 305 black ink cartridges.” The agent queries eligible UCP merchants, compares prices, and offers checkout inside the Google interface. Reminder: that journey is only open in Australia, Canada and the United States.

Fulfillment (Shipping and Tracking)

The Fulfillment capability allows the agent to communicate delivery times, shipping options (standard, express, pickup point), and provide post-purchase order tracking.

Concrete example: after an order, the user asks Gemini “where is my order from [Store]?” The agent queries the merchant’s UCP surface and returns delivery status, tracking number, and estimated delivery date.

Discount (Promotions and Codes)

The Discount capability allows the agent to discover and apply promotions, promo codes, welcome offers, or loyalty discounts. The merchant controls which promotions are exposed to agents.

Returns (Refunds and Exchanges)

The Returns capability allows the agent to facilitate product returns: initiate a request, generate a return label, track refund status.

Cart, Catalog and Identity Linking (since version 2026-04-08)

• Cart: the agent assembles a cart at the merchant instead of chaining single-item purchases.
• Catalog: product search and lookup, with variants, pricing and availability pulled directly from the merchant. This is the capability Shopify implements through the Storefront Catalog MCP.
• Identity linking: connecting a shopper to their merchant account through OAuth 2.0, which opens the door to loyalty benefits inside an AI conversation.

Shopify: UCP Enabled by Default Since June 17, 2026

This is the most actionable change of the past six months. With the Spring ‘26 Edition of June 17, 2026, Shopify announced that merchants are “UCP-enabled by default”: any surface built with UCP inherits the merchant’s checkout rules, discounts and customizations (Shopify, June 17, 2026).

Three practical consequences:

1. Merchants with eligible products are in Catalog by default. There is no admin toggle to “join” the agentic catalog.
2. Pre-approval for the agentic commerce layer has been removed. Catalog access now only requires an API key.
3. Your merchant rules follow. Discounts, customizations and checkout rules configured in your store apply to agentic surfaces, with no parallel configuration to maintain.

The reference developer hub is shopify.dev/docs/agents.

What this does not solve: data quality. Being exposed by default does not guarantee being picked. If your record returns a price that conflicts with the page, a missing variant or false availability, the agent drops you at comparison time. See our read of the edition in Shopify Spring ‘26: AI news for DTC brands.

How to Verify Your UCP Surface on Shopify

Verification takes 5 steps. Estimated time: 20 to 45 minutes.

Step 1: Verify the Shopify Catalog Surface

1. Test https://your-store.com/api/ucp/mcp with an MCP tools/list request.
2. Include the meta.ucp-agent.profile field expected by Shopify.
3. Verify that search_catalog, lookup_catalog, and get_product are listed.

Step 2: Test Catalog Behavior

1. Run a read-only tools/call on search_catalog.
2. Verify that the response contains at least one usable product.
3. Check critical fields: title, URL, price, availability, variants, media.

Step 3: Verify Technical Prerequisites

• Unique SKUs: every product and variant has a unique SKU. Agents use SKUs as identifiers. Check in Admin → Products → Inventory.
• Real-time inventory: inventory tracking is active and synchronized. An out-of-stock product must be immediately flagged as OutOfStock in schema.org.
• Standardized attributes: size, color, material, weight. Use Shopify’s standardized attributes (not freeform metafields) so agents can filter effectively.

Step 4: Verify Policies

UCP exposes your policies to agents. Verify that the following pages exist and are complete:

• Shipping policy: delivery times, costs, geographic zones, options (standard, express, pickup point)
• Return policy: eligibility window (14 days, 30 days), conditions, return process, who pays return shipping
• Terms and conditions: mention of AI agent-assisted purchases if required by local law

If you are targeting eligibility for Google checkout, these policies must also be declared in Merchant Center (see below).

Step 5: Read the Manifest, Then Cross-Check Reality

Test https://your-store.com/api/ucp/mcp first, then look at the /.well-known/ucp manifest if it is exposed. The manifest tells you what is declared:

• version: the supported specification version, which is 2026-04-08 for the current release
• capabilities: active capabilities, each with its own version
• the endpoints attached to each service

The manifest does not replace the behavioral test. Then confirm:

• tools/list: canonical tools exposed
• search_catalog: usable product response
• consistency: price, stock, variants and URL aligned with the page and JSON-LD

If /api/ucp/mcp returns a 404, the surface is not exposed on that store. Check the Shopify Catalog eligibility conditions (plan, password-protected store, eligible products) in the Shopify developer hub.

UCP and Google Surfaces

Google AI Mode and Gemini are the main consumers of UCP. When a user asks a commercial question (“best robot vacuum for pet hair”), Google:

1. Queries the Shopping Graph to identify relevant products
2. Queries compatible commerce surfaces (Shopping Graph, UCP manifests, catalog endpoints) for real-time data: prices, stock, shipping
3. Generates a conversational response with comparison, reviews and a purchase link
4. May offer in-agent checkout depending on country, merchant, channel and journey eligibility

Point 4 is the most misread: appearing in an AI answer and being eligible for checkout are two different things. A product can be cited, compared and clicked in AI Mode without agentic checkout being open for that merchant or that market.

Universal Cart: Google’s Consumer Surface

Announced on May 19, 2026, Universal Cart is a persistent, Gemini-powered cart spanning Search, the Gemini app, YouTube and Gmail (blog.google, May 19, 2026).

What it brings to the shopper:

• price drop tracking and price history
• restock alerts
• compatibility checking between products
• a cart that follows the user from one Google surface to another

For checkout, Universal Cart relies on UCP: payment runs through Google Pay and the merchant remains merchant of record.

Do not confuse Universal Cart with the cart capability. The cart capability is a building block of the specification, available to any compliant agent. Universal Cart is a consumer surface Google built on top of UCP.

Status as of July 23, 2026: Universal Cart is rolling out in the United States on Search and the Gemini app, with YouTube and Gmail announced to follow. Google has not confirmed general availability. Launch partners cited are Nike, Sephora, Target, Ulta Beauty, Walmart and Wayfair, plus Shopify merchants such as Fenty and Steve Madden.

UCP Checkout Eligibility: Markets and Requirements

This is the part most often distorted in content about the protocol. Here is the documented state.

Covered markets

UCP-powered checkout covers only Australia, Canada and the United States, for participating merchants and partners (Google Merchant Center Help). The United Kingdom was announced as a later step, with no date (blog.google, May 20, 2026).

Continental Europe, including France, is not eligible. One confusion to clear up: Merchant Center Checkout links, extended to France in July 2026, are a classic redirect to the merchant’s cart. That is not agentic checkout and it has nothing to do with UCP.

Merchant requirements on Google’s side

For a geographically eligible merchant, the documented list is as follows (Google for Developers and Merchant Center Help):

The onboarding path

On March 19, 2026, Google announced simplified onboarding in Merchant Center, rolling out “in the coming months”, with access still selective (blog.google, March 19, 2026). The described path has three steps:

1. Technical implementation following the developer guide
2. An expression of interest form
3. If selected, Merchant Center onboarding with sandbox validation

Simplified onboarding therefore does not mean open access.

What This Means for Merchants Outside the Three Markets

If you sell from a market that is not Australia, Canada or the United States, agentic checkout is not open to you today, and no date has been announced for continental Europe. Even the United Kingdom is announced without a timeline.

What remains actionable anyway:

• Your catalog surface exists independently of checkout eligibility. Your store’s Storefront Catalog MCP is a technical surface you can verify from anywhere, and it decides whether an agent understands your offer at all.
• Product truth requirements are identical across UCP, ACP and answer engines: prices consistent with local tax display rules, delivery times compliant with local consumer law, a structured and readable return window, current terms and conditions.
• Consistency work cannot be improvised at the last minute. The day eligibility opens, the data already in place decides, not an activation step.

The UCP Ecosystem

• Klarna joined UCP on February 2, 2026 (Klarna, February 2, 2026).
• Commerce Inc, Salesforce and Stripe are cited by Google as implementing UCP (blog.google, March 19, 2026).
• Buy now, pay later reaches UCP surfaces: Affirm and Klarna are offered inside Google Pay.
• The protocol moves beyond physical goods: UCP extends to hotel booking and local food delivery (blog.google, May 20, 2026).

What does not exist, and what you should stop looking for: an official adoption figure. No merchant count transacting through agents, no volume, no GMV. Shopify’s “millions of merchants” describes platform capacity, not agentic transaction volume.

How Verity Score Audits Your UCP

Verity Score automatically detects and analyzes your UCP configuration.

Automatic Detection

The audit starts with public Shopify and agentic surfaces. For UCP/MCP, Verity Score:

1. Tests /api/ucp/mcp and identifies exposed tools
2. Verifies Shopify canonical tools: search_catalog, lookup_catalog, get_product
3. Tests catalog behavior with a read-only search_catalog call
4. Cross-references with schema.org: do prices, stock levels, variants, and attributes match the page?
5. Verifies policies: are return and shipping policy URLs valid and citable?

UCP Score out of 100

Recommendations

For each detected gap, Verity Score provides:

• A precise description of the issue
• The path in Shopify admin to fix it
• The impact on your visibility in AI surfaces
• The correction priority (critical, high, medium)

UCP vs ACP: Where Both Protocols Stand

The ACP Situation, Without Shortcuts

According to CNBC (March 20, 2026), OpenAI ended Instant Checkout, the native payment flow inside ChatGPT: “Instant Checkout is moving to Apps, where purchases can happen more seamlessly”. Purchases now complete on the merchant site. This is credible press reporting, not an official statement, and it should be attributed as such.

However, the ACP protocol itself was not abandoned. Its stable 2026-04-17 specification shipped after that decision, the repository was still pushed to on July 18, 2026, and it is not archived. Reading “end of Instant Checkout” as “end of ACP” is a widespread mistake.

What Both Protocols Share

• Schema.org Product as the structured data foundation
• Real-time inventory
• Structured return policy
• Cross-source price consistency
• Verifiable trust signals (reviews, certifications)

The technical work is therefore largely shared. A store that exposes its catalog and policies cleanly serves both ecosystems, and answer engines at the same time.

Recommended Strategy

1. Implement the shared fundamentals: complete schema.org, consistent pricing, real-time inventory, structured policies
2. Verify your Shopify Catalog surface (it is on by default, but not necessarily correct)
3. Verify your data on the ACP and ChatGPT Shopping side
4. Run a Verity Score audit to validate both surfaces
5. Fix identified gaps in order of impact

Related articles

• GEO Audit: Complete Guide - The 9 factors that determine your AI visibility
• Shopify Spring ‘26: AI news for DTC brands - What the June 17, 2026 edition changes for brands
• Sell on ChatGPT - Agentic Storefronts and Shopify optimization for ChatGPT Shopping
• ACP: Agentic Commerce Protocol - The OpenAI + Stripe protocol for agentic commerce
• Perplexity Shopping - Merchant guide and readiness score
• Schema.org for Shopify - Technical guide to Product and Offer structured data
• llms.txt for Shopify - A useful AI content index, not the primary signal
• GEO Readiness - Assess your Shopify store’s AI maturity

Agentic commerce advances market by market and surface by surface, not all at once. The right question is no longer “should I enable UCP?” but “does my data hold up when an agent reads it?”

Ready to check your store? Run a free GEO audit →