Offline point of sale: what should work and what to test
A practical test to distinguish a screen that loads from an operation that actually continues.
Opening an application offline does not prove it can complete a sale. Test the entire flow: catalog, transaction, receipt and synchronization. Exact capabilities depend on configuration and provider.
Define the boundaries
Ask what is stored locally, how long offline operation is supported and which actions require a server. Test browser closure and device restart before relying on offline mode during an outage.
Separate recording from payment authorization
An offline sale does not mean a card terminal can authorize payment. Payment connectivity and provider rules are separate. Define approved collection methods and alternatives.
Run a controlled test
- Sync products and prices before disconnecting.
- Record a sale with test products.
- Check the receipt and change calculation.
- Reconnect and confirm the sale appears once.
- Verify stock movements and payment method.
- Test a repeated submission.
Use a demonstration environment without charging real customers or changing live stock.
Check conflicts between registers
Disconnected registers may sell the same item without seeing each other. Ask how stock discrepancies, price changes and pending sales are reconciled. Offline operation does not provide global real-time availability.
Write a recovery checklist
Assign responsibility, list permitted actions and review pending movements after reconnection. Rehearse with every shift. The test ends when records synchronize and can be reconciled, not merely when the network returns.
Use your cash closing procedure to check the result.
