Why we publish Rosuii's limitations
A useful demonstration should show where a workflow stops as clearly as where it starts. These three Rosuii examples explain why we put limitations beside capabilities.
Last verified: 2026-10-13
A restaurant buys a working shift, not a feature name. If “delivery integration” means the cashier must re-enter an order, or “refund” only means cancelling its status, the difference matters during service. A buyer should prefer a vendor that explains those boundaries before payment.
That is why we publish Rosuii's limitations beside its capabilities. Clear wording helps you decide whether the software fits your team, which plan to test and which tasks still need another process. It does not make this vendor-authored article an independent assessment.
Three distinctions that change a buying decision
Recording a marketplace order is not importing it
Rosuii lets staff record marketplace orders and tag the source on Starter and Pro; this tagging is not enabled on Growth. It has no production API connection that automatically imports Foodpanda, Pathao or other marketplace orders. A restaurant expecting orders to appear without staff entry needs to know that before planning its counter workload.
Use the delivery workflow and its limits to separate your own rider management from a marketplace connector.
Cancelling an order is not a controlled refund workflow
Rosuii supports cancellation and reverses configured recipe deductions and loyalty points when an order is cancelled. It does not provide a void, complimentary-item or refund workflow with reason codes, manager PIN approval and a refund-ledger entry. Changing an order's status does not establish that money was returned to a guest.
Before switching, show your team the POS controls and agree how it will approve and document a real refund. If those controls are essential, include them in your acceptance decision.
An export is not an accounting connector
Reports can export to CSV on Growth and Pro. Rosuii does not have an accounting-software connector. Your accountant must still check the export, mapping and reconciliation process; downloading a file does not mean another accounting system has received or accepted it.
Read the reporting scope and try a sample file with the person responsible for your books.
Ask for evidence that matches the claim
In a demonstration, ask: who performs this step, on which plan, using which device, and what happens when it fails? Keep one sample order, receipt and report so the team can compare the same workflow across vendors. A published description is a starting point, not proof that your printer, connection or merchant account is ready.
Our public storefront examples are not testimonials or measured outcomes; no approved case study is currently published. We will not turn a live menu into a claim that its restaurant saved time or increased revenue.
Start with the current plans and first-year cost calculator, then ask for a demonstration of your own service workflow. A limitation may be acceptable with a clear process—or a reason to choose something else. You should be able to make that decision before paying.
How we calculated and verified this
Rosuii publishes this editorial about its own product. We reviewed the approved product claims and linked feature conditions on 13 October 2026. This is not an independent review or a new production test.
Read next
See this workflow in Rosuii: Check Rosuii's capabilities and conditions
Sources checked
Last updated:
By Rosuii Team · Published by Rosuii, the software provider. · About the authors
Run your restaurant on Rosuii
POS, menu, inventory, payroll and more — built for Bangladeshi restaurants.
Start free
