01
Kitchen Opening & Daily Setup
Equipment checks, aggregator tablet boot-up, packaging inventory count, brand-wise mise en place, staff assignment, and yesterday's rejection review. All before the first order.
Free Cloud Kitchen Operations SOP for Indian Cloud Kitchens (2025-26)
80+ step-by-step procedures for running a delivery-only kitchen. Multi-brand management, Zomato/Swiggy order dispatch, packaging standards, rider handoff, inventory control, and FSSAI compliance. Built for Indian cloud kitchens.
- 10 sections covering every cloud kitchen operation, from morning setup to end-of-day closing
- Multi-brand SOPs: how to run 3-5 brands from one kitchen without mixing up orders or packaging
- Aggregator platform management, rider handoff protocols, and delivery-specific food quality standards
No spam. Instant download link to your
email.
Petpooja presents
Cloud Kitchen Operations SOP
For Indian Cloud Kitchens
80+
SOP items · 13-page PDF
FSSAI
What's Inside
Ten sections covering every cloud kitchen operation.
02
Multi-Brand & Station Management
How to run 3-5 brands from a single kitchen. Station assignment, shared ingredient strategy, menu engineering for delivery, and real-time availability updates across platforms.
03
Order Receiving & Kitchen Workflow
Order acceptance in under 60 seconds, KOT routing to the right station, priority by delivery time, multi-item batching, and special instruction handling.
04
Food Prep & Delivery Quality
Cooking for transit (not for the table), consistent portioning, wet/dry separation, batch cooking aligned to peak hours, and temperature danger zone management.
05
Packaging & FSSAI Labelling
Tamper-evident seals, food-grade containers, brand-specific packaging, FSSAI licence display, veg/non-veg marking, allergen information, and the "consume within" timestamp.
06
Dispatch & Rider Handoff
Dedicated dispatch counter setup, order verification before sealing, rider handoff in under 2 minutes, order number confirmation, and dispatch time logging.
07
Aggregator Platform Management
Menu photo updates, negative review responses within 24 hours, weekly commission reconciliation, promotion ROI tracking, and platform score monitoring.
08
Inventory & Procurement
Unified inventory across brands, reorder point calculations, evening stock counts, wastage tracking by brand and ingredient, FIFO enforcement, and delivery inspections.
09
Hygiene & FSSAI Compliance
Handwashing protocols, surface sanitisation between brands, per-brand FSSAI licensing, FoSTaC supervisor coverage, temperature logs, cleaning schedules, and pest control records.
10
Kitchen Closing & End-of-Day
Go offline 30 minutes early, complete pending orders, gas valve shutdown, platform reconciliation, wastage log, stock count, equipment deep clean, and shift notes for tomorrow.
Why This Matters
Why Cloud Kitchens Fail Without Written SOPs
Most cloud kitchens in India start the same way: a small kitchen, 2-3 brands on Zomato and Swiggy, and a team of 4-5 people who "know what to do." It works for the first month. Then orders scale to 80-100 per day, and everything breaks.
Wrong orders go out because nobody verified the KOT against the packed items. Brand A's packaging ends up on Brand B's food. A rider picks up the wrong bag because 12 orders are sitting on the same counter with no system. The Swiggy tablet goes offline for 20 minutes and nobody notices.
Cloud kitchens are harder to run than dine-in restaurants. Honestly. You're managing multiple brands, multiple platforms, and hundreds of delivery orders from a kitchen that's often smaller than a regular restaurant's. There's no front-of-house to catch mistakes. The customer opens the bag at home, and that's your one shot. A Petpooja analysis of why cloud kitchens shut down found that operational chaos, not lack of demand, is the top reason.
Written SOPs fix this. Not a 200-page document nobody reads. Practical, station-specific procedures that your team follows every shift. The opening cook boots up the tablets and checks packaging stock before going online. The dispatch person verifies every order against the ticket before sealing. The closing team reconciles orders across all platforms before leaving. Same steps, every day.
FSSAI applies the same Schedule 4 food safety standards to cloud kitchens as it does to dine-in restaurants. No exemptions for being delivery-only. Temperature logs, cleaning records, staff medical certificates, pest control documentation. Inspectors visit cloud kitchens too. And since you need a separate FSSAI licence for each brand name, compliance is actually more complex.
This SOP manual covers every operational area specific to cloud kitchens: multi-brand station management, aggregator platform handling, delivery-specific food quality, packaging and labelling, rider dispatch, and end-of-day reconciliation. 80+ procedures across 10 sections.
Sample Preview
5 SOPs from the manual.
Here's a preview of what you'll get inside:
Daily Opening: Boot up all aggregator tablets and POS. Confirm all brands show 'online' status. Check menu prices and item availability match today's stock before accepting orders.
Multi-Brand: Keep brand-specific packaging at each station. Containers, stickers, menu inserts, and bags for Brand A stay at Station A. One wrong container and the customer sees the wrong brand.
Order Dispatch: Verify every order against the KOT before sealing. All items present, correct brand packaging, special instructions followed, cutlery included. This 30-second check prevents wrong orders.
Packaging: Use tamper-evident packaging for every order. Sealed bags with brand stickers or heat-sealed containers. FSSAI licence number visible on every package.
Closing: Go offline on all platforms 30 minutes before closing. Complete pending orders first, then start shutdown. Reconcile the day's orders across all platforms before leaving.
... and 75+ more SOPs across food quality for delivery, inventory management, aggregator platform handling, FSSAI compliance, and hygiene in the full PDF.
Key Stats
Numbers every cloud kitchen operator should know.
15-30%
Aggregator commission on every order. Zomato and Swiggy charge this depending on your plan and city. Without tracking commissions weekly and reconciling payouts, cloud kitchens often don't realise they're losing money on specific items. Petpooja's free GST calculator can help you work out the tax component on these commissions.
Source: Zomato/Swiggy partner documentation (rates vary by plan and city). GST applies on commissions per GST portal guidelines.30min
The average delivery time customers expect for cloud kitchen orders in Indian metros. Your food sits in a bag for 20-30 minutes after leaving the kitchen. Recipes, packaging, and portion sizes must be designed for this transit time, not for immediate serving.
Source: Industry average based on aggregator platform data28-35%
Target food cost percentage for a profitable cloud kitchen in India. With aggregator commissions eating 15-30% of revenue, food cost above 35% usually means the kitchen is unprofitable on a per-order basis.
Source: Industry benchmarks for delivery-only kitchens in India
Common Mistakes
8 cloud kitchen mistakes that SOPs prevent.
01
Mixing up packaging across brands
Brand A's biryani in Brand B's container. It happens more than you'd think when 15 orders are being packed simultaneously. Brand-specific packaging stored at each station, not in a shared pile, prevents this.
02
Not verifying orders before sealing the bag
One missing item, one wrong dish, or one skipped special instruction. The customer opens the bag at home and there's no fixing it. A 30-second verification against the KOT catches most errors before they leave the kitchen. Use our Restaurant Kitchen SOP Manual for the core food safety procedures that apply to all kitchens.
03
Ignoring aggregator tablet connectivity during service
A Swiggy tablet goes offline for 20 minutes. You miss 8 orders. Those show up as "restaurant not accepting" on the platform and hurt your score. Assign one person to monitor all tablets during peak hours.
04
Cooking the same way for delivery as for dine-in
Crispy fried items get soggy in a delivery bag. Thick curries congeal. Rice dries out. Cloud kitchen recipes need adjustment for 20-30 minutes of transit. Slightly more gravy, separate packaging for crispy elements.
05
Running too many brands with too small a team
Five brands sounds great on paper. But if you have 4 cooks managing 5 brands during peak hours, quality drops. Start with 2-3 brands, nail the operations, then expand. Each new brand adds complexity exponentially. This common cloud kitchen mistake is the fastest way to bleed money.
06
Not tracking food cost per brand separately
Your biryani brand might be profitable at 30% food cost, but your pizza brand might be bleeding at 42%. Without brand-level tracking, the profitable brand subsidises the unprofitable one, and you don't see it. Our Food Cost Calculator can help you track this.
07
Skipping FSSAI licence for each brand name
Each brand name needs its own FSSAI registration or licence. One kitchen, five brands, five licences. Running unlicenced brands is a violation that can shut down your entire operation, not just the offending brand.
08
No end-of-day reconciliation across platforms
Orders accepted on Zomato, Swiggy, and direct channels. Cancellations, refunds, and commission deductions. Without daily reconciliation, you won't know your actual revenue until the bank statement arrives. By then it's too late to fix issues.
Comparison
Cloud kitchen without SOPs vs with this manual.
| Aspect | Without SOPs | With This SOP Manual |
|---|---|---|
| Morning setup | Whoever arrives first figures it out | 8-step opening checklist, same every day |
| Multi-brand management | Packaging mix-ups, brand confusion | Dedicated stations, brand-specific packaging storage |
| Order dispatch | Wrong bags, missing items, no verification | KOT-verified, sealed, order number confirmed with rider |
| Food quality for delivery | Same recipes as dine-in, food arrives soggy | Transit-adjusted recipes, wet/dry separation, thermal packaging |
| Platform management | Tablets go offline, reviews unanswered | Dedicated monitoring, 24h review response, weekly reconciliation |
| FSSAI compliance | One licence for 5 brands (illegal) | Per-brand licensing, proper labelling, all records maintained |
| End of day | Quick shutdown, no reconciliation | Platform reconciliation, wastage log, shift notes for tomorrow |
Run a cloud kitchen that works the same way every shift.
Download the free SOP manual. Print the station-specific sheets. Brief your team. Done.
FAQ
Frequently asked questions.
What operations does this SOP manual cover?
Ten areas: kitchen opening and setup, multi-brand station management, order receiving and kitchen workflow, food preparation for delivery, packaging and FSSAI labelling, dispatch and rider handoff, aggregator platform management, inventory and procurement, hygiene and FSSAI compliance, and kitchen closing. Each section has step-by-step procedures built specifically for delivery-only kitchens.
Is this different from a regular restaurant kitchen SOP?
Yes. Regular kitchen SOPs focus on dine-in service, table-side quality, and front-of-house coordination. This manual covers what's unique to cloud kitchens: running multiple brands from one kitchen, managing Zomato and Swiggy platforms, packaging for 20-30 minute transit, rider handoff protocols, and per-brand FSSAI licensing. The core food safety procedures (temperatures, hygiene, FSSAI Schedule 4) overlap, but the operational workflow is completely different. Petpooja's guide on how POS software helps cloud kitchens handle multiple brands covers the technology side.
Do I need a separate FSSAI licence for each brand?
Yes. Each brand name operating from your kitchen needs its own FSSAI registration or licence under the FSS (Licensing and Registration) Regulations, 2011. Petpooja's complete guide to cloud kitchen licences in India covers the full requirements. Some operators list all brand names under a single licence application, but each brand must be explicitly mentioned. Our FSSAI Compliance Checklist walks you through the licensing process step by step.
How many brands can I realistically run from one kitchen?
It depends on your kitchen size, equipment, and team. Most successful cloud kitchens in India run 2-4 brands. The key is menu overlap: if 60-70% of your base ingredients are shared across brands, you can run more brands without proportionally increasing inventory or prep work. Going beyond 5 brands from a single kitchen usually leads to quality issues unless you have 200+ sq ft per brand and dedicated staff. Petpooja's guide to starting a profitable cloud kitchen covers brand strategy in detail.
Can I use this for a single-brand delivery kitchen?
Absolutely. Skip Section 2 (multi-brand management) and every other section applies as-is. Single-brand cloud kitchens still need order dispatch SOPs, packaging standards, aggregator platform management, and FSSAI compliance. If you're using a kitchen display system (KDS) instead of paper tickets, the order workflow section still applies. Honestly, single-brand kitchens benefit even more because the SOPs are simpler to implement with a smaller team.
About Petpooja
Petpooja is India's leading SME business software suite, trusted by 1,50,000+ businesses across restaurants, retail, healthcare, manufacturing, and more. From billing and payroll to task management and procurement, Petpooja helps Indian businesses run better, every day.
Run your cloud kitchen on one dashboard
Petpooja POSS integrates Zomato, Swiggy, and direct orders into a single screen. Automatic KOT routing, real-time menu sync across all platforms, and detailed business reports. Pair it with Petpooja Tasks for digital SOP compliance with photo-verified proof and WhatsApp alerts.
Book a Free Demo
Call: +91-9104369797