The Website Is Becoming Infrastructure

Google, Shopify, OpenAI, Stripe and Visa compete in different parts of the commerce stack, yet their recent work points toward the same architecture. Google and Shopify are standardizing how software agents discover products and interact with carts. OpenAI and Stripe designed the Agentic Commerce Protocol so orders can originate in an AI interface while merchants keep their existing backend systems. Visa’s Intelligent Commerce Connect is explicitly protocol-agnostic and intended to connect agents to existing payment infrastructure.

The common feature is more revealing than the protocols themselves: none assumes that the retailer’s website must remain the place where every shopping journey begins.

For most of the commercial web’s history, interface and infrastructure were bundled together. The website attracted the shopper, presented the assortment, explained products, built the basket and led the customer into checkout. Product databases, inventory services and payment systems existed largely to support that page-based experience.

Agent-mediated commerce starts to separate the two. A shopper can discover a product in ChatGPT, Gemini, Copilot or another interface and arrive at the merchant late in the journey—or not arrive as a conventional page view at all. The retailer still needs product truth, price, inventory, identity, tax, promotions, cart logic and fulfilment. What becomes optional is the requirement that a human navigate those capabilities through the retailer’s own front end.

The destination becomes a capability layer

The numbers are still early, but the direction is visible. Adobe has measured rapid growth in AI-referred retail traffic. Shopify now distributes merchant products into AI channels through Agentic Storefronts and has opened its Catalog API and Universal Commerce Protocol infrastructure to developers. Google’s Universal Commerce Protocol can expose real-time product information and multi-item cart operations to agents.

This is distributed commerce in a more literal form than the phrase usually implies. A merchant’s catalogue can appear in a planning app, a search answer, a conversational assistant or a niche vertical tool. The commercial system becomes reusable outside the visual environment it was originally built to serve.

Shopify’s June 2026 developer release makes the ambition explicit. It describes its Catalog API as structured, queryable infrastructure for AI agents and UCP as the layer spanning discovery, carts and checkout. The details will evolve, but the strategic direction is clear: commerce capabilities are becoming composable.

Why this is not a scraping problem

It is tempting to reduce the transition to better machine readability: make the site crawlable, publish richer schema and let agents parse the rest. That is sufficient for some discovery use cases and inadequate for transactions.

A transactional agent may need product identity, variant rules, store-level stock, member pricing, delivery restrictions, loyalty entitlements and cart operations. Some facts can be published and cached. Others must be verified at the moment of action. A page is a presentation of commercial state; an agent needs controlled access to the state itself.

This resembles earlier platform transitions. Mobile did not make databases or payment processors obsolete. It increased the value of APIs that allowed the same business logic to operate through a new interface. Cloud computing separated applications from physical infrastructure without reducing the importance of the infrastructure underneath.

Retail is moving through a similar abstraction. UCP, ACP and the current generation of agent protocols may change or disappear. The durable requirement is that a merchant’s core capabilities can be called safely from more than one interface.

The counterintuitive result

The website therefore becomes more important in one sense and less important in another. It becomes less important as the mandatory starting point for discovery. It becomes more important as one authoritative manifestation of the merchant’s commercial system.

This distinction should influence investment. A beautiful AI shopping experience that cannot verify stock or manipulate the real cart is a demonstration. A less spectacular interface connected to reliable merchant services is infrastructure.

The most defensible retailer strategy is not to pick a single winning agent ecosystem. It is to make the merchant portable: coherent product identity, high-quality catalogue data, live commercial services, explicit permissions and a checkout that can accept transactions from multiple trusted surfaces.

The website is not disappearing. It is becoming one client of the commerce architecture it used to contain.

The website is not disappearing. It is becoming one client of the commerce architecture it used to contain.

“Integrate quickly without changing their backend systems.” — OpenAI, on the design goal of ACP