Keeps selling offline
Sales, orders and advance payments are stored on the device and synced with retries and a lock, so nothing is sent twice.
A dedicated till app: split payments, SIAT invoicing with contingency, kitchen orders and blind cash close with discrepancy detection. If the internet drops, sales are stored on the device and sync on their own without duplicates.
Without MKA
What you’ll measure
Sample indicators with illustrative data. In MKA they are computed live from your operation.
Try it right here
The cashier’s till and the customer display. Add two products, cut the internet and charge anyway: the invoice is issued in contingency and the till keeps selling. When the connection returns, the queue is sent by itself as a package. Press "Watch it run" to see it play by itself.
Try it right here
On the left, the cashier closes her till without seeing the expected amounts: she counts the drawer and declares card and QR. On the right, the supervisor: on close they see the difference per payment method and the issue lands in their queue on its own. "Watch it run" plays it by itself.
Example flow
The terminal is bound to its till; the session starts with its float and its shift target.
Sales targetsBenefits
Sales, orders and advance payments are stored on the device and synced with retries and a lock, so nothing is sent twice.
Invoices issued offline and sent in packages, CUFD alert and the status of each e-invoice.
The cashier counts without seeing the expected amount; the system detects the difference per payment method and sends it to the issues queue.
Cash, card, QR (with its reference), gift card and voucher on the same sale.
Kitchen printing, item annulment and salesperson reassignment.
In load tests it sustained 249 sales per second with 20 branches at once, with no duplicated numbering or stock.
In detail
All-in-One
Data flows between modules on its own: no integrations, no exporting or importing.
The sale is stored on the device and invoicing continues in contingency. When the connection returns it syncs with retries and a lock that prevents sending it twice.
No. The POS records the QR payment with its reference number as another payment method.
More in Omnichannel commerce
In 30 minutes we walk through your real flow: from sale to invoice, from stock to journal entry.