Tasting menu
A tasting menu is not a list of dishes — it is one offer, priced as a whole, told in a sequence of courses. Fenómenus models it that way: one record is one complete menu.
How the record is built
A tasting menu record holds:
| Field | Purpose |
|---|---|
| Title | The name of the menu |
| Subtítulo | A short qualifier — the number of courses, the season |
| Descripción | The introduction guests read first |
| Título del bloque "Entrantes" and Contenido de "Entrantes" | The opening block |
| Título del bloque 1 to 6, each with its Contenido | The six numbered course blocks |
| Nota al pie | The footer note — VAT wording, minimum diners, allergen advice |
| Precio menú | The price of the whole menu |
| Precio maridaje | The price of the wine pairing |
The block contents are rich text, so a block can be a single dish, several lines, or a course with its own explanation.
The pairing price exists only on this menu type. It is the price of the drinks pairing offered alongside the menu, and it is shown separately from the menu price.
Several menus, one type
Each menu is its own record, so a restaurant with a short and a long tasting menu keeps them as two records:
Tasting menu — 7 courses
Grand tasting menu — 12 courses
Seasonal game menuCategories still exist for this type, and they are used to group menus when there are several — for example All year and Seasonal. With only one or two menus, a single category is enough.
Writing the blocks
The block structure is what makes a tasting menu readable. A pattern that works:
- Give every block a title guests can pronounce: Snacks, From the sea, The grill, Sweet.
- Keep the block content to the dish names and the essential detail. Guests are reading a promise, not a recipe.
- Use the blocks in order and leave the ones you do not need empty. An empty block title means the block is not rendered.
Do not paste the whole menu into the description. The blocks are what the two menu designs lay out.
The footer note
Nota al pie is the line every tasting menu needs and most forget: whether prices include VAT, whether the menu is served for the whole table, the minimum number of diners, and where allergen information can be requested. It is rich text and it prints under the menu.
Prices
Tasting menus carry no per-item prices, because nothing on them is sold individually. They have:
- Precio menú — the menu price;
- Precio maridaje — the pairing price.
That is why this type has no Excel export, no bulk paste table and no price columns anywhere.
Public design
Tasting menus use their own two designs — Menu design 1 and Menu design 2 — instead of the five item layouts. The item layouts render grids and carousels of individual dishes, which is the wrong shape for a menu that must be read top to bottom in one piece.
The choice is made when the menu type is enabled, and it applies to every tasting menu on the site.
Allergens
Allergen information can be enabled for tasting menus from Content settings → Allergens. Because one record covers many dishes, allergens assigned here describe the menu as a whole. Most restaurants combine a conservative set of allergens on the record with a clear line in the footer note inviting guests to ask.
Translations
Tasting menus have the most translatable text of any type: the subtitle, the description, every block title, every block content and the footer note are all translated per language. Prices are shared across languages. Translate a tasting menu only when its content is final — it is the most expensive record on the site to redo.