Devices and sync exceptions

The fleet of registers and scanners, their backlog, and fixing sync problems.

Transcript

The fleet of registers and scanners, their sync backlog, revoking a lost device, and the exceptions page for sync and card problems.

0:00 Introduction

Your registers and scanners keep working when the internet is down, and send their work to the server when it comes back. In this episode we check on every device, and look at the page where sync problems end up.

0:13 The device list

Scroll the menu on the left and open Devices.

This page lists every register and scanner that has been enrolled. It refreshes by itself every thirty seconds.

The tiles at the top answer four questions. How many devices are online, meaning they reported in during the last two minutes. How many are offline or silent. How many are holding sales that have not reached the server. And how many have been stuck in that state for more than thirty minutes, which is an overdue backlog.

In this store the registers are closed, so they all show as silent. That is normal when a register is switched off or the tablet is asleep.

Each row is a device. You see its status, its name, the app and its version, where it is, and who is signed in. Then the unsynced sales and events still waiting on the device, and when it was last seen.

1:08 One device

Click a device to open its details.

The panel shows when it went offline, when it last synced, who enrolled it and when, and a fingerprint of its key. It also shows what the device itself reports, such as its app version and how many items need attention.

At the bottom is Revoke device. Use it when a register or scanner is lost, stolen, or retired.

The device can no longer upload anything. Its next request is refused, and it has to be enrolled again with a new code. Sales it already sent are kept. We will cancel.

1:46 Enrolling a device

To add a device, tap Enrol a device. It creates a one time code. Choose the kind of device, the outlet and the register. On the device, choose Enrol this device, and type the code. The code works once, and expires after fifteen minutes.

2:03 Sync exceptions

Most of the time, sales sync without any trouble. The Exceptions page is where the rare problems wait for a manager. Open it from the menu.

The first tab is Rejected offline sales. These are sales the register handed over, but the server could not record. You settle each one by hand, and then mark it resolved. Resolved ones are kept on the other button. Nothing is rejected right now.

The second tab is Card refunds. When you void or return a card sale, the card processor has to confirm the refund. Any that it has not confirmed are listed here. Pending ones are retried automatically every minute.

The third tab is Unclaimed card payments. That is a card payment that the processor approved, but no sale claimed, because the register never saved the sale. You either refund the customer, or dismiss it with a note if the sale was recorded another way.

If all three tabs are empty, as they are here, your devices and your payments are in step.

That is the end of reports and controls. In the next episode, we make signing in safer, with two-factor codes for sensitive roles.

See it run your store

Every screen, every flow, recorded from the real product. Watch a sale rung up, a delivery checked in and a store branded in minutes.