A meal subscription is a different business from on-demand delivery. The customer pays in advance, the kitchen plans production, and the delivery schedule is known. That predictability can improve margin and retention. It can also trap an operator in a plan that is priced below cost.
Subscription software has to handle recurring billing, menu rotation, cut-off times, pauses, skips, addresses and cancellations. If the platform only supports one-off orders, the subscription becomes a spreadsheet.
| Plan model | How it works | Best for | Main risk |
|---|---|---|---|
| Prepaid meal pack | Customer buys 10/20 meals upfront | Lunch clubs, offices | Breakage and refunds |
| Weekly subscription | Recurring weekly delivery | Families, health meals | Churn and menu fatigue |
| Daily tiffin | Fixed meal, fixed time | Students, workers | Route density and timing |
| Flexible credits | Buy credits, order when hungry | Hybrid on-demand | Unused liability |
| Corporate plan | Company pays per employee/meal | Office lunches | Invoicing and headcount changes |
Price the plan from the kitchen, not the discount
A subscription discount is not free. Calculate food cost, packaging, delivery, payment fees, support and expected skip/refund rate. Then set the plan price so the contribution per delivered meal is positive even in a low-utilisation week.
Prepaid plans improve cash flow, but they create a liability: the customer has paid for meals not yet delivered. Track the unredeemed balance and recognise revenue as meals are delivered. Do not spend the cash as if it were profit.
Menu rotation and cut-off times
Publish the menu a week ahead and set a cut-off two or three days before delivery. That gives the kitchen time to order stock and plan production. Customers need to skip, pause or change an address before the cut-off; after that, the meal is committed.
Rotate menus on a four-week cycle to avoid fatigue, but keep two or three favourites every week. Predictability is part of the value; surprise is not.
Delivery windows and route density
Subscriptions work best when deliveries cluster in a time window and a zone. A tiffin service that promises “between 12 and 2” across a wide city will struggle. Narrow the window and the zone, even if it means fewer customers at first. Density is the margin.
Pauses, skips and cancellations
- Allow a limited number of skips per month.
- Require notice before the cut-off.
- Offer a pause for holidays or travel.
- Make cancellation possible without a support ticket.
- Refund unused credit according to a clear policy.
- Track involuntary churn (payment failure) separately from voluntary churn.
Retention metrics
Track active subscribers, meals delivered per subscriber, skip rate, payment failure rate, month-1 and month-3 retention, contribution per meal and unredeemed liability. A plan with high sign-ups and low retention is a discount programme, not a subscription business.
What to test before launch
- Run one plan, one menu cycle and one delivery window for 30 days.
- Measure production cost, delivery cost and skip rate.
- Ask customers why they skipped or cancelled.
- Check that the software handles a pause and a refund.
- Confirm the unit economics at 50% and 80% utilisation.
- Only then add a second plan or zone.
See the food delivery software, the loyalty guide, or the $299 licence.
Subscription mistakes
- Spending prepaid cash as if it were earned revenue.
- Offering unlimited skips, which makes production planning impossible.
- Pricing on a full-utilisation week and losing money at 50%.
Track the unredeemed meal liability weekly and test the plan at low utilisation before adding customers.