Handle an internet drop

Every order rung up at the POS is sent to the server there and then, and there is no queue of orders on the device. So if the branch loses its connection, selling at the POS stops until the connection comes back.

What survives#

• The cart: saved on the device for 12 hours, so it isn't lost if the page reloads or closes.
• Held orders: saved on the server, so they aren't lost if the device fails.
• An order being sent: the POS retries on its own three times over about 4 seconds; if that fails, an error message appears.
• The kitchen display: shows Disconnected, reconnects on its own, then reloads every active order.
• The POS app on iPad or Android: if the page can't load, it shows a retry screen and reloads on its own when the network returns.

Retry without a duplicate order#

1. 01

   Step 1: Leave the cart as it is

   Don't change the items, quantities or payment method.

2. 02

   Step 2: Tap Confirm payment again

   Once the connection is back, tap Confirm payment. Even after a page reload, and within 15 minutes, the POS re-sends the same order under the same key: if the server already created it, it answers with that order and doesn't create a second one.

3. 03

   Step 3: Check Orders if in doubt

   Open Orders and check the latest orders before ringing the order up again from scratch.

Other screens#

• Clock needs a connection too; punches are not stored on the device.
• Printing runs over the branch's local network, not the internet, but it comes after the order is created. If the printer doesn't answer, the print dialog opens instead.
• Receiving deliveries is the one exception: marking a delivery arrived, counting it and commenting are saved on the device and sent by themselves, under your name, when the connection is back — see Inventory transfers.
• On Saudi accounts: if ZATCA itself can't be reached, simplified invoices are still signed and printed, and reported when it is back. This is about the connection to ZATCA, not the POS's own connection.