By S&S Co. Advocates & Solicitors · Published 21 October 2026 · Informational content, not legal advice: see our disclaimer
A home baker selling cakes through Instagram, a tiffin service run out of a residential kitchen, and a delivery-only cloud kitchen operating out of a rented commercial unit are, legally, all food business operators under the same statute, however different they feel from each other in practice. What changes between them is not whether FSSAI applies, it always does, but which tier of compliance applies, and how quickly a business crosses from the lightest tier into something far more demanding. Clients in this space consistently underestimate how fast that happens, and the Food Safety and Standards Act's criminal penalty provisions do not care how small or informal the kitchen felt when the business started.
This guide works through where a home-based or cloud kitchen operation sits on FSSAI's registration-versus-licence ladder, what changes once orders start coming through aggregator platforms, and the compliance obligations that have nothing to do with FSSAI at all but still apply to the same business.
Registration or licence: the threshold that actually matters
Every food business operator in India needs either a basic FSSAI registration or a full licence, and which one applies turns on annual turnover rather than on how the business describes itself. A small operation below the basic registration threshold needs only the lighter registration, a simple filing with modest annual fees, while a business crossing into a higher turnover band needs a state licence, and the largest operations, or those involved in certain categories such as import, need a central licence. A home baker or a single cloud kitchen unit usually starts out firmly in registration territory, but turnover from a successful aggregator listing can cross the state licence threshold considerably faster than the business owner expects, particularly once festive season or wedding bulk orders are added to a steady weekly baseline.
The consequence of operating above your actual turnover band while holding only the lower-tier registration is not a minor administrative slip. It is treated as operating without the licence the business actually requires, which carries its own penalty exposure under the Act independent of whatever food safety standard the product itself meets. Tracking turnover against the registration and licensing thresholds on a running basis, rather than checking once at the start of the business and assuming the position is fixed, is the single most common gap a home-based operation needs to close.
A home kitchen is not exempt merely for being a home kitchen
A persistent misconception among home-based food businesses is that cooking in a residential kitchen, rather than a dedicated commercial one, puts the business outside FSSAI's reach, or at least outside its hygiene expectations. Neither is correct. A home chef, a home bakery, a tiffin or dabba service, and a seller of homemade pickles, chutneys or snacks are all squarely within the definition of a food business operator once food is being sold, including sold occasionally through social media or a neighbourhood WhatsApp group rather than through a storefront, and the registration or licensing obligation attaches regardless of where the cooking actually happens.
What a home kitchen does change is the practical hygiene and infrastructure expectations an inspector applies, which are necessarily different from what a full commercial kitchen is expected to maintain, but different is not the same as absent. Basic food safety practice, safe storage, pest control, and clean water use remain expected of a home-based operation, and an operator who treats the home-kitchen setting as a reason to skip these basics is building exactly the kind of record that turns an ordinary complaint into a licence suspension.
What changes once an aggregator platform is involved
Listing a cloud kitchen or home-based business on a food delivery aggregator does not transfer FSSAI compliance responsibility to the platform. The food business operator preparing the food remains the one who needs the registration or licence, remains the one whose FSSAI number needs to be displayed and kept current on the listing, and remains the one who faces direct liability if a food safety issue traces back to a specific order. Aggregators typically require proof of a valid FSSAI registration or licence number before onboarding a kitchen, and a lapsed or expired registration can get a listing pulled with very little warning, which is a commercial risk worth tracking separately from the legal one.
A single licensed kitchen premises operating multiple delivery-only brands on an aggregator, a increasingly common cloud kitchen model, generally does not need a separate FSSAI licence for each brand name as long as all the food is genuinely being prepared from the same licensed premises under the same operator. What it does need is internal clarity about which brand's orders are actually coming from which kitchen, since a dispute or inspection that reveals food sold under one brand name was actually prepared somewhere other than the licensed premises associated with it creates exactly the kind of discrepancy that invites a wider investigation into the whole operation.
The licensing changes that have been phasing in
FSSAI has been moving toward a longer validity period for licences and registrations, intended to reduce the administrative burden of frequent renewal for compliant operators, alongside a general push toward processing registrations, licences and renewals through the FoSCoS online portal rather than older, more fragmented state-level systems. A cloud kitchen or home-based operator should check their current registration or licence validity period and renewal date directly on the FoSCoS portal rather than assuming an older validity rule still applies, since this is an area where the applicable framework has been actively changing and a business relying on outdated information risks an unintentional lapse.
Beyond FSSAI itself, a cloud kitchen or home-based food business operating at any real scale also typically needs GST registration once turnover crosses the ordinary GST threshold, and may need a trade licence from the local municipal body depending on how the premises is classified, along with a fire safety clearance for a dedicated commercial cloud kitchen unit, though a genuinely home-based kitchen operating out of a residential unit is less likely to attract the fire clearance requirement in the same way a standalone commercial kitchen would. None of these other registrations substitute for FSSAI compliance, and a business holding one but not the other remains exposed on whichever requirement it has actually missed.
What a prosecution under the Act actually looks like for a small operator
Operating without the registration or licence a business's turnover actually requires, or selling food found to be unsafe, substandard or misbranded, exposes the operator to the Act's penalty and prosecution provisions regardless of how small or informal the business considers itself. These provisions were written with the full range of food businesses in mind, from large manufacturers to a single home kitchen, and a home-based operator who assumes enforcement activity is reserved for bigger businesses is working from an assumption the statute itself does not support.
The practical defence available to a small operator facing a complaint or an inspection is usually not a legal technicality but basic compliance discipline: a current registration or licence matching actual turnover, batch and ingredient records that can show exactly what went into a specific order if a complaint is traced back to it, and prompt, documented corrective action the moment any issue is identified rather than after a formal notice arrives. Operators who can produce this kind of record when an inspector or a consumer complaint shows up are in a fundamentally different position than ones who cannot, whatever the underlying facts of the specific complaint eventually turn out to be.
Setting a growing home kitchen up to survive its own success
The businesses that run into the most serious trouble are rarely the ones that stayed small. They are the ones that grew quickly, usually on the back of a single viral order or a strong aggregator ranking, without the compliance side of the operation growing along with it. An operator going from a handful of weekly orders to a volume that genuinely crosses into state licence territory needs to treat that growth as a trigger for a compliance review, not as a happy problem to deal with once things settle down, because things rarely settle down in a way that makes the paperwork easier to catch up on later.
A short annual checklist, reviewed at a fixed point each year rather than only when a problem surfaces, covers most of what actually matters: current turnover against the applicable threshold, registration or licence renewal dates against the FoSCoS portal's current record, FSSAI number display across every active aggregator listing, and a quick look at whether GST registration or a municipal trade licence has become due as the business has scaled. None of this is complicated once it is written down, and the operators who struggle are almost always the ones who never wrote it down in the first place.
Frequently Asked Questions
Does a home baker selling cakes occasionally through Instagram need FSSAI registration?
Yes. Selling food, even occasionally and through social media rather than a storefront, makes the seller a food business operator under the Act, and the FSSAI registration or licensing obligation applies regardless of the sales channel or how small the operation feels.
Does listing on a food delivery app transfer FSSAI compliance responsibility to the platform?
No. The food business operator preparing the food remains responsible for holding and displaying a valid FSSAI registration or licence. Aggregators generally require proof of this before onboarding a kitchen, but the underlying legal responsibility for compliance stays with the operator, not the platform.
Can one cloud kitchen premises run several different delivery-only brand names under one FSSAI licence?
Generally yes, as long as all the food sold under every brand is genuinely prepared from that same licensed premises by the same operator. Problems arise only if food sold under a given brand name was actually prepared somewhere other than the licensed premises associated with it.
What is the biggest compliance mistake a growing home-based food business makes?
Not tracking turnover against FSSAI's registration and licensing thresholds as the business grows. A business that crosses into a higher turnover band while still holding only the lower-tier registration is treated as operating without the licence it actually requires, which carries its own penalty exposure.
References & Further Reading
The provisions and rulings below were relied on for this guide. The position can change with amendments and later decisions, so check the current text and the latest case law before acting on any of it.
- Food Safety and Standards Act, 2006 and FSSAI Licensing and Registration Regulations (registration versus licence thresholds based on annual turnover and business category)
- FSSAI's FoSCoS online portal framework for registration, licensing and renewal of food business operators, including phased validity and renewal changes
- Food Safety and Standards Act, 2006, penalty and prosecution provisions applicable to any food business operator, regardless of scale, for operating without the required registration or licence or for selling unsafe, substandard or misbranded food