What is agentic commerce?
A plain definition for ecommerce teams, plus the part most explainers skip: which of it you can actually observe on your own surfaces.
The short definition
Agentic commerce is commerce in which an AI agent carries out part of the shopping journey on a person's behalf: interpreting a request, searching, fetching product pages, comparing options, and in some cases initiating a delegated checkout. The intent originates with a human. The requests that arrive at your storefront increasingly do not.
For a merchant, that distinction matters because measurement stacks were built around a browser session. When the fetch comes from an agent, the browser assumptions — JavaScript execution, cookies, consent, session continuity — stop holding.
Where agents touch a merchant's surfaces
Agentic activity is not one event. It shows up across the same surfaces you already operate:
- Product data and feeds — structured data, availability, and price are read programmatically rather than skimmed visually.
- Storefront pages — product and category pages are fetched to confirm details an agent needs before recommending or buying.
- Cart and checkout — delegated purchase flows issue requests that look unlike a human session's timing and ordering.
- Payments and risk — an agent-initiated transaction reaches the same rails, but with different upstream context.
Why most stacks under-report it
Web analytics requires a browser to run a tag. Bot management is tuned to decide block-or-allow, not to attribute demand. A PIM knows what you sell, not who asked. A payment processor sees the transaction, rarely the agent that started the journey.
The practical consequence: a measurable share of eligible request events stays unclassified after deterministic labeling. That unclassified share is the gap Cartograph is being built to quantify — not to guess at what an external model concluded off-property.
Common questions
What is agentic commerce?
Agentic commerce is commerce in which an AI agent acts on a shopper's behalf — searching, comparing, fetching product pages, and in some cases initiating a delegated checkout. The buyer's intent is still human, but a growing share of the requests that reach a merchant's surfaces are issued by software rather than a person in a browser.
How is agentic commerce different from a bot or a crawler?
A search crawler indexes pages on a schedule. An agentic request is usually triggered by a specific user task and is aimed at a specific decision: which product, what price, is it in stock, can it be bought now. Both arrive as HTTP requests, which is why merchants need labeling rather than blunt bot blocking.
Can merchants see agentic traffic today?
Partially. Browser-based analytics needs JavaScript execution and consent, so it can under-count agent activity by design. Configured server, CDN, and application logs can capture requests that reach those observation points even when browser analytics does not fire, but coverage depends on source inclusion, routing, sampling, retention, and collection health. Log-origin evidence is a practical starting point, not proof of complete observation.
Does agentic commerce mean shoppers stop visiting my site?
Not necessarily. It means part of the shopping journey happens through an intermediary. The merchant surfaces are still fetched — the attribution and the measurement path change, not the underlying request.