Unsynced and refused work
The POS saves every bill on the device first and sends it to the cloud after. The amber 3 unsynced chip for work still on its way, the red 1 refused chip for work the cloud will not take, the list The cloud refused this work with Leave it and I have dealt with it, a bill the cloud refused, and work kept while the restaurant is suspended. On the Windows and the Android POS.
On this page
Every POS is local first. A bill, a dish, a discount, a payment, a shift: each is written to this POS's own storage the moment you press the button, and sent to the cloud after, in the order it happened. Nothing waits for the internet, and nothing is lost when it drops.
Two chips at the top of the table screen say how the sending is going:
- 3 unsynced, in amber: work still on its way to the cloud. It goes by itself.
- 1 refused, in red: work the cloud refused and will not take again. Someone has to look at it.
The two chips
- 3 unsynced, amber: how many changes made on this POS have not reached the cloud yet. Rest the pointer on it (Windows): Bills taken on this POS that have not reached the cloud. Tap it to send them now. It counts down as they go, and is gone at nought.
- 1 refused, red: how much work the cloud refused outright. Rest the pointer on it: Work the cloud refused. It will not retry. Tap it for the list. It does not go away by itself.
- 🔄 Refresh: does the same as a tap on 3 unsynced: the waiting work goes first, then the newest menu and settings come down.
A chip of 1 unsynced for a moment after each sale is normal: it is the sale on its way. It stays up while the internet is down, and goes down once the line is back.
Work still on its way
While work is unsynced, the POS goes on as normal. It also says so in a few other places:
| Where | What it says |
|---|---|
| The Paid screen, after a payment | Saved on this POS in amber instead of Paid, with Saved on this POS. It will reach the cloud when the connection returns. See Paid, or Saved on this POS. |
| The bill's summary | pending beside a row this POS worked out and the cloud has not confirmed yet. |
| Exit POS | 3 changes rung on this POS have not reached the cloud yet. They are kept safely on this POS and go to the cloud the next time it is opened. With nothing waiting: Everything rung on this POS has reached the cloud. |
Closing the POS, or the PC going off, loses nothing: the work is on this POS and goes the next time it is opened. See What works without the internet.
Work the cloud refused
Tap 1 refused. The list opens.
- The cloud refused this work, on red, with It is not queued and will not retry. Anything here has to be redone. under it.
- What it was, in plain words: A bill could not be opened, An item could not be added, A payment could not be recorded, A table could not be cleared, A bill split on this POS could not be made on the cloud, so the new bill is finished on this POS, and so on.
- Why: the cloud's own sentence, as it sent it. With none: No reason given. A refund made on this POS says Refund R0005 of bill SO-0412, RM 12.00: the cloud did not accept it. and the reason; a clock in or out names who and when.
- When it was done on this POS.
- Leave it: closes the list. The red chip stays, for a manager to see.
- I have dealt with it: in red. Marks everything on the list as dealt with, and the chip goes. The record is kept on this POS; nothing is deleted.
- Read each row: what was refused, and why.
- Redo what has to be redone: ring the bill again, record the payment in the back office, tell the owner. See The cloud refused a bill or a payment.
- Press I have dealt with it.
A refused row never holds up the rest. Work behind it goes on to the cloud.
The list is the same, with its first ten rows, and Leave it and I have dealt with it (in red) as two text buttons at its foot.
A bill the cloud refused
A bill opens on this POS at once and is told to the cloud behind your back. If the cloud refuses the bill itself, it is marked dead, plainly, so nobody goes on serving it:
- The cloud refused this bill, the cloud's reason under it, then Nothing more can go on it. Go back and start a new one. No dish can be added to it, and nothing on it is sent.
Back on the table screen the reason is said again, with OK. The refused bill is listed under 1 refused too.
When a new bill at a table is refused because a party was seated there on the cloud since this POS last heard, the POS opens that party's bill instead of saying the refusal.
Kept, not refused: when the cloud refuses the restaurant
When the restaurant is suspended or its subscription has lapsed, the cloud takes no work from it. That is not a refusal: the work is kept on this POS, and an amber banner over the tables says so, for example:
The cloud is not taking work from this restaurant just now (Your subscription has expired. Reports remain available). 3 bills are kept safe on this POS and will be sent when the restaurant is active again. Nothing has been lost.
It all goes, in order, once the restaurant is active again.