creekpos · Classic Desktop
Offline sales and safe recovery · Classic Desktop
This guide uses fictional training data. Available controls depend on your enabled features, plan and permissions.
Prepared against the tested 13 October 2026 build; check your deployed build before following a new control.
Who can use this
Cashier
Required tools
An offline-capable till or classic local Desktop. Requires the appropriate enabled features and entitlement; this guide does not add plan inclusions.
Before you begin
If a control is absent, check role, branch, enabled features and entitlement. If an order or price changed, refresh and review again. Do not repeat an uncertain financial action with a new request.
Classic Desktop uses local shop storage and can operate without cloud service. Maintain and verify native backups. Cloud-connected till offline queues are a distinct synchronization mechanism; do not overwrite their data with a standalone backup.
Steps
- Confirm whether you are using the classic local program or a cloud-connected till. Their storage and recovery workflows differ.
- In the local program, verify the local data folder and take a backup before maintenance. Work from saved receipts rather than recreating uncertain sales.
- For a cloud till, inspect its queue and replay status after reconnecting; accepted local input is not proof of cloud settlement.
- Verify the original receipt, stock movement and payment before retrying. Do not change request identifiers to bypass a stuck financial operation.
Check the result
Review the saved record and its audit/stock/payment state before continuing. A preview, queued request or accepted send is not proof of completed delivery or settlement.
Edition differences and limits
Classic Desktop uses local shop storage and can operate without cloud service. Maintain and verify native backups. Cloud-connected till offline queues are a distinct synchronization mechanism; do not overwrite their data with a standalone backup.