Oct 16, 2026 · 4 min read
Most restaurant POS software assumes you have a dining room. Cloud kitchens end up with empty table cards on every screen, table QR codes they will never print, and staff tapping past “Table 1” to find the takeaway counter.
Start with the right venue type
When you sign up, tell BistroBot you run a cloud kitchen. Tables then disappear everywhere — from the floor screen, the new-order screen and the QR codes page — and you work only with takeaway and online orders. If you switch an existing café to cloud kitchen, any open table orders are listed separately so you can still settle them. Cloud kitchen mode is part of the Diner and Gourmet plans.
One queue for every channel
Swiggy, Zomato and your own direct orders should arrive in one list that your team accepts and fires to the kitchen as KOTs, routed to the right station. No tablet per aggregator, no re-keying.
Menus that keep time
- ✓Give lunch and dinner items their own hours so nothing is ordered off-shift
- ✓Switch a whole category off when an ingredient runs out
- ✓Let AI inventory hide items automatically when stock runs out (Gourmet)
Don’t stop when the internet does
An offline hub on a computer in the kitchen keeps orders, KOTs and billing running on the local network during an outage and syncs everything back when the connection returns.
Know which channel pays
Channel and item reports for any date range — downloadable as Excel, PDF or CSV, or scheduled to your inbox — show which platform and which dishes actually make money.