A cloud kitchen may have no dining tables, no reception area and no traditional restaurant storefront—but it is still a food business, and the absence of seating does not remove its FSSAI compliance requirements.
Cloud kitchens have changed how food businesses operate in India. Entrepreneurs can prepare food from a dedicated kitchen, receive orders through food-delivery platforms or their own websites, and deliver directly to customers without maintaining a conventional dine-in restaurant.
This model can reduce the infrastructure required to start a food business, but it does not mean regulatory requirements disappear.
FSSAI specifically clarifies that cloud kitchens without seating arrangements require FSSAI Registration or License according to the applicable eligibility criteria.
For a new cloud kitchen, one of the first compliance questions is therefore not whether FSSAI applies, but which FSSAI category applies, what documents are required and how the application should be filed through FoSCoS.
The 2026 FSSAI reforms also changed the general turnover thresholds. From 1 April 2026, the revised general framework provides for Registration up to ₹1.5 crore turnover, State License above ₹1.5 crore up to ₹50 crore, and Central License above ₹50 crore, subject to the applicable kind-of-business criteria.
What Is a Cloud Kitchen?
A cloud kitchen is a food business that prepares food primarily for delivery or takeaway rather than dine-in consumption.
It may operate through:
- Swiggy or Zomato
- Its own website
- Mobile applications
- WhatsApp orders
- Instagram or social-media orders
- Direct telephone orders
- Corporate food orders
- Other online ordering channels
A cloud kitchen can operate under a single brand or manage multiple food brands from the same kitchen.
For example, one kitchen in Noida could operate separate online brands for:
- Biryani
- Burgers
- Chinese food
- Desserts
Even if customers never visit the physical premises, food is still being prepared, handled, stored and supplied commercially.
That makes FSSAI compliance relevant.
Does a Cloud Kitchen Need FSSAI Registration or License?
Yes.
FSSAI's licensing and registration FAQs specifically state that cloud kitchens with no seating arrangements require FSSAI License or Registration as per the eligibility criteria.
The absence of tables or a dine-in area does not change the fact that the business is preparing and selling food.
The applicable category depends on factors such as:
- Nature of food activity
- Kind of Business
- Turnover
- Location and premises
- Applicable FSSAI eligibility criteria
- Whether the business carries out any specially regulated activity
Therefore, a cloud kitchen should not simply select Registration because it has no restaurant seating.
FSSAI Registration vs License for a Cloud Kitchen
The current general turnover framework changed from 1 April 2026.
For eligible food businesses, the broad thresholds are:
Up to ₹1.5 crore: FSSAI Registration
Above ₹1.5 crore up to ₹50 crore: State License
Above ₹50 crore: Central License
However, turnover is not the only factor.
The FoSCoS system uses the Kind of Business (KoB) and applicable eligibility criteria to determine the relevant category.
This means two food businesses with the same turnover can potentially have different licensing requirements if their activities fall into different regulatory categories.
Example: Small Cloud Kitchen in Delhi
Suppose an entrepreneur starts a cloud kitchen in Dwarka, Delhi.
The business prepares:
- Biryani
- Kebabs
- Rolls
- Rice bowls
Orders come through online food-delivery platforms.
Its annual turnover is ₹25 lakh.
If the business falls within the applicable registration category, the current general turnover framework may place it within FSSAI Registration.
However, the entrepreneur should still check the specific FoSCoS eligibility criteria for the selected food-business activity before submitting the application.
The fact that the kitchen has no seating does not by itself determine the category.
Example: Growing Cloud Kitchen in Gurugram
Now consider a cloud kitchen operating in Gurugram with annual turnover of ₹3 crore.
Under the current general turnover framework, the business has crossed the ₹1.5 crore Registration threshold and may fall within the State License range, subject to its specific activity and eligibility criteria.
If the business later expands to multiple kitchens and its turnover grows substantially, its FSSAI licensing structure should be reviewed again.
This is why cloud kitchens should not treat FSSAI registration as a one-time startup task.
What Is FoSCoS?
FoSCoS stands for Food Safety Compliance System.
It is FSSAI's online platform for food-business registration and licensing and is designed as a pan-India platform for food-safety regulatory requirements.
FSSAI's current website directs food businesses to FoSCoS for applying for a new License or Registration and managing food-business compliance.
For a cloud kitchen, FoSCoS is the main online system through which the business can determine eligibility and submit the applicable application.
What Documents Are Required for Cloud Kitchen FSSAI Registration?
The exact documents depend on the selected Kind of Business and license category.
A cloud kitchen should generally be prepared with information and documents relating to:
- Applicant identity
- Business constitution
- Premises address
- Proof of possession of the premises, where applicable
- Nature of food business
- Food products handled
- Business turnover, where relevant
- Partnership/company documents, where applicable
- Photographs or premises-related documents where required
- Other documents specified by the selected FoSCoS category
The important point is that there is no single universal document list for every cloud kitchen.
A small proprietorship cloud kitchen and a larger company-operated food manufacturing/processing facility may have very different document requirements.
FSSAI's document framework is linked to the selected Kind of Business. The FoSCoS guidance explains that documents pertinent to the selected KoB are required for licensing applications, with additional documents potentially required depending on the circumstances.
Identity and Applicant Details
The application should accurately identify the person or entity operating the food business.
Depending on the business structure, this could be:
- Individual proprietor
- Partnership firm
- LLP
- Private limited company
- Other eligible legal entity
The applicant should ensure that the business name, PAN-related information and supporting records are consistent.
For example, if the cloud kitchen operates through a private limited company, the application should not incorrectly represent the business as a different individual-owned operation.
Proof of Premises
The cloud kitchen's actual operating premises are particularly important.
Depending on the circumstances, the business may need documentation establishing possession or use of the premises.
This can include documents such as:
- Rent agreement
- Lease agreement
- Ownership documents
- Electricity bill
- Other applicable premises-related proof
The exact document accepted depends on the current FSSAI/FoSCoS requirements.
A cloud kitchen should therefore use the address from which food is actually being prepared rather than simply using the owner's residential address if the commercial kitchen operates somewhere else.
Can a Cloud Kitchen Operate From a Rented Premises?
A cloud kitchen can operate from rented premises, subject to applicable legal, food-safety and local requirements.
For example, an entrepreneur may rent a commercial kitchen in:
- Noida
- Gurugram
- Delhi
- Ghaziabad
- Faridabad
The premises information used for FSSAI application should accurately represent the location of the food business.
The entrepreneur should also separately consider:
- Local municipal requirements
- Building-use restrictions
- Fire-safety requirements where applicable
- Waste disposal
- Water and sanitation
- Commercial-use permissions
- Society or landlord restrictions where relevant
FSSAI approval does not automatically replace other local permissions.
What About a Cloud Kitchen From a Home?
A cloud kitchen can also operate from a residential premises where the business and premises comply with applicable requirements.
However, the entrepreneur should not assume that operating from home means that only basic food registration is automatically sufficient.
The business should evaluate:
- Food activity
- Turnover
- Products
- Premises
- Hygiene arrangements
- Applicable FoSCoS category
- Local requirements
For example, a home-based kitchen preparing meals for a small number of local customers can have a different compliance profile from a high-volume food operation preparing hundreds of orders daily.
How to Select the Correct Kind of Business?
This is one of the most important parts of the FoSCoS application.
The applicant needs to identify what the business actually does.
A cloud kitchen may involve:
- Food service
- Food preparation
- Manufacturing or processing
- Retail
- Storage
- Delivery
- Multiple food activities
The appropriate Kind of Business should reflect the actual operation.
Selecting an incorrect category merely because it appears easier can create problems later if the FSSAI authority finds that the business activity does not match the application.
What Food Products Should a Cloud Kitchen Declare?
A cloud kitchen should accurately identify the categories of food it prepares or handles.
For example, a kitchen may prepare:
- Vegetarian meals
- Non-vegetarian meals
- Bakery products
- Desserts
- Beverages
- Ready-to-eat foods
- Snacks
- Packaged products
The actual product categories should be selected according to the current FoSCoS application and applicable food-category structure.
If the business later expands significantly into new product categories, it should review whether a modification to its FSSAI information is required.
How to Apply for FSSAI Registration for a Cloud Kitchen?
The broad process can be understood in the following stages.
Step 1: Identify the Business Structure
Determine whether the cloud kitchen operates as:
- Proprietorship
- Partnership
- LLP
- Company
- Other applicable structure
The legal structure should be consistent with the supporting documentation.
Step 2: Identify the Actual Food Activity
Determine whether the business is primarily preparing food, manufacturing/processing food, selling food or carrying out another activity.
Step 3: Check FoSCoS Eligibility
Use the current FoSCoS eligibility facility to identify the applicable Kind of Business and whether Registration, State License or Central License is required.
FSSAI's FoSCoS guidance specifically provides an “Eligibility of your food business” search facility for checking the relevant criteria.
Step 4: Prepare Documents
Gather the documents applicable to the selected category.
Step 5: Complete the Application
Submit the relevant application through the FoSCoS portal.
Step 6: Pay the Applicable Fee
The fee depends on the category and type of application.
Step 7: Respond to Any Authority Query
If the authority requests additional information or documents, respond through the applicable process.
Step 8: Obtain and Verify the FSSAI Approval
After approval, verify the details on the certificate/license and keep the record with the business's compliance documents.
What Is the Difference Between Form A and Form B?
The application form depends on the type of FSSAI approval.
FSSAI's published process describes Form A for Registration and Form B for licensing applications.
This distinction is important because a cloud kitchen should first determine whether it falls under Registration or Licensing before preparing its application.
Can One FSSAI License Cover Multiple Activities at the Same Premises?
FSSAI's guidance explains that a license is based on the premises and that multiple food-business activities carried out at the same premises can be covered under a single FSSAI license, subject to the applicable requirements.
This can be relevant for a cloud kitchen operating multiple food concepts from the same physical kitchen.
For example, suppose one commercial kitchen in Noida operates:
- A biryani brand
- A burger brand
- A dessert brand
If these activities are carried out from the same premises, the business should evaluate how the activities should be declared within its applicable FSSAI licensing structure rather than automatically applying for unrelated licenses for each online brand.
The actual structure should be determined according to the current FoSCoS requirements.
What If a Cloud Kitchen Has Multiple Locations?
This is different.
FSSAI's licensing framework is linked to premises.
A cloud-kitchen company operating three separate kitchens in:
- Delhi
- Noida
- Gurugram
should not assume that one location's approval automatically covers all three physical premises.
Each premises and its food activities need to be evaluated according to the applicable FSSAI framework.
This is particularly important for businesses following an expansion strategy.
What If the Cloud Kitchen Uses Multiple Online Brands?
Multiple brands do not necessarily mean multiple physical food premises.
Suppose a company operates five online food brands from one commercial kitchen.
The business should focus on the actual food activities conducted at the premises, rather than treating every online brand as an entirely separate physical food business.
The applicable FSSAI structure should reflect the actual operation and current FoSCoS requirements.
Cloud Kitchen Hygiene Requirements
A cloud kitchen may not have customers walking through its premises, but food-safety requirements still matter.
Important operational areas include:
Kitchen Cleanliness
Preparation surfaces, equipment, utensils and storage areas should be kept appropriately clean.
Personal Hygiene
Food handlers should follow appropriate hygiene practices.
Raw Material Storage
Ingredients should be stored appropriately, with attention to contamination, temperature and product integrity.
Cross-Contamination Control
Raw and cooked foods should be handled in ways that reduce contamination risks.
Temperature Control
Foods requiring temperature control should be stored and handled appropriately.
Pest Management
The premises should be maintained to reduce pest contamination.
Waste Management
Food waste and other waste should be handled appropriately.
The FSSAI framework includes sanitary and hygienic requirements for food businesses, and cloud kitchens remain food businesses even without seating.
Does a Cloud Kitchen Need an FSSAI License Display?
The business should follow the applicable FSSAI requirements concerning display of its registration/license information and other mandatory declarations.
The specific display requirements can depend on the business model and current regulations.
For online food businesses, it is also important to ensure that the FSSAI information presented to customers and platforms is accurate.
What About Food Delivery Platforms?
A cloud kitchen may receive most of its business through platforms such as Swiggy and Zomato.
The platform does not replace the cloud kitchen's own food-business compliance responsibilities.
The cloud kitchen should maintain its own:
- FSSAI approval
- Food-safety procedures
- Supplier records
- Purchase records
- Food preparation controls
- Complaint records
- Relevant invoices
- Other applicable compliance records
The delivery platform is a sales and logistics channel; it does not automatically become the substitute for the food operator's regulatory obligations.
What About a Cloud Kitchen Selling Through Its Own Website?
A cloud kitchen can also accept orders through its own website.
The same FSSAI requirements continue to apply.
In addition, the business should consider:
- Product descriptions
- Pricing
- Allergen information where applicable
- Packaging
- Delivery conditions
- Refunds and cancellations
- Customer complaints
- Online payment records
The website should not contain food-related claims that are inconsistent with applicable regulations.
What Are Common FSSAI Mistakes Made by Cloud Kitchens?
Assuming No Seating Means No FSSAI
FSSAI specifically states that cloud kitchens without seating still require Registration or License according to eligibility.
Choosing Registration Without Checking Eligibility
A low turnover does not automatically answer every licensing question.
Using the Wrong Premises Address
The application should accurately reflect the actual food-business premises.
Selecting the Wrong Kind of Business
The application should describe what the kitchen actually does.
Ignoring Food-Safety Practices
An FSSAI certificate does not replace day-to-day hygiene requirements.
Treating Multiple Brands as Completely Separate Kitchens
Where multiple brands operate from one physical premises, the business should evaluate the applicable licensing structure based on the actual activities at that premises.
Forgetting to Update the FSSAI Information After Expansion
Moving to another kitchen, adding activities or materially changing the business model can require a review of the FSSAI approval.
Example: Cloud Kitchen Expansion From Delhi to Noida
Suppose a food entrepreneur starts one kitchen in Delhi.
Initially:
- One kitchen
- One online brand
- ₹20 lakh turnover
- Local delivery
After two years:
- Two kitchens
- Three online brands
- ₹2.5 crore turnover
- Delhi and Noida operations
- Direct website orders plus food-delivery platforms
The entrepreneur should not simply continue using the original FSSAI setup without review.
The expansion has changed:
- Number of premises
- Business scale
- Turnover
- Online brands
- Operational structure
The business should review its FSSAI licensing position for each relevant premises and determine whether modifications or additional approvals are required.
Does the 2026 Perpetual Validity Change Cloud Kitchen Compliance?
FSSAI's 2026 reforms introduced perpetual validity for registrations and licenses, subject to suspension, cancellation or surrender.
This means the previous periodic-renewal model has changed. However, perpetual validity does not mean the cloud kitchen can ignore compliance after obtaining its approval.
The business must continue meeting applicable food-safety and statutory requirements.
A cloud kitchen should therefore distinguish between:
Validity of the approval
and
Ongoing compliance obligations
These are not the same thing.
Practical Document Checklist for a New Cloud Kitchen
Before starting the application, keep the following information ready where applicable:
- PAN and identity details of the applicant.
- Business constitution documents.
- Business name.
- Kitchen premises address.
- Proof of possession/use of premises.
- Details of food activities.
- Food product categories.
- Turnover information.
- Partnership deed or company documents, where applicable.
- Relevant declarations.
- Other documents required by the selected FoSCoS Kind of Business.
For specific licensing categories, additional documents can apply. FSSAI's Central License document list, for example, includes documents such as Form B, constitution documents and premises-related records, with additional requirements for certain manufacturing/processing activities.
Therefore, the final checklist should be generated based on the actual cloud-kitchen activity rather than copied from another food business.
Cloud Kitchen FSSAI Compliance Checklist
Before launching, review:
- Confirm the actual food-business activity.
- Identify the correct Kind of Business.
- Check the current FoSCoS eligibility.
- Determine Registration, State License or Central License applicability.
- Verify the kitchen premises.
- Prepare applicable address/premises documents.
- Prepare applicant/entity documents.
- Identify food categories.
- Review turnover.
- Complete the FoSCoS application.
- Upload the required documents.
- Respond to any authority queries.
- Verify the final FSSAI approval.
- Maintain food-safety and hygiene procedures.
- Keep supplier and food-related records where applicable.
- Review FSSAI requirements whenever the business expands.
Final Takeaway
A cloud kitchen is still a food business even when it has no seating, no dining area and no traditional restaurant storefront. FSSAI specifically confirms that cloud kitchens require Registration or License according to their applicable eligibility criteria.
The current 2026 framework also means that the general turnover thresholds have changed, while FSSAI has moved to a perpetual-validity model for registrations and licenses subject to ongoing compliance.
For a new cloud kitchen, the correct approach is to:
Identify the actual food activity → Check FoSCoS eligibility → Determine the appropriate FSSAI category → Prepare the correct documents → Apply through FoSCoS → Maintain ongoing food-safety compliance.
Whether you are launching a small cloud kitchen in Delhi, expanding a food-delivery business in Noida, or operating multiple delivery-only brands in Gurugram, getting the FSSAI category and premises details right at the beginning can make future compliance considerably easier.
Need Help With Cloud Kitchen FSSAI Registration?
If you are starting a cloud kitchen and need assistance determining the appropriate FSSAI category, preparing documents or understanding the FoSCoS application process, FilingSuvidha can help with the applicable food-business compliance requirements.
Website: https://filingsuvidha.com/
Phone: +91-9625995981
Email: info@filingsuvidha.com
Our focus is on transparent pricing and on-time delivery.
Disclaimer
This article is intended for general informational purposes and should not be treated as legal, food-safety, regulatory, tax or professional advice. FSSAI requirements can vary according to the food activity, premises, turnover, products and applicable Kind of Business criteria. FSSAI regulations, FoSCoS procedures and documentation requirements may change. Businesses should verify the latest requirements through the official FSSAI/FoSCoS system before applying or commencing operations.