Google UCP Explained: What E-Commerce Brands Need to Know About Universal Commerce Protocol

AI agents can now browse your catalog. UCP lets them buy from it too.

In January 2026, Google announced the Universal Commerce Protocol at NRF (the National Retail Federation conference). Co-developed with Shopify and other major commerce players, UCP is an open standard that lets AI agents do more than just find products. It lets them complete transactions.

If MCP is how agents read your catalog, UCP is how they buy from it. And it changes the economics of e-commerce in ways most brands haven't started thinking about.

What UCP Actually Does

UCP is a standardized protocol for AI agent commerce. It defines how agents interact with online stores to perform real transactions. Not just product discovery. Actual purchasing.

The protocol covers six core capabilities:

1. Product discovery. Agents can browse and search your catalog through a standardized interface.
2. Checkout. Agents can initiate and complete purchases on behalf of a customer, including payment processing.
3. Fulfillment. Shipping options, delivery estimates, and fulfillment status are all exposed.
4. Discounts and promotions. Agents can discover and apply available coupons, loyalty rewards, and promotions.
5. Order management. Order tracking, returns, and exchanges handled through the protocol.
6. Identity and loyalty. Customer accounts, loyalty programs, and preferences are recognized across agent interactions.

Think about what this means. A customer tells their AI agent: "Reorder my running shoes, but check if there's a better price anywhere." The agent queries multiple stores via UCP, compares prices, applies any available discounts, and places the order. No browser. No app. No checkout flow. Just a conversation.

The .well-known/ucp Endpoint

UCP works through a discovery mechanism that should feel familiar if you've worked with robots.txt or .well-known directories. Agents look for a UCP profile at:

https://yourstore.com/.well-known/ucp

This endpoint returns a JSON document describing your store's UCP capabilities. Which operations you support, what API endpoints to call, authentication requirements, and supported payment methods.

A basic UCP profile tells agents: "Here's what I can do, and here's how to do it." You don't need to support every capability on day one. Even a profile that only supports product discovery is better than no profile at all.

{
  "version": "1.0",
  "merchant": {
    "name": "Your Store Name",
    "url": "https://yourstore.com"
  },
  "capabilities": {
    "product_discovery": true,
    "checkout": false,
    "fulfillment": false,
    "discounts": false,
    "order_management": false,
    "identity": false
  },
  "endpoints": {
    "products": "https://yourstore.com/api/ucp/products",
    "product_detail": "https://yourstore.com/api/ucp/products/{id}"
  }
}

Who Built This and Why It Matters

UCP wasn't built by a startup. It was co-developed by Google and Shopify, with input from major retailers. That matters because adoption follows infrastructure. Shopify powers millions of stores. Google powers most product search. When they agree on a standard, the ecosystem follows.

This is not a "wait and see" protocol. It's backed by the two biggest forces in e-commerce infrastructure. The question is not whether UCP will matter. It's when your competitors will implement it.

How UCP Relates to MCP

People keep asking us this, so let's be clear:

• MCP (Model Context Protocol) is about data access. It lets agents read your product catalog, check prices, and verify inventory. Think of it as the "browsing" layer.
• UCP (Universal Commerce Protocol) is about transactions. It lets agents place orders, apply discounts, and manage fulfillment. Think of it as the "buying" layer.

They're complementary. An agent uses MCP to find the right product, then uses UCP to buy it. You'll eventually want both. But the implementation order matters.

Start with Schema.org (static structured data). Then add MCP (live data access). Then add UCP (transactions). Each layer builds on the one before it.

How to Check If Your Site Has UCP

The Pacestack scanner now checks for UCP compliance as part of our AI Agent Readiness scan. We're one of the first platforms to include UCP in our scoring.

The scanner checks:

• Whether a /.well-known/ucp endpoint exists
• Whether the UCP profile is valid JSON
• Which capabilities are declared
• Whether the declared endpoints are reachable

You can also check manually. Open your browser and go to https://yourstore.com/.well-known/ucp. If you get a 404, you don't have UCP yet. If you get a JSON response, you're ahead of almost everyone.

What to Do Right Now

Here's the honest assessment of where things stand and what makes sense for most brands:

1. If you have nothing: Start with Schema.org Product markup. It takes 30 minutes and gives AI agents basic structured data to work with. Read our Schema.org implementation guide for step-by-step instructions.
2. If you have Schema.org: Look into MCP. Give agents live access to your product data. Check our MCP guide for the breakdown.
3. If you have MCP: You're ahead of 99.9% of e-commerce brands. Now explore UCP. Start with a basic profile that declares product discovery capability. Full checkout support can come later.
4. If you're on Shopify: Watch for native UCP support. Given Shopify's role in developing the standard, it's likely they'll ship platform-level UCP integration. When they do, early adopters will have the advantage.

The brands that move on this now, while the infrastructure is still forming, will be the default choices when AI agents start handling a meaningful share of online purchases. That shift is already underway.

Don't wait for a perfect implementation. Deploy a basic UCP profile. Tell AI agents you exist and what you can do. Then iterate.