Agentic commerce is here: product data is the new shelf

For thirty years, winning the shelf meant winning eye-level placement, endcap space, or a page-one search ranking. In 2026, a growing share of purchase decisions never touch a shelf or a search results page at all: an AI agent reads a product's data, compares it against a handful of alternatives, and buys or recommends on a shopper's behalf. The new competition isn't for attention. It's for machine-readability.

The storefront is becoming an API call

The pattern has moved from theory to shipping product in under a year. OpenAI launched Instant Checkout inside ChatGPT in February 2026, built on the Agentic Commerce Protocol it co-developed with Stripe, letting US users buy from Etsy sellers and, on the way, over a million Shopify merchants including Glossier, SKIMS, and Vuori. By March, OpenAI had already pivoted the model again, shifting toward checkout inside individual retailer apps embedded in ChatGPT (Instacart, Target, Expedia) rather than one universal checkout button. Google is pursuing something similar with a Universal Commerce Protocol that lets agents query merchant catalogs, carts, and checkout flows through a single open standard. Shopify has built "agentic storefronts" that syndicate a merchant's catalog into ChatGPT, Microsoft Copilot, and Google's AI Mode automatically, and reports that AI-driven traffic to Shopify stores grew roughly 8x year over year in Q1 2026, with orders from AI-powered search up nearly 13x.

The moves and reversals matter less than the underlying shift they all point to: McKinsey estimates agentic AI could influence $3 trillion to $5 trillion in global retail commerce by 2030, with as much as $1 trillion of that in US retail alone. Whether the checkout button lives in ChatGPT, inside a retailer's own app, or behind Google's protocol, the agent still has to decide what to buy before anyone checks out. That decision is made by reading data, not by browsing a page.

Product data is the new shelf placement

An endcap worked because a human walked past it. An agent doesn't walk past anything. It queries a catalog, and the products that get returned, compared, and ultimately recommended are the ones whose data answers the agent's question completely enough to rank. As one industry breakdown puts it plainly, AI shopping agents read schema, not homepages — meaning the visual merchandising, the hero image, the brand story on the PDP, none of it factors into the agent's decision the way it does for a human shopper scrolling.

Shopify's own guidance to merchants is blunt about what replaces it: agents "read structured data — product titles, descriptions, images, pricing, inventory, shipping speeds — and use it to decide what to recommend," and merchants with rich, structured data get a compounding edge as AI shopping scales. That's a mechanism, not a marketing claim: an agent can't recommend an attribute it can't parse.

What agents specifically look for is more granular than a basic product feed. A minimum feed (name, image, price, availability) gets a product into consideration. It doesn't win. Full schema.org/Product markup with a proper Brand object, GTIN, MPN, dimensions, and material tends to outrank a thin listing, and offer-level fields like priceValidUntil, itemCondition, hasMerchantReturnPolicy, and shippingDetails increasingly decide which of several near-identical SKUs the agent actually selects, because those are the fields that answer real constraint questions like "can I get this by Thursday."

What breaks first: the gap between "in the PIM" and "in the feed"

Most catalogs already have a PIM or a spreadsheet with most of this information somewhere. The gap isn't that the data doesn't exist. It's that it's incomplete, inconsistently structured, or stale by the time it reaches the feed an agent actually reads. A supplier's raw feed rarely arrives agent-ready:

Before (raw supplier feed):

After (enriched attribute set):

Ask an answer engine "3/4 inch brass ball valve rated for gas lines, ships this week" and the raw feed doesn't have the fields to even enter that comparison. The enriched version answers the query in its own attribute schema, which is exactly what an agent is scanning for.

That gap between "we have the data somewhere" and "the data is complete, current, and structured in the feed an agent reads" is the actual battleground now. It's also why roughly 60% of ecommerce catalogs reportedly carry missing GTINs, inconsistent attribute naming, or stale inventory flags that cause agents to quietly downgrade or drop those products from consideration. None of that is a merchandising failure. It's a data maintenance failure, at a scale that manual review can't keep up with, especially with feed-freshness windows on pricing and inventory now measured in minutes rather than days.

Data enrichment is the shelf-stocking work now

Retailers spent decades getting good at physical shelf placement and, more recently, at search ranking. Agentic commerce asks for the same discipline applied to structured data: complete attributes, correct identifiers, current availability, and machine-readable policy terms, kept that way continuously as SKUs, suppliers, and prices change. That's less a marketing problem than an operations one, and it's squarely the kind of gap-filling, scoring, and continuous maintenance work Anglera does on top of whatever system already stores the catalog. The shelf changed. The work to earn a spot on it didn't get any smaller.

Sources:

• OpenAI: Buy it in ChatGPT — Instant Checkout and the Agentic Commerce Protocol
• Digital Commerce 360: OpenAI shifts checkout plans in its agentic commerce strategy
• McKinsey: The agentic commerce opportunity
• Shopify: How agentic commerce works