The Unit Economics of a Cloud Kitchen: What the Numbers Actually Look Like
24/03/2026. By Skope Kitchens
Most cloud kitchens don't fail because of bad food or poor reviews. They fail because the underlying numbers never made sense to begin with. Orders come in, ratings stay decent, and yet within six to twelve months the kitchen shuts down — not from lack of demand, but from margins that were never sustainable.
This guide walks through what real revenue and cost structures look like for a mid-performing kitchen in an Indian metro, where the money typically disappears, and which levers actually move the needle.
What unit economics actually means here
Unit economics comes down to one question: how much profit do you make per order, and does that hold up as you scale?
Most operators track total revenue. The ones who survive track profit per order and cost efficiency per kitchen. The distinction matters because if your per-order economics are broken, growth makes things worse, not better. More orders means more losses at a faster rate.
A realistic monthly P&L
Take a mid-performing cloud kitchen doing 150 orders a day at an average order value of ₹300. That's ₹13.5 lakh in monthly revenue — a reasonable baseline for this exercise.
The P&L table above shows where that revenue actually goes in an optimised scenario. Total costs come to roughly ₹9.89 lakh, leaving a net profit of ₹3.61 lakh — a margin of about 26.7%.
Before that number sounds encouraging, it's worth being direct: this is the good version. Most kitchens operate at 10–18% margins, and many run at breakeven or below in the early months. The numbers above assume reasonably tight control across every cost line. In practice, small inefficiencies compound quickly.
Where the money goes — and where it disappears
Aggregator commission is usually the single largest cost, running between 18–25% of revenue. At 22%, that's nearly ₹3 lakh on a ₹13.5 lakh month — before you've spent a rupee on food or staff. It's also one of the hardest costs to reduce, since most cloud kitchens depend almost entirely on Zomato and Swiggy for discovery.
Food cost is where margins most often collapse quietly. The range is 28–35%; at 32%, this kitchen spends ₹4.32 lakh on ingredients, packaging, and wastage. Poor portion control, too many SKUs, or menu items with no ingredient overlap can push this north of 40% before anyone notices.
Staff costs are frequently underestimated, especially early on. A team of two chefs and two helpers in a metro typically costs ₹80,000–₹1.2 lakh per month. The bigger risk isn't the headline number — it's what happens when kitchens hire reactively, lack any standard processes, and build operational dependency on individual cooks.
Rent and utilities at ₹80,000 feel manageable at ₹13.5 lakh revenue, but the ratio tightens fast if order volumes dip. Location visibility is largely irrelevant for a cloud kitchen; location efficiency — delivery radius, accessibility for riders, rent per sq ft — is everything.
Marketing and discounts deserve more scrutiny than they usually get. Aggregator ads, platform discounts, and visibility spends are often treated as growth investment. They are, but they also directly reduce the effective margin on every order they drive.
What the per-order math looks like
Breaking the P&L down to the order level makes the stakes concrete. On a ₹300 order: commission takes ₹66, food cost takes ₹96, and all other costs account for roughly ₹90. Total cost: ₹252. Profit per order: ₹48.
That ₹48 is your real unit margin. A ₹20 increase in food wastage per order, or a discount that brings the effective order value down to ₹250, wipes most of it out. At this level, every inefficiency is felt immediately.
Breaking the P&L down to the order level makes the stakes concrete. On a ₹300 order: commission takes ₹66, food cost takes ₹96, and all other costs account for roughly ₹90. Total cost: ₹252. Profit per order: ₹48.
That ₹48 is your real unit margin. A ₹20 increase in food wastage per order, or a discount that brings the effective order value down to ₹250, wipes most of it out. At this level, every inefficiency is felt immediately.
Near-total aggregator dependency is the most common trap. When 90–100% of orders come through platforms, the commission line is essentially fixed and high. There's no negotiating power, no brand ownership, and no way to build a repeat customer base that orders direct.
Unengineered menus are a close second. Too many items, low-margin dishes, and ingredients that don't overlap across the menu all push food cost higher silently.
Low average order values create a structural problem that volume alone can't fix. A kitchen running at ₹150–200 AOV faces commission and food cost percentages that leave almost nothing per order — and chasing higher volumes to compensate just increases operational pressure.
Overstaffing without systems leads to higher payroll, inconsistent output, and an operation that scales poorly. Standard processes reduce the headcount needed and make the kitchen less dependent on any individual.
Discount-driven growth can build order numbers that look encouraging while quietly compressing margins to the point where growth itself becomes the problem.
The five patterns that break the economics
Near-total aggregator dependency is the most common trap. When 90–100% of orders come through platforms, the commission line is essentially fixed and high. There's no negotiating power, no brand ownership, and no way to build a repeat customer base that orders direct.
Unengineered menus are a close second. Too many items, low-margin dishes, and ingredients that don't overlap across the menu all push food cost higher silently.
Low average order values create a structural problem that volume alone can't fix. A kitchen running at ₹150–200 AOV faces commission and food cost percentages that leave almost nothing per order — and chasing higher volumes to compensate just increases operational pressure.
Overstaffing without systems leads to higher payroll, inconsistent output, and an operation that scales poorly. Standard processes reduce the headcount needed and make the kitchen less dependent on any individual.
Discount-driven growth can build order numbers that look encouraging while quietly compressing margins to the point where growth itself becomes the problem.
A smarter way to start: the Kitchen-as-a-Service model
The levers that actually work
Raising the average order value is the single highest-impact lever available to any operator. Moving from ₹300 to ₹400 doesn't require new customers or more orders — just better menu design: combos, add-ons, meal bundles. Even a ₹50 improvement per order has a significant effect at scale.
Getting food cost below 30% requires discipline in three areas: supplier negotiation, portion standardisation, and menu simplification. Fewer SKUs with more ingredient overlap is usually the fastest path.
Running multiple brands from one kitchen is how the fixed cost structure starts working in your favour. Shared rent, shared staff, shared equipment — but separate storefronts that expand addressable demand without proportional cost increases.
Building direct ordering channels doesn't need to replace aggregators entirely. Even 10–20% of orders coming through direct channels measurably improves the overall margin profile.
SOP-driven operations reduce reliance on individual staff, cut wastage, and make the kitchen scalable. The cost of building these systems is real but one-time; the benefit compounds every month.
The thing most people get wrong about scaling
Many of the cost and complexity problems above aren't inevitable — they're the result of building everything from scratch in a model that doesn't require it.
Skope Kitchens takes a different approach. Instead of setting up a kitchen independently and absorbing every fixed cost upfront, operators launch through Skope's plug-and-play infrastructure — delivery-ready kitchens, proven SOPs, integrated inventory and order management software, and a team already in place. The result is a launch in under 10 days with substantially lower setup costs and a cost structure that's built for margin discipline from day one.
The things that typically drag down unit economics — inconsistent food cost, reactive staffing, no operational systems — are addressed at the infrastructure level rather than left to each operator to figure out independently. Skope also runs a multi-brand model from shared kitchen space, which means fixed costs like rent and equipment get distributed across multiple revenue streams rather than sitting entirely on one.
For anyone serious about the economics of cloud kitchens, that's a meaningful structural advantage.
If you're planning to launch or want to understand whether your current setup can be made more profitable, Skope offers a free expert consultation — schedule your call here.
The levers that actually work
Raising the average order value is the single highest-impact lever available to any operator. Moving from ₹300 to ₹400 doesn't require new customers or more orders — just better menu design: combos, add-ons, meal bundles. Even a ₹50 improvement per order has a significant effect at scale.
Getting food cost below 30% requires discipline in three areas: supplier negotiation, portion standardisation, and menu simplification. Fewer SKUs with more ingredient overlap is usually the fastest path.
Running multiple brands from one kitchen is how the fixed cost structure starts working in your favour. Shared rent, shared staff, shared equipment — but separate storefronts that expand addressable demand without proportional cost increases.
Building direct ordering channels doesn't need to replace aggregators entirely. Even 10–20% of orders coming through direct channels measurably improves the overall margin profile.
SOP-driven operations reduce reliance on individual staff, cut wastage, and make the kitchen scalable. The cost of building these systems is real but one-time; the benefit compounds every month.
Scaling does not fix broken economics. It amplifies them. A kitchen with a ₹30 per-order loss at 100 orders a day loses ₹90,000 a month. At 300 orders, it loses ₹2.7 lakh. Opening a second location triples the problem.
Growth works when margins are stable, processes are repeatable, and demand is predictable. Those aren't outcomes of scale — they're prerequisites for it.
The operators who build durable cloud kitchen businesses tend not to be the most creative cooks or the best marketers. They're the ones who understand their numbers clearly, control costs consistently, and treat profitability as something that has to be engineered before the business earns the right to grow.
Ready to build a kitchen with the right economics from the start?Start with Skope Kitchens — delivery-ready infrastructure, zero capex setup, and a team that's already helped over 8 brands launch and scale.
The thing most people get wrong about scaling
Scaling does not fix broken economics. It amplifies them. A kitchen with a ₹30 per-order loss at 100 orders a day loses ₹90,000 a month. At 300 orders, it loses ₹2.7 lakh. Opening a second location triples the problem.
Growth works when margins are stable, processes are repeatable, and demand is predictable. Those aren't outcomes of scale — they're prerequisites for it.
The operators who build durable cloud kitchen businesses tend not to be the most creative cooks or the best marketers. They're the ones who understand their numbers clearly, control costs consistently, and treat profitability as something that has to be engineered before the business earns the right to grow.
Ready to build a kitchen with the right economics from the start?Start with Skope Kitchens — delivery-ready infrastructure, zero capex setup, and a team that's already helped over 8 brands launch and scale.
Scaling does not fix broken economics. It amplifies them. A kitchen with a ₹30 per-order loss at 100 orders a day loses ₹90,000 a month. At 300 orders, it loses ₹2.7 lakh. Opening a second location triples the problem.
Growth works when margins are stable, processes are repeatable, and demand is predictable. Those aren't outcomes of scale — they're prerequisites for it.
The operators who build durable cloud kitchen businesses tend not to be the most creative cooks or the best marketers. They're the ones who understand their numbers clearly, control costs consistently, and treat profitability as something that has to be engineered before the business earns the right to grow.
Ready to build a kitchen with the right economics from the start?Start with Skope Kitchens — delivery-ready infrastructure, zero capex setup, and a team that's already helped over 8 brands launch and scale.
