How offline mode works at events — queuing, conflicts, and the sync panel

Turtini's event-day tools — door check-in, Wallet Charge, and Cash Sales — are built to keep running when the network can't. Here's the shared model behind all three.

Decisions happen on the device:
• Each tool carries what it needs to decide on its own: the check-in scanner pre-downloads the guest manifest, and wallet pay codes carry a signed, tamper-proof balance. So a scan or a charge is approved or refused instantly, with no server round-trip.

Everything is queued, nothing is lost:
• Every check-in, charge, and cash sale is written to the device first and uploaded when a connection returns. You can work through a total dead zone and catch up later — close the app, lose signal, swap to Wi-Fi; the queue survives.

No double-anything:
• Each action carries a unique key, so if it gets sent twice (flaky signal, a retry) the server still only applies it once. Scanning the same ticket twice on one device is caught immediately as a duplicate.

Conflicts are surfaced, never hidden:
• Some clashes can only be found once devices sync up — the same ticket admitted at two offline gates, or a wallet spent past its balance at two booths. Rather than silently pick a winner, these appear as conflicts in the sync panel so a person decides.

The sync panel:
• Every tool has a sync panel (a Sync button, usually showing Online/Offline). Open it to see what's queued, what failed, and any conflicts. You can Retry a failed item, dismiss it, or hit Sync now to push everything immediately.

Drawer totals:
• Wallet Charge and Cash Sales each show a per-device running total — your sales on that phone, including items still waiting to sync — for end-of-shift cash-out.