CASE · AI-AGENT COMMERCE READINESS · 10-DAY FIX
Four AI agents said it was backordered.
It wasn't.
Home Elegance USA sells 30 furniture brands across the US on a 30,855-product Shopify store. Traffic was fine. Google was fine. But shoppers who asked an AI assistant about a product got told it was backordered — on items sitting in stock. In 10 days we diagnosed the template bug behind it, shipped five fixes, and re-tested with the same 20-cell rubric. Every agent stopped saying "backordered." Three now explicitly confirm "In stock."
4 of 4 agents said in-stock furniture was backordered.
We tested the boring way: five buyer questions across four agents — ChatGPT, Gemini, Perplexity, Claude. 20 cells, scored, dated, repeatable.
Baseline (27 June 2026): 4 of 4 agents asserted that an in-stock item was backordered or unavailable. 0 of 4 confirmed "In stock." ChatGPT went further — it diagnosed the store's own site as broken, then recommended competitors instead. Gemini invented a fact: it told users the retailer was the wholesale brand it carries, and therefore "cannot sell" one of its actual brands. Wrong entity, wrong catalog, confident tone.
That last one matters. An agent that misidentifies who you are will confidently answer questions about you using someone else's facts.
Two lines of template logic. Nothing to do with inventory.
The product template rendered a "This item is backordered" sentence into the page HTML unconditionally — the condition it should have checked wasn't wired up. The real inventory status was painted in by JavaScript after page load.
Humans saw "In stock" because their browser ran the JS. Crawlers read the served HTML — where the only stock sentence present was the backorder one. Every agent read the page correctly. The page was lying.
This is why this is an agent-commerce problem, not an SEO problem: an AI agent's view of your store is the raw HTML, not the rendered page. Anything your theme paints in with JavaScript may as well not exist. Anything hardcoded in the template is treated as fact, even when your admin says otherwise.
Five fixes in 10 days.
- Backorder sentence made conditional; stock status server-rendered so agents read the true state from HTML (the paid objective).
- Page titles and meta rebuilt word-safe at the theme layer — undoing an SEO app's AI "one-click fix" that had truncated titles mid-word ("...Furnitu") across a catalog it flagged at 4,959 pages.
- JSON-LD deduplicated. brand re-attached to Product via a shared @id. Theme and SEO app had each been emitting their own Product/Organization/Breadcrumb nodes — competing graphs, agents picking the one with no brand.
- Review collection and AggregateRating wired live. Ratings are the field agents quote most in shopping answers.
- FAQ schema — 13 buy-intent questions covering shipping, returns, brands, location, and financing. Agents answer from the page or they guess.
Same 20 cells, same rubric, 12 days later.
Re-test on 9 July 2026, same query set, same scoring. Every agent stopped asserting backorder. Three now explicitly confirm "In stock." ChatGPT's own words on re-test: it had "crawled within the last week" and the page "explicitly shows the availability as In stock." The Gemini brand-entity hallucination — correct product, correct price, correct retailer — is gone.
AI Visibility Score (our rubric) moved from 5/10 to 7/10.
Correctness fixes, not ranking fixes — and we're saying so.
Category visibility stayed flat: 4/12 → 3-4/12. Ask "best affordable luxury furniture" and the store still mostly doesn't surface. Competitors still rank for its own brand keywords. That's the expected result. The five fixes were correctness fixes, not ranking fixes. When an agent describes you, it now describes you accurately. Whether it picks you in a competitive answer is a different mechanism — reviews, entity authority, third-party corroboration — and that's a 4–8 week arc, not a 10-day one.
Two more honest notes: one agent (Claude) still couldn't retrieve the product pages at all — we verified both URL forms return HTTP 200 with correct content and that robots.txt blocks no AI crawler; a coverage gap on the retrieval side, nothing to fix. And Perplexity invented a number — quoted a 25% restocking fee when the policy is 20% and "25%" appears nowhere on the site. That's the argument for the FAQ work in one line: when a site states a fact clearly and repeatedly, agents have less room to make one up.
Agents saying backordered
Every AI shopping agent stopped asserting an in-stock item was backordered.
Agents confirming In stock
Three of four now explicitly confirm availability. Claude retrieval still gapped.
AI Visibility Score
Same 20-cell rubric, 12 days apart. Dated, repeatable, client-verified.
Also from this client
AGENTS DESCRIBING YOU WRONG?
Same 20-cell teardown
for your store.
The same reproducible AI-agent commerce-readiness audit we ran for Home Elegance USA. Baseline, fix list, re-test.