Offline POS: What to Test Before You Buy
An offline POS needs to save a sale on the device and recover it when the connection returns. Test the actual trading workflow, including receipts, stock conflicts and register closing.
Define what must work during an outage
List the tasks needed to keep the counter running: selecting products, applying permitted discounts, calculating tax, accepting cash, recording the sale and producing a receipt. Decide which tasks can wait for a connection.
Ask separately about card authorization, gift balances, customer credit and changes to stock. These tasks may depend on information held by a bank or another register. The word offline on a product page does not define those boundaries.
Run an outage rehearsal
Start with a signed in register and a known stock quantity. Disconnect the network, complete two cash sales and close and reopen the application. Check whether the transactions remain available on the same device.
Reconnect and synchronize. Trigger a second synchronization and verify that each sale appears once. Compare the receipts, payment totals and physical stock against the central records. Repeat after an interrupted upload.
| Test | Record the result |
|---|---|
| Application restart during outage | Sales retained and accessible to the authorized user |
| Connection drops during upload | Each receipt has one central transaction |
| Same item sold on two devices | Conflict is identified and can be reviewed |
| Device authorization expires | New offline trading follows the stated policy |
| Cash register closes | All queued sales are accounted for |
Read the documented limits
Loyverse documents offline sales and shift management, locally stored unsynced receipts and synchronization after reconnection. Its offline guide lists restrictions for refunds, customer editing, integrated card terminals and stock visibility.
Use that level of detail when questioning any supplier. Ask for the offline procedure, supported devices and a recovery demonstration with your own items.
Check card processing independently
The sale being saved locally does not confirm a card payment. Ask the payment provider whether the precise reader and integration can collect offline card transactions, when authorization occurs and who bears the risk of a later decline.
Never treat a pending card attempt as settled cash. Staff need to know which payment states permit the goods to leave and how unresolved transactions are handed to the owner.
Current DSDillon POS operation
The deployed DSDillon POS release retains a basket on the device and requires an internet connection to complete sales and save business records. Full offline cash sale processing is under development.
For a business with frequent outages, an offline acceptance test belongs in the implementation contract. Include power backup, device loss, unsynced receipts and a named recovery contact in the operating procedure.
Questions before you decide
Does saving a basket mean the sale was completed offline?
A saved basket preserves selected items. A completed offline sale also needs a receipt reference, payment record, durable storage and a reconciliation process.
Can every cloud POS accept offline card payments?
Support depends on the processor, reader, software integration and operating region. Obtain written confirmation for the proposed setup and test it.
Tell us how your business sells.
Share your business type, locations, currencies, invoice requirements and payment providers. We will scope the workflow, connections and acceptance tests.
