Guides
Setting a meal delivery cut-off that actually holds
The 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.
What the cut-off protects
Two commitments sit behind it. The first is purchasing: once an order goes to a supplier, the ingredients are yours whether or not the customer still wants the meal. The second is labour: once prep has been planned around a set of counts, changing them means re-planning a shift.
A cut-off that sits later than either commitment is decorative. It looks like a rule while the business absorbs every change anyway.
Working out where yours belongs
Start from the physical constraint and work backwards, rather than picking a time that sounds reasonable.
Find the longest lead time
Identify the supplier who needs the most notice for the ingredients you cannot substitute.
Add your planning time
The hours between having final counts and being able to issue a purchase order and a prep plan.
Add a margin for exceptions
Enough room that a single late change does not immediately break the chain.
Publish the result
State it on the plan screen, not only in the terms, so customers see it while they are deciding.
Enforce it in software, not in conversation
A cut-off enforced by a person is a cut-off that varies by person, mood and hour. It also concentrates a difficult judgement on whoever happens to be reading messages, which is rarely the person who bears the cost of getting it wrong.
When the system simply moves a late change to the next open week, the rule stops being a negotiation. Staff are freed from defending it, and customers get a consistent answer, which is what they actually wanted.
Make the boundary visible to customers
Most late requests are not attempts to game the rule. They are made by people who had no way of knowing where the line was.
A plan screen that marks which upcoming days are still editable and which are locked removes a large share of those requests before they are sent — which is a support saving as much as an operational one.
Common questions
- How late can a cut-off reasonably be?
- It is bounded by your longest unavoidable supplier lead time plus the hours you need to plan production. Setting it later than that means the business quietly absorbs the cost of every late change.
- Should exceptions ever be made after the cut-off?
- Occasionally and deliberately, as a goodwill decision by someone who understands the cost — not as a routine accommodation. Routine exceptions turn the cut-off into a suggestion and the planning behind it into guesswork.
- What should happen to a change submitted too late?
- It should apply to the next open week rather than silently altering food already being purchased or cooked. Rolling it forward is honest, predictable, and costs nothing.
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.
- GuidesProduction planning for a meal-plan kitchenProduction planning here is unusually tractable, because unlike a restaurant you know your entire day before it starts. The difficulty is not forecasting — it is keeping the plan in step with a customer base that keeps changing its mind.
- 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.
- GuidesIngredient forecasting for meal-prep kitchensPurchasing is where a meal-plan kitchen’s margin is actually decided, and it is downstream of information the business already has. Most over-buying is not a forecasting failure but a plumbing failure.
- SolutionsSoftware for workplace lunch programmesA daily office lunch programme is not a corporate meal plan on a faster clock. The shorter cycle changes which parts of the operation are hard.