01
The native engine indexes, it doesn't understand
It ignores typos, the synonyms of your trade, and the order your products should come out in.
The engine
A proprietary search and indexing engine.
Heurix is not a layer on top of Algolia or Elasticsearch: it's our own engine, built in France, specialized in technical catalogs. Where generalist engines compare characters, Heurix reads the structure of your references.
The demo at the top of this page runs on this engine: the numbers on the right are measured, not promised.
benchmark_index10,000 refs
median_query_time≈ 10 ms
typo_tolerance2/word · 1/reference
rulepacks11 sectors, extensible
custom_rulesself-service, no regex
annotations2-level cascade
rankingrelevance > stock
group_by6,582 results → 52 families
conversion_roiHeurix Tracker — real visitor attribution
browse_discoveryprice, margin, popularity, manual merchandising
One reference, many ways to search for it
A product reference is never a random string of letters: it is several pieces of information compressed into one: family, dimension, material, standard. Heurix separates them, and your customer finds the product by any fragment, in any order, with or without typos.
The demo at the top of this page runs on that engine: the figures above are measured, not promised.
Nothing for you to write: eleven sector rule packs activate when you pick your sector. A term specific to your catalog? Add a Custom Rule from the console, describing what it should recognise. The mechanism is documented in full.
The sectors where this approach changes the most
The larger a catalog or content base, the more a well-tuned search matters, because native search fails exactly where precision is needed most.
Tools & hardware
Tens of thousands of references, standardized product codes (DIN, ISO), need to filter by dimension, material, compatibility.
Dedicated pack: hardware
Spare parts & industry
Search by manufacturer reference or equivalence, tolerance for multiple code formats depending on the supplier.
Dedicated pack: industry
And yours?
If your customers search by reference, dimension, or variant, the engine adapts. Tell us about your catalog.
≈ 10 ms
Instant response
Median engine response time, measured on a 10,000-product catalog. Every millisecond of latency costs conversions.
2 typos
Tolerated per word
"pul rond red neck" still finds red crewneck pullovers. Just one on references: change a single digit, and it's a different product.
$0
To get started
14-day free trial on the Search API: up to 2,000 requests and 2,000 products, no credit card. See pricing.
Up and running in 3 steps.
No plugin, no rebuild: your catalog, one API call, and the engine does the rest.
Index your catalog
One API call is enough: the catalog is created automatically, with your industry's rule pack (hardware, fashion, industry).
The cascade annotates every product
"M8 x 20 — A2", "M8x20 stainless screw", "m8x20 A2": three spellings, one product recognised. Your customers' queries go through the same rules as your product records. Matching happens on meaning, not on form.
Your customers find
Despite typos, despite different spellings, sorted by relevance then availability. And every result explains why it matches.
See the technical docs →
The full endpoint reference is in the API documentation. Integration guides with real code for Shopify, PrestaShop, WooCommerce, and Magento — plus, for PrestaShop and WooCommerce, a beta module provided on request.