Cloud kitchen: building a channel that is yours

A cloud kitchen is a kitchen with no dining room. No window, no sign, no passing trade. Every order arrives through a channel, and that changes the whole shape of the business.

This is a guide to the consequence most operators discover late: if the channel belongs to somebody else, so does the business.

What is different about running one

A restaurant with a room has three ways to be found: somebody walks past, somebody is recommended, or somebody searches. A cloud kitchen has one, and it is usually a marketplace listing.

That has three effects worth naming.

Your position is rented. Where you appear in a listing is set by somebody else, and it can change without notice or explanation.

Your customer is not yours. The relationship, the contact and the price of the next order all sit with the platform.

Your margin is thinner by design. There is no room, which saves rent, and the saving tends to be absorbed by the commission on every order.

None of that makes a cloud kitchen a bad business. It makes the channel question the whole business.

"A cloud kitchen without its own channel is a supplier to somebody else's app. The food is yours and almost nothing else is."

— Tanzeel ur Rehman, co-founder of Get Menu

Cloud kitchen Dubai: the practical version

In Dubai the marketplaces are how most cloud kitchens start, and that is a reasonable way to begin. They bring people who have never heard of you, and they absorb the cost of a late delivery.

The mistake is stopping there, because the second order from the same person costs you exactly as much as the first. That is fine when you are being introduced to somebody and expensive forever afterwards.

The fix is not to leave. It is to have somewhere for the repeat customer to go.

What your own channel needs

Your own ordering page, and the machinery around it that makes an order actually work without a room:

• Your own ordering page, with 12 page layouts so the menu reads the way you want it to.
• A QR code on every delivery bag, printed from a designer rather than a generic sticker, going to your page. This is the cheapest customer acquisition a cloud kitchen has, because the food is already in their hand.
• A menu you edit yourself, with options and add-ons carrying their own prices, and required choices the kitchen can trust.
• Orders that price themselves. Every line is re-priced from your live menu at checkout, so a page left open cannot sell at an old price.
• Messages nobody types. WhatsApp is the channel in this market and the platform is documented and built for business use. A confirmation reaches the customer the moment they order, the kitchen gets its ticket, and the rider gets a link carrying the GPS pin dropped at checkout. That is 3 messages in about 2 seconds.
• Live stock on items and on options, greying out what has gone, which matters more without a room because nobody can walk over and ask.
• Condo delivery rules, so a tower with its own fee or its own minimum is handled at checkout instead of on a call.
• Loyalty stamps, and tiers your regulars grow into, each carrying its own automatic discount.
• A wallet card in the customer's phone with no app to install, using Google's own loyalty card format.
• VAT invoices carrying your TRN, downloaded as a PDF without the customer logging in.
• Coupons, upsells and bundles with caps, exclusions and expiry dates, and never two automatic discounts at once.

There is no commission on orders through your own page, so the hundredth in a week costs the same as the first.

The bag is the whole strategy

If you take one thing from this: the delivery bag is the only physical contact a cloud kitchen has with a customer.

A restaurant with a room gets a second chance every time somebody walks past. You get one, and it is the moment the bag is opened. A code on it, going to your page, with a small reason to use it next time, is the entire acquisition channel you own.

It works slowly and it compounds. It is also the only version of this that does not involve paying somebody else for the same customer repeatedly.

Multiple brands from one kitchen

Many cloud kitchens run several brands from one unit, and the thing to check before committing is whether your software treats them as genuinely separate.

Each brand should have its own menu, its own hours and its own delivery area, with sales that can be read separately and together. If two brands share a stock count that is not actually shared in the kitchen, the numbers will mislead you within a month.

What we do not do

Payment is cash or your own card machine at the door. There are no online payments in our system, and for a cloud kitchen that is the limitation to weigh most carefully, because a marketplace takes payment up front and you would be asking a customer to pay on delivery instead. In some markets that is completely normal. Decide honestly whether it is in yours.

The benefit of the limit is that no card details are held in the system, and old order details clear automatically after 120 days. Pricing sits on the pricing page rather than in this article, and the trial runs 15 days with no card.

Frequently asked questions

Should a cloud kitchen leave the delivery apps?

Usually not, and rarely first. They bring people who have never heard of you. Build your own channel for the repeat customer, then decide with evidence.

What is the cheapest way to get customers onto my own page?

A code on the delivery bag. The food is already in their hand and they have already decided they like it.

How do customers pay on my own page?

Cash or your own card machine at the door. There are no online payments in our system, which is the trade-off to weigh for delivery specifically.

Can I run several brands from one kitchen?

Yes, and each keeps its own menu, hours and delivery area, with sales readable separately and together.

Do customers need an app for the loyalty card?

No. It goes into the phone's own wallet, which is already installed.