Delivery-only kitchens run on channels, not tables | HelloBooks POS A delivery-first POS for cloud and ghost kitchens: every Swiggy, Zomato and own-website order lands in one queue, fires to the kitchen with a prep timer, and settles with the aggregator commission split out — so each brand and each channel shows its true margin.
Delivery-only kitchens run on channels, not tables
A delivery-first POS for cloud and ghost kitchens: every Swiggy, Zomato and own-website order lands in one queue, fires to the kitchen with a prep timer, and settles with the aggregator commission split out — so each brand and each channel shows its true margin.
Part of HelloBooks POS · Industry verticals
A ghost kitchen has no counter and no dining room — its entire economics live in the delivery channels. HelloBooks ships a delivery-only layout built for exactly that: multiple virtual brands out of one kitchen, every aggregator order in a single inbox, a per-order prep timer that protects your rider-wait SLA, and commission accounted for at the moment of settle. Because it sits on the HelloBooks accounting engine, each order is a real journal and each brand is a real P&L — no spreadsheet reconciliation of Swiggy payouts at month-end.
1
Queue for every channel
Multi
Brands per kitchen
Auto
Commission split at settle
0
Dine-in overhead
Every detail, dialled in
Built for the till, validated against the canonical accounting engine — so every POS sale closes the books cleanly.
Every channel in one queue
Swiggy, Zomato and your own website orders drop into a single order inbox and fire to the kitchen the moment they arrive. No stack of aggregator tablets, no order re-keyed by hand, no missed ticket during the dinner rush.
- Swiggy + Zomato + own-website in one inbox
- Auto-fire to the Kitchen Display System
- Channel tag on every order
- Multiple virtual brands from one kitchen
Prep timer that protects the SLA
Delivery is a clock game — the rider is already on the way. Each order carries a prep timer so the kitchen always knows what is due next and what is running late, keeping rider-wait and food-ready times inside the aggregator SLA.
- Per-order prep countdown
- Colour-coded ageing on the KDS
- Ready-state pushed back to the channel
- Late-order visibility for the expo
Commission split, margin per brand
At settle, the aggregator commission is broken out from net revenue automatically. Combined with recipe-level ingredient draw-down, you see real contribution margin per brand and per channel — not the gross the customer paid.
- Commission separated at settle
- Recipe-level food cost per item
- P&L per virtual brand
- Swiggy vs Zomato vs direct margin
Why teams move off legacy tills
- One tablet per aggregator, orders re-keyed
- All brands blended into one revenue line
- Commission reconciled at month-end
- No view of prep time vs rider wait
- All channels in one auto-fired queue
- A real P&L per virtual brand
- Commission split at the moment of settle
- Prep timers on every order
Questions, answered
Can I run multiple brands out of one cloud kitchen?
Yes. A single kitchen can operate several virtual brands, each with its own menu and its own P&L, while the line works one unified order queue.
Do Swiggy and Zomato orders come in automatically?
They land in the same order inbox and fire to the kitchen like any other ticket, so your team stops re-keying orders off separate aggregator tablets.
How do I see true margin when aggregators take a cut?
Commission is split from net revenue at settle, and recipe-level ingredient draw-down gives food cost, so you get real contribution margin per brand and per channel rather than gross sales.
Is there any dine-in overhead I do not need?
No. The layout is delivery-first — no table map or floor plan to configure. You set up channels, menus and brands, and start taking orders.
Ready to automate your books?
Let AI handle the bookkeeping and reclaim hours every month. Get started free — no credit card required.