Why Vegan Menu Labels Still Need Clear Allergen Information
A practical look at why vegan and plant-based labels are not the same as allergen-free claims, and how hospitality teams can make menu information clearer for guests.
By Ashley Sykes
A guest sees a vegan icon next to a dish.
For one person, that answers the question. They avoid animal products, the dish looks suitable, they order.
For another guest, it answers almost nothing.
They still need to know whether it contains soya. Or sesame. Or nuts. Or whether the supplier has a “may contain milk” warning. Or whether the plant-based milk being used has changed since the last menu update.
Same menu icon. Very different level of risk.
That is the bit hospitality teams need to be careful with.
Vegan, vegetarian, plant-based and free-from are often spoken about as if they live in the same part of the menu. Operationally, they do not. They are different pieces of information, used by different guests for different reasons.
A vegan label can be useful. It just cannot be expected to do the job of allergen information.
Vegan is a dietary label, not an allergen guarantee
A vegan label usually tells the guest that animal-derived ingredients have not been intentionally used in the dish or product.
That is helpful.
It does not automatically tell the guest that the dish is safe for someone with an allergy to milk, egg, fish, crustaceans or any other allergen.
The
Food Standards Agency
has made this distinction clear. Vegan-labelled food may still carry allergen risk where cross-contact is possible, and people with allergies should not treat “vegan” as the same thing as “allergen-free”.
For operators, the practical point is simple.
🌱 A vegan menu tag helps with dietary choice.
✅ Allergen information helps with food safety decisions.
They need to work together, but one does not replace the other.
The menu problem usually starts with good intentions
Most of the time, this is not caused by anyone being careless, it starts with a sensible menu update.
- A new plant-based dessert goes live.
- A dairy alternative is added to the drinks menu.
- A vegan sauce replaces an older recipe.
- A new supplier spec lands in someone’s inbox.
- A menu designer adds a neat little vegan icon next to the item.
The menu is more inclusive, the guest has more choice, the team has something clear to point to. But behind that icon, a lot still needs to be checked.
- Does the ingredient contain any of the 14 regulated allergens?
- Is there a precautionary allergen statement from the supplier?
- Are there modifiers or toppings that alter the allergen profile?
- Does the guest-facing menu match the team information?
- Has the printed allergen sheet been updated as well?
Plant-based menus can make allergen communication harder
Plant-based menus have given hospitality teams far better range than they had a few years ago. That is a good thing. But they have also added more ingredients that need careful data behind them.
Plant-based milks. Vegan creams. Meat alternatives. Egg replacements. Nut-based sauces...
Some of these products are simple. Some are not.
- A plant-based drink may still involve soya.
- A vegan dessert may still carry a “may contain milk” warning.
- A meat-free dish may include sesame, mustard, gluten or nuts.
- A dairy alternative may be fine for one guest and unsuitable for another.
None of that means the item should not be sold - It means the menu needs to explain the item properly.
Ask a member of staff” is not enough on its own
There will always be a place for team conversations around allergens. Guests need to be able to ask questions and teams need to know how to respond. Managers need proper processes behind the scenes. Software does not replace supplier checks, kitchen controls, training or judgement.
But “please ask a member of staff” should not be doing all the work.
For many guests, the decision starts before they visit. They check the menu online. They scan for vegan options, milk alternatives, calories, gluten-free dishes or allergen information. If they cannot find enough confidence there, they may never arrive.
Even in-store, asking the team only works well if the team are looking at information that is current, clear and consistent.
If the guest-facing menu says vegan, the allergen PDF is three versions behind, and the team member is checking a spreadsheet saved by someone who no longer works there, the conversation becomes harder than it needs to be.
What clearer menu information looks like
A better setup does not need to make the menu complicated. Guests do not want a lecture next to every dish. Teams do not need more admin for the sake of it.
For each menu item, hospitality teams should be able to show:
- dietary tags such as vegan, vegetarian or plant-based
- the allergens the dish contains
- relevant “may contain” information
- nutrition information where it is being provided
- modifier or topping changes that affect the item
- the same core information to guests and teams
- updates that can be made without rebuilding every menu file manually
That last point is important.
If the allergen data changes, the guest-facing information should not be waiting for someone to remember to export a new PDF. If a vegan item changes supplier, the menu should not rely on someone spotting that the old version is still live. If a team member checks the information during service, they should not have to wonder whether they are looking at the latest copy.
Where Harlo fits
Harlo is built around a fairly simple idea: menu information is easier to trust when it is managed from one clear place. That includes
allergen information
nutrition information
dietary tags and
guest-facing menu content.
For a team managing vegan and plant-based dishes, that means the vegan label does not have to sit separately from the allergen data behind it. The dish can be maintained once, with the information then shown more clearly across the guest menu and team-facing view.
It also reduces the need to keep chasing old spreadsheets, static PDFs and separate menu files every time an ingredient changes.
That does not remove the need for proper food safety processes. It does make the communication layer easier to maintain.
A useful check for your own menu
Pick one item labelled as Vegan from your current menu.
Then check how many places that item exists.
🔲 Your website menu.
🔲 Your printed menu.
🔲 Your allergen matrix.
🔲 Your delivery platform.
🔲 Your EPOS description.
🔲 Your nutrition file, if you publish one.
🔲 Your supplier spec.
Now check whether they all tell the same story.