Service and connectivity: what to check before rollout
Rosuii can queue eligible POS orders offline. Live kitchen screens, online orders and gateway payments have different connectivity requirements. This page separates repository-supported behavior from operating commitments that still need written confirmation.
Code and document review: . This is not a live-service or customer-device test result.
Which workflows need connectivity?
| Workflow | Conditions |
|---|---|
| POS cash-order queue | Prepare a supported device with an online login and required data sync. Eligible cash orders can then remain queued locally during an outage. |
| Reconnection | Queued orders must still pass server permission, plan-limit and data checks. Reconcile orders and payments before clearing browser data. |
| KDS and kitchen updates | Live queues and status changes across devices require connectivity. Full offline kitchen operation is not claimed. |
| Printing | Test your printer model, connection and receipt/KOT output. Offline order queuing does not guarantee offline operation of every printer. |
| Online orders and gateways | Customer storefront orders and bKash/Nagad transaction confirmation require connectivity. |
Support arrangements
Published contact channels are on the contact page and include support@rosuii.com. This repository review did not establish approved fixed support hours, 24/7 coverage or a response-time SLA. Agree your service-hours coverage, printer setup, training and escalation process in writing before rollout.
Uptime and incident history
No publishable uptime measurement series or approved incident-history register was established in this review. No uptime percentage or claim of zero outages is made here.
What a future uptime report should disclose
Before publication, specify the monitored service, probe locations and interval, reporting period, successful-check definition, total checks and missing samples. Disclose treatment of scheduled maintenance and provider/device failures. Sample availability does not describe every user experience; this page does not claim that monitoring has been implemented.
Backup and recovery
An approved backup frequency, retention period, RPO/RTO and restore-test report were not established. A report export is not a complete backup. Obtain written answers about recoverable records, maximum data age, recovery time and who performs the restore.
Pre-rollout acceptance checklist
- Log in and sync a small test menu while online.
- Disconnect, enter a cash order and test printer output and your alternative kitchen-notification procedure.
- Reconnect and reconcile order references, totals and payment reports.
- Keep local data if a sync error remains; give support the error and order reference.
- Get written answers about your plan limits, export needs and recovery requirements.