operations9 min read

Cloud kitchen FDA compliance Maharashtra 2026

Maharashtra FDA Order 716/2026 for cloud kitchens: premises FSSAI licence, virtual brands, RUCO, packaging, rider handoff, aggregator listings, and inspection prep.

By Forkcast Editorial · HORECA research team

Cloud kitchens were over-represented in Maharashtra's June 2026 suspension list — not because the format is illegal, but because owners assumed delivery-only meant lighter compliance. Order FDA/COMM/FOOD/HRE/716-2026/07 says otherwise. If you are comparing formats, start with cloud kitchen vs casual dining economics; this guide covers what FDA expects once you are operating.

Are cloud kitchens in scope for Order 716/2026?

Yes. Commissioner Tukaram Mundhe's order names cloud kitchens, virtual brands, online food aggregators, and food courts alongside hotels and restaurants. The compliance order hub maps all rule areas; cloud operators hit the same RUCO, staff, and packaging clauses as dine-in — minus some customer-zone items if there is no seating.

A brand listing on Swiggy is not a licence. Inspectors verify the kitchen premises — address, layout, hygiene, certificates. Multi-brand kitchens face deeper checks on segregation and labelling.

What licence do you need — premises, not brand?

  • FSSAI state licence or registration — tied to the kitchen's physical address on FoSCoS.
  • Annual FoSCoS fee paid — unpaid perpetual licences treated as suspended from 1 April 2026.
  • Food Safety Display Board — displayed at premises entrance (photo-ready for inspectors and aggregator audits).
  • Virtual brands declared — every brand cooking from the same address listed on the licence application.

Pre-launch? See FSSAI licence Maharashtra and the full licence stack checklist.

Which Order 716 rules hit cloud kitchens hardest?

Rule areaCloud kitchen riskAction
RUCO / TPC (§6)High — fry-heavy menus use >50L/dayTPC meter, 8-hour log, UCO agency receipts
Staff certs (§3.3)High — high handler turnoverAnnual fitness + FoSTaC; 1 supervisor per 25
PackagingHigh — 100% packed ordersFood-grade only; no newspaper contact
Cold chainMedium — aggregator delay exposureFridge ≤5°C logs; FIFO for prepped items
Free water sign (§5(E))Low if no seatingRequired if counter pickup / food court
Calorie/allergen (chains 10+)Medium for multi-outlet brandsDigital menu disclosures on aggregators

RUCO and frying: cloud kitchens cross 50L fast

Wings, fries, and pakoda menus push many cloud kitchens past 50 litres of oil per day — triggering the daily register and mandatory UCO handover under §6. See the full RUCO deep-dive.

  • Test TPC every 8 cumulative frying hours; discard at ≥25%.
  • Store UCO in closed drums; never pour down drain.
  • Retain RUCO collection receipts — inspectors ask for the last 3–6 months.

Staff training and medical fitness

High churn makes cloud kitchens vulnerable on certificates. Every handler needs annual medical fitness and FoSTaC training; maintain one supervisor per 25 handlers. Details: FoSTaC and medical fitness guide.

Packaging, riders, and aggregator handoff

  1. No newspaper or printed paper for food contact — explicit 2026 enforcement item.
  2. Rider handoff zone — aggregators' riders should collect at a counter; not enter prep areas (§3.7).
  3. In-house delivery staff — FoSTaC Basic training records on file.
  4. Sealed outbound packaging — tamper-evident bags; brand label with FSSAI number where required.

Multi-brand kitchens: extra scrutiny

Operating 3–8 brands from one facility is legal if declared — but inspectors check cross-contamination, allergen segregation, and whether each brand's packaging is distinct. Undeclared brands on aggregators are a licence-misrepresentation risk.

Economics reminder: cloud kitchens carry 35–38% contribution margin after aggregator commission — see cloud kitchen vs casual dining. Compliance fines and suspension days erase months of that margin.

Pre-inspection checklist (45 minutes)

  1. FSSAI licence framed at premises entrance; FoSCoS fee current.
  2. Pull all medical fitness + FoSTaC certs; fix expiries before next shift.
  3. TPC log current; RUCO receipts filed; no newspaper in pack station.
  4. Fridge/freezer temps logged today.
  5. Virtual brands match FoSCoS declaration and aggregator listings.
  6. Run Inspection Ready with Maharashtra + cloud-kitchen profile selected.

Run the audit — then fix the licence stack

Forkcast Inspection Ready branches for delivery-only profiles — RUCO, packaging, rider training, and staff zones — with closure-risk scoring and Marathi UI.

Run Inspection Ready audit →

Still getting your licence?

Operating compliance assumes a valid premises licence. If you are pre-launch, file FSSAI and municipal approvals in parallel — hygiene habits are cheaper to build before the first aggregator listing goes live.

Open the licence checklist →

More for you

Cloud kitchen FDA compliance Maharashtra 2026 | Forkcast