QuickTill guide · 8 min read
Keep branches controlled when connectivity is unreliable.
Offline capability should be defined action by action. A till may continue selected sales locally while some fiscal, administrative or reporting actions still require the server. Managers need to know what is pending and which branch owns each movement.
Define offline behaviour clearly
Document which actions work without connectivity, what data must already be present, and which actions wait for a connection.
- Local product and price availability
- Pending sale and payment identifiers
- Visible synchronisation state
- Rules for fiscal and server-dependent actions
Protect facility-level stock
Each branch transaction should affect the correct facility and remain traceable when it synchronises.
- Store and warehouse assignment
- Branch-aware inventory items
- Controlled inter-facility transfers
- Movement history with user and time
Reconcile after reconnection
Synchronisation is complete only when pending work has a confirmed server result and managers can reconcile sales, stock, cashups and fiscal queues.
- Retry without duplicates
- Resolve rejected records visibly
- Review cashier and payment totals
- Confirm branch and central reports agree
Confirm fiscal, tax, hardware and connectivity requirements against the exact business and deployment. This guide is operational information, not tax or legal advice.