9 ms
What one search takes on a real catalogue of 1,859 products.
PRESTASHOP · TYPESENSE
A search engine
you can audit.
See where every result comes from and tune it yourself. It installs like any other module and answers as you type.
no card · uninstalls in one click
- 9 msper search
- 0,6 %of CPU at full load
- 1.7.6 – 9.0PrestaShop
- 7.3 – 8.4PHP
how it sits on a shop · two integrations, on a loop
0.6%
Of CPU with the server at full load. That copy of your catalogue lives entirely in memory, on our servers: when someone searches, ours is the machine that works. Yours only paints what already comes solved.
What it is built with
Nothing exotic, and nothing your hosting does not already have. The only new piece is the search engine, and we host it.
PrestaShop 1.7.6 – 8
It installs like any other module, from the back office. No composer, no shell access.
Typesense
The engine. It keeps the index in memory and handles typos. It runs on our infrastructure, not yours.
PHP
Whatever your shop already runs. It does not force you to change version in order to install it.
Smarty, your template
Product cards are painted with the product template your theme already uses. There is no second design to maintain.
JavaScript, no libraries
Zero dependencies added to your shop's front end. No extra jQuery, no whole framework just to paint a list.
And it tells you what they searched for and did not find.
Every search with no results is recorded. It is the literal list of what your customers came to buy and was not in the catalogue —or was, under another name.
What it does, plainly
Three things Dropfind does that your shop's search does not do today.
It finds what they meant
It tolerates typos and puts the product ahead of the accessory that mentions it.
It filters without drowning your server
The count for each option comes from the index, not from your database.
It shows you where you lose sales
Every search with no results is someone who wanted to buy and did not find it.
When they misspell it, or call it something else
PrestaShop's native search compares words. Dropfind understands that almost nobody types a product's exact name.
With typos
«charjer», «lightbuld», «keybord». What they wanted comes up, instead of an empty page that hands the sale to another shop.
By reference or EAN
Whoever arrives with the code in hand pastes it and the exact product appears. Each combination's code too, not just the parent's.
The product before the accessory
Searching for a model brings up the model, not the ten cases that name it in their description.
And in your own words
If your trade says it two ways, you declare it as a synonym and both lead to the same place.
And you can see why each result is there
This is the difference that gives this page its title. Every field —name, reference, EAN, brand, category, description— carries a weight, and you set that weight from the back office. Raise the weight of the reference if the reference is what rules in your shop.
There is no black box deciding for you that you cannot question. If a product shows up where it should not, you can see why and fix it.
HOW IT WORKS
Four steps and it is searching
No migration, no touching your database and no second template to maintain.
-
01
Your catalogue is copied to an index
Names, references, barcodes, prices and photos are copied to an index that lives on our servers, not yours. It keeps itself up to date: every time you change a product, the change travels there.
When someone searches, the question goes to that index. Your database never hears about it, and that is why your shop does not suffer however many searches there are.
-
02
It opens over your shop
Full screen or hooked onto the search box your theme already has. You choose which, and you can change your mind without touching a line of template.
-
03
It answers as you type
No waiting and no page reload. The cache lives on your server, so anything repeated is not queried again —and does not count as a request.
-
04
And you decide the order
Each field's weight is set from the back office. If someone searches a reference, the reference rules. And you can see why each result came up.
And the filters, included
Category filters are your shop's second search engine, and in PrestaShop they are also the usual reason it falls over when a crawler walks through them.
Dropfind Filters does that work in the index. It is in every plan.
See Dropfind Filters
Size ▾
Colour ▾
Price ▾
Brand ▾
68 products · 0 queries to your database
PRICING
Pay for the room you take
A record is one product in one language. That is the only axis, and every feature is in every plan.
Monthly
Yearly
save 20%
STARTER
€/month€/year
€19.00 a month, or €182.40 a year (€15.20 a month).
no lock-inworks out at €15.20/month
- 3,000 records1,500 products in 2 languages
- As many languages as you like
- 100,000 requests/month
No card!
Most chosen
GROWTH
€/month€/year
€34.00 a month, or €326.40 a year (€27.20 a month).
no lock-inworks out at €27.20/month
- 12,000 records4,000 products in 3 languages
- As many languages as you like
- 250,000 requests/month
PRO
€/month€/year
€59.00 a month, or €566.40 a year (€47.20 a month).
no lock-inworks out at €47.20/month
- 35,000 records8,750 products in 4 languages
- As many languages as you like
- 600,000 requests/month
−40%
SCALE
€/month€/year
€89.00 a month, or €854.40 a year (€71.20 a month).
no lock-inworks out at €71.20/month
- 75,000 records18,750 products in 4 languages
- As many languages as you like
- 1,500,000 requests/month
CUSTOM
Above 75,000 records, on your own server or with multistore. It is not one more rung on the ladder: it is another way of setting it up, with a fixed quote.
A record is one product in one language. A catalogue of 5,000 products published in Spanish and in French is 10,000 records. It is the only thing charged for, because it is the only thing taking up room: if you stop indexing a language, you drop a tier. A request is each query to the index —searching and filtering count the same— and the module keeps the results on your server, so repeats cost nothing.
What counts as a request, how to pick a plan and how to start →
What counts as a request
A request is each query to the index. And anything served from your own server's cache never travels, so it does not count.
Search · 1
A search that reaches the index counts as one.
Filter · 1
A category filter costs the same as a search. That is why the unit is called a request and not a search: otherwise the counter would climb without anyone having searched.
Typing letter by letter · 5 → 0
Measured typing one word: five requests for the first visitor, zero for the next ones with the same text.
Repeat · 0
A category seen twice goes from 1 to 0, and a filter state from 3 to 0. The cache lives on your server, so the saving is yours.
Your catalogue picks the plan
What really costs money to serve a shop is holding it in memory: 13.1 KB measured per record. Searching costs almost nothing —with the server at full load the CPU sits at 0.6%. That is why the ladder has a single axis: records. Charging separately for products and for languages billed the same space in memory twice, and punished whoever translates twice over.
Something useful follows from that: languages are not limited. Spread your records however you like —many products in one language, or fewer in five— and choose which ones you index from the module itself.
What is in the plan does not depend on size: every feature is in every plan. What changes is how much catalogue fits. See every feature →
If you get close to the ceiling you are warned in your back office, before anything happens.
← Back to the plansHow to start
No sales call and no migration. Four steps and the search is running.
1 · Thirty days
Free and without a card. If it does not convince you, you have left nothing behind.
2 · Install
You upload the module from the back office, like any other. No shell, no composer.
3 · Index
You paste your key and it takes the catalogue to the index. From there it keeps itself up to date.
4 · And if you do not carry on
The monthly plan is cancelled whenever you like. You uninstall the module and your shop goes back to its usual search.
