Peak-hour queue
Lunch and weekend traffic arrives in waves. Too many taps at billing create a queue before the kitchen has even seen the order.
For food-court restaurant operators
Food-court service compresses a restaurant into a busy counter, a pickup point and a kitchen under constant time pressure. Switch on multi-outlet mode and several counters trade on one shared menu: each dish counts as the sales of the outlet whose kitchen cooked it, any counter can take payment for another outlet's dishes, and the panel reports what each outlet earned, collected and owes the others. An outlet is a branch, so it needs Starter or above; Free has one branch and cannot run it. It all sits inside one Rosuii account — separate companies that each keep their own Rosuii account and their own bank settlement are not joined into one bill.
The queue is public, the menu is compact, and every missed handoff is visible to the next customer.
Lunch and weekend traffic arrives in waves. Too many taps at billing create a queue before the kitchen has even seen the order.
A guest pays at whichever counter is free, for a dish the counter next door cooked. At closing the two settle from memory and loose slips, and nobody quite agrees who owes what.
A spoken order number or loose slip can send the wrong bag to the wrong customer when the counter gets crowded.
A small food-court store room leaves little margin for late purchase records or ingredients that disappear without a wastage reason.
Keep the counter fast, let each kitchen print its own work, and let the panel work out what each outlet earned.
Add dishes from any outlet to one bill, with variations and combos priced from the shared menu, and take the whole payment at whichever counter the guest reached. Every line stays attached to the outlet that owns it.
Each dish is routed to a kitchen and counted as the sales of the outlet that owns that kitchen, so the counter that took the money does not take the sale with it. It stays off until you switch it on in Settings → Outlets and map each kitchen to its outlet.
Outlet revenue & collection and Inter-outlet settlement work out what each outlet earned, collected and owes the others from the orders themselves. Recording a payout logs that it happened; it does not move money between payment-method balances.
An order that touches three kitchens becomes three tickets, each carrying only that station's items and no prices, printed on that kitchen's own network printer without anyone pressing print. KDS is available from Starter where a screen suits the station better.
Record suppliers, purchases, production and wastage, then use low-stock alerts before a key item disappears during service. Ingredients come out of one shared inventory, not a separate store per outlet.
Read more:Food court & multi-outlet modeKOT and printingKitchen Display SystemReports, VAT and service charge
Illustrative workflow, not a customer claim
Use a representative order from your real menu. Include one combo, one modifier and one unavailable item. The goal is to expose slow taps and unclear handoffs before rollout.
Last verified against the product:
It depends on who operates the counters. When one business runs several counters, Rosuii's multi-outlet mode runs each counter as an outlet on one shared menu, counts each dish as the sales of the outlet whose kitchen cooked it, and reports what each outlet earned, collected and owes the others. When the counters are separate companies that each keep their own Rosuii account and their own bank settlement, Rosuii does not join them into one bill. Test your exact operating model before choosing.
Yes, once multi-outlet mode is on. One bill can hold dishes from several outlets and any counter can take the whole payment, while every line stays attached to the outlet that owns it. Rosuii does not divide one bill by seat or by item, and it does not transfer or merge tables.
Each dish is routed to a kitchen and counts as the sales of the outlet that owns that kitchen, with a per-dish override where you need one. Outlet revenue & collection and Inter-outlet settlement derive what was earned, collected and owed from the orders themselves, so a cancelled bill drops out on its own. Recording a payout logs that it happened rather than moving money between payment-method balances, and Rosuii does not calculate landlord commission or rent.
Yes. Give each station its printer address in Settings → Kitchens and switch auto print on; when an order reaches the kitchen, that station's ticket prints on its own printer with only its items and no prices. It needs a network ESC/POS printer with its own address — USB and Bluetooth printers are not reached this way — and either the Rosuii Windows or Android app or the Rosuii print agent running at the venue, because a browser cannot open a printer socket. Bengali prints only on a printer that carries a Bengali font, and printer hardware is bought separately.
Eligible POS orders and cash billing can queue on a device that was synced while online, then retry after reconnection. Live KDS, online payments and cross-device updates still need connectivity.
Rosuii starts at ৳0, but an outlet is a branch, so the single branch on Free cannot run multi-outlet mode. Starter ৳500/month allows 2 outlets, Growth ৳1,200/month 3 and Pro ৳2,500/month unlimited, so a five-counter food court needs Pro. Hardware and payment-provider transaction fees are separate.
Test a takeaway ticket and order-ready display with the actual counter and screen. Live CDS updates require connectivity and an eligible plan; cached data is not a shared offline network.
Check Windows POS devices and setupStart free, enter a representative menu and test the counter-to-kitchen handoff with your team.