digital menu for cloud kitchens
Digital Menu Setup for Cloud Kitchens: A Complete Guide
24 May 2026 · 5 min read
Cloud kitchens need a digital menu and direct WhatsApp ordering channel. Here's how to set one up, take direct orders, and reduce aggregator dependency.
Cloud kitchens operate without a dining room - which means no walk-in customers, no physical menu to hand out, and no natural way to build direct relationships with the people who eat your food.
Most cloud kitchens end up 100% dependent on Swiggy and Zomato, paying 22-30% commission on every order. It doesn't have to be that way.
A digital menu and WhatsApp ordering channel gives your cloud kitchen a direct-to-customer presence that you control. Here's exactly how to set one up.
What a cloud kitchen needs (that a regular restaurant doesn't)
A dine-in restaurant has a physical presence - customers walk past it, see the menu on a board, and interact with staff. That physical touchpoint builds familiarity and repeat visits.
Cloud kitchens have none of this. Your entire brand exists in a profile photo on Swiggy, a few item images, and reviews.
To build a real business, you need:
- A permanent home for your menu - a URL you control, not a listing on an aggregator that can change your ranking or delist you
- A way to take direct orders - so repeat customers can reach you without going through a platform
- A customer list - phone numbers you can broadcast to, not anonymous reviews you can't reach back
- Delivery radius control - since you deliver everything, knowing who's in range before they order matters
All four of these are possible with a digital menu and WhatsApp ordering setup.
Setting up your cloud kitchen menu on ZapMenu
Step 1: Create your restaurant profile
Sign up at zapmenu.in. Enter your cloud kitchen name, city, and kitchen area. You don't need a dine-in address - just your general delivery area. Your menu goes live at zapmenu.in/your-kitchen-name.
Step 2: Set up your menu with photos
Cloud kitchen menus live or die by their item photography. You don't have ambience to sell - the food has to do all the work.
Upload photos for every item. Phone photos are fine if the lighting is good. Use natural light, a clean background (a plain white plate on a wooden surface is standard). If photography isn't your strength, Rs 1,000-Rs 2,000 spent on a food photographer for a 2-hour shoot will cover most of your menu.
Mark items as veg, non-veg, or egg. Add bestseller markers to your top 3-4 items. These show prominently on the menu.
Step 3: Set your delivery zone
In Dashboard -> Settings, drop a pin on your kitchen location and set your delivery radius. ZapMenu uses this to tell customers whether you deliver to their address before they place an order - which reduces cancelled orders significantly.
You can also set a delivery charge - flat rate or distance-based.
Step 4: Enable WhatsApp ordering
Enter the WhatsApp number where you want to receive orders. Toggle ordering on. Your menu now has a cart and "Order on WhatsApp" button.
When a customer places an order, you receive a formatted message on WhatsApp:
- Item list and quantities
- Delivery address (with map link)
- Cooking instructions
- Estimated total
Step 5: Share your menu link
Your direct ordering channel is now live. Distribute the link:
- WhatsApp status and broadcasts
- Instagram bio
- Google Business profile
- Card inserts in every Swiggy/Zomato delivery order
Building a customer base as a cloud kitchen
Since you have no physical presence, customer acquisition requires more deliberate effort.
Use every delivery as a marketing opportunity
Every Swiggy or Zomato order is a chance to introduce a customer to your direct channel. Include a small card or sticker with:
- "Order directly and save Rs 30 - WhatsApp us: [your number]"
- A QR code linking to your ZapMenu page
- Your kitchen's Instagram handle
Capture phone numbers
When customers message you directly on WhatsApp, save their number. Build a broadcast list. Send updates when you add new items, run specials, or take a day off.
A broadcast list of 100 regular customers is worth more than 500 Swiggy ratings. You can reach them proactively; you can't reach ratings.
Instagram for discovery
Cloud kitchens that grow well typically have an active Instagram presence. Post your food, your packaging, your kitchen process. Use location hashtags for your delivery area. Instagram stories with your menu link in bio convert well.
Handling orders efficiently as a solo or small team
Cloud kitchens are often run by 2-5 people. Managing WhatsApp orders manually works at low volume but gets chaotic quickly.
Practical systems:
- Use WhatsApp Business with quick reply templates for order confirmation, estimated delivery time, and delivery updates
- Review ZapMenu's order history dashboard (Dashboard -> WhatsApp Orders stats) to track daily volume without manually counting chat messages
- Set ordering hours so customers can't place orders at 11pm when you're closed - ZapMenu supports ordering time windows
- Close ordering for the day when you're at capacity - toggle off in the dashboard
What about multiple brands from one kitchen?
Running multiple cloud kitchen brands from the same kitchen (a common model) is supported on ZapMenu's Pro plan - you can create multiple restaurant profiles under one owner account.
Each brand gets its own menu URL, QR code, and ordering channel. You manage them all from the same dashboard.
The cloud kitchen economics argument for direct ordering
Let's say your cloud kitchen does 150 orders/month at Rs 450 average order value through Swiggy/Zomato.
At 22% commission: you're paying Rs 14,850/month to the platforms.
If 40 of those orders (27%) move to direct WhatsApp ordering over 6 months:
- Savings: 40 x Rs 99 (22% of Rs 450) = Rs 3,960/month
- ZapMenu Pro costs Rs 399/month
- Net monthly saving: ~Rs 3,560
By month 12, that's over Rs 40,000 saved - from a channel that took 30 minutes to set up.
Cloud kitchens have a structural disadvantage in customer relationships. A direct digital menu and WhatsApp ordering channel is the most practical way to close that gap.