Shashi Mishra
Founder, Restrofi
TL;DR
A cloud kitchen lives or dies on delivery-platform commission, which can eat 25–30% of every order. The operators who profit run multiple virtual brands from one kitchen on a single management system that aggregates Swiggy, Zomato and direct orders into one dashboard — and push repeat customers to their own commission-free ordering website. Setup in India runs ₹3–8 lakh for a small kitchen, plus an FSSAI licence and GST registration.
What a Cloud Kitchen Actually Is in 2026
A cloud kitchen — also called a dark kitchen, ghost kitchen, or delivery-only kitchen — is a food business with no dining room. No tables, no waiters, usually no signboard a customer ever walks past. Every order arrives on a screen: Swiggy, Zomato, your own website, or WhatsApp. The kitchen cooks, packs, hands the bag to a rider. That is the entire operation.
In India the model exploded for one reason: rent. A 1,200 sq ft dine-in restaurant on a high street in Bengaluru or Pune can cost ₹2–4 lakh a month. A 300 sq ft cloud kitchen two lanes away costs ₹25,000–60,000. You trade footfall for delivery radius — and in a country where the two big aggregators reach tens of millions of users, that trade often makes sense.
By 2026 the market has matured well past the "just list on Swiggy" phase. The operators who survive run multiple virtual brands out of one kitchen — a biryani brand, a healthy-bowls brand, and a dessert brand sharing the same range and the same three cooks. Each brand is a separate listing on the aggregators, but the kitchen, inventory, and staff are pooled. That is exactly where a real cloud kitchen management system stops being a nice-to-have.
The Economics: Why Delivery Commission Decides Everything
Before you choose software or sign a lease, do the commission math, because it is the number that decides whether a cloud kitchen is a business or a hobby.
Aggregator commission in India typically lands between 18% and 25% of order value, but the effective take is higher once you add payment-gateway fees, mandatory discounts you fund, and ad spend to stay visible. Here is what a ₹100 order on an aggregator really looks like for many operators:
| Line item | Amount on a ₹300 order |
|---|---|
| Order value | ₹300 |
| Aggregator commission (~22%) | −₹66 |
| Payment + platform fees (~3%) | −₹9 |
| Discount funded by you (~10%) | −₹30 |
| Net you receive | ₹195 |
| Food + packaging cost (~35% of order) | −₹105 |
| Gross margin before rent/labour | ₹90 |
That ₹90 has to cover rent, gas, electricity, labour, and your salary. The lesson is brutal and simple: on aggregator-only orders, your margin is permanently rented from a platform. The single highest-leverage move a cloud kitchen can make is to convert repeat customers to a channel where you keep all ₹300 — your own ordering website. More on that below.
What a Cloud Kitchen Management System Must Do
A "cloud kitchen management system" is the software layer that turns a chaotic stream of orders from several platforms and several brands into one calm workflow. If you run two brands on Swiggy and Zomato, that is potentially four tablets beeping at once. A good system collapses that.
Here is the capability checklist to judge any cloud kitchen software against:
| Capability | Why it matters |
|---|---|
| Multi-channel order aggregation | Swiggy, Zomato, website and WhatsApp orders land in one screen instead of four tablets |
| Multi-brand support | Run several virtual brands from one kitchen, with separate menus but pooled reporting |
| Kitchen Display System (KDS) | Cooks see a live queue with prep timers instead of paper chits that get lost in a rush |
| Centralised menu management | Change a price or mark an item out-of-stock once and it syncs everywhere |
| Inventory & recipe costing | Track usage per dish so you know your true food cost and stop running out mid-shift |
| Direct/own-channel ordering | A commission-free website or QR link you own |
| Analytics across channels | See which brand, item, and hour actually make money |
If a vendor only does billing, it is a POS, not a cloud kitchen management system. You need the order-aggregation and multi-brand pieces, or you will be re-keying orders by hand at 9 PM on a Friday.
Restrofi handles the kitchen-side of this: orders from your own QR/website channel flow straight onto a live Kitchen Display System, and analytics show you item-level and hour-level profitability across the day. For aggregator order aggregation, many operators pair it with a middleware layer — the point is that your own orders never carry commission.
Aggregator Orders vs Your Own Cloud Kitchen Delivery Platform
There are two ways a cloud kitchen can fulfil delivery, and most successful kitchens use both deliberately:
1. Aggregator delivery (Swiggy / Zomato). They bring discovery — new customers who have never heard of you — and they own the rider fleet. You pay for that with commission. Treat aggregators as a paid acquisition channel, not as your whole business.
2. Your own delivery platform (direct ordering). A customer orders from your website or WhatsApp, and you fulfil with your own riders, a hyperlocal partner (Dunzo-style / Shadowfax / Porter), or even the aggregators' "pick-up" delivery-only API. You keep the full order value minus a small flat delivery cost. There is no percentage commission.
The strategy that works: acquire on aggregators, retain on your own platform. Put an insert in every aggregator order bag — "Order direct next time and get 15% off: [yourbrand].restrofi-style-link" — and slowly migrate your regulars. A customer who orders four times a month is worth far more to you on your own channel than on a 25%-commission channel. We covered the full playbook in how restaurants cut Swiggy and Zomato commission with direct ordering.
Building Your Own Cloud Kitchen Website
A "cloud kitchen website" does not mean a brochure site with your story and a contact form. For a delivery kitchen, the website is the storefront — its only job is to take orders.
A working direct-ordering website for a cloud kitchen needs exactly five things:
- A live, mobile-first menu with photos, prices, and real-time out-of-stock toggles.
- A frictionless cart and checkout — no forced app download, no account creation wall. Phone number + address is enough.
- Online payment — UPI first (it is how most Indian customers pay), plus cards.
- Order routing to your kitchen — the order should appear on your KDS the instant it is placed, not in an email you check later.
- A delivery hand-off — either your own rider, a hyperlocal partner, or pickup.
You do not need a developer to build this in 2026. A platform like Restrofi gives each brand a hosted ordering page and QR link, sends orders straight to the kitchen display, and takes zero commission on those direct orders — you pay a flat monthly fee instead. That difference is the entire margin story for a cloud kitchen: a flat ₹999/month against 25% of every rupee is not a close call once you cross even a modest order volume.
What It Costs to Set Up a Cloud Kitchen in India
Costs vary a lot by city and brand count, but here is a realistic range for a single, small cloud kitchen in a Tier 1/2 Indian city in 2026:
| Item | One-time | Monthly |
|---|---|---|
| Kitchen rent (200–400 sq ft, non-prime) | Deposit ₹50k–1.5L | ₹25,000–60,000 |
| Commercial kitchen equipment (range, chimney, fridge, prep) | ₹1.5L–4L | — |
| Initial inventory + packaging | ₹40,000–80,000 | restocked |
| FSSAI licence | ₹2,000–7,500/yr | — |
| GST registration | Free | filing |
| Cloud kitchen management software + website | — | ₹500–2,000 |
| Staff (2–3 cooks + 1 helper) | — | ₹60,000–1.2L |
| Aggregator onboarding | Usually free | commission per order |
Bottom line: budget roughly ₹3–8 lakh to open the doors on a single small cloud kitchen, with monthly running costs of ₹1.5–3 lakh depending on city and staffing. Multi-brand operators add menu and packaging cost per brand but reuse the same kitchen, rent, and core staff — which is exactly why the model scales on margin.
Licenses you legally need
- FSSAI registration/licence — mandatory for any food business. Registration (turnover under ₹12 lakh) is cheap; a State licence is needed above that.
- GST registration — required once you cross the turnover threshold or list on aggregators (they require it). Most restaurant food is taxed at 5% GST without input tax credit. See our GST billing guide for restaurants.
- Local trade licence / shop & establishment and fire NOC for the kitchen premises, per your municipal rules.
How to Launch a Cloud Kitchen: Step by Step
- Validate one tight menu first. Pick a cuisine you can cook consistently at delivery scale. Delivery-friendly, travels-well food beats fragile plated dishes.
- Lock a small, legal kitchen space with proper ventilation, water, and power — non-prime location, since no customer visits.
- Get your licences — FSSAI and GST before you take a single order.
- Set up your management system and KDS so orders flow to the kitchen on screen, not paper.
- Launch your own ordering website / QR channel — this is your commission-free engine from day one.
- List on aggregators for discovery, with menu photos that actually sell.
- Print every cost — recipe-cost each dish so you know your margin before you discount.
- Convert repeat buyers to direct with bag inserts, WhatsApp, and a first-order discount on your own site.
Where Restrofi Fits
Restrofi is built for exactly the part of a cloud kitchen that decides profitability: your own order channel. Each brand gets a hosted QR/website ordering page, orders hit a live kitchen display the moment they are placed, and analytics tell you which brand and which hour make money. There is no commission on your direct orders — a flat monthly fee instead — which is the whole point for a delivery-only business. If you run a delivery-first model, start with our cloud kitchens page and our pricing.
Frequently Asked Questions
What is a cloud kitchen management system?
It is software that pulls orders from every channel — Swiggy, Zomato, your own website, WhatsApp — into one dashboard, sends them to a kitchen display, manages menus and inventory across multiple virtual brands, and reports profitability per brand and item. A plain billing POS is not enough; a true cloud kitchen system handles multi-channel order aggregation and multi-brand operations.
How much does it cost to start a cloud kitchen in India?
Budget roughly ₹3–8 lakh to open a single small cloud kitchen in a Tier 1/2 city — kitchen deposit and equipment are the big one-time costs. Monthly running costs of ₹1.5–3 lakh cover rent, staff, inventory, and software. Multi-brand operators add menu and packaging cost per brand but reuse the same kitchen and staff.
Do I need my own website if I am already on Swiggy and Zomato?
Yes, if you want to keep your margin. Aggregators charge an effective 25–30% once you include commission, fees, and funded discounts. Your own ordering website carries no percentage commission — you pay a flat monthly fee. Use aggregators to acquire new customers and your own site to retain repeat ones.
What licenses does a cloud kitchen need in India?
An FSSAI registration or licence (mandatory for all food businesses), GST registration (required to list on aggregators and above the turnover threshold), and local trade/shop-and-establishment plus a fire NOC for the premises. Get FSSAI and GST in place before taking your first order.
Can I run multiple brands from one cloud kitchen?
Yes — this is the most profitable way to run a cloud kitchen. Several virtual brands share one kitchen, staff, and inventory while appearing as separate listings to customers. A management system that supports multi-brand menus and pooled reporting is essential to do this without chaos.