Fashion & retail: search that understands your references
“Wool turtleneck sweater size 38”: four pieces of information in four different vocabularies. One single query.
The problem, specifically in this industry
Fashion vocabulary mixes product family, cut, material, color, size, and season — often in no fixed order and with brand-specific abbreviations. An engine that treats the phrase as a bag of words doesn't know that “UK 10” is a size and not a reference, or that “turtleneck” is a cut attribute and not a distinct product.
What Heurix understands in your references
The mode rule pack activates when you pick this industry, at indexing time. It produces these annotations, each becoming a usable filter:
| Annotation | What it isolates |
|---|---|
TAILLE_38 | the size, distinguished from a model number |
COL_ROULE | the collar cut |
MAT_LAINE | the material |
SAISON_AW25 | the season, in professional format |
JEAN_T38_W30 | clothing size and jean size reconciled |
On real references
| Indexed reference | What the engine extracts |
|---|---|
| Merino wool turtleneck sweater, size 38 | FAM_PULL · COL_ROULE · MAT_LAINE · TAILLE_38 |
| Slim faded jeans W30 L32 | FAM_PANTALON · COUPE_SLIM · FINITION_DELAVE · TAILLE_30_32 |
| Striped cotton shirt AW25 | FAM_CHEMISE · MOTIF_RAYURES · MAT_COTON · SAISON_AW25 |
The trap a generalist engine falls into
A customer searches “red sweater size 38”. Your listings say “burgundy”, “size UK 10”, and “knit”. Three vocabulary gaps, and an empty result on a product you have in stock.
Why the pack changes the outcome
The fashion pack handles these vocabulary equivalences natively, and you add your own — house color names, collection abbreviations — via Custom Rules, with no regex to write.
🔧 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.