Hardware & tools: search that understands your references
An M8x20 screw and an M8x25 screw have nothing in common for your customer. They look nearly identical to a generalist search engine.
The problem, specifically in this industry
Your references encode a dimension, a material, a standard, and a head type into one compact string: “M8 x 20 - Stainless A2, DIN 933.” An engine that compares characters judges “M8x20” very close to “M8x25” — two products no one confuses on the shop floor. The error doesn't show up in your search stats: it shows up as a return.
What Heurix understands in your references
The outillage rule pack activates when you pick this industry, at indexing time. It produces these annotations, each becoming a usable filter:
| Annotation | What it isolates |
|---|---|
DIAM_M8 | the diameter, isolated from the reference |
LONG_20 | the length, distinguished from the diameter |
MAT_INOX | the material |
TETE_HEX | the head type |
NORME_DIN933 | the standard, recognized with or without spaces |
On real references
| Indexed reference | What the engine extracts |
|---|---|
| M8 x 20 - Stainless A2 | DIAM_M8 · LONG_20 · MAT_INOX · FAM_VIS |
| Screw TF DIN 7991 M6x30 zinc-plated | DIAM_M6 · LONG_30 · NORME_DIN7991 · TETE_FRAISEE |
| Hex nut M10 brass | DIAM_M10 · MAT_LAITON · TETE_HEX · FAM_ECROU |
The trap a generalist engine falls into
A customer types “screw m8 20 stainless” with no hyphen or “x”. Another types “M8X20” in solid capitals. A third searches “DIN933” with no space. All three mean the same product — and an unprepared engine returns three different results, or none at all.
Why the pack changes the outcome
The hardware pack recognizes these variants from the very first import, with no rule for you to write. On a generalist engine, you'd have to define the pattern for each reference family yourself, test it, and maintain it with every new product line.
🔧 A term specific to your catalog that the pack still misses? Add your own Custom Rule from the console, simply describing what it should recognize — no regex required.
Going further
The getting started guide covers the full setup, from sign-up to your first indexed catalog. The documentation details every endpoint.