Solutions
Managing mid-cycle subscription changes without re-typing them
Selling 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.
The change is the product
A meal-plan business is really a change-processing business that happens to cook. In a healthy operation the majority of customer contact is not complaints or sales — it is amendments, and how cheaply those amendments are absorbed determines how many customers one person can carry.
The cost of a change is not the decision, which takes seconds. It is the propagation: finding every place the old answer was written down and correcting it, without missing one and without breaking anything already committed.
The changes that actually arrive
Ranked roughly by how often a kitchen sees them.
Pause and resume
Travel, illness, Ramadan, a month away. The most common request and the one most likely to become a cancellation if it is made difficult.
Skip a single delivery
A lighter-weight pause. Different enough to deserve its own action rather than a note in a chat thread.
Swap a meal
Almost always harmless before the cut-off and impossible after it. The rule needs to be enforced by the system rather than remembered.
Change plan size
The commercially valuable one. It changes slot counts, production, purchasing, labels and the amount owed in the same breath.
Change address or notes
Trivial in a database and expensive on the road, because a stale address costs a delivery and a phone call.
Atomic, audited, or neither
Two properties make change handling trustworthy. Atomic: either every consequence of a change lands or none does, so there is never a half-applied upgrade where the customer is charged but the kitchen never heard. Audited: every change carries who made it and when, so a dispute is settled by looking rather than by remembering.
Without those, a system that propagates changes automatically is more dangerous than a spreadsheet, because it is trusted more.
Common questions
- What is a cut-off and why does it matter so much?
- A cut-off is the point after which a week is frozen for purchasing and production. It matters because it is the boundary between a change that is free and a change that means throwing food away, and it should be enforced by the system rather than by whoever answers the message.
- Should a plan upgrade take effect immediately or next cycle?
- Immediately if the current week is still open, and from the next week if the cut-off has passed. The important part is that the same rule applies every time, so customers and staff can both predict the answer.
- How should address changes reach the driver?
- By being the same record. A manifest generated at dispatch from the live customer record cannot carry an address that was changed yesterday, whereas an exported list printed on Sunday can and does.
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 subscription software and the lifecycle it has to modelSubscription software for digital products only has to keep charging a card. A meal subscription also has to keep a kitchen, a packing bench and a van in step with whatever state it is in today.
- 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.
- SolutionsThe customer record in a meal-plan business is an operational documentIn most industries a CRM is a sales tool. In a meal-plan kitchen the customer record drives what gets cooked and where it goes, which makes it the most operationally dangerous data in the business.
- SolutionsMeal delivery scheduling, cut-offs and the calendar problemScheduling looks like the simplest part of a meal-plan operation and is quietly one of the hardest, because the calendar a Gulf kitchen runs on is not the one most software assumes.