POS offline selling, shifts, cash control and the outlet dashboard
How BIZA POS keeps selling when the internet drops and posts every sale exactly once when it returns; how shifts, blind counts, X and Z reports, cash movements and cashier PINs keep the drawer honest; and how the live dashboard flags the shifts a manager should look at.
POS offline selling, shifts, cash control and the outlet dashboard
1. Offline selling
Every sale, return, counter open / close and cash movement is first saved on the device, then posted from a queue. If the connection drops mid-shift:
- The billing counter keeps selling from its cached catalog, prices, promotions and lot list; the strip shows Offline and N to send.
- Receipts print immediately with the billing counter's receipt reference; the invoice number is added when the sale reaches the server ("Invoice number follows once this sale is sent").
- When the connection returns the queue drains in order and exactly once: each sale carries an idempotency key, so a retry can never double-post, and a sale can never overtake the shift it belongs to. Two offline sales always produce exactly two invoices.
- Anything the server refuses for a reason a retry cannot fix (a serial number sold elsewhere first, a coupon used up meanwhile) stays visible as needs attention with the reason until a cashier retries or discards it — nothing disappears silently.
Settings: Keep selling offline (off = refuse to sell while offline) and Allow selling below recorded stock (whether an offline sale may exceed the cached stock figure). Returns work offline against the billing counter's copy of the sale; the server caps the refund when it syncs.
2. Shifts (shifts)
| Step | What happens |
|---|---|
| Open counter | Pick the terminal, count the drawer as the opening float. |
| Cash in / out | Anything that moves cash without a sale — float top-up from the safe, a safe drop, a courier fee — with a direction, reason, the drawer account and the counter account. Posts its own numbered journal entry. A mistake is voided with a reversing entry and a reason. |
| X report | The shift so far, any time: sales by tender, discounts, refunds, movements, expected cash. |
| Close counter | A blind count — the expected figure is hidden until the count is entered — then the Z report: float → sales → movements → expected → counted → variance, with notes. |
Require an open counter (recommended for cash businesses): a sale cannot be completed without a session, so no cash ever belongs to nobody. Off, sales still post in full but carry no shift.
3. Cashiers
A cashier is a real user with a POS role. On a shared counter, cashiers switch with a PIN — the next cashier is signed in as themself, so every sale, void and drawer open carries the right name. Five wrong PINs lock the PIN for 15 minutes. Lock counter hides the screen behind the PIN pad without closing the drawer; close the counter only at the end of the shift.
Every permission — discounts, price overrides, refunds, opening and closing counters, cash movements, opening the drawer, settings — is checked by the server, not just hidden in the interface.
4. Events and the audit trail
Line voids (with the value removed), cart voids, no-sale drawer opens (reason required), cashier sign-ins, kiosk assistance and guest QR orders are recorded as events, listed on the X / Z report and counted by the dashboard's attention flags.
5. The outlet dashboard
POS → Dashboard refreshes every 15 seconds, for today, yesterday, 7 or 30 days:
- Outlets — net sales (gross · refunded), sales and units, average basket, open shifts with voids and no-sales; every terminal side by side with its sales, basket, refunds, voids, expected drawer, last sale, online status and current cashier; sales by hour, tender mix and top items.
- Attention — shifts that crossed a threshold you set: cash variance at close, void rate, refund rate, manual discount rate, drawers opened without a sale, price overrides. Each opens the shift.
- Reconciliation — per tender, what the counters reported, what the receivable ledger recorded and what the journal debited, side by side with the status; unposted sales awaiting e-invoice clearance; and every drawer's float → expected → counted → variance.
- Tips — tips by server and by tender, ready to pay out.
You can also ask the BIZA assistant in plain language — "how did counter 2 do today", "which shift had the biggest variance this week".