Cloud Kitchen Compliance From Day One

A cloud kitchen skips the dining room but not the compliance stack - FSSAI, fire safety, trade licence and GST requirements apply the same way they would to a restaurant, based on the food preparation activity and turnover rather than the seating arrangement.

Key facts at a glance

• FSSAI licensing for a cloud kitchen depends on turnover and business activity, not on whether there is dine-in seating.
• FSSAI Registration applies up to Rs 1.5 crore turnover; State Licence up to Rs 50 crore; Central Licence above that.
• A fire safety NOC generally still applies to the commercial kitchen premises.
• A trade licence from the local municipal body is generally required for the premises.
• Food delivery platforms separately require sellers to upload a valid FSSAI licence number during onboarding.
• GST registration is required once turnover crosses the applicable threshold.
• Packaging and labelling must still meet FSSAI display requirements even without in-store display.

Why Cloud Kitchens Are Not a Compliance Shortcut

It is a common misconception that a delivery-only model means lighter regulatory requirements. In reality, the core statutory obligations - food safety licensing, fire safety, local trade permission and tax registration - are triggered by the fact that food is being commercially prepared and sold, not by whether customers physically visit the premises. A cloud kitchen operator who assumes fewer approvals are needed is likely to be caught out during a routine or risk-based FSSAI inspection.

The Core Compliance Checklist

Multi-Brand Cloud Kitchens

A single physical kitchen running several delivery-only brands - a common cloud kitchen model - generally needs its FSSAI status confirmed at the level of the legal entity and premises operating it. It is worth verifying directly with FSSAI whether multiple brands from the same kitchen and same legal entity can operate under one licence, since incorrect assumptions here can create licensing gaps across brands.

Packaging and Labelling for Delivery

Because cloud kitchen food is seen by the customer only through delivery packaging, labelling requirements still apply in that context: ingredient information, allergen declarations where required, and other FSSAI-mandated packaging disclosures. Skipping this because there is no physical menu board or in-store signage is a common gap.

Platform Onboarding Is Not the Same as Regulatory Compliance

Delivery platforms require an FSSAI licence number and other documentation before listing a kitchen, which can create a false sense that platform approval equals regulatory compliance. Platform onboarding is a business requirement set by the platform; it does not replace your actual statutory obligations to FSSAI, fire authorities, the municipal body, or tax authorities, all of which operate independently of what any delivery platform checks.

A Practical Setup Sequence for a New Cloud Kitchen

1. Confirm your FSSAI category based on projected turnover and apply.
2. Secure the fire NOC and trade licence for the kitchen premises.
3. Register the business for GST if turnover is expected to cross the threshold.
4. Ensure at least one FoSTaC-certified Food Safety Supervisor is in place.
5. Prepare compliant packaging and labelling before going live on delivery platforms.
6. Complete platform onboarding with your FSSAI licence number and other required documents.

If you are setting up or already running a cloud kitchen and want to check what compliance gaps might exist, ComplianceCheck's Food Business Assessment gives you a clear picture in a few minutes.

Sources

• Food Safety and Standards Authority of India - fssai.gov.in
• Ministry of Labour and Employment - labour.gov.in
• Goods and Services Tax portal - gst.gov.in
• Respective state fire and municipal authorities

This guide is general information, not legal advice. Requirements vary by state, sector and headcount - confirm specifics with a compliance professional or the relevant authority.