Cloud kitchen logistics in India connects four moving parts: vendor-to-commissary inbound, commissary-to-kitchen-pod transfers, aggregator pickup for last-mile, and reverse pickup of returnable containers and equipment. A working dark kitchen supply chain runs on scheduled recurring pickup slots, FSSAI-aware temperature handling, and a single B2B courier account with credit terms — not on retail courier bookings. This guide explains how to operationalise each loop, how multi-brand kitchens reconcile across brands, and how to set up a recurring B2B account that survives weekend surge.
Why Cloud Kitchens Need a Different Logistics Model
India’s cloud and dark kitchen segment is among the fastest-growing F&B sub-verticals — industry reports from FICCI and consulting firms cite annual growth rates in the high-20s to 30 percent range, far ahead of dine-in restaurant growth. The operating economics are unforgiving: rent, labour, and logistics are the top three cost lines, and logistics is the only one that compounds linearly with order volume. Every additional brand, every new pod, every new aggregator handoff adds a courier touchpoint.
Retail courier breaks at cloud kitchen scale for four reasons. SKU-level declared cargo is required per brand for accounting. Temperature variance between cold, hot-hold, and ambient food cannot be handled by a single vehicle without zoning. Pickup windows are fixed by service-prep timing — a 10 minute delay at the commissary can push lunch service into rider unavailability. And the reverse loop for returnable containers and aggregator rejects is a standing daily SOP, not a one-off booking.
For the broader business-account context, see the Business Courier Solutions India pillar guide. For the temperature-handling deep dive that this playbook references at multiple points, see the temperature-controlled food shipping canonical.
The Four-Loop Dark Kitchen Supply Chain
Every cloud kitchen, single-brand or multi-brand, runs four interlocking loops. Map your own ops onto this structure before negotiating a courier contract.
Loop 1: Vendor to Commissary Inbound
Daily produce, packaged ingredients, dairy, marinated proteins, and dry stores arrive at the commissary in a morning window — typically 6 to 8 am. Volume is large but predictable. Vendors are usually consolidated to a smaller list (8 to 15 suppliers for a 10-brand operation) because each vendor adds gate, PoD, and reconciliation overhead. This is the loop most often outsourced to a B2B courier with a fixed morning slot.
Loop 2: Commissary to Kitchen Pod Transfer
Pre-prepped semi-finished goods — sauces, gravies, marinated meats, par-baked breads, prepped vegetables — move from the central commissary to each kitchen pod two to three times a day depending on lunch and dinner service. FSSAI cold and hot zones apply at this stage. Cross-link: the bakery and confectionery logistics playbook covers the par-baked and fresh-baked freight profile in detail and applies directly to cloud kitchens that run a baking program.
Loop 3: Kitchen Pod to Aggregator Pickup
Final-stage cooked food is handed off to a Swiggy or Zomato rider at the pod for last-mile to the customer. The courier’s role in this loop is upstream — supplying clean packaging inventory to the pod, ensuring hot-hold containers are pre-positioned, and clearing aggregator rejects. The actual customer last-mile is rider-led.
Loop 4: Reverse Pickup
Returnable containers come back from pods to the commissary daily. Aggregator rejects and customer cancellations come back from delivery-partner hubs. Broken kitchen equipment goes out to OEM workshops for service and comes back when repaired. This is the loop most often skipped at the contract stage and most often the source of inventory loss.
Multi-Brand Cloud Kitchens: One Kitchen, Ten Brands, One Courier
The multi-brand model is now the default: a single physical kitchen hosts five to twenty virtual brands on aggregator platforms. One kitchen, multiple menus, multiple aggregator listings, multiple P&Ls. The logistics implication is brand-level accounting from the consignment note up.
Every commissary-to-pod transfer and every reverse pickup needs SKU-level declared cargo tagged to the correct brand. Without this, monthly courier invoices cannot be allocated back to brand P&Ls and unit-economics tracking falls apart. Packaging inventory inbound is its own SKU stream — biryani buckets for Brand A, kraft boxes for Brand B, hot-hold pouches for Brand C — and packaging stockout at the pod is one of the most common avoidable causes of late delivery.
Central reconciliation matters because the monthly courier invoice has to roll up across brands and pods on a single statement. Operators running 10 brands across 4 pods do not want 40 separate invoice lines to chase — they want one B2B invoice with a brand-and-pod breakdown that drops cleanly into the accounting stack.
Temperature Compliance: FSSAI Zones for Prepared Food
FSSAI’s catering and prepared-food advisories apply to every commissary-to-pod transfer. The three operational zones to design around are cold (dairy, marinated meat, pre-cut produce, sauces), hot-hold (parathas, cooked gravies, kebabs, biryani in hot-hold containers), and ambient (dry mixes, packaged goods, spices, rice). Mixing zones in the same vehicle compartment is the single biggest avoidable compliance failure.
Insulated container types commonly used in Indian cloud kitchen ops include thermal bags with reflective liners for hot-hold, cold boxes with reusable gel packs for chilled cargo, and electric hot-hold boxes for inter-city or extended transit. For inter-city commissary-to-pod transfers — common for chains running a central commissary in one city and pods in tier-2 cities — temperature loggers are now standard.
For a full breakdown of the chilled, frozen, and ambient classification system and packaging cost ranges, see the temperature-controlled food shipping guide, which is the canonical reference and is published with verified FSSAI citations. Official FSSAI rules are at fssai.gov.in.
Scheduled Recurring Pickup: The Daily Ops Calendar
A working cloud kitchen courier contract is a calendar, not a price sheet. The daily ops calendar below is typical for a mid-size multi-brand kitchen running both lunch and dinner service across two or three pods.
| Time slot | Loop | Use case |
|---|---|---|
| 6–8am | Vendor → Commissary | Daily produce, dairy, meat inbound |
| 10–11am | Commissary → Pods | Pre-prepped transfer for lunch service |
| 4–5pm | Commissary → Pods | Top-up transfer for dinner service |
| 11pm–12am | Reverse pickup | Returnable containers, aggregator rejects |
A B2B account locks each of these slots with a pre-allocated driver pool and ETA-locked drops. Monthly invoice rolls up all four slots. One-off bookings cause stockouts because pickup delays compound — a 30 minute commissary delay shifts lunch service into peak traffic, which delays dinner prep, which extends reverse pickup into next-day cleanup.
Bangalore’s cloud kitchen belt — Indiranagar, HSR Layout, Koramangala, Whitefield — concentrates the largest cluster of multi-brand operators in India. For operators expanding into or within the city, see our courier service in Bangalore coverage for pin-code and pickup-area detail.
Reverse Pickup: Containers, Aggregator Rejects, Equipment
The reverse loop is where margin leaks. Three streams flow through it. Returnable container loop — kitchen pods send empty hot-hold boxes, biryani buckets, and serving containers back to the commissary for cleaning and redeployment. Aggregator rejects and customer cancellations — food picked back up from delivery partner hubs, often non-returnable but tracked for write-off reconciliation. Equipment service returns — broken kitchen equipment (combi ovens, refrigeration units, dishwashers) sent out to OEM workshops and returned post-repair.
Reverse SOP is non-negotiable: photo PoD at pickup, condition check at receipt, segregated vehicle space so reverse-loop cargo does not contaminate forward-loop deliveries. The 11pm to 12am slot is the standard reverse window because it falls after service close and before the next morning’s vendor inbound. For the equipment service-return profile specifically, the restaurant equipment shipping playbook covers crating, vehicle selection, and OEM workshop coordination.
Peak Surge: Weekends, IPL Nights, Festivals, Monsoon
Cloud kitchen surge is more predictable than retail surge, which is exactly why it should be pre-blocked rather than spot-booked. Friday and Saturday dinner runs 1.5 to 2.5 times normal volume in most metros. IPL match nights produce well-documented spikes for biryani, pizza, and snack-format brands. Diwali, New Year, and regional festivals drive multi-day surges. Monsoon evenings in Mumbai, Bangalore, and Pune produce comfort-food spikes that compound with rider unavailability.
Pre-blocking vehicle slots 30 to 60 days ahead for these dates locks both capacity and price. Without pre-blocking, aggregator surge (1.5 to 3x rider rates) and courier surge can compound on the same night and either capacity becomes scarce or your delivery fee absorbs your margin.
For the catering-style event surge profile — where a single event generates a week of normal volume in one window — see the catering and event supply courier playbook, which applies to cloud kitchens that take on contract catering or large bulk orders.
Setting Up Your Cloud Kitchen B2B Courier Account
The four steps below are the HowTo sequence to operationalise a cloud kitchen B2B account from scratch.
- Map all four loops with daily and weekly volume per loop. Volume by loop, not by brand, is what the courier prices against.
- Tariff — request brand-level and pod-level declared-cargo brackets plus temperature surcharges for the cold and hot-hold zones. Lock loop-parity pricing so reverse pickup is billed as part of the loop, not a separate job.
- Schedule — lock fixed slots for vendor inbound (6–8am), commissary-to-pod transfer (10–11am and 4–5pm), and reverse pickup (11pm–12am). Pre-block surge dates for the next 90 days.
- Reconcile — monthly invoice broken down by brand and pod for unit-economics tracking. Demand a downloadable CSV that drops into your accounting tool, not a PDF.
For verified guidance on FSSAI and hospitality compliance, see the official Food Safety and Standards Authority of India portal and the Federation of Hotel and Restaurant Associations of India for sector-level reports and member protocols.
Frequently Asked Questions
What does cloud kitchen logistics actually involve?
Four loops: vendor-to-commissary inbound, commissary-to-kitchen-pod transfers, kitchen-pod-to-aggregator handoff, and reverse pickup of returnable containers and equipment. Each loop has its own time window, temperature zone, and SKU declaration — which is why retail courier doesn’t fit and a B2B scheduled-pickup account is required.
Is FSSAI compliance required for commissary-to-pod transfers?
Yes. Both commissary and kitchen pod are FSSAI-licensed premises, and prepared or semi-prepared food moving between them must follow FSSAI temperature and hygiene advisories — insulated containers, segregated cargo, and temperature logs on long-haul. See fssai.gov.in for current rules.
How do multi-brand cloud kitchens handle courier billing across brands?
SKU-level declared cargo per brand on every consignment note, rolled up monthly into a brand-and-pod-segmented invoice. This is essential for unit-economics tracking. A B2B account with reconciliation dashboards makes this manageable; retail courier bookings do not.
Who handles last-mile from cloud kitchen to customer — the kitchen or the courier?
Last-mile to the customer is usually handled by aggregator riders such as Swiggy and Zomato. The courier’s scope on the kitchen side is vendor inbound, commissary-to-pod transfer, packaging supply, and reverse pickup. Some kitchens also use a courier for direct-order last-mile when aggregator riders are unavailable.
What does reverse pickup mean for a cloud kitchen?
Returnable containers from pod back to commissary, aggregator-rejected parcels and customer cancellations from delivery partner hubs, and equipment service returns. Reverse pickup needs photo PoD and segregated vehicle space, and is best scheduled as a fixed nightly slot at 11pm or post-service closure.
How do cloud kitchens plan for peak surge nights like IPL or weekends?
Pre-block vehicle slots for predictable surge dates such as Friday and Saturday dinner, IPL match nights, Diwali, and New Year, and cap surge tariffs in the B2B contract. Without pre-blocking, both aggregator and courier surge compound and capacity becomes scarce.
Conclusion
Cloud kitchen logistics in India is not a courier-booking problem; it is a four-loop daily operating system that needs scheduled slots, FSSAI-aware temperature handling, brand-level SKU declaration, and a structured reverse pickup. Operators who lock these into a single B2B account stop firefighting and start scaling. To size a commissary-to-pod transfer plan for your kitchen, set up a cloud kitchen B2B courier account with CourierBook.