ChatGPT shopping · Jun 26, 2026 · 3 min read

Why AI Assistants Get Your Products Wrong (and How to Catch It Before Shoppers Do)

Stale crawls, variant blindness, facts trapped in images, policy drift — the five failure modes behind AI assistants misdescribing products, with the probe routine that catches them.

A shopper asks ChatGPT about your bestseller and gets a confident answer that's 20% wrong: last season's price, a discontinued colorway, a return policy you changed in January. Nobody tells you. The shopper just buys elsewhere — or worse, buys on the wrong facts and returns it angry.

We probe stores for a living, and assistants misdescribe established brands constantly. The errors aren't random; they cluster into five patterns, all fixable.

The five failure modes

  • Stale snapshots — the answer reflects your store as of the last crawl, not today. Price changes, sales, and stockouts arrive late; the model states them as present-tense fact.
  • Variant blindness — data flattened to the parent product. The assistant recommends the sold-out size, quotes the base price for the premium variant, or misses that the color exists at all.
  • Facts trapped in pixels — size charts, ingredient lists, and dimension diagrams that live in images. Invisible to most retrieval, so the model guesses from category averages.
  • Policy drift — your policy page, FAQ, and structured data disagree after an update touched only one of them. The assistant picks a truth; often the old one.
  • Borrowed identity — thin brand data forces the model to lean on third-party content: an old review, a Reddit thread, a competitor comparison. Your story gets told by whoever wrote about you last.

Why you never hear about it

These failures are silent by construction. The conversation happens on OpenAI's or Perplexity's servers; no analytics event fires; the shopper who was told the wrong thing doesn't file a ticket — they just don't arrive. The first detectable symptom is usually a support ticket that starts "but ChatGPT said…", which is the channel telling you it's been wrong for months.

The probe routine

The fix starts with detection. Build a panel of your fifteen most consequential questions — top products' fit/compatibility questions, shipping and returns, brand basics, your top three head-to-head comparisons. Run it monthly in fresh sessions across ChatGPT, Perplexity, and Gemini. Grade three things: present or absent, right or wrong, and whose sources got cited. Wrong-and-confident items are your priority queue.

Then fix upstream: push trapped facts into text and structured fields, make one policy surface canonical, complete variant data in feeds. The answers follow the data within crawl cycles.

This loop — probe, grade, fix, verify — is Kinect's AI Readiness Audit productized. We run it with your real shopper questions, verify every wrong answer against your live site, and hand you the ranked fix list. The same corrected catalog truth then grounds the AI sales rep on your storefront, so shoppers on-site get right answers even while the external crawlers catch up.

Frequently asked questions

How often do assistants' answers about a store change?

Product-level facts can shift with each crawl cycle — weeks. Brand-level narratives move slower. Monthly probing is the right cadence for most catalogs; weekly during peak season or a rebrand.

Can I just block AI crawlers instead?

Blocking removes your voice, not your presence — assistants will still answer from feeds, retailers, reviews, and forums. For a consumer brand, being absent means being described entirely by third parties.

What's the fastest single fix?

Canonicalize policies (one source of truth, everything mirrors it) and un-trap your size/spec content from images. Both are days of work and eliminate the most damaging wrong answers.

Related reading

Find out what AI is telling your shoppers

Kinect probes the assistants with your shoppers' real questions, verifies every claim against your live store, and fixes what's wrong — same-day setup, measured honestly.