Between 25% and 30% of cloud kitchens in India close within their first year of operation. An NRAI survey in 2023 found that nearly half the cloud kitchens in Delhi, Mumbai, and Bangalore were running at a loss (BBFT, 2024). Those are not small numbers for an industry that was supposed to be the low-cost, low-risk alternative to opening a restaurant.
The market itself is growing. India’s cloud kitchen segment hit USD 1.24 billion in 2025 and is projected to reach USD 3.69 billion by 2034 (IMARC Group, 2025). Money is flowing in, but a large chunk of operators aren’t surviving long enough to see any of it.
The reasons aren’t mysterious. They follow a pattern, and most of them come down to five operational mistakes that repeat across cities, cuisines, and price points.
Key Takeaways
- 25-30% of Indian cloud kitchens shut down within year one (BBFT, 2024)
- Kitchens that never track cost per order find out too late that volume was not profit
- Bloated menus push food cost above 40%, making profitability nearly impossible
- Operators who build a second ordering channel alongside delivery apps survive longer
Why Does a Single Ordering Channel Squeeze Margins?
Delivery platforms bring a cloud kitchen the two things it cannot build alone at the start: demand and a delivery fleet. A new kitchen with no signage, no footfall and no customer list gets discovered on day one because the listing puts it in front of thousands of nearby users. The commission pays for that reach, for the riders, for payment handling and for the marketing that drives app traffic.
The problem is not the cost. It is running on that one channel and never measuring what each order actually leaves behind.
Every platform sets its commission by contract, and the rate differs by city, category and the terms an operator signs, so the only rate that matters is the one on your own agreement. Take that number and put it against a single order before you look at anything else.
Work it out as a formula on one order, using your own figures for every line. Order value XX, minus your contracted commission, minus your own food cost, minus your packaging, minus the share of rent, gas and wages that order carries. Whatever survives is your real margin, and it is usually a long way below the order value.
Run the same order through your own website or phone line and the commission line disappears, though packaging and marketing costs rise to fill part of the gap. Neither channel is free. They simply cost differently, and a kitchen needs to know both numbers.
We see this across food businesses on Petpooja all the time: an operator at month six still pulling 100% of revenue from a single channel, with no idea what contribution margin per order looks like. The platform dashboard reports what the platform can see, which is orders and sales. Cost per order sits inside the kitchen’s own books, and that is where it has to be calculated.
What Happens When the Menu Is Too Big?
Consider a typical scenario: 35 items on the listing across three cuisines. Indian, Chinese, Continental. Looks great on the app. Inside a 300 sq ft kitchen it works differently. The cook switches between Schezwan sauce and biryani masala every other order, and the mise en place for three cuisines does not physically fit on two prep tables. By 8:30 PM the food quality slips because everything is being made in a rush.
The financial damage is quieter but worse. In a menu that size a large share of items barely move, selling once or twice a week at best. Ingredients for slow-moving dishes sit in the fridge until they expire, and food cost climbs and stays there.
Unlike a dine-in restaurant where a waiter can steer a customer toward a slow-moving dish (“the chef’s special today is excellent, sir”), a cloud kitchen has no such lever. The item either sells on the app or it rots in the fridge. Food cost control in a delivery-only model works differently for exactly this reason.
The fix is boring but it works: launch with 8-12 items in one cuisine. Run it for 45-60 days. Look at what actually sells. Then build the next round of menu items from that data, not from what you personally enjoy cooking.
Why Do Ratings Drop Faster Than Cloud Kitchens Can Recover?
When a dine-in customer has a bad experience, the manager walks over, apologises, maybe sends a free dessert. The relationship gets a second chance. A cloud kitchen doesn’t get that.
For example, imagine the dal arriving cold because the delivery rider spent 10-12 minutes finding the right tower in a housing society. The customer opens the box, sees lukewarm food, taps 2 stars, and moves on. The kitchen owner finds out three hours later when the rating notification pops up. By then there’s nothing to fix.
Ratings compound downward, and that is what makes them hard to climb out of. Here’s a common pattern: a kitchen’s rating slides from, say, 4.3 to 3.9 over one bad weekend. Listings with lower ratings tend to surface less often in a crowded local feed, so fewer people see it and fewer orders come in.
The operator panics and turns on a deep discount to pull volume back. Orders return, but at near-zero margin. The kitchen is now spending money to get orders that don’t cover costs, and the rating still hasn’t recovered because the underlying quality problem (cold food, late dispatch, leaking boxes) hasn’t been diagnosed.
The diagnosis part is where most operators are blind. Was the rating drop about food quality? Packaging? Rider delays? A star rating tells you something changed. Working out which part of your own kitchen caused it needs your own data.
A cloud kitchen POS that tracks KOT-to-dispatch time per order can show, for example, that Thursday 8 PM orders take 22 minutes to prepare versus 14 minutes on Tuesday. Now the operator knows Thursday’s prep line is the bottleneck. Without that data, it’s guesswork dressed up as troubleshooting.
How Does Multi-Brand Complexity Sink Small Operators?
Two brands from one kitchen. Double the listings, double the orders, same rent. Every cloud kitchen owner has run this calculation in their head by week three. Very few have done it successfully by month six.
Adding a second brand doesn’t just mean a new listing. It means a separate ingredient inventory, different packaging stock, a second set of quality standards, and a kitchen that now has to sort 15 incoming orders at 8 PM across two brands without mixing them up.
A common scenario we’ve seen play out: the cook grabs the wrong branded container during rush hour. A burger brand’s packaging goes out with a biryani order inside it. The customer flags it, the review lands on the wrong listing, and both brands take a ratings hit.
The food itself was fine. The problem was the absence of a system that tags each KOT to the correct brand before it reaches the packing station.
Brand count does not create demand on its own. A second listing draws on the same kitchen, the same cook and the same prep table, so whatever is shaky in the first brand gets doubled rather than diluted.
Work out your own break-even order count first, get the brand comfortably past it, then consider brand number two.
Why Don’t Operators Know They’re Losing Money Until Month-End?
Here’s a hypothetical that plays out in cloud kitchens daily. A busy Wednesday closes with a gross sales figure on the dashboard that looks healthy. The owner reads it, feels relieved, and goes home thinking the day was good.
Was it? Gross sales is the top line, not the takeaway. Deduct your commission at whatever rate your contract carries. Then your food cost, your packaging, and the day’s share of rent, salaries, gas and electricity. Run the same subtraction on your own numbers before you call a day good.
What is left is usually a fraction of what the dashboard showed, and on some days it turns negative. The owner won’t know until someone sits down with Tally at the end of the month. By then weeks of thin-margin days have already drained the operating reserve.
The kitchens that survive past year one share a habit, not a tool. They check their numbers every single day. They know by 6 PM whether the day’s orders covered costs or fell short. What they track is item-level profitability, not just total sales. The most common excuse we hear is that the numbers can wait for the weekend. A POS that sends a daily P&L summary to WhatsApp, which is what Petpooja POSS does for cloud kitchens, takes that excuse away.
Across 1,00,000+ food businesses on Petpooja, the cloud kitchen disadvantages that catch operators off guard almost always involve a delayed awareness of their own unit economics.
Conclusion
The cloud kitchen model itself isn’t the problem. A lower entry cost than a dine-in restaurant, no dining hall rent, and healthy margins when it is run well. The problem is a playbook that most operators copy from each other without questioning. A 30-item menu on day one. A single ordering channel at month six. No daily cost tracking, a second brand launched before the first can stand on its own, and discount-driven panic the moment ratings dip.
Operators who last beyond twelve months tend to do none of those things. Small menu, a direct channel running alongside the apps from month two, daily P&L on their phone, one brand until it is clearing its own break-even without paid boosts.
Frequently Asked Questions
25-30% shut down within their first year, on the BBFT figures cited above. Closure is not the only outcome worth watching, though. A far larger share keeps trading while running at a loss, which is why the survey finding matters more than the shutdown rate. Independent single-brand operators fare worse than franchise or multi-brand setups.
Because gross sales and profit are different numbers. Commission, food cost, packaging, rent and wages all come out before anything reaches the owner. Operators who don’t track item-level profitability often discover the shortfall only at month-end, long after they could have acted on it.
Readiness is about slack, not ambition. The first brand should be holding its volume without paid boosts, keeping its rating steady through a busy weekend, and its food cost should be a number the owner knows without looking it up. A second listing splits one kitchen, one cook and one prep table across two sets of standards, so any wobble in the first brand doubles.
Print QR codes on every delivery box linking to your own ordering page. Build a WhatsApp broadcast list from repeat customers and give them a reason to return, such as a loyalty stamp or early access to a new dish. Keep your menu prices consistent across every channel. This works alongside the apps rather than replacing them, since the apps keep bringing new customers the kitchen would not reach otherwise. More on cloud kitchen marketing strategies beyond platform ads.
Divide your fixed monthly costs by the profit you keep on an average order. That is your break-even order count, and it is specific to your rent, your food cost and your channel mix. Any number quoted as a general benchmark will be wrong for your kitchen, because those three inputs vary enormously.
