Cloud kitchen costs: the numbers before you start

A cloud kitchen is a commercial kitchen that cooks for delivery only — no dining room, no tables, no walk-in customers. Orders arrive through delivery apps or through your own storefront, and the food leaves by the back door. That is the whole definition. The hard part is not the idea. It is the operation.

Most cloud kitchens close. That is not a slogan and it is not a reason to avoid the model — it is the starting condition, and nobody renting you kitchen space is going to lead with it. But the reasons those kitchens closed are not mysterious, and most of them have nothing to do with the cloud kitchen idea itself.

This page goes through the numbers as they are, then through what the operators who survive do differently.

Why most cloud kitchens close

The first and largest reason: delivery-app commission. A kitchen that depends entirely on the apps hands over ⟨verify: commission band, % of order value⟩ of every order. Add food cost, packaging, rent and labour on top of that. What is left is a very thin margin, and one quiet week is enough to turn it negative.

The second: there is no repeat customer. Someone who orders through a delivery app is not your customer — they are the app’s. You do not have their number, you do not know when they order, and you cannot reach them. Every month you start from zero and buy the orders again.

The third: operational chaos. A kitchen with thirty subscribers can be run on a notebook and a messaging app. A kitchen with a hundred cannot. The mistakes start: a meal forgotten, a subscription that lapsed with nobody noticing, an order sent to the wrong address, an ingredient that ran out on a Sunday because nobody counted. Every mistake costs money and reputation, and reputation is the expensive one.

The fourth: expanding at the wrong time. A second kitchen before the first one is proven, or a menu of forty dishes when five of them carry most of the sales.

What it actually costs

The figures below are ranges rather than quotes, and they move with city, floor area and how much of the fit-out you inherit ⟨verify — replace with sourced figures for the markets this page targets⟩:

Setup costs

Rent for an equipped kitchen starts around ⟨verify: USD per month, small equipped unit⟩ for a small unit and reaches ⟨verify: USD per month, larger unit or better location⟩ for more space or a better location. A fully equipped kitchen saves you buying the equipment outright, and that is the single biggest difference in the capital you need on day one.

Licensing, commercial registration and food-safety certification: ⟨verify: USD, first year⟩. This is the line that varies most between countries — the steps themselves differ, not only the amounts.

Initial fit-out and opening stock: ⟨verify: USD, scales with menu size⟩.

Recurring monthly costs

Rent, labour (a cook and an assistant at minimum), raw ingredients, packaging, utilities, and app commission if you use the apps.

Packaging is the line people underestimate. A single meal container of reasonable quality costs ⟨verify: USD per container⟩. A hundred meals a day is ⟨verify: USD per month — must equal the per-container figure × 100 × 30⟩ on packaging alone.

Break-even

Work it out honestly before you start: add up every fixed monthly cost and divide by your gross margin per meal. The result is how many meals you have to sell each month not to lose money. If that number is larger than your kitchen can physically cook, the business does not work at those figures — and finding that out early is not a failure.

What the ones that survive do differently

They sell subscriptions, not one-off orders

This is the difference that matters. A one-off order comes through an app, the app takes a large share of it, and it does not repeat. A weekly or monthly subscription comes to you directly, with no commission, and it is known in advance. On Wednesday you know how many meals you are cooking on Sunday, so you buy accurately, waste less, and staff to a real number.

Subscriptions change the whole economics. Margin rises because the commission disappears. Waste falls because the quantities are known. Cash flow improves because the customer pays up front.

They own the customer relationship

The phone number, the order history, the preferences, the allergies. Those are the real assets of the business. A kitchen with three hundred subscribers it knows by name owns something. A kitchen with three hundred app orders a month owns nothing.

They start with a small menu

Five to eight dishes cooked well and consistently, instead of forty where half never sell and their stock is thrown away.

They organise operations before they break

This is where most of the closures actually happen. The business rarely fails at the first customer. It fails at the fiftieth or the hundredth, when the chaos outgrows what a notebook and a messaging app can hold.

Where operations break

There is a threshold every operator who has been through this recognises. Somewhere around ⟨verify: subscriber count where manual operations fail⟩ subscribers, things start slipping:

Messages pile on top of each other and one gets missed. Subscriptions lapse without anyone noticing, so you lose a customer who would have renewed if reminded. The day’s cook list is worked out by hand every morning, so the quantities come out wrong. Deliveries leave without being grouped by area, so the driver spends two extra hours on the road. Meal labels are written by hand, so a gluten-free meal reaches the wrong person.

Each of these is small on its own. Together they are the real reason kitchens close — not the cloud kitchen idea.

Sahtein is a meal-subscription management system built for exactly this stage: the menu, weekly and monthly plans, the day’s cook list, deliveries grouped by area, labels, and subscriber management in one place. It does not turn a losing business into a profitable one — no system does that. It prevents the chaos that closes the profitable ones.

You can look at what the system does in detail, or at the plans and pricing.

Is a cloud kitchen right for you?

Probably yes, if:

You already cook and sell to real customers, and you want to grow without opening a dining room. Or you have a clear specialism — diet meals, meals for athletes, a home kitchen with a particular character — and an audience that already knows you. Or you want to build a base of subscribers who pay in advance.

Probably not, if:

You are looking for a business that runs without you in it daily. A cloud kitchen is hard work with its owner present. Or your plan depends entirely on the delivery apps. Or you have not worked out your break-even yet.

The bottom line

The warning that most cloud kitchens close is not wrong. Most of them do. But they do not close because the idea is bad. They close because they are run on a thin margin, with no direct relationship to the customer, using tools that stop working somewhere past the fiftieth order.

Start small, sell subscriptions rather than one-off orders, keep your customers on your own books, and work out your break-even honestly before you pay the first month’s rent.