Prepared devices and queued sales
Prepare POS online, keep selling offline, then check every upload
Offline POS saves completed sales in the intended browser and device until they can upload under the same account. It requires preparation while connected. Other administration, inventory and delivery pages still need a connection, and a sale saved on the device is different from a sale already accepted by the server.
See the current packages and allowances before you choose.
What must you do before internet is lost?
Sign in and open the correct POS online on the phone or computer you will use. Wait for Connected ยท offline ready so the account, available catalogue and offline screen are prepared. Reopening offline needs HTTPS or localhost, supported service-worker behavior and persistent browser storage.
A new account or an unprepared device cannot download its first catalogue without internet. On an HTTP LAN address, do not assume offline reopening works; use the supported secure setup and check readiness before disconnecting.
| POS | Before recording sales |
|---|---|
| Distribution POS | Use an allowed administrator/order-taker account and select the permitted customer. |
| Customer POS | Use the shop owner or allowed shop employee account and its own catalogue. |
How do you save a sale while offline?
Select or scan products, check quantities, discounts and the amount received, then use Add sale. Wait for confirmation that the completed sale is saved on the device before entering another one. The cart clears after the local sale is committed; an unfinished cart is not the same as a saved sale and is not restored after reload.
Test before a busy day
Prepare POS, disconnect and save one small trial sale. Check it in On device before continuing.
Keep pending records safe
Do not clear site data, switch to a new browser/device or rely on temporary private browsing while sales still need uploading.
Understand receipt status
A local pending receipt is not a server-issued invoice. Review the accepted invoice after synchronization and test your printer in the intended workflow.
What happens when the connection returns?
Keep POS open under the original account. The queue retries on reconnect, when the tab becomes active and periodically while sales are pending. Use On device to inspect pending/error records and Sync now to request another attempt. If the browser was closed, reopen that account's POS online to resume.
The server checks queued sales and acknowledges successful uploads. Retries keep the same sale reference so a lost response can be reconciled instead of intentionally creating another sale. Check the queue and real invoice before manually re-entering a sale whose upload outcome is uncertain.
What if a sale cannot upload?
Read its On device error. An expired session requires the original account to sign in again. Changed prices can require Use current prices & retry; review the resulting total and balance because the amount originally received remains unchanged. Removed or inaccessible products and other rejected sales need explicit review.
- Download pending-sales data for reconciliation when needed; do not post customer records publicly.
- Do not clear unsynced sales to make an error indicator disappear.
- Offline operation cannot confirm every server-side stock, billing or serial conflict in advance.
- Customer POS and the serial-enabled distribution POS have different serial restrictions; test the correct screen for serialized goods.
When is the offline sale fully reconciled?
Confirm the server accepted the sale, inspect its actual invoice and review any outstanding queue errors. Server business records use upload time while the device-recorded sale time is retained separately. Reconcile that difference when reviewing a day that crossed an offline period.
Your next step
Try the workflow with your own business
Start with a small product list and a trial customer. Check stock, delivery, receiving and any local requirements before a wider rollout.