What is Universal Commerce Protcol?
Google’s Universal Commerce Protocol, announced at NRF 2026 in January and co-developed with Shopify, Etsy, Wayfair, Target, and Walmart, is an open standard designed to enable AI agents to complete purchases on behalf of consumers—without ever visiting a retailer’s website.
The protocol allows checkout, identity linking, and order management to happen entirely within AI surfaces like Google’s AI Mode in Search and Gemini. UCP is built on REST and JSON-RPC with native support for Model Context Protocol (MCP), Agent2Agent (A2A), and Agent Payments Protocol (AP2). It has been endorsed by over 20 major players including Stripe, PayPal, Visa, Mastercard, and American Express.
Merchants remain the Merchant of Record and retain ownership of customer data and relationships—at least on paper. But the transaction experience shifts entirely to the AI interface.
The Protocol vs. The Implementation: A Critical Distinction
Here’s what most coverage misses: UCP itself is an open, generic protocol. In theory, any platform could implement it. But the practical reality is that Google’s specific implementation routes through Google Merchant Center—the same infrastructure that already controls product feeds for Google Shopping.
This matters enormously.
When you implement UCP through Google Merchant Center, you’re not just adopting an open standard—you’re deepening your dependency on Google’s data infrastructure. Your product data, pricing logic, inventory signals, and promotional strategies flow through Google’s systems. Yes, you remain the “Merchant of Record” for legal and payment purposes. But being Merchant of Record is not the same as owning the customer relationship.
Merchant of Record means: You process the payment, handle fulfillment, and are liable for the transaction.
Customer relationship ownership means: You control the discovery experience, build brand affinity, capture behavioral data, and have direct communication channels with the buyer.
UCP, as implemented through Google Merchant Center, preserves the first while systematically eroding the second. The customer never visits your site. They don’t see your brand experience. They don’t enter your email nurture flows. They don’t browse your related products. Google mediates the entire interaction, and you fulfill the order.
If you’re going to participate in agentic commerce—and there may be good reasons to do so—this is the moment to demand direct relationships. Push for implementations that preserve your customer communication channels. Negotiate for access to customer data beyond what’s required for fulfillment. Consider whether UCP adoption should be contingent on terms that protect relationship ownership, not just transaction mechanics.
The protocol is generic. The implementation is Google’s. Know which one you’re actually adopting.
The Case for UCP
The proponents have reasonable arguments. UCP addresses a real problem: as AI agents begin to handle shopping on behalf of consumers, there’s currently no standardized way for these agents to interact with the complex logic retailers have built into their systems—payments, loyalty programs, delivery estimates, taxes, and returns. Without a common standard, every retailer would need custom integrations with every AI platform, creating fragmentation and chaos.
UCP provides open-source standards that allow merchants to preserve their existing tech stacks and business logic while becoming accessible to AI-driven discovery. The protocol is designed to reduce cart abandonment by enabling frictionless checkout, and its modular architecture lets merchants choose which capabilities to support.
Some industry voices suggest this could be as foundational to commerce as HTTP was to the web—a shared language that enables interoperability across the ecosystem.
The Case for Caution
Loss of Customer Connection and Experience Ownership
Retailers have invested billions in creating differentiated shopping experiences—curated product discovery, personalized recommendations, brand storytelling, and carefully designed checkout flows. UCP fundamentally bypasses all of this.
When an AI agent completes a purchase without the customer ever visiting your site, you lose the opportunity to upsell, cross-sell, build brand affinity, or create memorable moments. For customers who enjoy the shopping journey—browsing, comparing, discovering new products—this protocol eliminates that experience entirely. Not every purchase is purely transactional; sometimes the exploration is the point.
In a UCP world, your brand becomes only as good as your metadata. Retailers should think carefully before ceding these touchpoints to intermediaries.
Impact on Advertising Revenue
For retailers with significant on-site advertising businesses, UCP poses a direct threat to ad revenue. The advertising ecosystem depends on page views, browse sessions, and the discovery funnel—products, brands, and display placements throughout the shopping journey. When customers never land on the site, those impression and click opportunities disappear.
Even if a retailer could surface sponsored product selections within a UCP transaction, the volume and variety of ad placements would be dramatically reduced compared to a full on-site session. The substitution effect is clear: every transaction completed through an AI agent is a session that didn’t happen on your platform, with all the associated ad revenue that session would have generated.
This isn’t just about individual transactions—it’s about the long-term degradation of a business model that funds much of the retail experience.
Data Sharing and Strategic Vulnerability
Implementing UCP requires sharing structured product data, pricing logic, inventory levels, and promotional strategies with third-party platforms. Even though Google Shopping already receives product feeds, UCP goes deeper—exposing checkout logic, loyalty program structures, and real-time pricing. This creates significant data leakage to platforms that may also be competitors.
The more retailers standardize on UCP, the more commoditized their offerings become in the eyes of AI agents making purchase decisions.
Small Business Accessibility Gap
While proponents argue UCP democratizes access to AI commerce, the reality is more complex. Mom-and-pop retailers already struggle with the technical demands of modern e-commerce—managing product feeds, optimizing for Google Shopping campaigns, and maintaining accurate inventory data. Adding UCP compliance introduces another layer of technical complexity.
Yes, Shopify offers integrations, but many small businesses don’t use sophisticated e-commerce platforms or lack the technical resources to implement these protocols correctly. The businesses best positioned to benefit from UCP are large retailers with robust technical infrastructure, potentially widening the gap between enterprise and small-business commerce capabilities.
Historical Precedent: Remember Google Shopping Express?
Google’s Universal Commerce Protocol is not the company’s first attempt to insert itself between retailers and customers.
Google Shopping Express launched in September 2013 as Google’s high-profile attempt to compete in e-commerce by creating a virtual mall filled with top retailers’ products. Major retailers including Walmart, Target, Walgreens, and Best Buy initially partnered with the platform, seeing it as an alternative path to digital customers.
However, by August 2018—five years after launch—Google Express had failed to gain significant traction. Its retail partners had begun building out their own fulfillment businesses, including Walmart Grocery’s curbside pickup and Target’s Shipt. By late 2018, Target and Walmart were pulling out or pulling back from Google Express, and in September 2019, the platform was quietly absorbed into Google Shopping after being widely considered a failure. The Google Shopping app itself was shut down in June 2021.
The pattern is instructive: large retailers initially signed on out of competitive necessity and FOMO, participated with a limited subset of products, and ultimately retreated to invest in their own customer-facing infrastructure.
We may see the same dynamic with UCP—retailers sharing a minimal catalog of low-consideration, commodity products that transact easily through AI agents, while protecting high-margin, research-intensive categories that benefit from the full on-site shopping experience.
Recommendation
The fear of becoming “invisible” to AI agents is real, but it shouldn’t drive hasty adoption.
For retailers whose competitive advantage lies in owning the customer relationship end-to-end—from discovery through fulfillment and returns—and in the advertising business that funds platform innovation, the calculus is different. Rather than racing to integrate with protocols that commoditize the shopping experience and cannibalize ad revenue, consider investing in your own AI-native experiences that keep customers within your ecosystem.
If you do decide to participate, this is the moment to negotiate. Don’t accept the default terms. Push back on implementations that reduce you to a fulfillment endpoint. Specifically:
- Demand direct customer communication channels. If a customer buys through an AI agent, you should still be able to email them, market to them, and build a relationship beyond that single transaction.
- Negotiate data access. Being Merchant of Record should come with meaningful customer data, not just a shipping address.
- Preserve brand touchpoints. Explore whether UCP transactions can include branded confirmation experiences, follow-up communications, or loyalty program enrollment.
- Consider selective participation. You don’t have to put your entire catalog on UCP. Many retailers will likely expose commodity products where the transaction is purely functional, while protecting high-margin categories where the shopping experience adds value.
The retailers who come out ahead won’t be the ones who adopted fastest—they’ll be the ones who adopted on terms that preserved their strategic assets.
What’s Next
Understanding the protocol is step one. But before you decide whether UCP is right for your company, you need to understand why your competitors are adopting it—and whether their strategic rationale applies to you.
Read Part 2: Why Your Competitors Are Adopting UCP (And Whether You Should Too)
In Part 2, I break down the specific strategic logic behind each type of UCP adopter—from Shopify (selling shovels) to Walmart and Target (physical store hedges) to payment processors (pure volume play)—and provide a framework for evaluating your own company’s position.
Sources and Further Reading
Official Documentation
- Universal Commerce Protocol Official Site — The official UCP specification and documentation site
- Google Developers: UCP Implementation Guide — Google’s official merchant guide
- Google Blog: New Tech and Tools for Retailers — Google’s official announcement from NRF 2026
- Shopify Engineering: Building the Universal Commerce Protocol — Shopify’s technical deep-dive into UCP architecture
Analysis and Commentary
- Nekuda Substack: Everything You Wanted to Know about Google’s New Universal Commerce Protocol
- Abhishek Chaudhary: How Google’s Universal Commerce Protocol Will Force a Hard Pivot
- A Merchant’s Guide to Agentic SEO and Universal Commerce Protocol
- Get Ready to Rewrite Your Compliance Programs
Historical Context