Overview
Intermittent Wi‑Fi should not stop service. KorePOS Pro stores orders and payments locally when the connection drops, then syncs automatically when you are back online. Understanding offline behaviour helps managers train staff and avoid duplicate charges or lost tickets. KorePOS Lite requires connectivity for live authorisation and does not queue card payments offline.
Before you begin
- KorePOS Pro for offline order and payment queueing
- Latest app version on all POS and handheld devices
- Staff trained not to force-quit the app during sync
Step-by-step
Recognise offline mode
When connectivity is lost, KorePOS Pro shows an offline indicator in the status bar. Orders and payments you take during this period are stored securely on the device. Continue service as normal — totals, modifiers, and table states are preserved locally.
Monitor sync when back online
Once the network returns, KorePOS begins uploading queued transactions automatically. The sync indicator shows progress. Keep devices powered and the app open until sync completes. Large backlogs after a long outage may take several minutes depending on volume.
Avoid interrupting sync
Do not force-quit KorePOS or power off devices while the sync spinner is active. Interrupting sync can leave payments pending in your provider dashboard. If staff must switch devices, wait until sync shows complete on the primary terminal first.
Escalate failed sync
If sync does not complete within 15 minutes of stable connectivity, note the time range and affected device IDs. Email support@korepos.co.uk with your location name — do not attempt to re-charge guests until support confirms whether queued payments posted successfully.
Troubleshooting
- Offline indicator never clears
- Verify Wi‑Fi or cellular data works in a browser on the same device, toggle aeroplane mode off and on, and restart KorePOS. Check router firewall rules if only POS devices are affected.
- Duplicate charges after reconnect
- Stop taking new payments on affected devices, check the payments inbox for duplicate authorisations, and contact support before issuing refunds so records stay aligned.
- Orders missing after sync
- Open table history and closed checks on the primary terminal. If tickets are still missing, support can trace local queue logs using your location ID and timestamp.