Get found on-store
Discovery Prompts: the future of ecommerce search
By Ankit Minocha, founding team at Atomz. Updated January 21, 2026.
Site search returns a database query pretending to be discovery. Discovery Prompts guide a shopper from a vague intent to the right product, the way an AI assistant already does.
Most site search does not understand what a shopper means. When someone types 'dress' they get hundreds of results, and when they try 'something for a beach wedding' they usually get nothing useful, or the same hundreds of dresses again. That is a database query wearing the costume of search, and shoppers have stopped accepting it because they now have something better to compare it to.
When a customer asks ChatGPT what to wear to a summer wedding, they get a short, reasoned list, not eight hundred links. That is the standard they bring back to your store, and a search box that cannot meet it feels broken even when it is working exactly as built.
What a Discovery Prompt is
A Discovery Prompt is a suggestion that carries intent, shown before the shopper has to guess the right keyword. When someone lands on the page they might see 'beach wedding guest,' 'casual summer dress,' or 'date night outfit,' and clicking one returns products that match the occasion instead of the word.
These are not the autocomplete terms scraped from past searches. They are generated from your real catalog and the attributes on it, from what converts, and from the context of what the shopper appears to be looking for right now. The difference shows up in the numbers.
| Traditional autocomplete | Discovery Prompts | |
|---|---|---|
| Source | Past search strings | Catalog attributes and conversion data |
| Matches on | The keyword typed | The intent behind it |
| Handles "beach wedding guest" | Returns the same long list | Returns occasion-appropriate products |
| Click-through on suggestions | Around 3 to 5% | 25%+ across Atomz merchants |
That is not a marginal lift on the same idea. It is a different category of behavior, because the shopper is being guided instead of interrogated. Your own numbers will move with catalog quality, traffic mix, and where the prompts sit, so the audit is the honest place to see your starting point.
Why this is the same engine as AI shopping
The reason a Discovery Prompt works is the reason ChatGPT shopping works. The shopper expresses intent, the system reads the meaning, and it answers with products and a reason. Stores that win inside AI assistants are the ones whose catalog supports intent matching, and Discovery Prompts build that same muscle on your own storefront using the same logic on a different surface.
The engine underneath has two parts. The Discovery Agent reads your catalog, understands what each product is for, and generates prompts that map to real products and collections, adapting as conversion patterns and inventory change. Catalog Genius does the work that makes any of it possible, enriching each product with use case, material, fit, and the other attributes that give a prompt something concrete to point at, and normalizing variants so size and color do not become keyword noise.
The mechanism
A prompt is only as good as the catalog under it. 'Beach wedding guest' can return the right dresses only if the dresses carry occasion, fabric, and fit as structured attributes. Fill those fields and the prompt has something to match, but leave them empty and it has nothing.
The bottom line
Keyword search makes the shopper do the work of translating what they want into the words your index happens to hold. Discovery Prompts do that work for them, which is exactly what an AI assistant does and exactly what your customers now expect. Get intent right on your own store, and you are already speaking the language of agentic discovery.
Subscribe to The Agentic Operator