The Universal Commerce Protocol (UCP), published at ucp.dev, is an open standard that gives AI agents one common language for finding a product and buying it, plus everything that happens after the sale, across any participating retailer. If you sell online and you're not integrated, Google's new Universal Cart (along with AI Mode and Gemini agents) will route purchases to merchants that are.
This is already shipping: UCP went live on January 11, 2026, co-developed with Shopify, Etsy, Wayfair, Target, and Walmart, and endorsed by the major payment networks (Visa, Mastercard, Stripe) and big-box retailers (Best Buy, Home Depot, Macy's). Per Google's announcement, UCP creates "common language" across the entire shopping journey for agents and systems. It is the commerce equivalent of HTTPS becoming default: a standard that started optional and quickly became the cost of admission.
> UCP works alongside three companion standards Google built for agents: one for agents talking to each other, one for safely authorizing payments, and one for exposing tools. UCP is the commerce-specific one.
What UCP actually standardizes
The protocol covers three phases. In discovery, an agent finds your products. At checkout, it completes the purchase. After the sale, the agent handles order tracking and returns, plus whatever support the buyer needs next.
The standard fields the spec requires from every product listing:
- Price: current, with currency and any quantity-tiered breaks
- Availability: stock status, lead time, and shipping windows
- Return policy: window, restocking fees, and exclusions
- Shipping: methods, costs, estimated arrival, restrictions
- Product identifiers: GTIN, MPN, SKU, the barcode and catalog numbers that uniquely identify each item, mapped consistently across catalog and feed
- Conversational attributes: FAQs, plus the accessories that work with the item and the products a shopper might buy instead
That last one is new. Merchant Center is rolling out conversational attribute fields built specifically for agent discovery in AI Mode and the Gemini app (and in the Business Agent chatbot). These go beyond the keyword-matching world of the traditional product feed.
How UCP relates to Product schema
Short answer: UCP requires schema. Long answer: UCP is what schema becomes when it has to support transactions, not just rich results.
Product schema (schema.org/Product with the Offer extension) tells search engines about your products in a structured way. UCP requires the same field-level consistency, then layers on transactional commitments. Your stated availability has to be accurate enough that an agent can act on it without checking back. Your shipping estimate has to be honored. Your return policy has to be machine-readable in the same way it's human-readable.
In practice, here's what this means for a small ecommerce site: every Product schema field you ship now has to be true at the moment an agent reads it, because the agent might purchase on the same request. Stale inventory data was a UX nuisance for human shoppers. For agent shoppers, it's a failed transaction and a refund cycle.
I cover the schema fundamentals in the structured data spoke. For UCP specifically, the bar is one notch higher: your Product schema has to feed from the same source of truth as your live inventory system, or your agent-mediated orders will fail at fulfillment.
The Universal Cart experience
Per Google's May 2026 announcement, Universal Cart aggregates items across merchants into a single cross-merchant cart that lives inside Google Search, the Gemini app, and (coming soon) YouTube and Gmail. Launch partners include Nike, Sephora, Target, Ulta, Walmart, Wayfair, and Shopify merchants who opt in.
The user experience: a shopper says to Gemini, "I need a wedding-guest dress under $200 and shoes to match." The cart aggregates options across all UCP-integrated merchants, runs price monitoring and deal detection in the background, validates compatibility (the shoes go with the dress), and checks out through Google Pay. The shopper never touches a merchant's website, the merchants keep seller-of-record status, and the transaction settles cleanly.
Merchants outside the cart never enter that comparison at all.
For the boutique retail and small ecommerce world we work with at Space & Story (see the boutique retail playbook), UCP integration is no longer something to evaluate in 2027. It's a 2026 question with a roughly six-month window before the small-merchant onboarding path is crowded.
Agent Payments Protocol: the trust layer
The piece that makes any of this safe is the Agent Payments Protocol (AP2), the payment-authorization standard mentioned earlier. Per Google Cloud's AP2 announcement, AP2 is "privacy-preserving" and uses "tamper-proof digital mandates." The user sets a spend limit and rules, the agent gets a cryptographically signed mandate, and the merchant validates that mandate before processing.
Agentic commerce only works if the user trusts the agent to spend their money, and AP2 is the mechanism for that trust. It lets the user say "spend up to $200 on dress, $100 on shoes, must ship within seven days." The agent transacts inside that envelope. The merchant validates the envelope. Nothing exceeds the user's stated limit.
Smaller merchants don't have to implement AP2 themselves. Shopify and the major payment processors handle it. But you do need to know it exists, because the friction-free transactions you're going to start seeing are running on this rail.
Agentic calling for local service businesses
The booking-adjacent piece worth flagging: per Google's documentation, agentic calling lets Google place phone calls to local businesses on a user's behalf for product availability and pricing questions. It's currently U.S.-only and scoped to toys, health/beauty, and electronics, with restaurants next in line.
What this means for a non-ecommerce local business (a contractor, a restaurant, an HVAC company) is that your Business Profile data is now an API. Phone number, hours, category, services offered: these are not just discovery signals. They are the inputs to an automated call that may close the deal without a single page view. The knock-on effects for analytics and attribution and how you handle inbound leads deserve their own post, but the short version is: keep your Business Profile clean, and answer your phone.
What we recommend for small ecommerce
Five priorities, roughly in order.
Start by auditing your Product schema against the UCP field requirements. Every product needs price, availability, return policy, shipping, identifiers, and at least one round of conversational attributes (FAQs, accessories, substitutes). If you're on Shopify, much of this is wired by default once you opt into the UCP partnership. If you're on WooCommerce, BigCommerce, or a custom stack, the work is on you.
Your Merchant Center feed comes second: confirm it is accurate and current, and that it picks up the new conversational attribute fields as they roll out. The traditional XML/CSV feed is necessary but no longer sufficient on its own.
Third, make sure your stated availability matches your real inventory, because the single fastest way to lose UCP-mediated orders is to fail at fulfillment when your schema promised something your warehouse couldn't deliver. Connect your inventory system to whatever produces your structured data.
If you're a U.S. retailer, activate the Business Agent in Merchant Center. This is the branded chatbot that surfaces on Search and answers product questions in your brand voice. It's free, it's available now, and competitors who turn it on get the agent traffic.
Finally, treat the next 12 months as the open-onboarding window. Adoption will follow the same path HTTPS did: optional at first, then non-optional. Merchants who integrate now get clean traffic, while the ones who wait get rate-limited onboarding queues.
What this doesn't replace
UCP doesn't replace your website, your traditional SEO, your product photography, or your brand voice. It adds a transactional layer for agent-mediated purchases on top of the consumer-facing experience you already run, and both layers have to work.
It also doesn't make smaller merchants compete on equal footing with Amazon overnight. The advantage UCP gives smaller, specialty retailers (boutiques, niche brands, regional sellers) is that an agent looking for "handmade ceramic dinnerware from a small studio" can now find and transact with you as easily as with a giant. That advantage is real, but you have to ship the integration.
Sources
- Universal Commerce Protocol announcement, Vidhya Srinivasan, Google Ads & Commerce
- UCP specification, UCP open standard
- Introducing the Universal Cart, Google Shopping
- Agent Payments Protocol (AP2), Google Cloud
- Agentic calling for local businesses, Google Shopping
- New ways to plan travel with AI in Search, Julie Farago, Google Search