Guides
Requirements for allergen handling in meal software
This is the one area where a missing requirement has consequences beyond money. Evaluate it more carefully than anything else on your list.
Requirements in priority order
Structured allergen fields
Not free text. Text can only be read by a person who happens to look; structure can be checked automatically against every assignment.
Validation of DEFAULTED meals
The check most systems skip. A slot auto-filled at the cut-off is the assignment nobody reviewed, and therefore the most dangerous one.
Warning at more than one point
At assignment, on the production list, at packing, and on the label. A single warning gets missed on a busy morning.
Customer-maintained records
With changes taking effect on future assignments immediately. A record only the office can edit goes stale.
Allergens on the printed label
Derived from the recipe, not typed. The label is the only safeguard that reaches the person eating.
Test it with a defaulted meal
When evaluating, ask the vendor to demonstrate a customer with a dairy allergy whose slot is auto-filled at the cut-off with a dish containing dairy. Watch what happens.
A system that only validates customer-chosen meals will pass a normal demo and fail exactly where a real kitchen is most exposed, because nobody was watching when that meal was assigned.
What no software requirement covers
Cross-contamination, mislabelled supplier ingredients, and recipes whose ingredient lists were entered incorrectly. Software narrows one specific class of error and leaves those untouched.
They are process and training problems. Any vendor implying their software makes your kitchen allergen-safe is selling you something dangerous.
Common questions
- What is the requirement most systems miss?
- Validating meals that were assigned automatically at the cut-off rather than chosen by the customer. That is the assignment nobody reviewed and therefore the one most likely to cause harm.
- Should allergen data be free text?
- No. Free text can only be acted on by a person who happens to read it at the right moment, which on a busy morning is nobody. Structured fields can be checked automatically.
- Does allergen software make a kitchen safe?
- No. It narrows one class of error — a customer assigned a dish containing their allergen. Cross-contamination and incorrect recipe data remain process and training problems.
See how this works in practice
The home page walks through the same mechanics against a real admin loaded with a demonstration kitchen: production, packing, routes and the customer side.
Related reading
- SolutionsAllergen management software for meal businessesEvery other field in a meal-plan system can be wrong and cost you money. This one can be wrong and cost someone a hospital visit, which is why it deserves different treatment from the rest of the customer record.
- GuidesAllergen management in a meal-prep kitchenAllergen handling is the one part of a meal-plan operation where a data-entry problem becomes a medical one. It deserves a different standard of care from the rest of the customer record.
- SolutionsMeal label software for prep kitchensThe label is the last line of defence in a meal-prep operation and the only artefact the customer actually reads. Everything about how it is produced matters more than it appears to.
- GuidesThe packing workflow, and where it goes wrongPacking is the join between two opposite shapes of the same day: the kitchen cooked totals, and the customer receives one specific box. Nearly every visible error in a meal business is made at that join.
- GuidesBilingual meal labels for Gulf kitchensA label in a Gulf prep kitchen frequently has two audiences who do not share a language, and one field on it is safety-critical.