AI Agents Don't Get Sold To — They Parse. We Measured Which Distributor Catalogs They Can Actually Read

Agent-mediated buying is not a new sales channel — it is a parsing problem, and most distributors are failing the parse. We measured 37 distributor catalogs against the signals an AI agent actually reads before it selects a SKU, and the median score was 58 out of 100. The fix nobody wants to hear is also the cheapest one: stop building storefronts and start finishing the catalog.

The debate is happening at the wrong altitude

Distribution Strategy Group has argued that Google's AI Mode and the emerging Universal Commerce Protocol create a new gatekeeper for distributors — "the algorithmic buyer" — and that distributors need a channel strategy built around it. Their companion piece on AI search frames this as a discovery problem: side-by-side comparisons and sponsored placement inside AI Mode are replacing the click-through to a distributor's own site.

That framing treats agent commerce as a marketing question — where do we show up, how do we bid, what's our presence strategy. It's the wrong altitude. An agent executing a purchase order for pneumatic fittings or safety gloves isn't browsing a results page and forming a preference the way a procurement buyer does. It's issuing a query against structured data, filtering on attributes, and selecting the first candidate that satisfies the spec. There's no impression to win, no brand story to land, no funnel. There's a parse, and either your SKU survives it or it doesn't.

DSG's reporting on agentic commerce reaching wholesale distribution gets closer to this, and their November piece on the Amazon-Perplexity dispute correctly reads that fight as a proxy war over who controls the data layer an agent is allowed to touch. But the operator takeaway keeps landing on strategy — protocols to watch, platforms to court — rather than on the unglamorous work sitting underneath all of it: does the product page actually contain the data an agent needs, in a form an agent can read.

What an agent is actually reading

Strip away the protocol talk and an AI shopping agent needs the same twelve or so things a marketplace feed has always demanded — title, brand, GTIN or MPN, category, price, availability, and a real attribute set, ideally exposed as schema.org Product markup in the HTML a crawler receives, not just rendered client-side after JavaScript runs. Guides aimed at exactly this problem now put the bar at a fully attribute-rich, schema-tagged record per SKU, and warn that a mismatch between what's in the structured data and what's on the page is enough to get a listing dropped from consideration — Google's own shopping infrastructure already enforces that consistency check, and agents built on top of it inherit the same intolerance for contradictory data.

The volume argument is no longer hypothetical. Google is processing over a billion AI-shopping-related queries a month, and Gartner's own survey research puts AI use in a recent B2B purchase at 45% of buyers already, with Gartner separately projecting agents will handle a majority of B2B buying process steps within a few years. Buyers still validate with a rep before signing — Gartner's own numbers put that at 69% — but the shortlist the rep is validating gets assembled by the parse, not the pitch. If your SKU never enters that shortlist, the rep never gets the call.

What we actually measured

This is the argument Anglera built the Digital Readiness Index to test. Rather than survey distributors about their digital strategy, we measured their live sites directly — four pillars, fourteen signals, 100 points, no self-reported input, scored the way a crawler or an agent would encounter the page. Product Data Depth and structured Machine & Agent Readiness together carry more than half the score, because those are the two pillars that determine whether a SKU is parseable at all.

The results, published in the Top Distributors 2026 index, are not flattering. Across the distributors we could measure, the median score was 58 out of 100. Only about one in five carried Product schema.org markup in the server-rendered HTML a crawler actually gets — the majority render it client-side, if at all, which means most agent-facing tools never see it. Roughly a third exposed a GTIN or standard identifier an agent could match against a manufacturer catalog. A number of otherwise-large distributors failed the cheapest signal in the entire framework: a sitemap that resolves. That's not a strategy gap. That's a site that a crawler, let alone a purchasing agent, cannot fully find.

None of this required guessing at anyone's internal roadmap. It's what's sitting on the public page today, and the full methodology is published so any distributor can check its own score against the same fourteen signals.

The move is not a new storefront

The instinct DSG's coverage tends to provoke — a UCP integration project, an AI-commerce task force, a rebuilt PDP template — is a bigger initiative than the problem requires. An agent doesn't care about your storefront's design system. It cares whether SKU 4471-B has a real name instead of a part number, a published price, a complete attribute set, and schema markup that says so in the HTML. That's a catalog-completeness problem, and it's solvable SKU by SKU without touching the site's front end at all.

Practically, that means treating this quarter as a data sprint, not a platform migration: audit attribute depth against the pages that are actually thin, add Product JSON-LD to the templates that are missing it, publish the sitemap that's silently broken, and stop gating pricing behind a login where the product itself isn't restricted. None of it requires ripping out the commerce platform or the PIM already in place.

That's the wedge Anglera is built around — a layer that sits on top of whatever PIM a distributor already runs and does the SKU-level enrichment work of getting attributes, identifiers, and structured markup complete, without a rip-and-replace project. Most distributors can get a flat file moving through it in about a month. The agents are already parsing. The only question this quarter is whether there's anything for them to read.