Cloud Kitchen Singapore: Setup, Licensing and Costs

A cloud kitchen lets you sell food without a dining room. In a market where rent and manpower are the two costs that decide whether an F&B business survives, that is a serious proposition — and it is why the model keeps spreading in Singapore.

Here is what a cloud kitchen actually is, how it differs from the terms people use interchangeably, what you need to start one here, and the operational trap most first-timers walk into.

What is the difference between cloud, ghost and central kitchens?

These three get used as synonyms. They are not, and the difference changes what you need to build.

• Cloud kitchen — a kitchen producing food for delivery only. No dining area, no walk-in trade. Orders arrive through delivery platforms or your own online store. Suits operators testing a concept, or scaling delivery without a storefront.
• Ghost kitchen — effectively the same thing. “Ghost” emphasises that the brand has no physical presence a customer can visit. In practice the terms are interchangeable.
• Central kitchen — a production facility supplying your other outlets, prepping and distributing to shops that do final assembly and service. Suits multi-outlet groups standardising quality and cutting per-site prep.

The practical distinction: a cloud kitchen sells to customers. A central kitchen supplies your own shops. Some operators run both — a central kitchen that also fulfils delivery-only brands.

Why does the model appeal in Singapore?

• Rent. Delivery-only space costs a fraction of a shopfront in a mall or on a main street, because you are not paying for footfall you do not use.
• Manpower. No front-of-house means a materially smaller team — significant given how tight F&B hiring is here.
• Speed to test. You can launch a concept, see whether anyone orders it, and close or pivot without a fit-out and a lease you are locked into.
• Multiple brands, one kitchen. One production line can serve several delivery brands targeting different cuisines or price points.

What does it cost to start?

Costs vary widely by facility, equipment and concept, so treat any single headline number with suspicion. Budget across these buckets:

• Kitchen space — renting a slot in a shared cloud-kitchen facility, or leasing and fitting out your own unit
• Equipment — cooking line, refrigeration, packaging station
• Licensing — the relevant SFA licence and related approvals
• Delivery platform commission — typically the largest ongoing cost, charged per order
• Packaging — a real line item at delivery volumes, not an afterthought
• Technology — POS, order management, inventory

The cost people underestimate is platform commission. Every order through a delivery aggregator carries a percentage. At cloud-kitchen margins, that percentage often decides whether the model works — which is why most operators eventually push customers toward their own ordering channel.

What licensing do you need?

A cloud kitchen must be licensed by the Singapore Food Agency in its own right. The absence of a dining area does not exempt it — and which licence you need turns on who you sell to, not on whether you have seats.

• Selling retail, direct to consumers (including through delivery platforms) — you need a Food Shop Licence. SFA’s food shop category already covers takeaway kiosks, takeaway food carts and caterers, none of which have a refreshment area. Note that “food caterer” is a food-shop business type, not a separate licence class.
• Preparing food for distribution to wholesalers and retailers — you need a Licence to Operate a Food Processing Establishment. SFA’s examples for this category include central kitchens.

Food handlers. Everyone handling food must hold valid WSQ Food Safety Course (FSC) Level 1 certification at the point of licence application, and you must register them with SFA. Retraining is required within five years, and within ten years thereafter. An FSC Level 3 Food Hygiene Officer is additionally required for food caterers, canteens, food courts, and restaurants occupying two or more adjacent units or with a kitchen area over 16 sq m.

The shared-kitchen rule that catches operators out. Renting a slot in someone else’s facility does not put you under their licence — and this is not a grey area. SFA states that where a licensee subleases premises in part or in whole, the new operator must apply for a new licence, and specifically that for cloud kitchens, each subdivided unit must apply for its own licence. Licences are also not transferable between licensees or UENs.

We have written the licensing process up in detail in our SFA food shop licence guide for new operators.

What is the operational trap nobody warns you about?

Here is what actually goes wrong, and it is not the food.

You launch on one delivery platform. Then a second. Then a third, because why not. Then you add your own ordering page to escape commission. Now you have four tablets on the pass, each pinging, each with its own menu that must be updated separately, each reporting sales in its own dashboard.

At twenty orders a day it is irritating. At two hundred it is a failure mode: missed orders, mismatched menus, a stock count nobody trusts, and no single view of what you actually sold.

Add a second brand out of the same kitchen and it compounds. Two brands across four channels is eight places a price change has to be made correctly.

The fix is architectural, not heroic. Orders from every channel need to land in one system, hit one kitchen display, and draw down one shared inventory. Otherwise you are paying staff to be middleware.

What should you look for in your tech stack?

1. Consolidated order intake — aggregator orders arriving in your POS, not on separate tablets
2. One kitchen display (KDS) — a single queue the kitchen works from, regardless of source
3. Shared inventory across brands — one stock pool, so selling out on one brand updates the others
4. Your own ordering channel — the only reliable way to reduce commission exposure over time
5. Per-brand and per-channel reporting — you need to know which brand and which platform actually makes money
6. Offline capability — a kitchen that stops accepting orders when the connection drops is losing revenue

Warely runs POS with kitchen display and offline mode, GrabFood integration, and an online store on the same inventory — so delivery and direct orders share one stock pool and one set of numbers. If you are weighing a cloud-kitchen setup, talk to us and we will be straight about which channels we integrate today and which we do not.

Is a cloud kitchen right for you?

It probably is if you want to test a concept cheaply, delivery is already most of your revenue, you have a proven menu that travels well, or you want a second brand without a second shopfront.

It probably is not if your food does not survive twenty minutes in a box, your margins cannot absorb platform commission, your brand depends on the room and the service, or you rely on walk-in discovery.

Frequently asked questions

Licensing requirements and platform terms change. Verify current SFA requirements and commission rates before committing.