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
Rosuii is food court POS and management software for Bangladesh. Each counter runs as an outlet on one shared menu, a guest pays once at any counter, and the panel reports what each outlet earned, collected and owes the others. It starts on Starter at ৳500 a month for 2 outlets; Growth covers 5 outlets and Pro has no published outlet cap. All outlets sit inside one Rosuii account; separate companies that each keep their own Rosuii account 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. Stock is shared by default; separate outlet balances can be enabled in Settings → Outlets after entering and checking opening quantities.
How Rosuii's food court billing system handles each job, and which jobs it does not do.
| Food court need | How Rosuii handles it |
|---|---|
| One bill for food from several counters | One bill holds dishes from several outlets, and any counter can take the whole payment |
| A central billing counter | One counter can collect for dishes cooked by other outlets; every line stays with the outlet that owns it |
| Sales by counter or vendor | Each dish counts as the sale of the outlet whose kitchen cooked it, with a per-dish override |
| Settlement between vendors at closing | The Outlet revenue & collection and Inter-outlet settlement reports show what each outlet earned, collected and owes; payouts are recorded |
| Payment before cooking | Pay-first can be set per outlet, and the server refuses to send an unpaid order to the kitchen |
| Each kitchen sees only its own ticket | Per-station tickets without prices print on that kitchen's own printer; KDS screens are available |
| An order-ready display for pickup | The customer display (CDS) shows orders being prepared and ready; the order number is the pickup token |
| Stock per counter | Stock is shared by default; separate outlet balances can be switched on |
| Landlord commission or rent | Not calculated by Rosuii |
| Sending money between vendors' banks | Not done by Rosuii; a settlement is a record only |
| Counters with separate Rosuii accounts | Not joined into one bill |
Solutions
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.
| Counters (outlets) | Plan | Monthly | Yearly | Per counter per month, on the yearly price |
|---|---|---|---|---|
| 2 | Starter | ৳500 | ৳3,500 | about ৳146 |
| 3 to 5 | Growth | ৳1,200 | ৳8,400 | ৳140 with 5 counters |
| 6 or more | Pro | ৳2,500 | ৳17,500 | about ৳146 with 10 counters |
The daily order limit is shared by all outlets: 150 orders on Starter, 500 on Growth, and no published cap on Pro. A busy food court should choose its plan by orders a day as well as by counters. There is no setup fee; printers and screens are bought separately.
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. Test the conditions for moving or merging tables in your own demonstration.
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. The printer can be a network ESC/POS printer with its own address, or one attached to the computer running the Rosuii desktop app. Either way the Rosuii app or the Rosuii print agent must be running at the venue, because a browser cannot open a printer socket. Raw ESC/POS text depends on the printer's language/font support; Windows-rendered output uses a different path. Test Bangla names on the selected setup. 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's food court POS starts on Starter at ৳500 a month or ৳3,500 a year, for 2 outlets and 150 orders a day. Growth covers 5 outlets and 500 orders a day for ৳1,200 a month or ৳8,400 a year, and Pro has no published outlet or order cap for ৳2,500 a month or ৳17,500 a year. There is no setup fee; printers and screens are bought separately.
Food court management software runs billing, kitchen tickets and sales reports for several food counters under one roof. It keeps each counter's sales apart and shows who owes whom when one counter takes payment for another. Rosuii does this through multi-outlet mode, from the Starter plan.
When every vendor's counter is set up as an outlet inside one Rosuii account, each dish counts as that vendor's sale and the settlement report shows what each one is owed. Rosuii records payouts but does not move money, and it does not calculate the landlord's commission or rent. Vendors that keep separate Rosuii accounts are not joined into one bill.
Any counter can take the full payment for dishes from other outlets, so one counter can work as the billing counter. The order number is the pickup token, and the customer display shows which orders are being prepared and which are ready. There is no separate token counter per outlet that resets each day.
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.