Solutions
Allergen management software for meal businesses
Every 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.
Structured data is the whole discipline
An allergy written in a notes box can only be acted on by a person who happens to read it at the right moment. An allergy stored as structured data can be checked automatically against every meal that customer is ever assigned, including ones assigned by a default rule at the cut-off when nobody was looking.
Everything else — the warnings, the labels, the training — depends on that. If the data is not machine-checkable, none of the safeguards downstream can be automatic.
What to evaluate in a system
The method of allergen control is covered in our operational guide. These are the questions to ask of the software itself.
Is the data structured or free text?
If allergens are stored as a note, no automatic check is possible at all and every safeguard downstream depends on a person reading it at the right moment.
Does it check at assignment or only at packing?
Catching a conflict when the meal is chosen means changing it costs nothing. Catching it at the bench means the portion already exists.
Does it check DEFAULTED meals?
The dangerous case is a slot auto-filled at the cut-off when nobody was looking. A system that only validates customer-chosen meals misses exactly the assignment nobody reviewed.
Can the customer maintain their own record?
An allergen list only the office can edit goes stale, and stale allergen data is the dangerous kind.
Does the warning reach the printed label?
Screens are the kitchen’s view. The label is the only part of the system that travels with the food.
Software is not a food safety programme
Conflict detection catches a customer being assigned a dish whose recipe contains something they react to. It does not catch cross-contamination in your kitchen, mislabelled supplier ingredients, or a recipe whose ingredient list was entered incorrectly in the first place.
Those are process and training problems. Software narrows the window for one specific class of error; it does not replace a food safety programme, and any vendor implying otherwise is selling you something dangerous.
Common questions
- Should the system block a conflicting meal outright?
- Flagging prominently with an explicit override is usually better than a hard block. There are legitimate cases — a reformulated recipe, a customer correcting their own record — and a block that cannot be overridden gets worked around informally.
- Who should be able to update allergen data?
- The customer, with the change taking effect on future assignments immediately. A record only the office can edit goes stale, and stale allergen data is the dangerous kind.
- Does this prevent cross-contamination?
- No. It catches a customer being assigned a dish whose recipe contains their allergen. Cross-contamination in the kitchen is a process and training problem that software does not solve.
See it running against a real kitchen
The product pages show the actual admin loaded with a demonstration kitchen — production, packing, routes and the dashboard, exactly as an operator sees them.
Related reading
- 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.
- 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.
- SolutionsKitchen management software for meal-plan productionA meal-plan kitchen does not take orders through the day. It receives a fixed obligation the night before and has to discharge it exactly — which is a different management problem from a restaurant pass.
- SolutionsMeal prep software for batch kitchensMeal prep is a manufacturing problem wearing a catering costume. You cook in batches against aggregate demand, then split those batches back into individually owned, individually labelled boxes — and the join between those two shapes is where errors live.
- GuidesRequirements for allergen handling in meal softwareThis is the one area where a missing requirement has consequences beyond money. Evaluate it more carefully than anything else on your list.