Guides

Allergen management in a meal-prep kitchen

Allergen 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.

Structured fields, not notes

An allergy recorded in a free-text notes box can only be acted on by a person who happens to read it at the right moment. An allergy recorded as structured data can be checked automatically against every meal that customer is ever assigned.

That difference is the whole discipline. Everything else — labels, warnings, training — depends on the data being machine-checkable in the first place.

Where the check has to happen

Once is not enough. Each of these points catches a different failure.

  1. At assignment

    When a meal is chosen or defaulted for a customer, flag any conflict immediately, while changing it is still free.

  2. On the production screen

    Show conflicts at the top of the day’s list, so nobody starts cooking a portion that should not exist.

  3. At packing

    Repeat the warning above the label list, because the packing bench is where the wrong box physically gets made.

  4. On the label itself

    Print the allergen information on the box, so the last line of defence is the customer.

Preferences and allergies are different data

A dislike that is ignored produces an annoyed customer. An allergen that is ignored produces a hospital visit and, in a licensed kitchen, a regulatory problem. Storing them in the same casual field guarantees they will eventually be treated with the same casual care.

Keep them separate in the model, and let the severity of the field drive how loudly the system behaves when it is violated.

Common questions

Should a system block a conflicting meal outright?
Flagging prominently and requiring an explicit override is usually better than a hard block, because there are legitimate cases — a reformulated recipe, a customer correcting their own record — and a block that cannot be overridden gets worked around.
Who is responsible for keeping allergen data current?
The customer should be able to update it themselves, and the kitchen should see the change take effect on future assignments immediately. A record only the office can edit goes stale, and stale allergen data is the dangerous kind.
Do allergen warnings need to be on the physical label?
Yes. Screens are the kitchen’s view; the label is the only part of the system that travels with the food and reaches the person eating it. It is the last point at which an error can still be caught.

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.