In this article +
- What makes cloud kitchens different
- The six things a cloud kitchen POS must do
- GST note for cloud kitchens
- Cloud kitchen POS comparison
- Where Ecomeal fits for cloud kitchens
- Checklist before you sign
- The real margin on a delivery order
- Direct orders: the margin lever
- A weekly cloud kitchen review
- Frequently asked questions
- Sources
The short answer
For most cloud kitchens, aggregator integration decides everything. Shortlist POS systems that pull Swiggy and Zomato orders straight into one screen and print KOTs automatically: Rista by DotPe, UrbanPiper Prime and Petpooja are strong here. Then compare multi-brand menus, reconciliation of payouts, and food cost by brand. Ecomeal doesn't integrate aggregators yet, so it suits kitchens with a strong dine-in or takeaway side rather than delivery-only operations, for now.
NRAI's India Food Services Report 2024 identifies cloud kitchens and delivery-led formats as a major segment of the market (MediaBrief summary). If you're running one, you already know the joke: you opened a restaurant and became an operations manager for three apps.
What makes cloud kitchens different
| Dine-in restaurant | Cloud kitchen |
|---|---|
| One brand, one menu | Often several brands from one kitchen |
| Orders from waiters and counter | Orders from apps, website, phone |
| Payment collected at the table | Payment arrives days later, minus commission |
| Guests see the food | Guests see a photo and a rating |
| Packaging is a takeaway detail | Packaging is a real cost line |
The six things a cloud kitchen POS must do
1. Pull aggregator orders into one screen
Five tablets beeping in five tones is not a system. The POS should accept Swiggy and Zomato orders directly, print KOTs automatically, and update order status back to the app. Rista lists "2-way aggregator integrations" for cloud kitchens (Rista by DotPe). UrbanPiper's origins are in aggregator middleware and its POS is described as strongest at managing delivery channels (Petpooja blog).
2. Run multiple brands from one kitchen
Your biryani brand and your burger brand share a kitchen, staff and some ingredients. The POS should keep separate menus and invoices per brand while letting the kitchen see one queue. Rista lists multi-brand invoices from one system.
3. Switch items off everywhere, instantly
When the chicken runs out, it needs to disappear from every brand on every app at once. Otherwise you'll get the order, cancel it, and lose ranking. Rista mentions centrally managed item status and automatic material-based stock-outs.
4. Reconcile aggregator payouts
Aggregators pay you later, after commission, ads, discounts and other deductions. Reconciliation means matching each payout to the orders it covers. An independent review places Petpooja's aggregator reconciliation in its operations add-on (DineOpen). Without it, many kitchens discover their real margin months late.
5. Count packaging as food cost
A ₹250 biryani in a ₹22 container with a ₹4 bag, ₹3 cutlery pack and a ₹2 sticker has ₹31 of packaging. That's 12% of the price before a single grain of rice. Add packaging to your recipes so it shows up in plate cost. Our food cost calculator lets you add it as an ingredient line.
6. Report by brand and channel
You need to know which brand, on which app, at which time, actually makes money after commission. Brand-level and channel-level reports are essential.
The cloud kitchen paradox
You have 4.5 stars on two apps, three brands trending, and a kitchen running flat out. Then the payout arrives. Reconciliation is the reason some cloud kitchens grow and others just get busier.
GST note for cloud kitchens
Food supplied through Swiggy and Zomato has its 5% GST collected and paid by the platform under Section 9(5), since 1 January 2022. You still report these sales. Direct orders (your own website or phone) are taxed by you, typically at 5% without input tax credit (TAXAJ). Your POS should handle both correctly. Confirm with your CA.
Cloud kitchen POS comparison
| Rista by DotPe | UrbanPiper Prime | Petpooja | Ecomeal | |
|---|---|---|---|---|
| Aggregator integration | Two-way | Core strength | Yes | Not yet |
| Multi-brand | Multi-brand invoices | Ask | Yes | Ask in demo |
| Central item on/off | Yes | Ask | Yes | Yes, across POS and QR |
| Reconciliation | Ask | Ask | Reported in add-on | No |
| Brand/channel reports | Channel filters | Channel focus | Reports | Dine-in vs takeaway split |
| Published price | No | No | Rates on request | ₹333/month + GST billed yearly |
Where Ecomeal fits for cloud kitchens
Honestly: if delivery apps are 70% or more of your orders, wait for our aggregator integration or choose one of the systems above. Ecomeal fits hybrid kitchens: a takeaway counter or small dine-in with delivery on the side, where fast counter billing, a synced QR menu, customer segments and AI Up Sell deals for slow dishes earn their keep.
Checklist before you sign
- Aggregator orders auto-accepted and KOT printed, shown live
- Item off in one tap for all brands and apps
- Multi-brand menus and invoices
- Payout reconciliation report, shown with a real payout
- Packaging cost in recipes
- Brand and channel profit report
- Total yearly price including integration fees
The real margin on a delivery order
Here's why reconciliation and packaging matter, using an illustrative ₹400 delivery order. Commission and charges vary by platform, contract and city; use your own payout statements.
| Line | ₹ | Notes |
|---|---|---|
| Menu price | 400 | |
| Discount you funded | −40 | Part of an app offer |
| Platform commission (illustrative 25%) | −90 | On the discounted value |
| Other charges and ads (illustrative) | −20 | Varies a lot |
| Packaging | −30 | Containers, bag, cutlery, stickers |
| Food cost (illustrative 32%) | −115 | On ₹360 |
| What's left for rent, staff, profit | 105 | 26% of menu price |
All numbers illustrative.
A dish that looks healthy at 32% food cost leaves a quarter of the menu price after the platform, packaging and discounts. That's why cloud kitchens need channel-level reporting, and why many push for a share of direct orders.
Direct orders: the margin lever
Direct orders through your own website, WhatsApp or phone skip platform commission. They need:
- A simple ordering link or QR
- A POS that records them as a separate channel
- A way to recognise repeat customers
Ecomeal's customer QR menu is synced with the POS, and its customer screen shows repeat rate, average spend and loyalty tiers, which helps when you're building direct, repeat business alongside aggregators.
A weekly cloud kitchen review
- Orders and revenue by brand and by platform
- Effective deduction % per platform (commission + ads + funded discounts + charges)
- Packaging cost per order
- Cancellations and refunds by brand
- Items switched off most often (stock-outs)
- Slow dishes per brand: drop, rework or promote
Frequently asked questions
Which POS is best for a cloud kitchen in India?
Choose one with strong Swiggy and Zomato integration first. Rista by DotPe, UrbanPiper Prime and Petpooja are common choices.
Do cloud kitchens pay GST on Swiggy and Zomato orders?
The platform collects and pays the 5% GST on food sold through it under Section 9(5). The kitchen still reports those sales. Direct orders are taxed by the kitchen.
Can I run multiple brands on one POS?
Many POS systems support multiple brands with separate menus and invoices from one kitchen. Ask for a live demo with two brands.
Does Ecomeal work for cloud kitchens?
It works for hybrid kitchens with counter or dine-in sales. Swiggy and Zomato integration isn't live yet.
Sources
- NRAI India Food Services Report 2024, summarised by MediaBrief
- Rista POS by DotPe, checked 15 Oct 2026
- Petpooja blog: Top 5 Restaurant POS Software in India
- DineOpen: Petpooja Pricing 2026
- TAXAJ: GST on restaurants (2026)
See it in your Kitchen.
Ecomeal Lite starts at ₹333/month + GST, billed yearly. A short demo on WhatsApp shows you billing, KOTs and AI Up Sell on your own menu.