2026-08-09 · agentic commerce · readiness

The second buyer: agents are shopping, most stores are not ready

New IDC research commissioned by WooCommerce puts a name on what operators have been seeing in their logs. The readiness gap it describes is not a marketing gap. It is a data gap — and it is fixable.

TL;DR — An IDC InfoBrief sponsored by WooCommerce (July 2026) argues that every store now serves a second kind of buyer: AI agents that ignore design and persuasion entirely and evaluate structured product data, live inventory and accurate pricing instead — and that will not recommend what they cannot verify. Most merchants, the research finds, are not prepared for that buyer. We agree with the diagnosis, and we think the prescription is more concrete than the discourse suggests: readable catalog data, live endpoints on the merchant's domain, and verifiable provenance. All three are deployable today.

What the research says

The InfoBrief — Build for What's Next: Open-Source Architecture and the Future of AI Commerce, authored by IDC's Heather Hershey and sponsored by WooCommerce — synthesizes IDC's 2026 predictions and spending data into one commercial claim: agent-mediated shopping is no longer a forecast, and merchant preparedness lags well behind it. The framing that stuck with us is the second buyer. A human buyer responds to photography, copy and layout. The agent buyer parses fields. Where a field is missing, wrong or stale, the agent does not squint and guess generously the way a person might — the product simply drops out of consideration.

The sharpest line in the research is about trust: an agent will not recommend a brand it cannot verify. That sentence deserves more attention than the traffic projections around it, because it names the actual mechanism of exclusion. Verification is not a vibe. It is the ability to check a claim — this price, this stock state, this seller — against an authoritative source at decision time.

The gap, made concrete

"Not ready" is abstract until you look at what an agent actually encounters on a typical WooCommerce store. Three failures repeat:

None of these is solved by better product photography or a faster theme. That is why we call it a data gap: the missing layer is structured, live, attributable product data served from the domain that owns it.

What readiness looks like when it ships

Our answer to the second buyer is deliberately boring: publish the catalog the way machines read, from the store itself. KaliCart Bridge puts discovery documents, bounded read-only search and honest price and stock blocks on the merchant's own domain — live WooCommerce data, not a copy. The federated catalog adds the cross-store layer with consent and provenance attached, so an agent that asks "which store has what I need" gets answers a merchant actually stands behind. And because readiness is measurable, ready.kalicart.com will scan a domain and show which of these layers exist on it right now.

We have also started publishing what happens when the second buyer shows up: one week of real agent traffic on the federated catalog — five hundred searches by an agent nobody prepared for, navigating governed taxonomy without help. The research says that buyer is coming. Our logs say it has visited.

Where we would push back

Two cautions, in fairness. First, this is sponsored research: WooCommerce commissioned a study whose conclusion favors investing in commerce infrastructure, and while the mechanism it describes matches what we observe, adoption projections in sponsored work deserve the usual discount. Second, readiness is necessary, not sufficient. A perfectly readable catalog still competes for agent attention through distribution — registries, discovery signals, network membership. Fixing the data gap makes a store eligible. It does not make it chosen. Merchants should hear the first claim as urgent and the second as honest.

Sources