OFFLINE POS
An offline POS that saves every sale on the device first, keeps a queue of what still needs sending, and syncs it once the connection is back, without ringing anything up twice.
Table 06The neighborhood café
Sample order #10421 × Espresso₪ 12.00
1 × Fresh mint tea₪ 6.00
1 × Pistachio pastry₪ 18.00
Each operation goes into a local queue on the device before anything else, so a dropped connection never has to stop the order in front of you.
When the connection returns, waiting operations are sent in order. The server checks each one’s ID, so a sale that was already recorded is never applied a second time.
What works offline depends on your devices and setup, and we walk through yours in the demo. Card authorisation and other outside services still need their own connection.
Designed around interrupted connections, busy teams, and the details that make every shift add up.
Operations enter a local queue, so a connection interruption does not have to interrupt the workflow.
Pending operations are sent when connectivity returns. Failed attempts are tracked for retry.
The server checks operation identifiers and returns an existing successful result when an operation is replayed.
The device application stores pending operations in SQLite with their status and retry history. Synchronization processes that queue separately. Offline capabilities depend on the device and setup; we walk through yours in the demo.
The server checks an operation log scoped to the restaurant, device, and operation ID. Previously successful operations return their recorded result instead of applying the business action again. Failed operations can be retried; this is not a promise that every conflict resolves automatically.
Server-side permission checks verify the restaurant scope, then evaluate user-specific or role-based permissions for reading, writing, and deleting resources. This is a product mechanism, not a security certification.
The AI runs in its own function with no access to the database. It sees only what the person asking is allowed to see, its figures come from your reports, and any change it proposes is limited to small menu and printer changes that wait for your confirmation. Each restaurant has a monthly AI allowance and spending cap.
Sales are stored locally for as long as the connection is down and sync when it returns. We check the setup for your devices during the demo.
No. Each operation carries an ID, and the server returns the recorded result for one it has already applied instead of applying it again.
Cash and the till keep working. Card authorisation depends on your card terminal and its own connection.
LET’S MAKE YOUR NEXT SHIFT EASIER
A free, personal demo built around your restaurant. Bring your questions. We’ll bring the Wi-Fi-off moment.