Guides
Setting up meal plans properly the first time
Plan definitions are cheap to get right at the start and expensive to change once customers are on them, because every alteration is a conversation with everyone affected.
What to decide, in order
Meals per week
The number that drives slot generation and therefore what the kitchen owes. Keep the set small; every additional tier multiplies the combinations you support forever.
Delivery days
Per customer, not per plan. Meals per week and delivery days are different numbers — several meals often arrive in one drop.
Term length
And whether it ends or renews. This single choice determines whether you need renewal conversations or cancellation handling.
The cut-off
Derived from your longest supplier lead time plus planning. Set it once, publish it, enforce it in software.
Pause and skip rules
Extend or forfeit. Written into the terms before the first customer asks.
Resist plan proliferation
The instinct when a prospect asks for something slightly different is to create a plan for it. Three plans become nine, and every operational rule now has nine cases.
A smaller set with clear rules serves customers better than a large set nobody can explain, and it keeps the exceptions manageable when someone inevitably needs one.
The field people forget
An authoritative end date. Without it a plan runs forever, and kitchens end up producing for customers who finished paying months ago — a loss that appears nowhere in a profit and loss report because the revenue was never expected.
Set it at creation, derive it from the term, and let it expire the subscription on its own.
Common questions
- How many meal plans should a kitchen offer?
- Fewer than instinct suggests. Every additional tier multiplies the combinations your operational rules have to handle, and a small clear set is easier for customers to choose from too.
- Are meals per week and delivery days the same thing?
- No, and conflating them causes confusion. Ten meals a week commonly arrives across two or three drops, so the two numbers are configured independently.
- What is most often missed at plan setup?
- An authoritative end date. Without one the plan runs indefinitely and the kitchen keeps cooking for customers whose paid term finished, which no report surfaces.
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 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.
- 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.
- GuidesImplementing meal delivery software without a bad weekThe 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.
- GuidesThe meal subscription management workflowMost operational failures in this business are not decisions made wrongly but decisions that failed to travel. Setting out the workflow explicitly is how you find where yours leaks.
- 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.