F&BosA cloud kitchen POS should run several brands from one kitchen, bring Zomato, Swiggy, ONDC and direct orders into one queue, send them to a kitchen display, deduct ingredients and packaging by recipe, and show each dish's margin after commission. Aggregator integration varies by vendor: check whether it's live, which platforms it covers and what it costs.
In a cloud kitchen, the POS is less about the counter and more about the queue, the kitchen and the numbers. For how a POS works generally, see our restaurant POS system guide; for the quick-service counter version, our QSR POS guide.
10 things a cloud kitchen POS needs
| # | Feature | Why it matters |
|---|---|---|
| 1 | Multi-brand menus | Run several virtual brands from one kitchen, each with its own menu and prices. |
| 2 | All orders in one queue | Zomato, Swiggy, ONDC, your own website and phone orders should all reach the same kitchen and stock. |
| 3 | Channel-aware pricing | A dish priced for a direct order can lose money after an 18–30% aggregator commission. |
| 4 | Kitchen display with prep timers | Platforms reward kitchens that hand over on time; timers show where you slow down. |
| 5 | Packing station checks | A checklist and order screen at packing cut missing items and bad ratings. |
| 6 | Recipe inventory, including packaging | Containers, bags and cutlery are a real cost per order, not an overhead. |
| 7 | Margins after commission | Each dish's contribution on each channel, not just its menu price. |
| 8 | Payout reconciliation | Match what platforms owe you with what they actually pay. |
| 9 | Guest data from direct orders | Aggregators keep most customer details; direct orders let you build your own base, with consent. |
| 10 | Multiple kitchens | One dashboard for every kitchen and brand as you expand. |
Aggregator integration: what it does and what to ask
With full integration, Zomato and Swiggy orders arrive in the POS automatically, go straight to the kitchen display, deduct stock and land in your reports. Menu changes and item availability sync to the platforms, so a dish that runs out goes offline everywhere.
Without integration, orders come in on the platform's tablet and staff enter them in the POS. It takes a few seconds per order, but it's the only way your stock, food cost and reports stay accurate. An order that never reaches the POS never deducts its ingredients.
Ask every vendor:
- Is Zomato and Swiggy integration live today, or on the roadmap?
- Does it cover menus and item availability, or only incoming orders?
- Does it cost extra per platform or per outlet?
- Does it support ONDC and my own website orders?
- How are aggregator orders shown for GST, since platforms pay GST on them under Section 9(5)?
Margins after commission: a worked example
The same ₹400 order, through an aggregator at 22% commission and through ONDC at 2–4%. Food and packaging costs are illustrative:
| Aggregator at 22% | ONDC at 2–4% | |
|---|---|---|
| Customer pays | ₹400 | ₹400 |
| Platform commission | 22%: ₹88 | 2–4%: ₹8–16 |
| You receive | ₹312 | ₹384–392 |
| Food cost of the dish | ₹100 | ₹100 |
| Packaging | ₹12 | ₹12 |
| Contribution per order | ₹200 | ₹272–280 |
Same dish, same kitchen, ₹72–80 more per order through the low-commission channel. That's why cloud kitchens price their delivery menus to cover commission and push direct and ONDC orders where they can. For the full P&L, see cloud kitchen profit margins in India, and check your real rate with the Zomato and Swiggy commission calculator.
Running several brands from one kitchen
- Give each brand its own menu, prices and channels.
- Share ingredients and recipes across brands, so stock stays accurate.
- Report each brand's sales, food cost and margin separately, so you know which brands carry the kitchen.
Kitchen display, packing and prep times
A kitchen display shows each order by station with a timer, and records prep times, which affect how platforms rank you. Add a packing station with an order checklist and, for delivery bags, a printed slip. Compare a KDS vs a KOT printer.
Inventory, packaging and food cost
Set up recipes that include packaging: the container, lid, bag and cutlery for each item. With recipe-linked inventory, every order deducts both food and packaging, and weekly variance shows whether portions are drifting. Our guide to the cloud kitchen food cost formula explains the maths.
Growing direct orders
- Offer your own ordering link or WhatsApp ordering in packaging inserts and social posts.
- List on ONDC for lower commission.
- Collect customer details on direct orders, with consent, and reward repeat orders.
Reconciling platform payouts
Platforms deduct commission, promotions, refunds, taxes and fees before paying you. Match every payout against your POS records each month to catch wrong deductions. Our guide to reconciling Zomato and Swiggy payouts walks through it, and the Zomato and Swiggy partner guide covers the platforms.
Frequently asked questions
What is a cloud kitchen POS?
A POS built for delivery-only kitchens: it manages several virtual brands from one kitchen, brings orders from aggregators, ONDC and direct channels into one queue, sends them to a kitchen display, deducts stock and packaging by recipe, and shows margins after platform commission.
Does a cloud kitchen POS integrate with Zomato and Swiggy?
Some do and some don't. With full integration, aggregator orders arrive in the POS automatically and menus and item availability sync. Without it, orders are taken on the platform tablet and entered in the POS manually. Ask every vendor whether integration is live today, which platforms it covers, and what it costs.
How much commission do Zomato and Swiggy charge cloud kitchens?
Base commission typically runs 18–30% of the order value, with promotions adding more during campaigns. On a ₹400 order at 22%, you receive ₹312. ONDC typically costs 2–4%, which is why many cloud kitchens push direct and ONDC orders.
Why do cloud kitchens need recipe-linked inventory?
Margins are thin after commission, so small portioning and packaging leaks matter. Recipe-linked inventory deducts ingredients and packaging for every order and shows the gap between expected and actual use each week.
Can one POS manage several cloud kitchen brands?
Yes, if it supports multi-brand menus. Each brand keeps its own menu, prices and channels, while the kitchen, stock and reports are shared, so you can see whether each brand is profitable on its own.
Related POS guides
QSR POS system
Fast billing for quick service restaurants.
Read the guide → INVENTORYRestaurant POS with inventory
How every bill updates your stock.
Read the guide → CLOUD KITCHENSHow to run a cloud kitchen in India
The complete operating guide.
Read the guide →