Agentic shopping is moving from demos to production: users will increasingly ask an AI to research, compare, buy, and even handle post-purchase steps—without bouncing across dozens of merchant sites.
To make that possible at scale, Google and partners have introduced the Universal Commerce Protocol (UCP): an open-source standard intended to standardize how AI surfaces, merchants, and payment providers talk to each other across the commerce lifecycle. (Reference: Under the Hood: Universal Commerce Protocol (UCP) )
This article breaks down what UCP is, how it works conceptually, how it connects to other protocols (AP2, A2A, MCP), and what product/tech teams should do now.
What is Google's Universal Commerce Protocol (UCP)?
The Universal Commerce Protocol is an open-source standard introduced by Google in January 2025, designed to power the next generation of agentic commerce. According to the official documentation, UCP establishes a common language and functional primitives that enable seamless commerce journeys between consumer surfaces, businesses, and payment providers [1][2].
Co-developed with industry leaders including Shopify, Etsy, Wayfair, Target, and Walmart, UCP is endorsed by over 20 global partners across the ecosystem [3]. Major payment providers such as Adyen, American Express, Mastercard, PayPal, Stripe, and Visa have also committed their support, demonstrating the protocol’s broad industry acceptance [3].
At its core, UCP addresses what Ashish Gupta, VP/GM of Merchant Shopping at Google, describes as the need for a shared language across the ecosystem [3]. The protocol enables AI agents to discover merchant capabilities, invoke checkout processes, apply discounts, and manage orders while maintaining merchants as the seller of record throughout the transaction [4].
Why Does the Ecosystem Need a Standard Now?
The commerce landscape faces a critical challenge: traditional infrastructure was designed for direct human interaction, but AI agents now need to act autonomously on behalf of users. This shift creates what industry leaders describe as an “N×N integration bottleneck,” where every platform must build custom connections with every merchant [1].
According to Google’s announcement, businesses face fragmented commerce journeys that lead to abandoned carts and frustrated shoppers [3]. When consumers interact with AI assistants like Google’s AI Mode in Search or the Gemini app, they expect seamless transitions from product discovery to final purchase. However, without a standard protocol, each AI platform requires separate integrations, slowing ecosystem adoption and creating inconsistent experiences [3].
PayPal’s SVP and Head of AI, Prakhar Mehrotra, emphasizes that interoperability allows retailers to connect once and reach many environments while maintaining trust, transparency, and control [5]. The protocol addresses three fundamental requirements: enabling agents to work across different commerce systems, reducing integration complexity for merchants, and ensuring secure transactions with verifiable user consent [13].
As Michelle Gill, GM of Small Business and Financial Services at PayPal, notes, the next generation of commerce will be defined by how well the industry builds open, trusted infrastructure that serves everyone [5]. UCP provides this foundation by standardizing how AI agents, merchants, and payment providers communicate [4].
How UCP Works (Conceptual Overview) ?
UCP operates through a modular architecture built on three core components: capabilities, extensions, and profiles. This design allows the ecosystem to interoperate through one standard without requiring custom builds for each integration [1][4].
Capabilities represent core commerce building blocks. The initial launch focuses on three primary capabilities: Checkout enables complex cart logic, dynamic pricing, and tax calculations across millions of businesses; Identity Linking allows customers to connect loyalty programs and member accounts; and Order Management provides post-purchase support including tracking and returns [2][4].
Extensions augment these capabilities with specialized functionality. For example, merchants can offer real-time discounts, apply subscription billing, or specify custom delivery requirements without modifying the core capability definitions [4]. This approach prevents feature bloat while allowing merchants to differentiate their offerings.
Profiles enable dynamic discovery. Businesses declare their supported capabilities and payment options in a standardized profile format. When an AI agent initiates a shopping interaction, it fetches this profile to understand what the merchant can support, then configures itself accordingly [1]. This discovery mechanism eliminates the need for hard-coded integrations.
According to Shopify’s engineering blog, the protocol separates the shopping service layer, which defines core transaction primitives like checkout sessions and line items, from the payment layer [6]. This separation allows payment handlers to be modular and extensible. Each payment provider publishes their own handler specification, merchants advertise which handlers they accept, and agents select the appropriate one for each transaction [6].
The protocol supports both synchronous and asynchronous flows. For real-time purchases where humans are present, agents can complete transactions immediately with explicit user approval. For delegated tasks, agents can operate under pre-approved conditions specified through intent mandates, enabling scenarios like automated purchasing when specific criteria are met [8][13].
UCP's Relationship with AP2, A2A, and MCP
UCP is designed to work seamlessly with three complementary protocols that together form the foundation of agentic commerce: Agent Payments Protocol (AP2), Agent2Agent (A2A), and Model Context Protocol (MCP). Understanding these relationships is essential for implementing complete agentic commerce solutions [1][4].
Agent Payments Protocol (AP2) provides the security layer for agent-initiated payments. Announced by Google in September 2025, AP2 addresses critical questions that arise when autonomous agents make purchases: How do you verify user authorization? How can merchants trust that an agent’s request reflects true user intent? Who is accountable if something goes wrong? [8]
AP2 introduces mandates, which are cryptographically signed digital credentials that serve as verifiable proof of user instructions [8][13]. The protocol defines three types: Cart Mandates for human-present transactions where users approve specific purchases in real-time; Intent Mandates for human-not-present scenarios where users pre-approve conditions like budget limits or timing constraints; and Payment Mandates that provide transaction context to payment networks without exposing sensitive data [13].
UCP integrates with AP2 by supporting these mandate mechanisms within its checkout flows [1][8]. When an AI agent using UCP initiates a purchase, it can attach the appropriate AP2 mandate to prove user authorization. Payment handlers within UCP can then validate these mandates before processing transactions, ensuring every payment is backed by cryptographic proof of consent [13].
Agent2Agent (A2A) enables communication between different AI agents. Introduced by Google in April 2025 and now managed by the Linux Foundation, A2A allows agents built on different frameworks by different vendors to collaborate effectively [9][14]. The protocol supports discovery through agent cards, negotiation of interaction modalities, and coordination of long-running tasks [14].
UCP supports A2A as a transport mechanism [1]. While UCP can operate through REST APIs for direct merchant integrations, it also provides A2A bindings that allow merchant agents to expose their commerce capabilities to consumer-facing agents. This approach is particularly valuable for complex scenarios where multiple specialized agents need to collaborate on a purchase decision [14].
Model Context Protocol (MCP), developed by Anthropic and adopted broadly across the industry, standardizes how AI models connect to external tools and data sources [10]. MCP enables agents to access databases, call APIs, and retrieve information in a consistent way across different AI platforms.
According to the official documentation, developers should use MCP for tools and data access while using A2A for agent-to-agent communication [14]. UCP extends this model by providing commerce-specific primitives on top of these foundation protocols. An agent might use MCP to access product data, A2A to communicate with a merchant’s shopping agent, UCP to handle the checkout flow, and AP2 to secure the payment [1][10].
This layered approach follows proven design principles. As Shopify’s engineering team explains, thoughtfully layered protocols survive and thrive by separating responsibilities, defining clear interfaces, and enabling composition [6]. UCP applies this pattern to commerce, creating a modular system where each protocol handles its specialized domain while working together seamlessly.
What Google Says Merchants Get Out of It
Google positions UCP as delivering tangible value across three dimensions: expanded reach, reduced friction, and maintained control. The official implementation guide outlines specific benefits that address core merchant concerns about adopting new technology [2][3].
Expanded reach comes from connecting with high-intent shoppers directly within AI surfaces. Merchants using UCP can capture customers during the research phase in AI Mode in Search and the Gemini app, turning discovery moments into instant sales opportunities [2][3]. Google emphasizes that merchants maintain access to users on these surfaces while using existing Merchant Center account shopping feeds, minimizing additional setup requirements [2].
Reduced checkout friction addresses one of e-commerce’s persistent challenges: cart abandonment. By enabling direct purchases within conversational flows, UCP keeps users engaged throughout the transaction [3]. Customers can complete purchases using payment information already stored with Google Wallet or PayPal without leaving the AI interaction [5]. This seamless experience reduces drop-off rates and improves conversion.
Merchant control represents perhaps the most significant value proposition. According to Google’s documentation, merchants remain the Merchant of Record for all transactions, retaining full ownership of customer relationships, data, and the post-purchase experience [2][3]. Standard security and privacy practices apply to the interaction, but merchants own the transaction. This model contrasts with marketplace approaches where platforms intermediate the customer relationship.
Google also highlights flexibility in implementation. UCP offers two integration paths: a native integration that embeds checkout logic directly with Google AI surfaces, and an embedded option that allows merchants to maintain fully customized checkout experiences through iframe-based solutions [2]. This choice enables merchants to balance ease of integration against brand differentiation requirements.
The protocol’s modular design means merchants can select which capabilities and extensions they want to support [4]. A retailer might start with basic checkout functionality and gradually add features like loyalty program integration or subscription management as their needs evolve. This incremental adoption path reduces implementation risk and allows merchants to align UCP deployment with their broader digital strategy.
Sundar Pichai, CEO of Google, explained at the 2026 National Retail Federation event that UCP enables personalization at scale [11]. When a customer searches for a product, the protocol allows merchants to provide new member pricing or loyalty enrollment instantly for first-time buyers, while offering returning customers special discounts based on purchase history. This dynamic personalization happens within the conversation without breaking the user experience.
Why Product Teams Should Care (Beyond "Yet Another Protocol")
For product teams evaluating UCP, the question is not whether to adopt another protocol, but whether to participate in the fundamental restructuring of digital commerce. The implications extend far beyond technical integration, touching customer acquisition strategy, competitive positioning, and long-term platform dependencies [7][12].
Market access and customer intent represent the primary strategic consideration. AI-powered search and conversational interfaces are rapidly becoming the default discovery mechanism for many product categories [3][7]. Research from industry analysts indicates that consumers increasingly start product searches within AI assistants rather than traditional search engines or retailer websites. Product teams that integrate with UCP gain native access to these high-intent moments when customers are actively researching and ready to purchase [2][3].
This access comes with lower acquisition costs than traditional channels [7]. Instead of bidding for ad placement or optimizing for search rankings, merchants using UCP can be discovered organically when their products match customer needs expressed in natural language. The conversational context allows for richer product differentiation based on features, use cases, and customer requirements rather than just keywords and bidding strategies.
Competitive dynamics are shifting toward early adopters. As Vanessa Lee, VP at Shopify, notes, the protocol can scale to every product a customer might want to purchase [7]. This universality means that categories adopting UCP first will establish consumer expectations for frictionless AI-driven purchasing. Late adopters may find themselves excluded from major customer touchpoints or forced to compete at a disadvantage against merchants already integrated into conversational commerce flows.
The endorsement by major retailers including Target, Walmart, Best Buy, The Home Depot, Macy’s, and Zalando signals that UCP integration is becoming table stakes rather than experimental [3][7]. When industry leaders commit to a standard, the competitive pressure on smaller merchants intensifies. Product teams must evaluate whether they can afford to be absent from channels where their competitors are actively selling.
Platform risk and strategic independence require careful consideration. Google controls significant distribution through Search and its AI properties, and UCP provides a standardized way to access this distribution [2][12]. However, relying on any single platform for customer acquisition creates dependency. The protocol’s open-source nature and multi-platform support partially mitigates this risk by enabling merchants to implement once and potentially reach multiple AI surfaces [4].
The key advantage of UCP over proprietary alternatives lies in its industry-backed governance. With over 50 organizations contributing to its development and the protocol now managed under open-source principles, no single company controls its evolution [3][7]. Product teams can invest in UCP integration with reasonable confidence that the standard will remain stable and vendor-neutral.
Implementation pragmatics matter for resource-constrained teams. UCP maps one-to-one with standard retail operations, meaning core commerce logic does not need to change [1][6]. The protocol was designed specifically to align with existing business logic rather than requiring merchants to adapt their processes. Native SDKs for multiple languages allow developers to integrate within their existing technology stacks without major architectural changes [2].
Shopify’s implementation provides a reference point: merchants using Shopify can enable UCP functionality through the platform’s Checkout Kit with minimal custom development [6][7]. For merchants on other platforms, the specification includes detailed documentation, sample implementations, and conformance tests that accelerate integration. Product teams can estimate implementation effort based on their existing commerce infrastructure and the specific UCP capabilities they need to support [2][4].
Data ownership and customer relationships deserve product team scrutiny. Unlike marketplace models where platforms control customer data, UCP explicitly preserves merchant ownership [2][3]. Transaction data, customer information, and behavioral insights remain with the merchant. This ownership is critical for teams building customer lifetime value models, personalization engines, or retention programs that depend on direct customer relationships.
The protocol also supports identity linking capabilities that allow merchants to recognize returning customers and apply their loyalty benefits or preferences during AI-assisted shopping [4][11]. This capability maintains the connection between a merchant’s existing customer base and new conversational commerce channels, preventing the fragmentation that can occur when customers interact through intermediary platforms.
Future extensibility positions UCP as an investment rather than just another integration. The roadmap includes planned expansions into travel, services, and other verticals beyond shopping [7]. Extensions for loyalty program management and personalization are already in development. Product teams implementing UCP today gain a foundation that will support richer commerce experiences as the protocol evolves, rather than facing repeated integration efforts as new capabilities emerge.
Conclusion
Google’s Universal Commerce Protocol represents a critical inflection point in digital commerce infrastructure. By providing a standardized framework that enables AI agents, merchants, and payment providers to communicate seamlessly, UCP addresses the fragmentation that has hindered the adoption of agentic commerce [1][4]. The protocol’s industry-wide support from major retailers, payment networks, and technology platforms demonstrates a rare consensus that a common standard is needed [3][7].
For merchants and product teams, UCP offers concrete benefits: expanded access to high-intent customers discovering products through AI interfaces, reduced checkout friction that improves conversion rates, and maintained control over customer relationships and data [2][3]. The modular architecture allows incremental adoption, reducing implementation risk while providing a foundation for future commerce capabilities [4].
The protocol’s integration with complementary standards like AP2, A2A, and MCP creates a cohesive ecosystem where each component addresses specific technical challenges [1][6]. Together, these protocols form the infrastructure layer that will enable the next generation of AI-driven shopping experiences. As conversational interfaces become the primary discovery and purchasing mechanism for more product categories, merchant participation in this ecosystem will increasingly determine market access and competitive position [7][12].
The question for business leaders is no longer whether agentic commerce will transform retail, but whether their organizations will participate in defining how that transformation unfolds. UCP provides the standardized foundation that makes participation practical at scale [4]. Early adopters gain experience, visibility, and competitive advantages in emerging channels, while the open-source governance model provides reasonable assurance that investments in the protocol will remain relevant as the ecosystem matures [3][7].
Sources and References
- Google Developers Blog. (2025). “Under the Hood: Universal Commerce Protocol (UCP).” https://developers.googleblog.com/under-the-hood-universal-commerce-protocol-ucp/
- Google for Developers. (2025). “Google Universal Commerce Protocol (UCP) Guide.” https://developers.google.com/merchant/ucp
- Google Blog. (2025). “New tech and tools for retailers to succeed in an agentic shopping era.” https://blog.google/products/ads-commerce/agentic-commerce-ai-tools-protocol-retailers-platforms/
- Universal Commerce Protocol Documentation. (2025). “Universal Commerce Protocol (UCP).” https://ucp.dev/
- PayPal Newsroom. (2025). “From Search to Checkout: PayPal Supports Trusted AI Checkout with Google.” https://newsroom.paypal-corp.com/2025-01-11-From-Search-to-Checkout-PayPal-Supports-Trusted-AI-Checkout-with-Google
- Shopify Engineering Blog. (2025). “Building the Universal Commerce Protocol.” https://shopify.engineering/ucp
- Shopify News. (2025). “The agentic commerce platform: Shopify connects any merchant to every AI conversation.” https://www.shopify.com/news/ai-commerce-at-scale
- Google Cloud Blog. (2025). “Announcing Agent Payments Protocol (AP2).” https://cloud.google.com/blog/products/ai-machine-learning/announcing-agents-to-payments-ap2-protocol
- Google Developers Blog. (2025). “Announcing the Agent2Agent Protocol (A2A).” https://developers.googleblog.com/en/a2a-a-new-era-of-agent-interoperability/
- Anthropic. (2024). “Introducing the Model Context Protocol.” https://www.anthropic.com/news/model-context-protocol
- Google Blog. (2026). “Read Sundar Pichai’s remarks at the 2026 National Retail Federation.” https://blog.google/company-news/inside-google/message-ceo/nrf-2026-remarks/
- Search Engine Land. (2025). “Google launches Universal Commerce Protocol for agent-led shopping.” https://searchengineland.com/google-universal-commerce-protocol-467290
- PayPal Developer Community. (2025). “Agent Payments Protocol: Building Verifiable Trust for Agentic Commerce.” https://developer.paypal.com/community/blog/PayPal-Agent-Payments-Protocol/
- A2A Protocol Documentation. (2025). “Agent2Agent Protocol.” https://a2a-protocol.org/latest/
- IBM Think. (2025). “What Is Agent2Agent (A2A) Protocol?” https://www.ibm.com/think/topics/agent2agent-protocol
Need guidance implementing agentic commerce protocols in your organization?
On 32steps.com, I support organizations and product teams seeking guidance in discovering and gradually adopting AI-driven commerce solutions — from evaluating protocols like UCP to implementation planning, technical integration, team onboarding, and continuous optimization. My approach is based on continuous learning and close collaboration with the people I work with, helping you navigate the transition from traditional e-commerce to agentic shopping experiences.
I would be delighted to discuss how Universal Commerce Protocol and related AI technologies can create concrete value for your business, from a realistic and pragmatic perspective that stays aligned with your commerce strategy and customer experience goals. Whether you’re exploring initial integration options or optimizing existing implementations, let’s work together to position your organization for success in the agentic commerce era.
You may also be interested in these articles: “Predictive CRM: How to Anticipate Customer Needs Using AI ?”
Feel free to share this article on your social networks.
If you have any questions, contact us by email — we’ll be happy to reply.
Follow our Pinterest page for a boost of visual inspiration and new ideas.
