Dietary Tags and Allergen Labeling on Restaurant Menus
Roughly one in ten US adults has a food allergy, and far more are shopping a menu with somebody else’s restrictions in mind: the gluten-free sister, the vegan coworker, the kid with the peanut allergy. When a group picks a restaurant, one unlabeled menu can lose the whole table.
Good dietary tags are cheap to add and do two jobs at once: they win the orders of restricted diners, and they cut the back-and-forth that slows service (“does the pad thai have peanuts?” asked forty times a week). Done carelessly, though, tags create risk, because an allergen tag is a promise.
This guide covers what to tag, how to tag it, and where the legal lines actually are. Tags are also a layout element, and they follow the same discipline as everything else on the page; for the full system see our menu design and engineering guide.
The big 9 allergens
US federal law recognizes nine major food allergens. The first eight come from FALCPA (2004); sesame became the ninth under the FASTER Act, effective January 1, 2023.
| # | Allergen | Common menu hiding spots |
|---|---|---|
| 1 | Milk | Butter, ghee, whey in breads, “non-dairy” creamers, fried batters |
| 2 | Eggs | Mayo, aioli, fresh pasta, meatballs, egg wash on breads |
| 3 | Fish | Worcestershire sauce, Caesar dressing, fish sauce in “vegetable” dishes |
| 4 | Crustacean shellfish | Shrimp paste, seafood stocks, fry-oil cross-contact |
| 5 | Tree nuts | Pesto, dessert crusts, mole, salad toppings, nut oils |
| 6 | Peanuts | Sauces in Thai and West African dishes, candy garnishes, fry oil |
| 7 | Wheat | Soy sauce, roux in soups and gravies, dusted proteins |
| 8 | Soybeans | Soy sauce, edamame, tofu, many fry oils and margarines |
| 9 | Sesame | Tahini, buns and bagels, za’atar, sushi garnish, sesame oil |
An important nuance: the federal labeling requirement attached to these nine applies to packaged foods, not to your menu. There is no federal law forcing restaurants to print allergen information. But that is not the end of the story: some states and cities add their own rules (Massachusetts, for example, requires an allergen-awareness notice on menus and a certified staff member), the FDA Food Code pushes allergen awareness in staff training, and ordinary negligence liability applies everywhere. The practical standard is simple: know what is in every dish, train the floor, and never guess.
What US restaurants should actually print
The industry-standard approach has three layers:
- A menu statement. One line, usually at the bottom: “Please inform your server of any food allergies. Our kitchen handles milk, eggs, wheat, soy, peanuts, tree nuts, fish, shellfish, and sesame.” This invites the conversation and is honest about shared-kitchen reality.
- Dietary tags for lifestyle choices. Vegetarian, vegan, gluten-free eaters mostly self-serve from symbols. This is where tags shine.
- Server-mediated allergen answers. For true allergies, the safe pattern is a trained human plus an ingredient reference (a printed allergen grid in the service station, or detailed item notes on your digital menu), not a guest squinting at symbols.
A tag system that works
| Tag | Meaning | Watch out for |
|---|---|---|
| V | Vegetarian | Fish sauce, gelatin, chicken stock in “vegetable” soups |
| VG | Vegan | Butter finishes, honey, egg pasta, dairy in buns |
| GF | Made without gluten ingredients | Fryer cross-contact, soy sauce, spice blends |
| DF | Dairy-free | Butter, cream in mashed potatoes, cheese garnish |
| N | Contains nuts | Distinguish peanuts vs tree nuts if you can |
| S | Spicy (1 to 3 levels) | Calibrate honestly; three levels maximum |
Rules that keep the system useful:
- One legend, once per menu. Define every symbol in a single line near the top or bottom. Never make guests hunt.
- Letters beat icon soup. A “V” is self-evident; a tiny leaf, a wheat stalk with a slash, and four other pictograms at 8 points are not. If you use icons, use very few.
- Tag the dish as served. If the salad is vegan until the default parmesan lands on it, it is not vegan. “VG without cheese” is honest; a bare VG is not.
- Audit tags every time a recipe changes. The chef swaps to a butter finish and the DF tag silently becomes a lie. Tag review belongs in the same quarterly audit as your menu engineering numbers.
Claims to make carefully
“Gluten-free” vs “made without gluten ingredients.” The FDA’s gluten-free standard (under 20 parts per million) was written for packaged food, and FDA guidance expects restaurants using the term to live up to the same meaning. If you share a fryer or a flour-dusted prep area, you cannot honestly promise it. Many restaurants use “made without gluten-containing ingredients” or “gluten-friendly” precisely to signal “safe for preference, ask us about celiac.” That phrasing is not lawyer-speak; it is accuracy.
Cross-contact is the real risk. Most restaurant allergy incidents are not about the recipe; they are about the shared fryer, the same tongs, the crumbs on the cutting board. Your menu language should never promise more separation than your kitchen practices deliver.
Never let a server improvise. “I think it’s fine” is how incidents happen. The rule that works: any allergy question a server cannot answer from the reference sheet goes to the kitchen, every time.
Train on a rhythm, not once. A 15-minute allergen refresher each quarter, plus a one-line callout in pre-shift whenever a recipe changes, keeps the floor’s answers matched to the kitchen’s reality. Free training resources exist specifically for restaurants (ServSafe Allergens is the best known), and in some jurisdictions a certified person is required. The menu statement invites the question; training is what makes the answer safe.
Where digital menus quietly win
Paper rations space; a phone menu does not. On a digital menu, each item can carry full tag details and notes (“contains fish sauce,” “fryer shared with breaded items”) without cluttering the printed page, and guests can check at their own pace before they even arrive. Since the menu on their phone is often the first one guests read, tags there do the filtering work before the party ever picks a restaurant. Make sure that phone version is also readable by everyone, including low-vision guests and screen-reader users; the specifics are in digital menu accessibility.
Keeping tags synchronized is the last piece. A dish tagged DF on the printed menu and untagged on the QR menu reads as sloppy at best and dangerous at worst. VisibleMenus stores tags on the item itself, so the hosted QR menu, the printable to-go menu, and your Google menu all show the same truth, updated in one place.
Tags are a small design investment with an outsized return: more groups can say yes to you, service moves faster, and restricted diners, the most loyal repeat customers in the business once they trust a kitchen, know you take them seriously.
