Skip to content

Notifications and alerts

The device raises three kinds of alert, and they want different responses.

An incoming online order plays a sound so a counter nobody is watching still notices:

It plays for 10 seconds.

Switch it on per device, under This device’s settings. A kitchen tablet in a noisy room wants it on; a manager’s tablet on a desk usually does not. It is deliberately long enough to survive a busy pass.

Set it on at least one device that a person can hear. An online order nobody accepts is an order the customer is still waiting on — see Accept or reject an online order.

Notifications collects what happened while you were on another screen — new orders, reservations, and status changes. It is a log, not a queue: clearing it changes nothing about the orders themselves.

These show up on the screens themselves rather than in the notifications list, and each one is telling you to do something before service suffers:

Alert Where What it wants
Low Stock Alerts Dashboard Reorder, or mark the item out of stock
Sync failed Orders Retry the order, or discard it
Open till warning Reports Close the till shift before the day close
Receipt layouts not synced Printing Run Sync menu & device data
Offline banner Register Keep taking orders; they will upload
Another active Hub exists Devices Set one of the two tablets to Solo or Worker
This device has no usable secure keystore App information Nothing urgent — the app works normally

Two of them are worth saying plainly. Offline is not an error — the Register keeps working and offline behaviour explains what is queued. But fiscal venues are different: where fiscalisation is required, orders and payments are blocked while offline, because a receipt that cannot be signed cannot legally be issued.

Fiscalization requires internet. Orders and payments are blocked while offline.

Tap to Pay needs a connection. The Register says so rather than failing at the terminal:

Card Tap-to-Pay needs internet. Use Cash, or record Card to sync later.