The allergen filter is wrong

The public allergen filter does one thing: it hides the dishes that carry the allergens a guest selects. Most reports come from expecting the opposite behavior, or from allergen data that is incomplete on the items themselves.

How it is meant to behave

• A guest ticks the allergens they want to avoid and selects Filter.
• The menu reloads showing only the dishes that do not carry those allergens.
• The selection is remembered in the guest's browser for 30 days, and it follows them as they move between menus.

So a dish disappearing after filtering is the filter working. A dish remaining visible is the thing to investigate.

A dish that should have been hidden is still visible

The dish is missing that allergen in its own record.

1. Open the item.
2. Look at the allergen panel in the side column.
3. Tick the missing allergen and update the item.
4. Reload the public menu and filter again.

Allergen assignments are applied to a menu item and its translations when the item is saved, so correcting the source item corrects every language.

Every dish disappears

If filtering by one common allergen empties the whole menu, the allergen is assigned to items that do not contain it. This usually happens when a batch was ticked quickly. Review the affected items individually; there is no bulk allergen editor, precisely because this information should not be applied in bulk without review.

The filter does not appear on a menu

The filter is only rendered on menu archives whose content type carries allergen information.

1. Open Settings → Restaurant settings → Content settings → Allergens.
2. Under Which types of content have allergen information?, confirm the menu type is ticked.
3. If the menu type is not ticked, its items have no allergen data and no filter.

Separately, the category navigation has its own Filters toggler, configured per menu type in Content settings → Content settings. If the toggle is off, the filter panel has no opener even when allergen data exists.

The list of allergens is wrong

The allergens offered to guests are the ones in your allergen library, not a fixed legal list.

• Add, rename or remove them under Content settings → Allergens.
• Restore Defaults replaces the list with the built-in set and removes the existing allergens, so use it deliberately.
• Renaming an allergen changes it everywhere at once, including on items already using it.

See Manage the allergen library.

Icons are missing or wrong

Each allergen carries its own icon, chosen in the allergen library. An allergen created without an icon falls back to the built-in icon only when its name matches a built-in allergen; a custom allergen with no icon has none to fall back to.

A guest says the filter "stuck"

The selection is stored in the guest's own browser and persists across pages for 30 days. It is per device, not per account, and clearing it is done by unticking the allergens and filtering again. This is also why two people at the same table can see different menus — each device remembers its own selection.

The separate Show allergens in dishes switch works the same way: it remembers its state in the guest's browser and only controls whether the allergen icons are displayed. It does not filter anything.

What the software does not do

Fenómenus stores and publishes the allergen information you enter, and filters on it. It does not derive allergens from a dish name, verify a recipe, or check compliance. Accuracy is the restaurant's responsibility — see The allergen disclaimer.