Cloud kitchens explained simply – in 3 points
- No dining room: a cloud kitchen produces exclusively for delivery and collection – no table service, no tables, no walk-in customers.
- 100% digital: orders come in via delivery platforms (Lieferando, Uber Eats, Wolt) or your own online shop.
- Low fixed costs: without a dining room, front-of-house staff or a prime location, start-up investment and running costs fall considerably.
The delivery-only model is one of the fastest-growing trends in hospitality. But who does a restaurant without a dining room really pay off for? And which operational challenges lie in wait? This guide gives you a practical overview – from the definition and the business model to the concrete steps for getting started.
1. Definition: what does cloud kitchen mean?
The term “cloud kitchen” describes a commercial kitchen that produces food exclusively for delivery and collection. There is no dining room, no tables, no table service. All customer interaction is digital – via delivery platforms such as Lieferando, Uber Eats or Wolt, or via your own online shop.
The name follows the logic of “cloud computing”: the infrastructure exists, but the end customer does not see it. Just as you do not visit a server room when you use an app, no guest ever steps into the kitchen of a cloud kitchen. Internationally, the terms ghost kitchen, dark kitchen, virtual kitchen and delivery-only kitchen are also common.
Explained simply: imagine a restaurant that consists only of a kitchen. No entrance for guests, no waiters, no menu on the table. Instead: an efficient production site that cooks food, packs it and gets it to the customer via a delivery service.
2. Ghost kitchen, dark kitchen, virtual kitchen – the differences
In everyday use the terms are often used interchangeably, but they differ in nuance:
| Term | Focus / nuance | Typical scenario |
|---|---|---|
| Cloud kitchen | Umbrella term for kitchen-based delivery-only concepts | A provider supplies kitchen infrastructure (kitchen as a service), several brands produce there |
| Ghost kitchen | Emphasises invisibility – no sign, no public footfall | Independent operation on an industrial estate, delivering under its own brand name |
| Dark kitchen | Mainly used in Europe and the UK, identical in substance to ghost kitchen | Deliveroo Editions, former Gorillas kitchens |
| Virtual kitchen | Emphasises the brand: a virtual restaurant exists only as an online presence | An existing restaurant kitchen runs a second brand for delivery only |
| Virtual brand | A pure brand without its own kitchen – production by partners | A food influencer launches a burger brand, produced in someone else's rental kitchen |
3. The cloud kitchen business model
The business model of a delivery-only restaurant differs fundamentally from the classic hospitality approach. Here are the key building blocks:
Revenue streams
- Delivery platforms: Uber Eats, Lieferando, Wolt – reach in exchange for commission (typically 15–30%)
- Your own online shop: higher margin, but you need to build your own customer base
- Catering & B2B: lunch delivery for offices, event catering as an additional business
- Multi-brand strategy: one kitchen, several virtual brands – e.g. bowls, burgers and poke from the same production
Cost structure at a glance
| Cost block | Classic restaurant | Delivery-only kitchen |
|---|---|---|
| Rent / space | Large (dining room + kitchen + storeroom) | Small (kitchen + storeroom only) |
| Staff | Kitchen + front of house + host | Kitchen + packaging only |
| Start-up investment | €80,000–500,000+ | €20,000–80,000 |
| Cost of goods | 28–35% | 26–33% |
| Platform commission | 0% (direct business) | 15–30% (main channel) |
| Marketing | Walk-ins + local | 100% digital (SEO, paid, social) |
Multi-brand: one kitchen, many brands
One of the strongest concepts in the food delivery business is the multi-brand strategy. A single kitchen runs several virtual brands in parallel that share infrastructure, staff and storage. Each brand has its own branding, its own menu and its own platform profile.
The model is efficient – but it places high demands on stock management. When three brands work from the same storeroom, consumption per brand has to be clearly attributable. Otherwise the multi-brand strategy quickly turns into a costing problem.
4. Delivery-only vs. classic restaurant
Where delivery-only concepts score
- Faster start: operational in weeks instead of months – no elaborate dining room design needed
- Lower fixed costs: less space, fewer staff, no prime location required
- Scalability: new sites or brands can be added comparatively quickly
- Data-driven from day 1: every order is digital – analysis and optimisation are possible straight away
Where classic restaurants are stronger
- Guest experience: atmosphere and personal contact cannot be replaced digitally
- Brand loyalty: regulars are built more easily through personal relationships
- Higher margins: no commission deducted by delivery platforms, strong drinks revenue (often 70%+ margin)
- Flexibility with shrinkage: daily specials from leftover stock, spontaneous recommendations – hardly possible in the delivery business
Hybrid models as the future: many successful venues combine both worlds: a classic restaurant with a dining room plus one or more virtual brands that generate additional revenue from the same kitchen – especially outside peak times.
5. Advantages and disadvantages of a cloud kitchen
Advantages
- Low start-up investment: €20,000–80,000 vs. €80,000–500,000+ for a classic restaurant
- Location flexibility: industrial estates, backyard kitchens or kitchen-as-a-service spaces – no need for a prime location
- Fast testing: new dishes, brands or concepts can be launched and validated in days
- Focus on production: no dining room management, no service training – full focus on the kitchen and quality
Disadvantages
- Platform dependency: delivery platforms take 15–30% commission and control the customer relationship
- No hospitality experience: emotional customer loyalty is much harder without personal contact
- Loss of quality in transit: not every dish survives 20–30 minutes of delivery time without suffering
- Packaging costs: sustainable packaging is expensive but essential for brand perception
- Precise inventory management required: without a dining room as a buffer (daily specials, spontaneous recommendations), stock has to be exactly right
6. How to start a cloud kitchen: step by step
Step 1: define the concept and target market
What do you want to offer? For whom? Delivery customers order differently from guests on site. Proven concepts in the food delivery business are bowls, burgers, wraps, curry and poke – dishes that pack and travel well.
Step 2: choose a kitchen model
- Your own kitchen: rent and fit out commercial premises – full control, higher investment
- Kitchen as a service: rental kitchen (shared kitchen) with shared infrastructure – low entry costs, less flexibility
- Repurpose an existing kitchen: use your restaurant outside peak hours or a catering kitchen
Step 3: permits and hygiene
Even a restaurant without a dining room is subject to the same food hygiene rules: a HACCP plan, instruction under the German Infection Protection Act (Section 43), business registration and, where applicable, inspection by the local health authority (Gesundheitsamt). Allow 4–8 weeks for this.
Step 4: set up delivery platforms
Register with at least two platforms for reach. Invest in professional food photos – in the delivery business, customers buy with their eyes before they order.
Step 5: optimise the menu for delivery
Test which dishes still look and taste good after 20–30 minutes in transit. Cut down to your strongest 15–20 items – in the delivery business, less is almost always more.
Step 6: set up stock management and processes
Before you go live, you need clear processes for purchasing, storage and stocktaking. This is where many delivery-only concepts fail: they start with gut feeling instead of data. Set up structured stock management from the start – whether via a specialised stocktake tool, an inventory management system or at least a properly maintained spreadsheet.
Quick-start tip: start lean: one brand, 15 dishes, one delivery partner. Only once kitchen, storage, ordering and delivery are running smoothly do you scale to more brands and platforms.
7. Cost of goods and stock management: the decisive success factor
If there is one area that decides success or failure for delivery-only concepts, it is cost of goods. The reason: without drinks revenue and without the option of selling leftover stock as a daily special, every euro lost in purchasing hits the margin directly.
The specific challenges
- Several brands, one storeroom: without clean allocation, costing per brand is impossible
- Open containers everywhere: opened sauces, half-used packs, open spice containers – not easy to scan
- Time pressure: between the lunch peak and evening production there are often only 30–45 minutes for the count
- Changing staff: the stocktake system has to be intuitive enough for anyone to use
- Several storage locations: fridge, dry store, prep station, packaging store – everything has to be mapped
Cost-of-goods formula for delivery-only venues
Cost of goods (%) = (opening stock + purchases – closing stock) ÷ revenue × 100
Clean stocktake data is the basis for opening and closing stock – without it, the formula is worthless.
Typical delivery-only venues aim for a cost of goods of 26–32%. Because dishes are standardised, tighter control is possible than in classic restaurants – but only with regular, reliable stocktakes.
Which tools help with stock management?
The market offers various approaches to food cost control and stocktaking in hospitality:
- Specialised stocktake tools: focused on F&B reality: open containers, slider input, cut-off-date workflows. Examples: BarBrain, Supy, Apicbase
- Inventory management systems: more comprehensive solutions with purchasing, recipe management and costing. Examples: MarketMan, Lightspeed Restaurant
- POS-integrated solutions: POS systems with a stocktake module – often less in-depth, but seamlessly integrated
- Excel / Google Sheets: workable at the very start, but barely maintainable beyond 50+ items
Common mistake: many founders invest heavily in platform presence and marketing but skimp on inventory management. The result: revenue grows, margin does not – because nobody knows where the costs actually are.
8. Market data: figures, growth and trends
The market for delivery-only concepts is growing rapidly – driven by changing consumer behaviour, rising delivery demand and the search for cost-efficient hospitality models.
Global market size
The global market was estimated at around USD 73–78 billion in 2024 and is expected to grow to more than USD 140–190 billion by the early 2030s – with compound annual growth rates (CAGR) of 9.5–12%, depending on the source.
Sources: Grand View Research (USD 73.2 billion, 2024), IMARC Group (USD 78.1 billion, 2024), Market Data Forecast (USD 74.2 billion, 2024)
The market in Germany and Europe
Europe is a growing market with regional fragmentation. According to several analysts, Germany is the fastest-growing European market for delivery-only concepts, with a market volume of around USD 3.9 billion (2025) and a forecast tripling to approx. USD 10.1 billion by 2034.
Sources: IMARC Group – Germany Cloud Kitchen Market (USD 3.9 billion, 2025); Virtue Market Research – Europe Cloud Kitchen Market (Germany with 20% market share, fastest growth)
Trends shaping the market
- Hybrid models: restaurants add virtual brands from their existing kitchen to their offering
- Kitchen pods: modular kitchen units that can be set up quickly – the fastest-growing sub-segment
- Sustainability: packaging and delivery logistics are becoming a differentiator for brand perception
- Data as a competitive advantage: venues that manage cost of goods, order patterns and food costs based on data scale more profitably
Consolidation: large players such as Kitopi, Rebel Foods and CloudKitchens (Travis Kalanick) increasingly dominate the infrastructure
Conclusion: cloud kitchens are more than a trend
The cloud kitchen concept goes far beyond a pure delivery kitchen. It is a fundamentally different business model for hospitality – leaner, more data-driven and more scalable than the classic approach. But it comes with its own challenges: platform dependency, lack of customer contact and the need to manage cost of goods and stock precisely.
If you want to run a cloud kitchen successfully, you need, besides a strong concept and good food, one thing above all: control over the numbers. And that starts with a clean, regular stocktake – the foundation for costing, purchasing and profitability.






.jpeg)
