StoreCashierDocumentation Free 1.6.6 Pro 1.5.6 Apps 1.5.0

Sync & the outbox PRO APP

Every sale and cash-register event made in the app goes into the outbox on the device and is uploaded to your website one at a time, in the order it was made. Nothing is uploaded twice and nothing leaves the device before the site confirms it. The Pending / Sync screen shows the queue, the problems and a log. This page explains every status, button and timing.

Where: the app → Pending / Sync (cloud icon) · tap the ONLINE / OFFLINE pill · Alt+S = Sync now
Pending sync screen offline: status OFFLINE, 4 waiting, queue with three sales and one cash-out event marked WAITING
Offline: three sales and a cash-out wait in the queue, in the order they were made.

The Pending / Sync screen#

PartWhat it shows
StatusONLINE, SYNCING or OFFLINE.
Waiting to uploadSales and register events in the outbox.
Sync issuesRejected items that need a manager.
Last sale synced / Data refreshedLast confirmed upload; last download of changes from the site.
Sync nowUpload now and refresh data.
Queue (n)Each waiting item: local number, badges, time, customer, number of lines, attempts, last error, total. Buttons: print, delete (unsynced sales only). Register events show “Cash out”, “Register open”…
Sync issues (n)Rejected sales with the server’s reason, Retry and delete. See Sync issues.
Synced but flagged for reviewSales the site saved but flagged (oversold, total differs, serial, plan renewal).
Cash register – flagged by the serverRegister events applied with a remark, with Mark as seen.
Sync logLast events: back online, “Sale D3-000002 synced as invoice INV-1002”, rejections, upload pauses…

Item statuses#

BadgeMeaning
WAITINGIn the outbox, not uploaded yet (offline, or waiting its turn).
UPLOADINGBeing sent now.
ERROR – RETRYINGThe site answered with a temporary error; the app retries with growing pauses (5 s up to 10 min) without blocking later sales.
WAITING FOR THE SERVERRegister close waiting until earlier items of the session arrived on the site (re-sent every 20 s).
OFFLINEThe sale was completed while offline.
SYNCEDConfirmed by the site; the invoice number is shown.
SYNCED – REVIEWSaved, but flagged for a manager.
REJECTEDThe site cannot accept it; it stays on the device under Sync issues.

The rules (why sync is safe)#

  • Order: uploads strictly oldest first, one at a time. Register open → sales → cash moves → close arrive in the right order.
  • Exactly once: each sale carries a unique id. If an answer is lost (Wi-Fi drop during upload), the app sends the same sale again and the site returns the first result — never a second order.
  • Removed only after confirmation: a sale leaves the outbox only when the site answered “synced” or “needs review”. It then moves to the sales history (last 500 kept).
  • Network error: the run stops and continues when the connection is back.
  • Server busy (same sale being saved): retry after 5 s.
  • Refusal: status REJECTED, kept on the device. Rejected items are never deleted automatically.
  • License or version problems (device license, app older than the site’s minimum version, Pro license inactive): uploads pause, a banner explains why, sales stay waiting.
  • Revoked device: the app locks and asks for a new pairing code; the outbox is kept and uploads after pairing again (the queued sales are re-attributed to the new pairing).

Timing#

WhatWhen
Connection checkEvery 15 s (5 s timeout + one longer confirmation)
Upload of a new saleImmediately when online
Download of changes (prices, stock, products, customers, settings)Every 60 s, and on Sync now
Offline retry5 → 10 → 20 → 40 → 60 s
Upload timeout90 s (then retried with the same id)
Full re-downloadWhen the site asks for it (data older than 30 days, very many changes), or Settings → Re-download all data. The outbox is always kept.

After the connection returns#

Pending sync screen online: queue empty, one rejected sale with Retry, one synced sale flagged oversold_offline, sync log
Back online: two sales synced, one rejected (product deleted on the site), one flagged because stock ran out offline.

The log shows each result. In the example above D3-000002 became INV-1002, D3-000004 became INV-1003 but is flagged oversold_offline, and D3-000003 was rejected because its product no longer exists on the site. What to do with each: Sync issues & fixes.

Deleting an unsynced sale#

Use the red bin on a waiting or rejected sale only when the sale did not really happen (cancelled and money returned). The app asks:

Sale D3-000003 ($5.50) has NOT reached the server. Deleting it removes it permanently from this device and puts its stock back. Only do this if the sale did not really happen (e.g. it was cancelled and the money returned). This cannot be undone.
  • Online, the app first asks the site whether it already has the sale and refuses if so (“The server already has this sale – it cannot be deleted. Syncing…”).
  • Synced sales can never be deleted in the app (“Synced sales cannot be deleted from the app.”) — use a return or the website.
  • A sale that was part of an offline register session is taken out of the queued closing too, so the server does not wait for it.
  • A card payment that was approved for the deleted sale becomes available again under Approved card payments not used yet.
A sale shows “3 attempt(s)” and an error.

Read the error under it. Temporary errors retry by themselves. License or version messages need the fix shown in the banner. A rejected sale needs a manager (Sync issues).

Can I make the app upload faster?

Press Sync now. Uploads already start immediately when online.

Why does the stock on the site differ from the app for a moment?

The app subtracts sales that are still waiting. After upload and the next refresh both agree.