Dietary requirements must enter the decision before an ingredient is ranked for flavour, price or availability. A system that first finds a convincing replacement and then tries to make it fit an allergy request has reversed the order of work. Some boundaries exclude a candidate entirely. Others require clarification from the responsible team before any recommendation can be considered.

Start by distinguishing the requirement. Food allergy, coeliac disease, intolerance, a religious requirement and an ethical preference are not interchangeable categories. Do not ask a model to infer a guest’s needs from a dish name or a casual comment. Use the restaurant’s established communication procedure, avoid unnecessary personal data, and record the operational instruction accurately.

Unknown is not a passing result

A useful tool needs at least three states: evidence supports consideration, evidence excludes the candidate, or information is insufficient. Collapsing the third state into “probably suitable” creates a dangerous shortcut. Missing product specifications, unclear preparation records or a changed supplier should cause a pause for verification.

In the European Union, Regulation (EU) No 1169/2011 provides the food-information framework, including the substances or products listed in Annex II. The familiar list is a legal information baseline, not a complete list of everything to which a person might react. The restaurant must also consider the guest’s stated requirement and the rules applicable to its operation.

Check the exact product

An ingredient category is not a product declaration. “Oat cream,” “stock,” “miso” and “vegetable spread” can describe products with very different formulations. Read the actual label and match it to the pack being used. Check compound ingredients and supplier changes. A product description remembered from a previous delivery is weaker evidence than the current specification and packaging.

Example: dairy-free request

A plant-based cream alternative may appear relevant, but the specific label, other recipe components and the preparation environment still require review.

Example: gluten-free request

A plant-based product is not necessarily gluten-free. Oats, sauces, stocks and processing statements need product-specific checks rather than category assumptions.

These examples illustrate checks, not approved substitutions. They do not establish the suitability of any particular product or meal. “Vegan,” “lactose-free,” “milk-free” and “gluten-free” carry different meanings and should not be used as synonyms. Certification or a supplier statement may contribute evidence, but its scope and the kitchen’s own handling still matter.

Include the route through the kitchen

The ingredient is only part of the picture. Storage, scoops, chopping boards, fryers, mixers, cloths, hands and service utensils can all affect cross-contact risk. An inventory connection cannot tell a model whether a container was handled appropriately or whether a cleaning procedure was completed. Those are operational facts requiring real controls and records.

Build the review around the restaurant’s food-safety management system. The Codex General Principles of Food Hygiene and the Codex food-allergen management code provide relevant frameworks, while local authorities set and enforce applicable requirements. A substitution tool should support those procedures, not create an alternative approval route around them.

A constraint is a boundary to respect, not a score to trade against convenience.

Keep communication precise through service

Once an authorised change is made, the relevant recipe record, allergen information and front-of-house briefing need to agree. Avoid describing a changed dish by its old ingredient list. Record which product was used and who reviewed it, and make the current instruction available to the staff preparing and serving the dish.

Do not store guest medical details in an open-ended AI prompt when a minimal operational requirement will do. Separate the information needed to prepare a meal from personal information that is not needed for the task. This website’s contact tool is not a channel for urgent allergy decisions, clinical advice or individual meal clearance.

Know when to stop

If the label cannot be checked, handling history is uncertain or the team cannot confidently execute its controls, stop the substitution pathway. The appropriate response may be an alternative dish with established controls, an honest limitation, or a decision not to serve. Taste testing cannot resolve an allergen question, and a high model confidence score cannot replace evidence.

Sources & further reading

Next: taste, test, then decide →