The PrestaShop search that understands your references
Test it first on your own site: search the same reference in three forms — M8x20, M8 x 20, M8-20. If one of the three doesn't return the right screw first, this page is for you.
What native search can't do
Reference spellings
Measured on PrestaShop 9.1, with a catalog that writes “M8x20”: “M8x20” finds the screw, “M8 x 20” returns nothing, “M8-20” returns the M8-40 screw. Customers only reliably find products if they type the way your catalog was entered.
A correction that swaps words silently
PrestaShop fixes typos with no floor: it replaces a missing word with the closest one in your catalog, up to five letters away. On a 177-product fastener catalog, a nonsense query like “zzzzzz” returned a ball bearing.
Short words vanish
PrestaShop ignores words under three characters, as shipped: M8, A2, 20. “M8” alone returns nothing, and in “stainless screw M8 20” only “stainless screw” is actually searched.
The integration, concretely
The mechanism PrestaShop provides for
Our module relies on ProductSearchProviderInterface, the interface PrestaShop designed for a module to supply results. Nothing is bypassed, nothing breaks on update.
Your theme doesn't change
The module decides which products come out and in what order. Your templates, faceted filters, and product pages stay exactly yours.
Automatic fallback
If Heurix doesn't respond within three seconds (default timeout, adjustable), native search takes back over. Your visitors never see a broken page.
2 to 3 days
That's the integration time observed for a catalog already exported, settings and checks included.
The module is paid: you buy it on PrestaShop Addons, and it connects to your Heurix account.