Skip to content
RosuiiRosuii

Offline Restaurant Billing: An Internet-Outage Checklist

What to prepare before the outage, what staff can do offline and what to reconcile when the connection returns.

By 3 min read
Share
Offline Restaurant Billing: An Internet-Outage Checklist

Last verified: 2026-09-07

The internet goes down just as your lunch queue grows. The useful question is not whether your POS opens; it is whether each sale can be recovered correctly.

Rosuii’s Windows client stores previously loaded data locally and queues eligible sales and payment records. This checklist separates offline counter work from live server actions, so staff know what to do without making promises the network cannot keep.

Before service: prepare the device

Connect, sign in and select the correct restaurant and branch. Refresh the menu and offline data while the connection is healthy. An empty cache cannot supply menu items that the device has never loaded.

Keep a simple handover note: which till was prepared, who checked it and which printer was tested. If you change menu prices or payment settings, refresh and repeat a small test before the shift. Local data is a snapshot, not a guarantee of the latest server state.

During the outage: separate records from confirmations

For a takeaway cash sale, identify the local order and its payment record together. Do not tell a customer a bKash/Nagad payment succeeded merely because you selected that method. Follow your actual payment-verification procedure.

Do not repeatedly submit an uncertain sale as a new order. The queue uses a stable idempotency key for replay protection, but manually creating another sale is a separate action. Keep the original reference and investigate it first.

TaskCounter rule
Eligible POS saleSave in the local queue and keep its temporary reference.
Payment recordUse the supported recording flow; distinguish it from gateway confirmation.
Kitchen communicationUse an agreed fallback; another device may not receive the order live.
Attendance or order-item editWait for connectivity; these changes require server validation.

After reconnection: reconcile, do not just dismiss the banner

A restored Wi-Fi icon does not prove every request succeeded. The server may reject a change or a session may need attention. Keep unresolved references in the handover record until the issue is explained.

  • Allow the queue to retry.
  • Confirm which temporary references became server orders.
  • Check the amount and payment attached to each sale.
  • Review pending or failed work instead of entering it again.
  • Verify kitchen and delivery follow-up separately.

Internet backup and data backup solve different problems

A mobile hotspot can restore connectivity. It cannot recover unsynchronised sales from a damaged disk. Likewise, locally cached menu data is not a backup of every action on another counter.

Do not clear application storage, uninstall or replace the PC while pending work remains. Plan for power as well as connectivity, and ask support how to recover an affected device before making destructive changes.

Rehearse before the real lunch rush

Use a controlled test account or a documented test sale. Disconnect, create an eligible order, record payment, print, reconnect and verify the server record. Have another cashier explain the pending-work screen.

The drill is successful when the team can identify incomplete work and recover it. A stopwatch alone cannot tell you whether the accounting trail survived.

How we calculated and verified this

Product details were checked against Rosuii’s Flutter client, Windows build configuration and offline queue code on 7 September 2026. These are source-code checks, not independent Windows hardware or printer certifications. No measured time savings, customer counts or universal hardware compatibility are claimed.

Use this checklist with the Rosuii Windows POS demo. Ask your cashier to perform the reconnection checks, not just watch the initial offline sale.

Related guides

See this workflow in Rosuii: Check the Windows app and offline workflow

Sources checked

Start using Rosuii for free

Last updated:

Share

Frequently asked questions

Is everything available offline?
No. Eligible sales and payment records can queue on a prepared device. Initial login, gateway confirmation, live cross-device updates and server-validated changes need connectivity.
What does an offline order number mean?
It is a temporary reference for a locally queued sale. Reconcile it with the server order after synchronisation; do not treat it as proof that the server already accepted the sale.
Can I clear the cache to fix a stuck order?
Do not clear local data while unsynchronised work remains. Keep the order reference and investigate the pending or failed work with support first.

Run your restaurant on Rosuii

POS, menu, inventory, payroll and more — built for Bangladeshi restaurants.

Start free