FEATURES · SEARCH + FILTERS
Everything it does,
written out one by one.
This is not a how-to: it is the inventory. If you are wondering whether Dropfind does one particular thing, the answer is on this page.
Everything below is configured from the PrestaShop back office. No console, no files, no touching your theme.
The technical names sit under each function, in case you recognise the Typesense parameter behind it.
DROPFIND SEARCH
Finding what the customer meant to type
PrestaShop's native search runs LIKE '%text%' against the database: either the string matches or there is no result. Here the engine is Typesense, and that changes what is possible.
«snekaers», «trosuers», «lighbulb»: corrected on the fly against your own catalogue, not against a dictionary. How many typos are tolerated is adjustable, and in the broad mode it goes up to two.
num_typos · typo_tokens_threshold
Prefix search: products appear from the first few letters, with no need to finish the word or press enter. And with the cache on your own server, typing a whole word costs five requests for the first visitor and zero for the rest.
prefix
What wins when the word appears in several places. Out of the box the reference and the EAN weigh more than the name, and the name far more than the description. It is changed field by field from the panel.
query_by · query_by_weights
Name, reference, EAN-13, combination references, combination text, manufacturer, categories and short description. Searching by the code of one specific size works.
When what was typed looks like a code, typo correction switches off. Without this, searching for PNRB15 returned PNRB18 because of a typo nobody made. Prefix autocomplete stays alive: PNRB still brings back PNRB3, PNRB6, PNRB12.
DROPDOWNSEARCH_REFERENCE_MODE
Strict: no prefix and no dropping words, for technical catalogues. Balanced (default). Broad: two typos, and it may drop one word from the query rather than return nothing.
DROPDOWNSEARCH_MATCH_MODE
«When somebody searches for gift, these products first.» They are written per term and per product id. They deliberately do not ship preloaded: the ids of one shop mean nothing in another.
DROPDOWNSEARCH_BOOST_RULES
The vocabulary your customers search with that is nowhere in your product pages: «bulb» = «lamp», «jumper» = «hoodie». And the statistics panel tells you which ones are missing, because searches with no results are usually exactly that.
DROPDOWNSEARCH_SYNONYMS
When there is nothing to return, it suggests the nearest query that does have results in your catalogue, instead of leaving the screen blank.
DROPDOWNSEARCH_DID_YOU_MEAN
Whoever types a product's full name sees it at the top, and where the word sits inside the name counts: «dining table» beats «table leg».
prioritize_exact_match · prioritize_token_position
At equal relevance availability wins, and then the shorter name. Showing what is sold out first is the quickest way to lose a sale you had already made.
sort_by
From how many letters searching starts, and how many products fit in the dropdown.
MIN_QUERY_LENGTH · PAGE_LIMIT
DROPFIND SEARCH
How it looks, and how much it looks like your shop
Desktop and mobile are configured separately. What works on a 27″ screen almost never works on a six-inch one.
You tell it which search box your theme has —a CSS selector— and Dropfind mounts on top of it. It does not replace the template nor force you to change theme. Separate selector for mobile.
INPUT_SELECTOR · INPUT_SELECTOR_MOB
And different on mobile from desktop, if you like. With an adjustable dropdown width.
LAYOUT_MODE · LAYOUT_MODE_MOB · DROPDOWN_WIDTH
Also separately on each device. Out of the box: grid on desktop, list on mobile.
RESULTS_LAYOUT · RESULTS_LAYOUT_MOBILE
Image, price, reference, EAN, stock status and an add-to-cart button. Each one switches on or off.
SHOW_IMAGE · SHOW_PRICE · SHOW_REFERENCE · SHOW_EAN · SHOW_STOCK · SHOW_CART
Primary, secondary, links and prices. And if your theme does something odd, a block of your own CSS loaded after everything else.
COLOR_* · CUSTOM_CSS
Uploaded from the panel, in whichever layout you choose — or none at all.
LOGO_MODE · LOGO_FILE · LOGO_LAYOUT
Before anything is typed —and optionally when there are no results— you can show featured products, a banner with a link, or both. It is the most-seen space in the search box and out of the box it is blank.
EMPTY_MODE · EMPTY_PRODUCTS · EMPTY_BANNER_*
Every text the shopper sees is a PrestaShop translation string. There is no closed list of languages: whichever one you have set up in the shop gets translated.
DROPFIND SEARCH
The catalogue, the prices and what it costs
Two modes: the indexed price (fast, served straight from the index) or the exact price computed by PrestaShop on the spot, which respects specific prices, customer groups and taxes. The same setting governs search and filters.
DROPDOWNSEARCH_PRICE_MODE
Repeated queries never leave your shop again: they are served from disk. Typing a word goes from five requests to zero for the second visitor. With configurable expiry and a file cap, and a generation-based invalidation that never makes you delete anything by hand.
CACHE_ON · CACHE_TTL · CACHE_MAX_FICHEROS
You save a product and it is queued; the cron rebuilds it in full from the database. Editing the same product ten times indexes once, and a retry duplicates nothing. Adjustable batch size.
INGEST_BATCH
Languages are not capped by plan. The ones you do not index take up no room, so leaving out a language nobody uses moves you down a tier.
LANG_SEL
You decide: either the search falls back to PrestaShop's native one, or it switches off. And the warning reaches your back office before anything happens.
OVER_LIMIT_MODE
What gets searched, what finds nothing, what gets clicked and what ends up in the cart. The whole funnel, in the back office. Searches with no results are your pending synonym list.
ANALYTICS_ENABLED · SEARCH_METRICS_LOGGING
The module is not installed from Addons, so PrestaShop would never warn you. It does it itself, from its own panel.
Verified range. Multistore included.
DROPFIND FILTERS
Category filters, against the index
Native filters compute every count with queries against your database, and that is why a crawler walking through combinations brings the shop down. Here the counts come from the same index as the search.
Zero queries against your database per filter applied. The load does not grow with the number of combinations somebody decides to walk through.
Categories, manufacturer, attributes, features and price. And within the features, which of your groups take part: decided at index time, not on every query.
DROPFINDFILTERS_FACETS · FACET_FEATURES
Side column, fixed dropdown or floating dropdown. With an adjustable number of groups visible before the «show more».
LAYOUT · GROUP_LIMIT
Values as clickable tags or as a list with checkboxes, with a cap on values visible before the «+».
VALUE_STYLE · CHIP_LIMIT
And the limits come from the real catalogue, not from a number typed in by hand.
It can render the thumbnails with your theme's template, with its own, or work it out by itself. With the container, the product classes and the result counter all targetable by selector.
CARD_MODE · CONTAINER · PRODUCT_CLASSES · COUNT_SELECTOR
Two filter blocks at once is confusing. Whatever is left of the previous module gets hidden, with extra selectors if your theme is unusual.
HIDE_RIVAL · HIDE_RIVAL_SEL
The default hook or the one you name, plus an unhooked mode to place it by hand. Your own CSS too, as in Search.
HOOK · UNHOOKED · CUSTOM_CSS
Filters is not charged separately. It shares the index and the plan with Search: if you have an account, you have it.
And about crawlers: the module publishes a
robots.txt with the filter combinations excluded, so that Google does not spend its time walking a space nobody is interested in.
Is something missing from this list?
If you need a feature that is not here, say so. The settings catalogue has grown almost entirely out of merchants' requests.