Home / Resources / FMCG Shelf Space

How Indian FMCG brands are losing shelf space to AI recommendation engines

"What's the best detergent for hard water?" "Which protein bar has the least sugar?" "Suggest a budget-friendly face wash for oily skin." Every one of these used to end on a supermarket shelf or a Google results page. Increasingly, they end inside ChatGPT, Gemini or Perplexity — with the assistant simply naming two or three brands and stopping there. If yours isn't one of them, you didn't lose a sale. You never entered the aisle.

The new shelf has no physical space constraint — and that's the problem

A physical shelf is scarce: a category buyer picks 6–8 SKUs and the rest don't exist to the shopper standing there. AI recommendation is supposed to be the opposite — infinite shelf, every brand theoretically retrievable. In practice it behaves more like the physical shelf than anyone expected. Models default to naming 2–4 brands per category in a conversational answer, because that's what reads as a helpful, non-overwhelming response. The selection criteria aren't shelf fees or distributor relationships — they're which brands the model has seen described clearly, consistently, and by multiple independent sources.

Why category leaders still get skipped

We see this pattern constantly in India-market prompt testing (see our study of 50 Indian brands, 34 of which were invisible): market share and AI visibility are only loosely correlated. A brand can dominate general trade and modern trade and still not get named when someone asks an AI assistant for a recommendation in its own category. The reasons are consistent:

• Product pages describe features, not use-cases. Models retrieve answers to questions like "best for hard water" — if your PDP never uses that phrase, you're invisible to that exact query even if the product genuinely qualifies.
• No third-party corroboration. A brand's own website claiming "India's #1 choice for sensitive skin" carries little weight. The same claim repeated across retailer listings, review sites and comparison articles does.
• Ingredient and claim data is inconsistent across platforms. Different sugar content on the D2C site vs. the Amazon listing vs. Blinkit is enough for a model to default to a competitor with cleaner, matching data everywhere.
• Regional and vernacular queries are unanswered entirely. A huge share of category questions in India are asked in Hinglish or regional language phrasing that FMCG content teams never write for.

What "being on the shelf" actually requires

The compounding risk for FMCG specifically

FMCG has a trait that makes this more urgent than most categories: purchase frequency is high and switching cost is low. A shopper who gets a confident AI answer naming a competitor has no friction stopping them from just buying that instead — no long sales cycle, no contract to break, no habit to overcome beyond next week's restock. Every category question an assistant answers without naming you is a small, repeatable leak, and it repeats at the pace people actually reorder shampoo, snacks or detergent — weekly, not annually.

Where to start

Don't try to fix every SKU and every claim at once. Start with your highest-volume category question, get the entity data consistent everywhere it appears, publish one clear use-case page that directly answers it, and get it corroborated in at least one third-party comparison piece. Re-run the prompt panel in four weeks. This is the same six-lever method we lay out fully in our Complete Guide to Generative Engine Optimization.