Before most teams pick an autocomplete API, they want the unfiltered version: which typeahead APIs actually hold up on a storefront, whether Algolia is overkill, and whether a PrestaShop or Shopify search module is “good enough.” Those threads show up on Reddit, in Slack, and in every vendor bake-off. This article answers them directly.
This is not a roundup of comments. It is the same evaluation a search engineer ends up writing after the tenth “Algolia vs Typesense vs roll-your-own” post.
What those threads are actually asking
Most of those discussions collapse into four questions. If you can answer them for your catalog, you do not need another round of vendor screenshots.
| Thread theme | The useful test |
|---|---|
| Algolia vs Typesense vs Elasticsearch vs Meilisearch | Can you change backends later without rewriting the search bar? |
| Prefix matching looks fine in the demo | What happens on typos, German compound words, and “gift for dad”? |
| PrestaShop / Shopify / “webshop” modules | Can you keep checkout and the index, and only swap the autocomplete API? |
| Google Suggest scrapers | Are you completing Google’s queries, or ranking your products? |
You probably do not need to replace the engine
The loudest advice is “just switch to X.” That is the expensive answer. An autocomplete API can sit in front of the index you already run. SuggestAPI does that: keep Algolia, Typesense, Elasticsearch, or Meilisearch, and route the storefront search bar through one endpoint.
That is also the right model for PrestaShop and other webshops. The catalog, theme, and checkout stay. The autocomplete API is the piece that recovers typos and returns products, categories, and collections while the shopper types. See Bring Your Own Search for the adapter model.
Prefix autocomplete is why the threads stay angry
A lot of “our search sucks” posts are not engine problems. They are prefix problems. The bar completes strings. It does not rank the next useful product. A production search suggestions API has to tolerate messy input and return destinations a theme can render — not only the next few letters.
If the thread you opened is full of latency screenshots and empty of typo examples, it is measuring the demo, not the storefront.
Skip Google Suggest scrapers
“Autocomplete scraper API” shows up next to ecommerce autocomplete in search results. That is a different product: it copies Google’s public suggest endpoint. It does not know your SKUs, inventory, or merchandising rules. A storefront autocomplete API has to search your catalog.
A short checklist before you post another “which vendor?” thread
- One endpoint for the search bar, not a new index migration.
- Product, category, and collection suggestions — not phrase completion only.
- Typo tolerance on the languages your shoppers actually type.
- Merchandising so “hero SKU” is a rule, not a hope.
- A path to agent-ready responses later, without a second search stack.
That list is what we use on the autocomplete API page and in How to choose autocomplete search software. If you want to try it on your catalog, join the SuggestAPI waitlist.