62 Lakh Indian Food Businesses Are Completely Unregistered

Open Swiggy or Zomato and order from what looks like a restaurant — a branded name, a curated menu, 4.2-star ratings, photos of gleaming dishes. What you probably don't realise is that this "restaurant" may be operating from a 200-square-foot room in a residential building, a shared industrial kitchen that simultaneously handles twelve different "brand" menus, or a home kitchen registered under a different address than the one actually cooking your food. This is India's cloud kitchen industry: a ₹40,000 crore sector that has scaled faster than any inspection or hygiene framework designed to govern it.

Here is the number that changes how you think about every food delivery order: as of the most recent regulatory data, only approximately 62 lakh food business operators out of roughly 1.5 crore operating in India are registered on FoSCoS (Food Safety and Compliance System), the FSSAI's digital platform. That's roughly 40% coverage — meaning an estimated 60% of food businesses, including a substantial proportion of cloud kitchens, are operating in a grey zone of either no FSSAI registration or incomplete compliance. And Delhi's Department of Food Safety only began its first systematic inspection drive targeting cloud kitchens and dark stores on April 1, 2026 — meaning that for years prior, the explosive growth of this industry proceeded with virtually no coordinated inspection framework.

A cloud kitchen (also called a ghost kitchen or dark kitchen) is a food production facility that exists solely to prepare food for delivery — no dining room, no walk-in customers, no front-of-house staff. From a consumer perspective, it presents as a restaurant on a food delivery app. From a physical perspective, it could be anything from a purpose-built commercial kitchen space renting capacity to multiple brands, to a home kitchen operated by someone who listed themselves as a restaurant business on Zomato.

The model has several distinct variations in India. "Virtual brands" are food brands that exist only on delivery apps — no physical restaurant presence, no standalone brand identity beyond the Swiggy or Zomato listing. Many such brands are operated by a single kitchen running multiple virtual brand menus simultaneously: the same kitchen might prepare orders for "Punjabi Tadka Express," "South Bites by Meenakshi," and "Wrap & Roll by Rahul" — three different Swiggy listings with different branding, prices, and menus — all from the same pots and the same staff. "Shared kitchen spaces" are purpose-built facilities that rent kitchen space by the hour or by the month to multiple food operators, none of whom have a permanent kitchen of their own. And "home kitchens" are exactly what they sound like — individuals cooking from home and listing on food delivery apps under a registered cloud kitchen address that may or may not correspond to where the food is actually prepared.

Each of these models creates a different regulatory challenge. A virtual brand operating from a legitimate commercial kitchen with a valid FSSAI licence at that location is compliant. A virtual brand operating from an unregistered home kitchen, or a shared kitchen space where the FSSAI licence belongs to the space but the individual brands operating within it may not be separately compliant — those create gaps that inspectors have not historically been equipped to close.

Under FSSAI regulations, any food business with annual turnover above ₹12 lakh must obtain a central licence; those with turnover between ₹12 lakh and ₹20 crore need a state licence; and smaller operators (below ₹12 lakh annual turnover) need only a basic registration rather than a full licence. For cloud kitchens, the key regulatory question is: does the FSSAI registration belong to the kitchen space, the cloud kitchen operator, or the individual brand? In shared kitchen models, this creates ambiguity: if the shared kitchen holds the FSSAI licence and a brand operating within it doesn't hold a separate one, regulatory inspectors visiting the facility encounter a compliance picture that looks adequate at the facility level but may not capture individual brand accountability.

As of 2026, FSSAI uses geo-tagging and digital monitoring to verify the physical location and hygiene standards of food businesses applying for licences — a step toward closing the "registered address doesn't match actual kitchen" gap. However, ongoing monitoring of compliance for already-registered businesses remains resource-constrained. Food safety inspectors at the state level are responsible for huge geographic areas and large numbers of businesses; cloud kitchens — because they are not considered high-value or large-scale food businesses — are typically inspected only if a complaint is filed, not on a proactive scheduled basis.

In April 2026, Delhi's Department of Food Safety launched the city's first coordinated systematic inspection of cloud kitchens and dark stores. The inspection covered cloud kitchens operating on Swiggy, Zomato, Blinkit, and other platforms. The key findings that emerged: multiple cloud kitchens were found operating without a valid FSSAI licence despite being listed as active restaurants on delivery platforms; several inspected kitchens had hygiene conditions including inadequate ventilation, absence of pest control records, and unsafe food storage temperatures; and in some cases, the address listed on the food delivery app did not match the actual location of food preparation.

This matters not just for Delhi — it demonstrates what happens when systematic inspection is actually applied to a sector that has grown largely uninspected. The April 2026 drive was initiated following complaints and media reports about hygiene conditions in cloud kitchens, not as a routine regulatory function. Prior to it, the norm was complaint-driven inspections only, which means that cloud kitchens that receive no customer complaints — regardless of their actual hygiene standards — face essentially no regulatory scrutiny.

The Print reported that most cloud kitchens operating under Swiggy and Zomato in Delhi fall under state-level food safety authorities, inspected by lower-rank officers, because they are not classified as high-turnover food businesses. There is no comprehensive registry of cloud kitchens operating in Delhi, no consolidated complaints database, and no systematic risk-based inspection schedule — a regulatory gap that the April 2026 drive was a first step toward closing, but not a solution to.

Swiggy and Zomato both require restaurant partners — including cloud kitchens — to submit a valid FSSAI licence as part of the onboarding process. The platforms do not conduct physical hygiene inspections of partner kitchens themselves; their role is documentation verification, not inspection. Whether the FSSAI licence is current, whether it covers the specific type and scale of food production being done, and whether the actual kitchen conditions correspond to the registered premises — these are regulatory functions, not platform functions, and platforms rely on FSSAI to perform them.

This is not a criticism unique to Indian platforms — food delivery platforms globally are documentation verifiers, not food safety inspectors, and regulatory frameworks are typically built on the assumption that independent inspection agencies perform that function. The problem in India is that the inspection agency (FSSAI and state food safety departments) does not have the capacity, coverage, or data infrastructure to proactively inspect the 1+ lakh cloud kitchens estimated to be operating across India's major cities. The result is a compliance ecosystem that depends almost entirely on operators self-reporting accurate information — a known weakness in any regulatory framework.

On the platform side, Zomato introduced an "Assured" and "Gold" programme for partner restaurants that includes hygiene and quality metrics, but these primarily reflect customer-reported data and platform audits of food packaging and delivery, not physical kitchen inspections. Swiggy has similar quality-tier programmes. Both platforms have removed partner restaurants following sustained negative reviews or regulatory action — but reactive removal after problems emerge is fundamentally different from proactive hygiene verification before problems reach consumers.

A specific subset of cloud kitchens that has grown rapidly in India is the home kitchen segment — individuals cooking from their domestic kitchens and listing on food delivery apps under names like "Tiffin by Priya" or "Ghar ka Khana by Sunita." FSSAI regulations technically permit home-based food businesses to operate with a basic registration for small-scale production, subject to compliance with hygiene standards applicable to any food business. In practice, enforcement is minimal: a home-based operator registered under one address but cooking in a different space, using shared domestic facilities, with no refrigeration or temperature-monitoring equipment, and no pest control programme, may nonetheless appear on a food delivery app as a legitimate restaurant — because the platform checks documents, not conditions.

During the COVID-19 pandemic, home kitchen registrations expanded dramatically as both a livelihood necessity and a policy response to support small food entrepreneurs. Many of these operators have continued operating post-pandemic with minimal regulatory follow-up. The food safety risk in this segment is not that home-cooked food is inherently unsafe — traditional home-cooked food made with care is often among the safest available — but that regulatory hygiene standards exist for reasons (temperature control, pest exclusion, cross-contamination prevention, water safety) that domestic kitchens, not designed for food business operations, may not reliably meet.

Check the FSSAI number on the listing. Most delivery app restaurant listings display an FSSAI licence number. You can verify this at foscos.fssai.gov.in by searching the FBO (Food Business Operator) name or licence number — confirming that the licence is active, current, and registered to the address listed.

Be sceptical of very new listings with very high ratings. Cloud kitchens can populate ratings quickly through incentivised first orders. A restaurant listed on Zomato for three weeks with 200 five-star reviews should be viewed with more scepticism than one with 2,000 reviews accumulated over two years.

Prefer cloud kitchens with a physical address visible on Google Maps. A kitchen address you can verify on Maps — showing a commercial kitchen space or restaurant premises, not a residential apartment — provides more confidence than a listing with an address that doesn't correspond to any visible food business.

For recurring orders (lunch tiffin, weekly meal delivery), ask for the FSSAI licence number directly. Legitimate operators will provide it readily. If a cloud kitchen is reluctant to share its FSSAI number with a regular customer, that is a reason to order elsewhere.

Report hygiene concerns via the FSSAI's Food Safety Connect portal or the National Consumer Helpline (1915). Individual complaints about specific cloud kitchens are, currently, one of the primary triggers for inspections — your report can directly initiate regulatory action.

One of the most widely misunderstood aspects of India's cloud kitchen industry is the multi-brand kitchen model — where a single physical kitchen simultaneously operates multiple distinct "restaurant" brands on food delivery apps. A diner ordering from "Punjabi Dhaba Express" on Zomato and their neighbour ordering from "South Spice Corner" on Swiggy may both be receiving food from the identical kitchen, made by the same people, using the same equipment, at the same address — with no indication on either app that these are not separate, distinct restaurants.

This model is completely legal and has legitimate economic logic: a kitchen with the capacity to produce 200 orders per shift can expand its revenue by operating multiple virtual brands targeting different cuisine preferences, without the cost of opening additional physical locations. The food safety implications depend entirely on the hygiene and compliance standards of the underlying kitchen — if the kitchen is compliant with FSSAI standards, all the brands operating from it benefit from that compliance. If the kitchen is not, all brands are exposed to the same risk.

From a consumer trust perspective, the multi-brand kitchen model creates an information asymmetry: the diner believes they are choosing between different restaurants based on cuisine, reviews, and brand identity — unaware that multiple "choices" are functionally the same kitchen. This is not inherently a food safety problem, but it does mean that the reviews and ratings accumulated by each brand may reflect the specific dishes ordered rather than any meaningful difference in the underlying kitchen's hygiene standards. A complaint about one brand's food quality that should logically also alert consumers of the co-located brands goes siloed in the data of that specific listing.

The April 2026 Delhi inspection drive specifically looked at multi-brand kitchen operations as a priority category — because a single inspection of a multi-brand kitchen has implications for multiple app listings, making it a high-leverage point for the limited available inspection resources. Documenting the relationship between physical kitchens and virtual brand listings is a step toward the kind of supply chain transparency that would let consumers understand what they are actually choosing between when they select "restaurants" on a delivery app.

Search trends in India show significant interest in "cloud kitchen food safe india," "is swiggy food safe," "zomato restaurant FSSAI license check," "ghost kitchen hygiene," and "who inspects cloud kitchens india." There is also interest in "home cloud kitchen FSSAI registration" from entrepreneurs looking to start cloud kitchen businesses, suggesting that the industry continues to grow rapidly. Consumer sentiment in food delivery reviews and social media shows increasing attention to food quality and preparation conditions — users sharing photos of poorly packaged or visibly unhygienic deliveries have generated viral social media moments that have forced platform responses in individual cases.

India's cloud kitchen industry is one of the most exciting food entrepreneurship stories in the country — enabling thousands of small operators to reach millions of customers without the capital costs of a physical restaurant. It is also, currently, one of the least systematically inspected segments of the food supply chain. The April 2026 Delhi inspection drive was a beginning, not a solution. Until systematic, proactive inspection capacity matches the scale of the industry, the gap between "looks like a restaurant on your app" and "meets food safety standards in reality" will remain — and the tools that exist for you to verify before you order (FSSAI licence check, Maps verification, careful review reading) are genuinely worth using.