Restaurant Management System

How a Cloud Kitchen Runs Its Orders, Brands and Stock

A cloud kitchen, also called a ghost kitchen or dark kitchen, cooks only for delivery and pickup. There is no dining room, so the whole operation is the path from an incoming order to a rider at the door. Cloud kitchen software keeps that path in one system: orders, kitchen tickets, stock and riders.

This guide follows one delivery order through that path, using Kappino's cloud kitchen software as the example.

Step 1: orders arrive from several channels

A delivery kitchen rarely takes orders from one place. In Kappino, orders can come from:

  • the POS
  • the QR and online ordering page
  • a WordPress or WooCommerce website, through the Kappino Connect plugin
  • WhatsApp

Each order lands on the live Orders board with its source marked, so the team works from one list. Takeaway orders carry the guest's name, phone and pickup time, and returning guests are filled in by customer autocomplete. Order management explains the board in detail, and our guide to WhatsApp ordering covers that channel.

Step 2: the order becomes station tickets

A cloud kitchen often has several stations: grill, fryer, cold prep, desserts. Kappino routes each order to the right station by category or item, so each cook sees only their part.

On the kitchen display, each ticket has a timer that turns amber at 8 minutes and red at 15. A preparation number on each line tells the team what to make first.

If an unpaid order is changed in the POS, only the new lines go to the kitchen, marked as added. Dishes already cooking stay as they are. The kitchen display can cancel a ticket only before preparation starts.

Step 3: stock follows each sale

Each dish has a recipe. When the order is placed, the recipe ingredients are deducted from stock automatically, and put back if the order is cancelled. Low-stock alerts warn you before an item runs out.

The menu editor shows the recipe cost and margin for every dish. For a kitchen that serves several brands, the same ingredients may appear in many recipes, so this is how you see what each dish really costs. Our article on food inventory management software follows one ingredient through this process.

Step 4: the order goes out with a rider

When the food is ready, staff mark the order ready on the kitchen display and dispatch it to a rider with a single tap.

In the Kappino Rider app, the rider:

  • shares their GPS location
  • marks the order collected, then delivered
  • attaches a proof-of-delivery photo

The photo stays on the order. Delivery rider management covers dispatch and the Rider app.

Step 5: run several brands from one kitchen

Many cloud kitchens sell under more than one brand name from the same space. In Kappino you set each brand up as its own branch. Every branch has its own menu, prices, stock and reports.

You can switch between brands or view them side by side, and see everything together under "All branches". If two brands share a store room, stock can be moved between branches with inventory transfers.

The same setup works if you open a delivery-only kitchen next to an existing restaurant. The new kitchen becomes a separate branch in the same account, with its own menu, stock and riders.

Step 6: control who sees what

A cloud kitchen team may include cooks, dispatchers, brand managers and franchisees. Kappino's roles and permissions matrix covers 30 modules. You can hide the modules a role doesn't use and decide who sees which branch.

A franchisee can have access to their own branch only, while head office sees every branch's figures.

Step 7: read the results and plan the next service

Every completed order feeds the reports. Order history can be filtered by status, channel and date range, and searched by order number, guest name or phone.

On plans with AI Sales Forecasting, completed orders also feed the forecast. It learns from your own order history, day-of-week patterns, seasonality and public holidays, to help you plan stock and staff. How sales forecasting works explains the method.

A short setup checklist for a cloud kitchen

  • List every channel you take orders from, and connect each one.
  • Map your categories to kitchen stations before the first service.
  • Add recipes to every dish, so stock and margin follow each order.
  • Create one branch per brand, each with its own menu and prices.
  • Set up roles, so each person sees only the modules and branches they need.
  • Run one test order from each channel through to a delivered status.

Frequently asked questions

What is cloud kitchen software?

It's software for delivery-only kitchens. It handles order intake from several channels, kitchen tickets by station, recipe-based stock and delivery riders in one system.

Can one cloud kitchen run several brands?

Yes. In Kappino each brand is set up as its own branch, with its own menu, prices, stock and reports. You can view them separately or together.

Do I need dine-in features?

No. You only use what you need. Tables and reservations are available if you add a dine-in counter later, and unused modules can be hidden by role.

Which plan does a cloud kitchen need?

It depends on the features. The Starter plan covers one branch with POS, orders, kitchen and inventory. Delivery Riders Management is part of the Growth plan. AI Sales Forecasting, the WordPress and Shopify website integration and extra branches are part of the Professional plan. See pricing for current details.

Kappino Restaurant OS

Run your restaurant from one connected workspace.

POS, orders, kitchen flow, inventory, reporting and AI tools built for modern restaurant operations.