1994–2000: SSL/HTTPS makes the web safe for commerce
Before Netscape introduced SSL (Secure Sockets Layer) in 1994, there was no safe way to transmit credit card data over the internet. The protocol encrypted communications between browser and server, a simple but revolutionary concept. When HTTPS became the web standard in the early 2000s, it unlocked mass e-commerce adoption.
The lesson: a security standard adopted by the entire industry creates trust that benefits every merchant, not just those who invented the standard. No single company could have created equivalent trust on its own.
2003–2010: OAuth solves identity and authorization
OAuth (2006, standardized in 2010 as OAuth 2.0) addressed a fundamental question: how can a user authorize a third-party application to access their account without sharing their password? This protocol enabled "Login with Google", "Connect with Facebook", and thousands of e-commerce integrations that rely on delegated authorization.
For e-commerce specifically, OAuth enabled the ecosystem of marketplace integrations, shipping APIs, and payment gateways that merchants rely on today. The open standard meant any developer could integrate with any service, creating network effects impossible with proprietary auth systems.
2011–2015: Schema.org makes product data machine-readable
In 2011, Google, Microsoft (Bing), and Yahoo jointly launched Schema.org, a shared vocabulary for describing structured data on web pages. For e-commerce, schema.org/Product, schema.org/Offer, and schema.org/Review types became the standard way to describe product information to search engines.
Merchants who implemented schema.org markup gained rich snippets (star ratings, prices, availability) in search results, a direct competitive advantage. The open standard created a level playing field: any merchant, regardless of size, could make their products machine-readable.
2016–2020: WebAuthn and payment standards modernize checkout
The W3C's Web Authentication API (WebAuthn, 2018) standardized biometric authentication for the web, enabling fingerprint and face authentication at checkout. Payment Request API standardized browser-native payment collection. PSD2 in Europe enforced open banking APIs, enabling new payment flows.
Each standard reduced friction at a different point in the purchase journey, authentication, payment entry, bank authorization, collectively cutting checkout abandonment rates significantly across the industry.
2026: UCP brings open standards to agentic commerce
The Universal Commerce Protocol, launched January 11, 2026 at NRF by Google and Shopify, follows the same pattern as its predecessors:
- It addresses a new problem created by a new technology (AI agents buying on behalf of users)
- It is open-source and royalty-free (github.com/Universal-Commerce-Protocol/ucp)
- It has strong founding coalition support (Walmart, Target, Carrefour, Zalando, Adyen, Stripe, Mastercard, Visa, Amex)
- It creates a level playing field where any merchant can make themselves accessible to any AI agent
Why open standards consistently win over proprietary alternatives
History shows a consistent pattern: when a proprietary system and an open standard compete to solve the same problem, the open standard typically wins in markets with network effects. The reason is mathematical: the value of a standard grows with the number of participants (Metcalfe's law). A proprietary system captures value for its owner; an open standard distributes value across all participants.
Amazon's proprietary voice commerce (Alexa Skills) vs. UCP-compatible voice commerce (Google Assistant + Gemini) is the current real-world test of this principle. The proprietary system locks in both merchants and consumers. The open standard lets any merchant reach any agent.
What this means for merchants today
The track record of open standards in e-commerce suggests that UCP will become the default interface between AI agents and merchants, just as HTTPS became the default security layer and schema.org became the default product vocabulary. Merchants who implement UCP early, before it becomes a basic expectation, gain the same first-mover advantages that early schema.org adopters gained in search rankings.
The question is not whether to implement UCP, but when. Given the trajectory of AI agent adoption in consumer shopping, the window for early-mover advantage is measured in months, not years.