Cloud Kitchen: Technology for a Delivery-Only Restaurant

What a dark kitchen is

A dark kitchen (also called a cloud kitchen or ghost kitchen) is a production kitchen with no dining room. All sales go through delivery: aggregators, your own website, an app or a Telegram bot.

How the model differs from a regular restaurant:

• no dining room — no need to pay for a high-footfall location or table service;
• the location is chosen by delivery zone, not pedestrian traffic;
• one kitchen often runs several brands with different menus;
• all revenue depends on online channels and speed.

So technology here is not an add-on but the foundation of the business.

What the stack consists of

Order aggregation

Without aggregation, the kitchen has several tablets — one per aggregator — and a staff member re-enters orders into the POS by hand. It is slow and error-prone.

An order aggregator (order aggregation middleware) pulls orders from all channels via API and passes them to the POS and KDS as a single stream. Key features:

• automatic order acceptance without manual confirmation;
• a shared stop-list: an ingredient runs out and the dish is hidden in every channel at once;
• syncing statuses back to the aggregator: "cooking", "ready", "handed to courier".

Before choosing, check which aggregators in your city and which POS system the solution works with.

KDS: the kitchen display

A Kitchen Display System replaces paper tickets with screens at each station. What it gives a dark kitchen:

• an order is split by station: grill, cold prep, assembly;
• timers show which orders are at risk of being late;
• dishes from different brands in one order are finished in sync;
• the "ready" mark goes automatically to the aggregator and couriers.

Multi-brand menus

One kitchen might run, for example, a burger brand, an Asian brand and a salad brand on shared prep. That requires:

• a single database of dishes and recipes, with brands as storefronts on top of it;
• management of prices, photos and descriptions per brand and channel;
• food cost and margin tracked separately per brand;
• shared inventory, so an ingredient stop-list affects every brand.

Courier integration

Delivery options:

• the aggregator's couriers — the simplest, but you do not control delivery;
• a third-party delivery service via API;
• your own couriers — you need a dispatch module and a courier app.

Either way, the courier must get the ready signal on time instead of waiting at the kitchen.

Demand analytics

A dark kitchen runs on data. What to track:

• demand by hour and day of week — to plan prep and shifts;
• sales by brand, dish and channel — which brands pull their weight and which do not;
• preparation time by station and time to courier handover;
• cancellations and complaints with reasons;
• margin after aggregator commissions — this is what shows real profit.

Common mistakes

• Launching without order aggregation and re-entering orders into the POS by hand.
• Different menus across channels that are updated manually and drift apart.
• Counting revenue without subtracting aggregator commissions.
• Too many brands at launch for one small kitchen.