Guides
How to manage recurring meal orders
Once an order repeats, the operational job stops being order entry and becomes amendment handling. Almost everything that goes wrong at scale traces back to that shift being unacknowledged.
Generate forward, but bounded
Future deliveries have to be made concrete so the kitchen can see next week and the customer can plan around it. But generating them indefinitely creates days that exist past the end of the paid term — and cooking for a term that has expired is a pure loss that no report surfaces.
The sensible bound is the paid term on one side and the cut-off on the other. Inside that band, days are real and editable; outside it they either do not exist yet or are frozen.
Amend the future, never the past
The rule that prevents most data disasters is that anything already delivered or failed is a record of a physical event and must never be rewritten to make the current state look tidy.
Cancel a subscription and future scheduled days disappear. Delivered days, their outcomes and their invoices stay exactly as they were, because they are the evidence you will need if the amount is ever questioned.
The amendments that dominate the workload
Pauses and skips
By volume, the majority of contact. Worth making self-service before anything else is automated.
Meal swaps
Free before the cut-off, impossible after it. The rule needs to be enforced rather than remembered.
Plan size changes
The commercially important one, because it changes slots, production, purchasing and the amount owed together.
Address and access changes
Cheap to record and expensive to miss, since a stale address costs a delivery and an interrupted kitchen.
Common questions
- How far ahead should recurring deliveries be generated?
- Far enough that customers can see and plan their upcoming weeks, and never beyond the end of the paid term. Generating past the term is how kitchens end up producing food for customers who have finished paying.
- Should each delivery be editable independently?
- Yes, up to the cut-off. Independent editability is what lets a customer skip one day without disturbing the rest, which is a much lighter action than pausing the whole plan.
- How do you stop a recurring order cleanly?
- Skip every future scheduled day, remove them from production and manifests, and leave delivered history, proof of delivery and invoices untouched. Clean stopping is mostly about what you do not delete.
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
- GuidesHow to manage meal-plan pauses and skipsPausing is the most common request a meal-plan business receives and the one most often handled badly — usually because it is treated as a note rather than as a state change with consequences.
- SolutionsOrder management when the orders repeat themselvesOrder management systems assume an order is created, fulfilled and closed. A meal-plan order is created once and fulfils itself over and over, which breaks most of the assumptions underneath the category.
- GuidesSetting a meal delivery cut-off that actually holdsThe cut-off is the single most consequential number in a meal-plan operation. It is the line between a change that costs nothing and a change that costs food.
- GuidesRenewals and churn in a meal-plan businessMost meal-plan customers do not leave in a dramatic moment. Their term quietly ends, nobody notices, and a month later they are simply gone — which makes renewal an operational problem before it is a marketing one.