Imagine someone choosing a restaurant for six friends. Five can order almost anything. One needs reliable information about an allergy.
They open your menu. The photos look good. The ingredients are vague. A small line says “ask staff”, but there is no obvious way to do that before making the booking.
The group might still call. They might also choose somewhere easier to assess.
Clear allergen information is part of helping a guest make a safe, informed choice. It is not a reason to promise that every request can be accommodated. Your website should support an accurate conversation with trained staff, not replace it.
This is not a rare-use audience
A 2025 Food Standards Agency and Ipsos UK report found that 83% of surveyed adults with food hypersensitivity ate out or ordered takeaway at least monthly. The survey covered England, Wales and Northern Ireland and included 780 adults with food hypersensitivity plus 184 parents of affected children. It does not establish how many Australian group bookings are lost through unclear menus.
It does show why these guests should not be treated as an occasional edge case.
Separate three different statements
Your menu may say what a recipe contains. Your kitchen process determines how cross-contact is managed. Your staff establish whether a particular request can be fulfilled on that occasion.
Those are related, but they are not interchangeable.
For example, “made without peanuts in the recipe” is not automatically the same claim as “safe for someone with a peanut allergy”. A dietary preference label should not be used to answer a different safety question.
Food Standards Australia New Zealand emphasises staff training, accurate and up-to-date information, and allergens that may be present directly or indirectly. Use that guidance alongside the requirements and specialist advice that apply to your location. This article is a communication checklist, not food-safety certification.
Build a menu-information handover, not another forgotten document
Select one menu item and trace the information from supplier to customer. Who checks an ingredient substitution? Who updates the recipe record? Who changes the online menu? Who tells the person taking the order?
Use a working record like this:
| Information | Who should verify it in your process? |
|---|---|
| Current ingredient and supplier details | The person approving ingredients and recipes |
| Relevant preparation and cross-contact considerations | The responsible kitchen or food-safety lead |
| Customer-facing wording | A trained reviewer using the verified information |
| Change date and next check | A named owner, not “the team” |
Do not invent missing fields to complete the table. An unanswered safety question needs escalation, not attractive copy.
A single changed sauce can make yesterday's wording inaccurate. Build a short pause into substitutions: confirm the information and update the people and channels affected before serving the revised item.
Make the next conversation easy to start
Give guests a visible contact route near the menu and explain when they should speak with the team. Consider wording such as:
“Please tell our team about any food allergy before ordering. We will check the current ingredients and preparation arrangements with you.”
That is a suggested starting point to review against your actual process. Do not use it to imply that the request has already been accepted.
For online orders, a typed note is a request, not proof that somebody has read and approved it. Decide how staff will acknowledge relevant requests, check them with the kitchen and communicate when the order cannot be safely fulfilled.
If your current system cannot support that handover reliably, provide a clear alternative contact process rather than leaving a false sense of certainty on the payment screen.
Test the information as a guest would
Open the mobile menu without staff access. Can you find the information without zooming into a blurred image? Do labels have explanations? Is the contact method visible before checkout? Does the answer match what the kitchen currently knows?
Then ask a staff member to handle a fictional query using the normal process. Keep it outside live service. Look for the point where they would need to guess, search an outdated file or rely on one person's memory.
Fix that point first. Making uncertainty visible internally is much better than hiding it behind a confident answer.
For a suspected reaction or serious safety incident, follow your trained emergency procedures and obtain appropriate help; do not treat it merely as a review or marketing issue.
Give guests clarity before asking for commitment
The commercial value of clearer information is worth investigating, but safety does not need a sales justification. Review a small set of dishes, verify the current records and make the contact route obvious. Never promise that this work will capture a particular number of group bookings.
A handover that makes ownership clear
- A named person verifies ingredient and supplier information.
- A second person checks that the customer-facing version matches.
- Staff know who can answer questions during each service.
- A substitution triggers a fresh check before the item is sold.
The UK research and Australian/New Zealand guidance above have different geographic scopes. Use the food authority rules that apply to your venue; this is an information workflow, not a complete compliance checklist.
Connect the menu to a trained person
When considering a branded website or app, discuss your menu journey with BizAppMaker. Bring the information your kitchen has verified and test whether guests can find the contact route before ordering. Confirm how special requests reach staff; a note entered online is not acceptance of an allergy request. The platform does not replace ingredient records, trained staff or your food-safety procedures.
Take a look at how BizAppMaker works for restaurants, or try the live app demo.