Shopify Just Made UCP the Default. Is Your Store's Profile Actually Working?

Two weeks ago, Shopify shipped Spring '26 Editions. The headline was "Agentic commerce for every developer" - and they meant it. Every Shopify store now exposes UCP endpoints for Catalog, Cart, and Checkout as MCPs. AI agents in Copilot, ChatGPT, Perplexity, and Meta ads can discover, browse, and buy from your store through these endpoints.

This is not a niche developer feature you can ignore. It's the new default commerce layer.

But here's what the launch announcement didn't tell you: having UCP enabled is not the same as having a working UCP profile. And after a platform update this large, profiles break in ways that are invisible to humans.

What Shopify Editions actually changed

The Spring '26 Edition shipped three MCP-powered UCP capabilities:

• Catalog - AI agents can browse your product catalog, search, and filter. ChatGPT asks "show me waterproof hiking boots under $200" and your store answers.
• Cart - Agents build carts on behalf of users. Full lifecycle: add items, modify quantities, remove, view.
• Checkout - Complete purchase flow through the agent. Agent initiates, your store processes.

These endpoints are now part of the default Shopify install. You don't need a plugin. You don't need to configure anything. They're just there.

That's the good news. Here's the catch.

Three ways your UCP profile broke during the update

Platform updates change things. Even when they're supposed to be seamless. Here's what we're seeing in scans of Shopify stores after the Spring '26 rollout:

1. The manifest shape changed but your monitoring didn't notice.

Shopify added new capability declarations to the manifest. The JSON structure shifted. Some fields moved, some were renamed. If you validated your profile three months ago against the March 2026 spec, that green checkmark is now stale - the spec evolved, your manifest didn't update, and the mismatch creates parsing errors for agents running the latest SDK.

This is the most common failure we see: profiles that were valid in Q1 2026 that silently became invalid when the protocol advanced.

2. Catalog endpoints exist but return empty responses.

Your store has products. Hundreds of them. But the Catalog MCP endpoint returns zero results. Why? Because the catalog indexing happened during setup and hasn't refreshed. You added 50 products since then. They exist on your storefront. Human visitors see them. AI agents don't.

The endpoint is there. It responds with 200 OK. It looks healthy at a glance. But an agent asking "show me your winter collection" gets nothing back.

3. Payment handlers reference your old gateway configuration.

You switched payment processors last month. Your checkout works fine for humans. But the UCP payment handler declaration still references the old gateway's endpoint. The agent tries to initiate a payment against a handler that no longer exists on your store.

The human checkout path is fine. The agent checkout path is silently broken.

The protocol didn't stop moving

Shopify Editions isn't the only thing that changed. In March 2026, Google shipped a major UCP update that added Cart support, catalog access, and simplified onboarding. The protocol is in active development. Capabilities that were "draft" in January are now "stable." Validation rules changed. Transport requirements tightened.

If your last UCP check was more than a month ago, you're validating against a spec that no longer matches what agents actually expect.

What you should check today

Don't wait for a customer to tell you their AI assistant can't find your store. They won't. They'll just buy from a competitor whose profile works.

Here's what to verify:

1. Does your manifest serve correctly? Hit /.well-known/ucp on your domain. Does it return valid JSON with Content-Type: application/json? After caching plugin updates and CDN changes, this header gets wrong more often than you'd think.

2. Do your capability endpoints actually work? Having the declarations in the manifest is step one. The endpoints they point to need to return real data. Test your Catalog search. Test your Cart lifecycle (add, view, modify, remove). Test your Checkout flow end-to-end as an agent would.

3. Is your namespace/origin alignment still correct? CDN migrations, domain changes, and proxy updates can break this. The origin declared in your manifest must match what the agent actually reaches.

4. Are your signing keys current? Key rotation happens on a schedule. If your infrastructure rotated keys but the manifest wasn't updated, agent signature verification fails.

5. Did your platform's latest update change anything? After every Shopify update, WooCommerce release, or platform change, re-validate. The update that adds new features might also break existing ones.

One validation isn't enough anymore

The common pattern is: validate once, fix what's broken, assume you're done. That worked when UCP was an optional spec with slow adoption. It doesn't work now that UCP is the default commerce layer on Shopify and Google is actively routing AI shopping agents through it.

Your profile can pass today and fail tomorrow. Not because you changed anything - because the platform updated, the protocol evolved, or your infrastructure drifted. The agents don't file bug reports. They just move on.

Is your store actually discoverable by AI shopping agents? Validate your UCP profile now - free, no account needed. We run 4-level validation (structural, rules, network, and agent simulation) against the current spec to show you exactly what agents see when they browse your store.

Managing multiple stores? Start a free 7-day trial for monitoring and multi-domain dashboards. No credit card required.