Local branch database
Till 1 hosts the branch PostgreSQL database. Additional tills discover it and register.
Cashiers sell at full speed online or offline. Sales sit in a local branch database, and everything replays to HQ and your ERP when the connection returns.
The sequence from the connection dropping to the books catching up.
Cash sales, cash tender, credit-account sales and local stock lookup continue on the branch database.
M-Pesa STK and card terminals wait for the connection. Cash and credit carry on.
Unsigned invoices wait in the offline queue.
Pushes to HQ that fail are queued locally, with retry.
Retries start and fiscal signing resumes.
The outbox replays to HQ and on to the ERP. A screen resolves any master-data conflicts.
Offline behaviour is explicit, so branch managers know what to expect.
Till 1 hosts the branch PostgreSQL database. Additional tills discover it and register.
Failed pushes to HQ are queued locally with retry, then replayed on reconnect.
A screen resolves differences between local and HQ master data.
Run Sync now, a master-data pull or an outbox replay from Settings and operations health.
Yes. Cash sales, cash tender, credit-account sales and local stock lookup continue offline on a local branch database.
No. Sales are stored locally, and failed pushes queue in an outbox that replays on reconnect.
When connectivity returns, the outbox replays to SalesLife HQ, which validates, stages and posts them to your ERP.
M-Pesa STK, card terminals, HQ sync and cloud fiscal signing pause until connectivity returns.
Till 1 hosts the branch database, with encrypted backups and a safe-mode recovery start available.
Book a live demo with a SalesLife retail specialist, or email hello@saleslife.com.