Allergen menu labeling for restaurants

For most independent restaurants, allergen menu labeling should do one job: help a caller spot likely risks before they order. Keep it direct. Use a short note next to the item, such as contains dairy, contains nuts, or contains wheat.

A practical setup for a pizza shop, deli, or family restaurant looks like this:

• Put allergen notes next to each item on the main menu.
• Use the same wording everywhere: website, PDF, photos, and printed menu.
• Keep the labels short enough that a caller can read them fast.
• If a menu item can be changed, note the base recipe first, then modifiers.

Example:

• Pepperoni slice — contains dairy, wheat
• Garden salad — may contain egg in dressing
• Chicken wrap — contains wheat; ask about dressing

If you need a deeper phone menu structure, pair this with making your menu easy to order by phone. That helps callers hear the item first and ask follow-up questions only when needed.

Keep the labels short and predictable. A busy owner does not need a legal essay on every line. A caller needs to know the main allergen risk and who to ask if they need more detail.

Try this simple format:

A few writing rules help:

1. Label the base item, not just the special request.
2. Use “contains” for ingredients you know are in the recipe.
3. Use “may contain” only when that is truly the case for your kitchen flow.
4. If the item changes daily, say so plainly.

For example, a cashier can say: “The chicken parm hero contains dairy and wheat. If you have an allergy, I can have the kitchen check the prep notes before we confirm it.” That is clearer than trying to improvise after the order is already in motion.

The safest move is to treat allergy questions as a staff handoff, not a guess. ROAL does this by sending allergy-sensitive questions to staff with a summary, while still collecting the rest of the order details.

A good phone flow is:

1. Take the order items, sizes, modifiers, and notes.
2. Capture the caller’s name and phone.
3. Flag the allergy question for staff review.
4. Confirm the order back only after the kitchen has the needed detail.

Use a script like: “Thanks for letting me know. I’m sending this to the restaurant team with your allergy note so they can check the ingredients before confirming.”

That is especially useful for combinations like:

• Gluten allergy plus a sauce question
• Nut allergy plus dessert or salad dressing
• Dairy allergy plus cheese, butter, or cream sauces

ROAL also answers menu, hours, address, and parking questions from the restaurant’s public information, but allergy-sensitive calls go to staff. That keeps the phone moving without forcing a bad guess.

Consistency matters more than fancy wording. If your website says one thing, your PDF says another, and your front counter menu says a third thing, callers lose trust fast.

Use one source of truth and update it everywhere at the same time. A simple workflow is:

• Edit the item name and allergen note in one master menu.
• Check the website menu page.
• Check any PDF menu.
• Check menu photos or social posts if customers rely on them.
• Test the wording by reading it out loud.

Worked example: Say your chicken wrap used to be listed as plain chicken and now includes a garlic sauce with dairy.

• Old label: chicken wrap
• Updated label: chicken wrap — contains wheat, dairy
• Phone note: ask if caller wants sauce on the side

If your menu changes often, this pairs well with keeping your online menu accurate. ROAL can read menu details from public pages or from a menu you upload, so the cleaner your source is, the cleaner the phone experience becomes.

Give your team one short rule: do not speculate. If a caller asks about an allergen, staff should either verify ingredients or hand the call off to someone who can.

A simple checklist for the counter, kitchen, and phone:

• Know which items have the most common allergens.
• Know which sauces, dressings, and breads need extra checking.
• Never promise a safe result without checking the recipe and prep notes.
• Keep the allergy note visible on the ticket.
• If the caller sounds unsure, ask a follow-up question before confirming.

Here is a useful phrase for staff: “Let me check the recipe and prep notes before we confirm that item for you.”

For owners who use phone ordering, this is where ROAL helps reduce mistakes. It can take the order and send a clean ticket to the kitchen screen, but it will hand off allergy-sensitive questions to staff instead of guessing. That is the right line to draw.

Allergen labeling can actually save time when it is done well, because the caller gets the key facts up front. It can also slow things down if your menu is vague and every order turns into a long back-and-forth.

A simple way to think about it is to compare two paths:

If you want a rough cost view, plug in your own numbers:

• Say you lose 5 phone orders a week because callers can’t get clear ingredient answers.
• Say your average order is $28.
• That is $140 in weekly order value you may be missing before you even count delivery-app commission or labor.

You can compare phone-order costs with your own numbers using the AI phone host cost calculator. ROAL’s pricing is simple: $0.90 per completed phone order, with no monthly fee, no setup fee, and no per-minute fee. That can make it easier to use a phone host for menu questions without adding a fixed bill every month.