Sales rung while offline

A till on the desktop app keeps selling when the connection drops. Each sale it rings is stored on that computer and sent to the server once the connection is back, on its own. Nothing is lost if the app is closed in between: the sales stay on the till until they are sent.

Seeing what is waiting

Open Settings›Sync on the till. It has two lists:

• Not yet synced: sales still on this till. When the server can be reached, Send now sends them at once instead of waiting.
• Synced in the last 30 days: sales that reached the server, with when each was rung and when it arrived.

Each sale is marked with one of four states:

• Waiting: still on the till, and it will be sent.
• Needs attention: the server refused it, or sending failed too many times. It stays on the till until it is sent. Retry tries it again. Its details say in words why it is stuck and what to do (see A stuck sale).
• Synced: the server has it, as the till rang it.
• Synced — differs: the server has it, but a figure differs from the till's, shown as till and server for the receipt number, sale time, totals or exchange rate.

A sale's details

Tap a sale to see it whole: its receipt number (with a button to copy it), items, discount, delivery fee, payment, order type and customer. A waiting sale shows its Next try and its Failed attempts. A synced one shows the till's figures beside the server's.

Sale time is when the sale was rung, and the server files it under that time, so an offline sale lands in the right day's takings. Synced is when it arrived.

A stuck sale

Under the server's own message, a stuck sale says what happened:

• Its shift was closed before it arrived. It can no longer go into that drawer by itself. Choose Carry over: a supervisor enters their PIN and a reason, and the sale goes into the shift it was rung in, marked as arrived after close. Its cash was already in that shift's count, so no drawer changes: in the books, the cash settles the overage the close recorded for it. The closed shift's report lists it under Sales that arrived after close, with who approved it and why.
• It belongs to another register's shift. This till was paired to a different register since it was rung. Pair it back to the register the sale was rung on, and it sends.
• The till is not paired to a register. Pair it to the register the sale was rung on.
• The server could not be reached. Check the till is online, then retry.

Closing a shift with sales unsent

A till will not close its shift while it holds sales the server has not had, and says why on the count screen. Each till also tells the server what it holds, so the shift cannot be closed from another device on the same register either: that device is told which till still holds sales, and how many. Bring that till online and they send; a supervisor's PIN can close the shift anyway, and those sales are then carried over as above. A till that has never reported (an older version) does not block a close.

Pairing a till to another register, or unpairing it, warns when it still holds unsent sales: they stay on the till and send only once it is paired back to their register.

Where it applies

Only a till on the desktop app holds sales offline. A browser session has nothing to sync and says so. Some things need the server and are refused offline, such as a sale on a customer's account (see Taking payment).