As of 5 November 2026, the holiday picture for online retail is unusually well quantified. Adobe expects US online holiday spending to reach a record 275.1 billion dollars in November and December, and Salesforce expects 20 percent of holiday e-commerce traffic to originate from AI chat agents. The same research stream contains a less comfortable number: 41 percent of multichannel retailers report inconsistent pricing across channels, and 40 percent report inventory that is not synced in real time. Those two gaps are precisely what an AI agent checks first, which turns a back-office reconciliation problem into a visibility problem.
Four numbers that explain the risk
The pricing inconsistency figure is the one that should worry brand teams most, because an AI agent does not average prices, it compares them. If a marketplace listing shows a promotional price while the brand store shows list price, the agent may describe the product as available at a discount in one place and at full price in another, in the same answer. The shopper sees a contradiction before ever reaching a checkout page, and the cheapest interpretation usually wins the click.
Why product pages fail the machine-readability test
Adobe found US retail product pages average 66 percent machine readability, the lowest of any page type. The cause is rarely missing content; it is content that exists only for humans. Price rendered by a script, availability loaded asynchronously, size and compatibility buried in an image, promotional terms described in a banner rather than in structured fields. An agent that cannot parse those values has to guess or skip, and skipping means the product does not enter the shortlist.
Where price gaps come from
Most cross-channel price gaps are not pricing strategy; they are timing. A marketplace promotion ends at midnight, a brand site discount starts in the morning, a coupon is applied by the retailer rather than the brand, and a reseller holds old stock at an old price. Each event is small, but together they mean the same SKU carries four different prices across four surfaces on the same day. During a peak week, that is the normal state rather than the exception.
| Gap type | Typical cause | What an agent sees | Control |
|---|---|---|---|
| Promotion timing | Different start and end times | Two prices in one answer | Shared promotion calendar |
| Coupon stacking | Retailer-funded coupons | A price the brand never set | Coupon registration rules |
| Reseller pricing | Old stock, unauthorised sellers | Price below the floor | Authorised seller monitoring |
| Currency or tax display | Regional settings | Prices that look inconsistent | Normalised feed fields |
Inventory sync is the second failure point
An agent that recommends an out-of-stock product creates a worse experience than one that ignores it, because the shopper arrives at a dead page. With 40 percent of multichannel retailers reporting inventory that is not synced in real time, this is not an edge case. The practical fix is not to sync everything; it is to sync the priority assortment at the frequency it actually changes, and to publish availability in a field an agent can read rather than in a banner a human can read.
What to fix before the peak week
The order of work matters more than the size of the programme. Start with the two hundred products that carry the holiday plan, because a clean dataset on those beats a messy dataset on the whole catalogue. Then fix the fields an agent reads first: price, availability, shipping cutoff and return terms. Finally, check what the agent actually says, using the same questions a shopper would ask, and compare the answer against the page.
Brands already running product feeds for search and social have most of the raw material. The gap is usually governance rather than technology: who owns the field, how often it is refreshed, and who is accountable when a price changes in one channel and not another. Without that ownership, feed quality decays within weeks of any migration or site update.
Verification checklist
Four steps sit below, each producing an artefact that can be re-run after the peak season rather than a one-off audit. The aim is a repeatable read on three questions: is the brand describable, is it priced consistently, and is it purchasable at the moment an agent recommends it. None of the steps requires a new platform, only ownership and a fixed cadence.
FAQ
Does an inconsistent price across channels really affect AI answers?
Yes, because an agent reads whatever surface it can parse. If one surface shows a discount and another shows list price, the answer can contain both, and the shopper resolves the contradiction by choosing the lower one or leaving. The risk is not the price itself but the ambiguity.
What does machine readability mean in practice?
It means the values an agent needs are present as text in structured fields rather than rendered by scripts or embedded in images. A price inside a JavaScript widget, or a size chart inside a JPEG, is effectively invisible. Fixing this is usually a templating change, not a replatforming project.
Should brands optimise for AI agents or for shoppers first?
Both, and the work overlaps. The fields that make a product describable to an agent, such as size, compatibility, availability and price, are the same fields shoppers use to decide. Cleaning them for machines tends to improve the human page as well, which is why the investment is rarely wasted even if AI traffic disappoints.
How should AI referral traffic be measured?
Treat it as directional rather than exact. Referrals from assistants often appear in analytics as branded search or direct traffic, so the reliable signal is a combination: visibility in tracked questions, then product page traffic, then add-to-cart, then revenue. Any single metric can mislead during a peak week.
