Guides
Managing meal deliveries in Excel
Excel runs more Gulf meal-plan kitchens than any software does, and for a long stretch of a business’s life that is the right answer. It is worth being precise about what it does well and exactly where it stops.
What Excel genuinely does well here
It is fast to change, costs nothing, and everyone can already use it. For a kitchen where one person holds the week, a well-structured workbook is genuinely a good operating system — better than badly-chosen software, which adds process without adding truth.
It also handles the arithmetic of this business without difficulty. Multiplying selections by portion sizes, exploding recipes into ingredient quantities and summing a delivery run are all things a spreadsheet does correctly.
The limitation is not capability. It is that a spreadsheet cannot guarantee that changing one fact updates every other place that depends on it.
The specific failure
A customer pauses on Tuesday. Here is what has to happen, and what actually happens.
| In a spreadsheet | In a system that propagates |
|---|---|
| Someone remembers to remove them from the cook list. | The portions leave the cook list automatically. |
| Someone remembers to reduce the ingredient requirement. | Purchasing recalculates from the remaining selections. |
| Someone remembers not to print those labels. | The labels are not generated. |
| Someone remembers to pull the delivery stop. | The stop disappears from the route. |
| Someone remembers to adjust the billing record. | The billing record reflects the pause. |
| Five chances to forget, every time, for every change. | One action, five consequences, atomically. |
Structuring the workbook properly while you are on it
If you are staying on Excel — and you may well should be — this is the structure that survives longest.
One workbook, not five files
Separate files are separate truths. Sheets within one workbook at least sit next to each other where a discrepancy is visible.
Selections as the only input
Cook list, ingredient requirement and pack list should all reference the selections sheet, never be typed independently.
A conflicts column that must read zero
One number to check before cooking starts, covering allergen conflicts and unresolved changes.
An exceptions log with dates and names
Same day or not at all. This is what settles a billing dispute six weeks later.
No manual totals
Any figure typed rather than calculated will eventually be the one that is wrong.
How to know you have reached the end of it
Not by revenue, and not by customer count. The signal is corrections — how often something has to be put right after the fact. A box produced for someone who paused, a purchase order for meals nobody ordered, a customer charged for a week they skipped.
When those stop being memorable incidents and start being a normal part of the week, propagation has failed, and no amount of workbook discipline will restore it. For most operators that happens between two and four hundred meals a week, earlier if customers change plans often.
The other signal is people. The moment a second person makes changes, the version of the truth held in one head stops being the truth, and a spreadsheet has no mechanism to reconcile two people’s edits beyond hoping.
Common questions
- Is Excel a legitimate way to run a meal delivery business?
- Yes, for a long stretch of one. A well-structured workbook beats badly-chosen software, which adds process without adding truth. The limitation is not arithmetic — it is that a spreadsheet cannot propagate a change automatically.
- What exactly breaks first?
- Change propagation. A single pause requires five separate manual updates — cook list, purchasing, labels, delivery and billing — and each is a chance to forget. The failure is silent until a box reaches someone who paused.
- How do I know when to move off it?
- Count corrections, not customers. When putting things right after the fact becomes a normal part of the week rather than a memorable incident, propagation has failed. Typically two to four hundred meals a week.
- What is the best structure while I am still on Excel?
- One workbook rather than several files, with the cook list, ingredient requirement and pack list all referencing a single selections sheet, plus a conflicts column that must read zero and a dated exceptions log.
When one change has to reach five places
Mealroh derives all five from one set of selections, so they cannot disagree. See it on a demonstration kitchen.
Related reading
- GuidesSpreadsheets vs meal delivery softwareThis comparison is usually written by software vendors and is usually unfair. Spreadsheets are excellent at several things software is bad at, and there is exactly one thing they cannot do.
- GuidesMoving a meal-plan business off spreadsheetsSpreadsheets are not a mistake. They are the correct tool for an operation still working out what it is, and they fail for a specific, identifiable reason rather than because they are unprofessional.
- GuidesMeal production plan templateA production plan is four connected documents pretending to be one: what to cook, what to buy, what goes in each box, and what went wrong. This template keeps them on one sheet so they cannot disagree.
- GuidesWhere re-typing happens, and how to remove itNobody sets out to enter the same fact six times. It accumulates one reasonable decision at a time, and by the time it hurts, the duplication is spread across five documents nobody wants to consolidate.
- GuidesDo you actually need meal delivery software?We sell this software, so treat what follows accordingly — but the honest answer for a meaningful number of kitchens is not yet, and buying early tends to end with the spreadsheet running alongside the system.