Guides
What meal production software actually has to do
A requirements list is more useful than a feature comparison, because it is yours. These are the capabilities that determine whether the number your kitchen cooks to can be trusted.
Non-negotiable
Counts derived, never typed
Production totals computed from customer selections. If anyone maintains them by hand, they will diverge on the first mid-week change.
Frozen at a cut-off
The day stops moving once purchasing and prep have committed. Late changes roll forward.
Aggregate and individual views
Totals per recipe for the line; per-customer attribution for packing and allergen checks.
Allergen conflicts surfaced pre-service
At the top of the day, not discovered at the bench.
Recipe explosion to ingredients
Canonical units, on-hand deduction, explicit shortfalls rather than silent rounding.
Worth having
Bilingual recipe names
Where the brigade and the menu are written in different languages.
Progress visibility
Cooked, packed, dispatched, without walking the floor.
Yield and waste factors
On the recipe rather than in someone’s head, so they can be reviewed.
Seasonal demand profiles
Configurable, because Ramadan inverts the daily shape for a month on dates that move.
The requirement nobody lists
Ask what happens when a customer changes a meal after the cut-off. A system that lets it silently rewrite today’s production is worse than a spreadsheet, because it looks authoritative while being wrong, and your kitchen will stop trusting it within a fortnight.
The correct behaviour is unglamorous: accept the change, apply it to the next open week, and tell the customer that is what happened.
Common questions
- What is the most important production requirement?
- That counts are derived from customer selections rather than maintained by hand. Everything else is secondary, because a typed number will diverge the first time somebody changes a plan mid-week.
- Should production software handle inventory?
- It should at least deduct on-hand stock to give a true purchasing requirement. Full inventory management is a bigger discipline and often better handled separately.
- How should post-cut-off changes behave?
- They should apply to the next open week, never rewrite a day that purchasing and prep have committed to. Silently altering today is how kitchens learn to distrust the system.
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
- 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.
- GuidesProduction planning for a meal-plan kitchenProduction planning here is unusually tractable, because unlike a restaurant you know your entire day before it starts. The difficulty is not forecasting — it is keeping the plan in step with a customer base that keeps changing its mind.
- GuidesIngredient forecasting for meal-prep kitchensPurchasing is where a meal-plan kitchen’s margin is actually decided, and it is downstream of information the business already has. Most over-buying is not a forecasting failure but a plumbing failure.
- SolutionsMeal delivery software for kitchen managersA kitchen manager needs one thing from software above all others: a number they can trust before they start cooking, that nobody will change halfway through the morning.
- 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.
- SolutionsMeal subscription software requirementsMost requirement lists for this category describe features. The ones worth writing describe failures — because every meal subscription system can create a subscription, and they differ entirely in what happens when one changes mid-cycle.