Wine & spirits: search that understands your references
The vintage isn't a detail: 2015 and 2016 are two different wines, two prices, two availabilities.
The problem, specifically in this industry
A wine listing carries an estate, an appellation, a vintage, a bottle format, an alcohol level, and sometimes a farming method. The vintage is a four-digit number a generalist engine confuses with a reference or a price. The format changes everything too: a magnum isn't a standard bottle.
What Heurix understands in your references
The vins rule pack activates when you pick this industry, at indexing time. It produces these annotations, each becoming a usable filter:
| Annotation | What it isolates |
|---|---|
MILLESIME_2015 | the vintage, distinguished from any other number |
FORMAT_MAGNUM | the bottle format |
DEGRE_13 | the alcohol level |
COULEUR_ROUGE | the color |
ELEVAGE_BIO | the farming method |
On real references
| Indexed reference | What the engine extracts |
|---|---|
| Château X 2015 - Magnum | MILLESIME_2015 · FORMAT_MAGNUM · COULEUR_ROUGE |
| Brut Crémant 2019, biodynamic | MILLESIME_2019 · TYPE_MOUSSEUX · ELEVAGE_BIODYNAMIE · MOUSSEUX_MILLESIME_2019 |
| Oak-aged white, 13% | COULEUR_BLANC · ELEVAGE_FUT_CHENE · DEGRE_13 |
The trap a generalist engine falls into
A customer searches “magnum 2015”. Without vintage or format recognition, they get every wine containing “2015” anywhere — including a $20.15 price or an internal reference code.
Why the pack changes the outcome
The wine pack isolates vintage and format as filterable attributes, not as text. You can then offer an “all magnums” or “2015 vintage” page without building the taxonomy yourself.
🔧 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.