UNIT-ECONOMICS GUIDE
Cloud-kitchen unit economics: connect each order to monthly break-even
A cloud kitchen may avoid a dining room, but it does not avoid unit economics. Delivery-platform charges, packaging, discounting and advertising can make the variable-cost structure unusually important. Build the model from one delivered order, then scale it to realistic capacity.
Start with average restaurant revenue per delivered order
Use delivered orders and restaurant-owned revenue under a documented definition. Separate cancelled or fully refunded orders because they can carry cost without normal revenue. Segment by brand or cuisine when their order values and recipes differ materially.
Worked monthly model
Assume average restaurant revenue is ₹500 per delivered order. Average food cost is ₹150, packaging ₹30, platform services ₹100, funded discounts ₹35, advertising ₹25 and refund or waste allowance ₹10. Contribution is ₹150 per order.
If monthly fixed cost is ₹300,000, simplified break-even is 2,000 delivered orders per month. At 30 operating days, that is about 67 orders per day. This result is meaningful only if the kitchen can deliver that volume at the assumed cost and quality.
| Per delivered order | Amount |
|---|---|
| Restaurant revenue | ₹500 |
| Food cost | −₹150 |
| Packaging | −₹30 |
| Platform services | −₹100 |
| Funded discount | −₹35 |
| Advertising | −₹25 |
| Refund/waste allowance | −₹10 |
| Contribution per order | ₹150 |
Add capacity and step costs
Break-even is not perfectly linear. At a certain daily volume, an additional cook, packing station or equipment shift may be required. Delivery delays can increase cancellations and reduce ratings. Model capacity bands: for example, up to 60 orders per day with the current team, 61–100 with an additional staff cost, and more than 100 with added equipment.
Separate peak capacity from daily average. A kitchen averaging 67 orders may still fail if 50 arrive in a two-hour dinner window and the line can process only 30.
Run sensitivity cases
Test at least four changes: a 5% fall in order value, a 3 percentage-point rise in food cost, a higher effective platform fee, and a lower organic share requiring more advertising. Small changes can shift break-even sharply because the denominator is contribution per order.
Also test improvement cases such as a better menu mix, lower packaging cost, reduced refund rate or higher add-on attachment. Avoid relying on one optimistic forecast.
Metrics worth reviewing weekly
- Delivered and cancelled orders by daypart.
- Restaurant revenue and contribution per delivered order.
- Food and packaging cost by brand or menu category.
- Effective platform-service cost as a percentage of defined revenue.
- Restaurant-funded discount and advertising per order.
- Refund, rejection and complaint rate.
- Order preparation time and peak-hour capacity utilisation.
- Repeat contribution when reliable cohort data is available.
Frequently asked questions
Is bank payout the same as revenue?
No. Payout is a cash settlement after multiple deductions, credits and tax movements. Revenue and contribution require consistent economic classification.
Should rent be divided per order?
You may divide fixed cost by volume for planning, but keep it separate from variable contribution so the break-even relationship remains visible.
Can multiple virtual brands share costs?
Yes, but use a documented allocation driver such as preparation time, labour hours, storage or delivered orders. Avoid arbitrary allocations that hide a weak brand.
Illustrative business education, not financial advice. Replace all example inputs with actual outlet data.