Solutions
Meal prep software for batch kitchens
Meal 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.
Cooking is aggregate, packing is individual
The kitchen wants one number: how many portions of each recipe to produce today. The packing bench wants the opposite: which specific portion belongs to which named customer, with their allergens on it. Both views have to come from the same underlying selections, or the counts and the boxes will disagree.
When those two views are maintained separately — a cook list in one sheet, a label file in another — the failure is not that the totals are wrong. It is that they are right on average and wrong for individuals, which is exactly the error a customer notices.
What a prep-focused system has to get right
Aggregate cook lists
Portions per recipe for a production day, summed across every plan and every customer, so the kitchen has one number to work to.
Portion attribution
Each portion traceable back to the customer who chose it, which is what makes an individual label possible at all.
Allergen conflicts
A flag raised before anyone lifts a pan when a customer has been assigned a meal containing something they react to.
Labels that carry the warning
Macros, allergens and a use-by date printed per portion, so the information survives the trip from screen to box.
Shelf life
A use-by date derived from the production day rather than typed, because a hand-typed date is the one that will be wrong.
Allergens are a food-safety control, not a preference field
A dietary preference that is ignored produces an annoyed customer. An allergen that is ignored produces a medical incident and, in a licensed kitchen, a regulatory problem. They should not be stored in the same casual way, and the allergen check should happen at the point where the meal is assigned to the person, not at the point where the box is packed.
The practical test of a system is whether the warning is visible in three places: on the production screen, above the label list, and on the label itself. If it only appears in one, it will eventually be missed on a busy morning.
Common questions
- How is meal prep software different from recipe management software?
- Recipe software tells you how to make a dish. Meal prep software tells you how many of it to make today, for whom, with which warnings attached, and what to buy tomorrow as a result. The recipe is an input, not the product.
- Do labels really need to be generated by the same system?
- Yes, because a label is a claim about a specific portion belonging to a specific person. Generated from a separate file, it drifts the moment a customer changes a meal, and a wrong allergen label is the most expensive error in the operation.
- How should use-by dates be handled?
- Derive them from the production date and the recipe’s shelf life rather than entering them by hand. Derived dates cannot be forgotten on a busy morning, and they stay correct when a production day moves.
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 production planning and ingredient forecastingProduction planning is the join between what customers chose and what the business has to buy. When those two are maintained separately, food cost drifts and nobody can say exactly why.
- 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 delivery software for subscription kitchensMost software sold to food businesses is built for one-off orders. A meal-plan kitchen sells a commitment that runs for weeks, and almost every operational problem it has comes from that difference.
- SolutionsMeal plan software for businesses that sell plans, not mealsA plan is a contract with a shape: a number of meals, a set of delivery days, a term, and a set of rules about what the customer may change and when. Software that does not model that shape will be fought with.