Cloud kitchen compliance in India: the full checklist
A cloud kitchen in India needs the same core compliance as a dine-in restaurant — an FSSAI licence per kitchen, GST registration, shops-and-establishment and labour registration — plus carefully reviewed Swiggy/Zomato contracts, since delivery is its entire revenue. The main difference is dependence on aggregators, not lighter rules.
Does a cloud kitchen need an FSSAI licence?
Yes. A cloud kitchen is a food business and needs an FSSAI licence exactly like a dine-in restaurant, tied to the kitchen premises and decided by turnover — Basic, State or Central. Delivery-only status does not exempt you.
If you run multiple brands from one kitchen, you generally operate under one licence for that premises; separate kitchens each need their own.
How is cloud-kitchen compliance different from a dine-in restaurant?
The legal obligations are largely the same; the risk profile is different. A cloud kitchen has no walk-in revenue, so its aggregator contracts with Swiggy and Zomato are effectively its whole business — commission, exclusivity and payout terms matter more than for a dine-in outlet.
You also carry less on premises-facing rules (seating, signage) but the same food-safety, GST, labour and POSH obligations.
What contracts and registrations should a cloud kitchen prioritise?
Prioritise three: the FSSAI licence for the kitchen, GST registration and returns, and a careful review of every aggregator contract before signing. Add shops-and-establishment/labour registration and, once you reach 10 employees, a POSH Internal Committee.
Because aggregators are your only sales channel, the commission and exit terms in those contracts directly set your margin.
What trips up cloud kitchens most often?
Two things: a lapsed FSSAI licence that gets the storefront suspended by an aggregator, and aggregator contract terms — commission creep, ad spend and auto-renewal — quietly eroding margin. Both are avoidable with tracking and a contract review.
EatSafe Legal keeps each kitchen's licence and renewal dates in one place and can review aggregator contracts so the terms don't surprise you.
Frequently asked questions
Can I run multiple brands from one cloud kitchen on one FSSAI licence?
Generally yes — the licence attaches to the premises, so multiple virtual brands operating from the same kitchen usually run under that one licence. Separate physical kitchens need separate licences.
Does a cloud kitchen need GST registration?
Yes, on the same basis as any food business once it crosses the turnover threshold or lists on aggregators, which require GST details.
Do POSH rules apply to a delivery-only kitchen?
Yes. Once a kitchen has 10 or more employees it must constitute a POSH Internal Committee, regardless of whether it serves dine-in customers.
Is a cloud kitchen's FSSAI fee different from a restaurant's?
No. The same turnover-based tiers and fees apply — Basic ₹100, State ₹2,000–₹5,000, Central ₹7,500 per year.
What is the biggest compliance risk for a cloud kitchen?
A lapsed FSSAI licence, because aggregators verify it and will suspend your storefront — which, for a delivery-only model, means zero revenue.
Do I need aggregator contracts reviewed for a cloud kitchen?
It is especially worth it, because those contracts are your entire revenue channel. Commission, exclusivity and payout terms decide whether the model is profitable.
This guide is general information for Indian restaurants, not legal advice. Rules change and specifics vary by state and situation — confirm with a qualified professional. EatSafe Legal connects you to verified CAs and lawyers when you need one.
Let EatSafe Legal handle this for you.
Track licences, review contracts, reply to notices and draft HR docs — with reminders before every deadline.
Start free for 7 days