How to manage allergens across a hospitality kitchen

Use the guidance for the food and jurisdiction

The official FSA guidance covers providing allergen information and applicable labelling requirements. It distinguishes non-prepacked food from prepacked for direct sale. Do not treat the PPDS rules often called Natasha's Law as a definition of all prepacked food.

For Scottish operations, use Food Standards Scotland's technical guidance. Confirm the rules for the way the venue prepares, packages and sells its food.

Keep the actual ingredient evidence

Maintain the current product label, supplier specification and recipe version together. If the documents conflict or a formulation is unclear, clarify it with the supplier before relying on the record. Do not assume one document is always sufficient or that every similar product has the same formulation.

Include bought-in sauces, garnishes and components in the recipe record. The dish name alone cannot establish which ingredients were used.

Make substitutions trigger a review

When a delivery contains a substitute, record the exact product received and identify the recipes and service information affected. Assign a responsible person to review the change before the changed dish is served.

A useful record includes the supplier product, date, affected recipes, evidence checked and the person who approved the updated information. Keep the old version identifiable rather than silently overwriting it.

Keep cross-contact assessment distinct

Ingredient information and cross-contact controls are related but different questions. A recipe with no deliberate use of an allergen is not proof that the preparation environment avoids cross-contact.

Follow the relevant regulator guidance and the business's trained procedures for storage, preparation, cleaning and service. Do not make an allergen-free promise from an ingredient spreadsheet alone.

Give the service team a dependable handoff

The kitchen and front-of-house team should refer to the same approved information. Train staff to escalate uncertainty and communicate accurately instead of guessing. Confirm who owns the record during a shift and how a changed ingredient reaches the team.

For groups, record site variations. If two kitchens use different products or preparation methods, one shared record may not describe both correctly.

Use connected records without outsourcing the decision

Hops' La Cage onboarding story describes recipes and allergen data being mapped during setup. Connected ingredient and recipe records can make a review easier, but their completeness depends on the information entered and the operating process.

The venue remains responsible for verifying the food and communication it provides. Discuss the ingredient-record workflow with Hops as part of that process, not as a guarantee of compliance or an automated safety decision.

Related context: How to price a menu: recipe costing explained and How to do a stock take: a practical guide for hospitality operators.

Hops Inventory and Finance connect stock and operational records. Arrange a demo using an example from your venue to confirm the workflow and supported scope.