Agentic Commerce: Who Sells When AI Buys? (2026)

Agentic commerce begins when an AI agent performs a consequential shopping task for a person, including product discovery, comparison, selection, or checkout. ChatGPT, Gemini, Perplexity, and Copilot can increasingly use combinations of public pages, structured product data, merchant feeds, indexes, and partner catalogs, depending on the platform, market, and surface.

For a brand or e-commerceSelling products online through your own store or marketplaces. For AI visibility the deciding factor is whether the shop's catalog is readable by machines.Read more operator, the consequence is immediate: a machine may assess the offer before a shopper visits the store. A wrong price, unnamed size, missing identifier, or broken checkout handoff can remove an otherwise suitable product from consideration.

This guide gives a founder a plain-language model and a Monday audit. It covers the buying agent, the seller-side obligations, and the evidence needed to test whether a product can move from a customer request to the correct variant on the brand’s checkout.

The shelf is becoming a query.

Agentic commerce starts with consequential action

Agentic commerce is a purchase process in which an AI agent performs at least one consequential task for a person, such as finding products, comparing offers, selecting an option, or initiating checkout. The operator’s first job is to identify which task moved to the agent and test the product evidence that task requires.

The threshold is consequential action. Rewriting a product description does not meet it. Narrowing 2,000 shoes to three pairs that fit a shopper’s size, budget, and waterproofing requirement does.

Four stages make the idea concrete:

• Discovery: The agent turns intent into candidates. “Waterproof hiking boots under $180 in men’s size 11” becomes a retrieval task across available pages, feeds, indexes, or catalogs.
• Comparison: The agent aligns evidence that stores describe differently. “Waterproof membrane,” a named material, and “rain-ready” need explicit supporting facts before they can carry the same meaning.
• Selection: The agent filters or orders options under the shopper’s constraints. OpenAI says organic shopping results can consider relevance, price, availability, quality, and whether the merchant is the maker or primary seller (OpenAI). Its exact weighting remains proprietary.
• Checkout: The agent may create a cart, send the shopper to a merchant, or complete an authorized flow where the platform and merchant support it. OpenAI commerce documentation, Google’s published Universal Commerce Protocol announcement, and Perplexity Shopping show distinct versions of that journey.

Full autonomous payment is one form of agentic commerce. It is not required for the category.

Six terms keep the operating model clear

Agentic commerce: A buying journey in which an AI agent performs a consequential part of finding, comparing, selecting, or transacting for a person.

Shopping agent: Software that interprets a shopper’s intent and takes buying actions, such as retrieving products, checking constraints, or initiating checkout.

Agentic Selling: The seller side of agentic commerce, covering the work that helps a brand’s products become retrievable, understandable, comparable, actionable, and ready to transact.

Structured product data: Product facts stored in named fields, such as price, currency, stock status, size, and identifiers, so machines can interpret them consistently.

Merchant feed: A regularly updated catalog file sent to a shopping platform, usually containing product identifiers, offers, images, variants, and availability.

Agentic storefront: A store experience that can assemble approved selling components around a visitor’s request and support people and buying agents. See the fuller definition of an agentic storefront.

Consequential action separates adjacent systems

The appeal is obvious: any shopping experience with generated text can look agentic. The operating evidence challenges that view. The useful dividing line is who performs the consequential buying action and where the action occurs.

One product can span several rows. A search surface can add a cart, while a merchant experience can call tools and carry a selected variant into checkout.

Public commerce systems make this an operating issue

Four observable developments matter more than a speculative market forecast. OpenAI documents product feeds and commerce integrations. Google and Shopify have published the Universal Commerce Protocol, or UCP, for supported commerce interactions. Perplexity operates shopping experiences and a merchant program. Microsoft operates Copilot surfaces whose product inputs and commerce availability vary by product, market, and implementation.

These developments do not establish universal adoption. They show that external buying surfaces can accept seller inputs, making catalog quality a current operating concern.

The Monday change is modest. Add named AI buying surfaces to catalog quality assurance alongside Google Merchant Center, the public storefront, and checkout.

Agentic commerce creates a buy side and a sell side

The buy side is a shopping agentSoftware agents that search, compare and complete purchases on a buyer's behalf. They read structured catalog data and transact through protocols like ACP and MCP.Read more acting for a person. The sell side is the brand’s capacity to present products that the agent can retrieve, understand, compare, select, and carry into a transaction.

That seller-side craft is Agentic Selling.

The buy side carries more of the shopping task

A buying agent captures intent such as product type, budget, recipient, use case, delivery date, size, and preferences. It then retrieves candidates through the sources available to that system.

Comparison follows. The system checks constraints and may exclude a candidate whose requested size is unavailable or whose delivery promise cannot be established. Where supported, it can initiate a cart, request authorization, and hand the order to the merchant.

Published protocols divide this work differently. The Agentic Commerce Protocol documents supported commerce interactions in an ecosystem associated with OpenAI and Stripe; its scope depends on the referenced specification and implementation. Google and Shopify’s UCP describes a broader commerce journey. AP2, the Agent Payments Protocol, describes signed mandates for expressing intent and authorizing transactions.

Names and specifications will evolve.

For operators, the durable sequence is intent, retrieval, comparison, transaction, authorization, and order handoff. A protocol can transport an action. Accurate product facts still have to exist.

The sell side makes the answer possible

Every buy-side capability creates a seller obligation: retrieval needs an accessible product, comparison needs explicit identity and attributes, selection needs a current offer and valid variant, and transaction needs a working handoff. Operators should inspect evidence at each stage because one unresolved field can break the journey.

Infrastructure cannot reconcile a product page showing $129 with a feed showing $149. It cannot safely infer that navy exists in medium or create a missing product identifier.

A GTINThe GS1 Global Trade Item Number, the identifier that lets engines merge your offer with the same product sold elsewhere. A valid GTIN is numeric, 8 to 14 digits, with a GS1 check digit.Read more, or Global Trade Item Number, identifies a trade item and is commonly encoded in a barcode. Where applicable to the category and platform, a valid GTIN or an accurate brand-and-MPN combination can help resolve identity. MPN means the manufacturer part number assigned by the maker.

Agentic commerce determines product findability in AI surfaces

ChatGPT, Gemini, Perplexity, Copilot, and AI Overviews can use different combinations of indexes, structured page data, merchant feeds, and partner catalogs. No single system necessarily uses every source, and its implementation can vary by market and surface.

Retrieval is the step where a system fetches relevant records or passages before producing an answer. Current, consistent evidence can make a product easier to retrieve and compare than facts confined to a visual banner, although each platform controls its own selection and presentation.

For operators, AI findability begins with agreement across the public page, structured markup, feed, variant state, and checkout handoff. When those surfaces conflict, the engine may encounter incomplete evidence. Test them from outside the store with fixed prompts, timestamped product samples, and recorded outputs.

For implementation depth, read generative engine optimization for e-commerce and the guide to Google Shopping feed optimization.

Five sell-side failures block a clean journey

A lifestyle image cannot carry the full offer

A multimodal system may process a photo of a red leather bag. The image alone cannot reliably establish its $320 price, current stock, return window, or whether the shown color is the purchasable variant.

Express the product with schema.org Product and its offer with schema.org Offer, where appropriate. The matching feed record should carry the same SKU, title, link, image, price, availability, and applicable identifiers.

Retrieval can skip the persuasive page sequence

A person may scroll past a hero image, open an accordion, and infer that “weekend-ready” describes a 35-liter bag. An AI surface may receive one indexed passage, feed row, or tool result and never encounter the persuasive block lower on the page.

Each retrievable unit carries more responsibility. State capacity, dimensions, material, compatible use, and offer facts directly.

Price contradictions create competing versions

A page showing $79 and a feed showing $89 present two versions of one SKU. The generated answer can become inaccurate, while the feed can encounter item-level issues.

Google Merchant Center’s guidance is blunt: “The price on your landing page must match the price in your product data” (Google, price and availability consistency guidance). The guidance applies to submitted product data and landing pages; promotions, regional pricing, and update delays still require careful testing.

Check the rendered page, structured markup, and feed after every promotion begins and ends.

An ambiguous variant can stop the handoff

Imagine a runner asking for a women’s size 8 shoe in blue. The parent page shows six colors and eight sizes, yet the feed does not connect blue size 8 to a purchasable option.

The system has a family page and lacks a safe SKU for handoff. Depending on the platform and catalog architecture, meaningful purchasable variants should have stable identity, accurate availability, a matching landing state, and a checkout path that preserves the selection.

A real-time shelf is built from constraints

“A carry-on backpack for a 16-inch laptop, under $200, arriving by Friday” acts like a shelf assembled for one request. A product record that omits laptop fit or dimensions may be absent from that comparison even when the bag would work.

This closes the opening issue. The visual store can persuade a person, while explicit product truth supplies the shelf built from a query.

Monday’s audit starts with two SKUs

Choose one revenue-leading product and one long-tail item. A polished hero SKU can conceal failures across thousands of less-managed records.

Keep the purchase on the brand’s checkout. The audit tests whether an external buying surface can arrive with a valid product and variant while the brand remains merchant of record.

Seller-side measurement must start outside the store

Reading the store’s own application programming interface, or API, shows intended data. Testing the public page, rendered structured markup, submitted feed, and available AI surface shows what an external system can obtain.

Freeze a prompt set and timestamp the SKU sample. Then make one controlled catalog change, such as moving an item from in stock to out of stock, and observe when each surface reflects it. This method measures propagation without inventing a universal benchmark.

Token counts are engineering inputs. The presence of llms.txt, a proposed file for machine-readable site guidance, does not establish retrieval, factual accuracy, citation, or checkout success.

Representative-SKU audit template

Use one row per check and duplicate the sheet for every test date. Leave cells blank until evidence exists; record unknown when a surface cannot be inspected.

Classify category specificity in three merchant-readable bands: exact and specific, such as “women’s waterproof hiking boots”; plausible but imperfect, such as “outdoor footwear”; and too broad to compare, such as “apparel and accessories.”

Ground the audit in the OpenAI product-feed specification, Google’s Merchant Center specification, schema.orgMachine-readable schema.org markup (Product, Offer, AggregateRating) embedded in a page as JSON-LD. It is the canonical way to hand engines unambiguous product facts.Read more Product and Offer, OpenAI’s bot documentation, and the robots.txt standard, RFC 9309.

The brand agent closes the seller-side loop

Veliu is the brand agent that studies the market, readies the store, and sells to people and to the AI shopping agents that arrive. It reads the public catalog from outside so it can work with current prices and valid variants, adapts the on-site selling experience using permitted signals and approved components, answers shopping agents machine to machine, and returns the questions customers asked. Checkout stays on the brand’s rails, with the brand as merchant of record. Behind the agent sits over a year of R&D on a live delegated-commerce marketplace: 50K+ customers, 300K+ delegated transactions, over €100M transacted.

Turn the model into one operating routine

1. Add buying agents as real readers in catalog quality assurance.
2. Treat price, stock, identifiers, variants, dimensions, and use cases as selling material.
3. Test hero products and the long tail with the same evidence standard.
4. Give one owner authority to resolve disagreements across merchandising, feeds, SEOSearch Engine Optimization: earning visibility in classic search results through content, links and technical site health. In 2026 it remains the base layer that AI search builds on.Read more, and commerce engineering.
5. Preserve the selected product and variant through the brand’s checkout.

The concrete next move is to choose one hero SKU and one long-tail SKU today, then complete the outside-in audit with evidence URLs and timestamps before the next promotion starts.

Author: Veliu Editorial Team

Methodology note: Veliu Editorial Team reviewed the linked primary documentation from OpenAI, Google, Perplexity, schema.org, Google Merchant Center, the Agentic Commerce Protocol, AP2, and RFC 9309 as available on July 29, 2026. The review compared documented seller inputs, retrieval surfaces, transaction steps, and implementation caveats. It did not test every market or account configuration, and it used no market forecast, simulated audit score, or inferred platform weighting.