Guides
Implementing meal delivery software without a bad week
The risk in this migration is not data loss. It is the week where half the operation is in one system and half in another, and nobody is certain which is authoritative.
An order that limits the damage
Move the things that must not disagree first, and switch them cleanly rather than gradually.
Customers, plans and allergens
One authoritative record of who is on what, with dietary needs structured and a precise address. Everything downstream derives from this.
Weekly selections
The other half of the source of truth. Once this and the customer record are in one place, derivation becomes possible at all.
Production and purchasing
Now generated rather than maintained. This is where the daily time saving actually appears, and where confidence is won.
Labels and delivery
Derived from the same selections, so the box, the label and the stop cannot disagree.
Reporting last
Once the operational data is trustworthy, reporting is a view rather than a reconciliation exercise.
Do not run both for long
A parallel period feels prudent and is the main source of implementation pain. Two systems holding the same customer facts means two versions of Tuesday, and staff will trust whichever one was right last time.
Pick a cut-over week, ideally a quiet one, and switch the source of truth in a single step. Keep the old spreadsheet readable for reference, but stop writing to it entirely on that date.
What usually goes wrong
Addresses and allergens. Both are typically held as free text, and both need structure to be useful, so migration means cleaning rather than copying. Budget real time for it and do it before the cut-over rather than during.
The second surprise is cut-off enforcement. If the rule has been flexible in practice, the first week of consistent enforcement generates customer conversations. Warn people in advance and it is a non-event.
Common questions
- How long should a parallel run last?
- As short as possible, ideally not at all. Two systems holding the same customer facts produce two versions of the same day, and staff will trust whichever was right most recently.
- What is hardest to migrate?
- Addresses and allergens, because both are usually free text and both need structure to be useful. That is a cleaning exercise rather than a copy, and it should happen before cut-over.
- When is the best time to switch?
- A quiet week, with the cut-off rule communicated to customers in advance. The first week of consistent enforcement is otherwise mistaken for the software being inflexible.
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
- 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.
- GuidesHow to choose meal delivery softwareMost software evaluations start with a feature comparison, which is the wrong end. Start from where your current week breaks, because that is what you are actually buying a fix for.
- GuidesOnboarding a new meal-plan customerSignup is the only moment a customer will patiently answer questions. What you fail to capture there, you will spend the next six months chasing — or worse, guessing at.
- 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.
- SolutionsManaging mid-cycle subscription changes without re-typing themSelling the subscription is the easy part. The work is everything that happens after, when a customer changes something and five downstream systems need to hear about it before Tuesday.