Running a Dispatch-Ready Cloud Kitchen in Hyderabad

Do not ask every cook to monitor aggregator tablets, answer rider calls and pack completed dishes. Assign one order controller per busy shift, even if this responsibility rotates among trained team members. The controller accepts orders, reads modifiers aloud or marks them on the kitchen ticket, watches preparation times and groups items by order number. Cooks remain responsible for recipe accuracy; the controller owns order completeness and dispatch sequence.

During quieter periods, the controller may also handle packing. At peak time, split packing and handover if order volume creates a queue. A practical dinner team might include a hot-line cook, a preparation or assembly cook, a packer-controller and a utility worker. Cross-train one person as backup for each position, but avoid informal switching during a rush. A written station allocation at shift start prevents two people assuming the other checked an order.

Packaging should be specified dish by dish rather than purchased as a collection of convenient container sizes. Biryani, gravies, fried snacks, beverages and bakery items create different heat, moisture and movement risks. Test each menu item after 30 minutes in a closed delivery bag, including travel over uneven roads. An item that looks correct at the pass may arrive poorly in Nanakramguda or the Financial District if steam softens it or oil weakens the container.

Maintain a packaging specification sheet showing container size, lid type, liner, seal, cutlery and outer bag for every item. Add the full packaging cost to the recipe cost: container, lid, condiment cup, label, tape and carry bag. Saving ₹2 on a weak gravy container is not economical if it causes leakage, refunds and remakes. Limit approved alternatives so staff do not improvise when one stock-keeping unit runs low.

Set a fixed sequence that works for every aggregator and direct order. The packer first matches the ticket to prepared items, then checks portions, modifiers and accompaniments. Containers are closed, wiped, sealed and labelled before entering the outer bag. The final count should include small items such as chutneys, dips, breads, desserts and beverages. These are easily missed because they may come from a different station or refrigerator.

Labels should display the order number prominently, with vegetarian or non-vegetarian identification where relevant. If several brands operate from one kitchen, include the virtual brand name so similar orders are not exchanged. Place the ticket or checklist at the packing bench rather than relying on the aggregator screen across the room. Only the controller should close the bag after confirming the item count against the ticket.

Create a marked rider collection point away from food preparation and packing benches. The handover person should confirm the order number verbally and on the rider’s screen before releasing the bag. Never hand over an unsealed order because the rider is impatient. In high-demand areas such as Madhapur or Jubilee Hills, multiple riders may arrive together; arrange completed bags by aggregator and order number, not by arrival time alone.

Keep a simple daily error register covering missing items, wrong items, leakage, damaged packaging, delayed preparation and incorrect handover. Record the shift, order number and responsible stage without using the log to blame individuals. Review it for ten minutes before the next busy shift. Repeated missing dips indicate a checklist problem; recurring leaks indicate a container or filling problem. Correct the process first, then retrain the relevant position and verify the change over subsequent shifts.