MILabs
Build

Menu and allergen assistant for catering businesses

A menu and allergen assistant for caterers that answers dish questions from your recipe records, with sources cited for each reply.

Updated 2026-07-08

Why Catering need a menu and allergen assistant

Catering work often means answering allergen questions about dishes that are still in planning. A client may ask about a canapé, a sauce or a dessert well before the event, and the answer has to match what the kitchen will send out on the day. Dishes in this trade are usually built from sub-recipes, so a dressing or pastry base can carry an allergen that never appears in the main item's name. Planners, chefs and front-of-house staff each pick up these questions from different angles, and a shared record keeps their answers aligned. A menu and allergen assistant gives the whole team one reference point for each booking. Because each reply points back to the recipe record, a head chef can check it quickly rather than rebuilding the answer from scratch.

Features for this industry

  • Catering dish records with each component listed, including sauces, dressings and pastry bases
  • Allergen flags for the allergens named in your labelling rules, tracked at ingredient level
  • Event-specific views that show only the dishes on one booking's run sheet
  • Answers that cite the recipe record behind them, so a planner can confirm the source
  • Review step for supplier substitutions before any changed allergen flag goes live
  • Clear handoff to the head chef when a question falls outside the recorded information

At a glance

BuildMenu and allergen assistant
IndustryCatering
Complexitymoderate
ToolsClaude, ChatGPT, Airtable
First release
  • Dish list built from your current menu, with each item's ingredients recorded
  • Allergen flags for each ingredient, covering the allergens named in your labelling rules
  • Replies that cite the recipe record behind each answer
  • A staff-only review view for changes to ingredients or suppliers
  • Plain answers when information is missing, directing the user to a staff member

Examples

Platter enquiry from a planner

A planner asks whether a grazing platter contains sesame or tree nuts before a corporate lunch. The assistant reads the component records for the platter, including the hummus and dukkah lines, and gives the answer with a reference to the recipe sheet. A staff member confirms the reply before it goes into the proposal.

Dietary question at a tasting

A couple at a tasting asks which canapés are dairy free and whether the dessert uses any gluten-containing biscuit base. The assistant lists the dishes with flags drawn from the menu record and points to the base recipe. The event lead checks the answer against the current supplier sheet before the tasting ends.

Supplier swap between events

A supplier replaces a pastry brand between two events, and the new product may contain a different allergen. A staff member updates the ingredient line in the menu record, and the review view shows every dish that uses it. The assistant answers from the revised record only after the change is approved.

The local angle

MILabs is an agency based in Sydney, so the local angle here is the Sydney catering market itself. The city has a large mix of caterers, hotels, bakeries and event venues, and many of them serve corporate, cultural and community bookings where planners ask allergen questions long before the day. NSW food businesses operate under the NSW Food Authority and under Australian food labelling standards, so a menu record reflects how those rules apply to each product rather than to a generic list. Because MILabs works remotely with clients beyond the city, the same approach carries to a regional caterer or a business interstate.

Sessions run by video call and the shared record lives in the business's own tools, so the work does not depend on where the kitchen sits. Businesses outside Sydney can still expect the same structure of review, ownership and source citation.

good questions, straight answers

Frequently asked questions

How does a menu and allergen assistant for catering start?
The easiest first step is to say hello through the enquiry form, and we'll take it from there. Most catering teams begin with the dishes they serve most often. For every ingredient, including sauces, dressings and bases, the allergens that apply under your labelling rules are recorded. A small trial on one menu or one type of event lets staff test the replies before the record covers the full range.
Why does a catering business need a menu and allergen assistant?
Catering businesses answer allergen questions across several stages, from the first enquiry through to service on the day. When each person relies on memory or on a separate document, replies can differ, and component changes can reach some people and not others. A single record that the assistant reads from gives the same answer every time and shows which recipe it came from. Staff confirm replies for a guest with a serious allergy.
How does a menu and allergen assistant handle catering client information?
The assistant works from your menu and recipe records, so it holds only the dish and ingredient details your team stores there. Client names, guest counts and personal dietary notes can stay outside the menu record entirely. Access is limited to the staff who need it, and the review view is open only to people who approve changes. How any chat tool stores and processes messages is covered in the setup conversation.
How does a menu and allergen assistant fit with software catering businesses already use?
Many caterers already keep recipes and stock in spreadsheets, and the assistant can start by reading from the same kind of table. Airtable is one option for holding the menu record, since it stores records in tables that people can edit and review. Accounting and booking software can stay as it is, with the assistant taking dish details from the menu record. Other connections come later, once the team trusts the menu record.
What could go wrong with a menu and allergen assistant in catering?
The most useful habit is keeping the record current. When a supplier product changes, updating the ingredient line straight away keeps every quoted answer aligned with the packet in the kitchen. Each dish is added before it appears on a proposal, and a named owner for each change keeps the process steady. Staff compare the record against labels regularly, and replies send people to a staff member whenever information is absent.
let's make something happen

Custom development: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.