TasteGraph
Allergens & SafetyMarch 18, 2026 · 3 min read

Gluten-Free, Vegan, and Allergen-Free: Why These Are Not the Same Thing

A vegan dish can still be dangerous for someone with a nut allergy, and that gap gets missed more often than it should.

A menu with a single leaf icon meaning plant-based and a single wheat icon meaning gluten-free looks tidy, but it quietly assumes these categories protect against things they were never designed to address. A vegan dish loaded with cashews is still a serious problem for a guest with a tree nut allergy, no matter how many plant-based badges it carries.

Preference, intolerance, and allergy are different problems

A guest choosing vegan food is usually making a lifestyle or ethical choice. A guest avoiding gluten because of a sensitivity wants to feel comfortable, not sick, a few hours later. A guest with a true allergy is managing a risk that can range from uncomfortable to medically serious. These are three different stakes levels, and treating them as one filter flattens information that actually matters.

The confusion is understandable, because these categories genuinely overlap sometimes. A dish can be vegan, gluten-free, and free of a guest's specific allergen all at once. The mistake is assuming that overlap is guaranteed rather than coincidental, and building a menu system that treats one label as a proxy for the others.

Where the conflation causes real problems

Sesame is common in vegan cooking as a protein and fat source, and often gets no special mention because the dish already reads as accommodating due to being vegan. Gluten-free baked goods frequently use eggs as a binder, which the gluten-free label says nothing about. A dish can tick every dietary preference box on a menu and still contain the exact allergen a guest is trying to avoid.

This is especially common with substitute ingredients that show up specifically because a dish is trying to be accommodating in one direction. A gluten-free pizza crust built around a nut flour solves one guest's problem while creating a new one for a different guest entirely, and if the menu only tracks the gluten-free label, that new problem goes completely unflagged.

  • Vegan does not mean nut-free, soy-free, or sesame-free
  • Gluten-free does not mean dairy-free or egg-free
  • Vegetarian does not mean shellfish-derived ingredients are absent, since some sauces use fish-based stocks or pastes
  • A dietary preference filter and an allergen filter should be presented as separate, not merged into one badge

Give guests both filters, clearly separated

The fix is not complicated: keep dietary preference tags and allergen tags visibly distinct on the menu, and let guests filter by both independently rather than assuming one implies the other. A guest should be able to see that a dish is vegan and still see, separately, that it contains sesame.

A quick test for your own menu

Pick any dish currently labelled vegan or gluten-free on your menu and ask, separately, whether it is also free of each of the nine common allergens. If the honest answer to any of them is I am not sure, that dish has a gap worth closing, regardless of how confidently the existing dietary label reads.

This small exercise, run across a handful of your most popular accommodating dishes, usually surfaces the gap faster than a full menu review would, simply because it forces the question to be asked explicitly rather than assumed away by an existing label.

It is also worth training front of house staff to hear the difference in a guest's question. Do you have anything vegan is a preference question. Does this contain any nuts at all is an allergy question, even if the guest happens to also be vegan, and it deserves a different level of certainty in the answer they get back.

A menu that gets this distinction right ends up serving both groups better, not just the allergy-conscious one. Guests choosing vegan for ethical reasons are not managing risk, so they benefit from a simpler, faster filter, while guests managing an allergy benefit from a more rigorous one, and conflating the two slows down and under-serves both at once.

TasteGraph tags allergens and dietary preferences as separate fields on every dish, so a vegan label never gets mistaken for an allergen-safe guarantee, and a guest filtering for their actual allergy sees an accurate result regardless of what other labels the dish carries.

TasteGraph

See what a menu that reorders itself around every guest looks like on your own dishes. Bring what you already have and go live in about 10 minutes.

Build your menu free

More on Allergens & Safety