Guides
The packing workflow, and where it goes wrong
Packing 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.
Aggregate in, individual out
The kitchen works to one number per recipe. The bench works to one box per person, each carrying a name, their allergens and a use-by date. Both views must come from the same selections, or the totals will be right while individuals are wrong — which is exactly the error a customer notices.
When the label file is maintained separately from the cook list, this is where the divergence becomes physical.
A bench sequence that catches errors
Resolve conflicts first
Any allergen conflict flagged on the production list is dealt with before packing starts, not discovered mid-run.
Print in route order
Labels ordered the way the boxes will be loaded means the bench and the van agree, which removes a re-sort.
Label before filling
The label defines what goes in the box rather than describing what already did.
Count against the manifest
Boxes per stop checked before loading, so a short load is caught in the kitchen rather than at a customer’s door.
The errors worth designing against
Three recur across almost every operation: the right meal in the wrong person’s box, a correct box with a stale label, and a short load discovered at the door. Each is cheap to prevent at the bench and expensive to resolve afterwards.
All three are fundamentally information problems rather than diligence problems, which is why exhorting the team to be careful does not fix them for long.
Common questions
- Should labels be printed before or during packing?
- Before, in the order the boxes will be loaded. The label should define what goes into the box rather than describe what already went in, which is what makes it a check rather than a record.
- How are short loads best caught?
- By counting boxes against the manifest before the van leaves. Discovering it at a customer’s door costs a return trip and a conversation, both avoidable in the kitchen.
- Why is packing where allergen errors surface?
- Because it is where a specific portion is committed to a specific named person. If the warning has not reached the bench, there is nothing left downstream to catch it except the customer.
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 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.
- 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.
- 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 packing software for prep kitchensThe packing bench is the narrowest point in a meal-plan operation. Everything upstream converges here as totals, and everything downstream leaves as named boxes — and almost every error a customer ever notices is created in that conversion.