Use the mobile app and handle a poor connection
The mobile app supports field work such as meter readings. Selected operations can be saved to a local queue when the account and previously loaded data allow it. Offline capture is not proof that the shared platform has accepted an operation.
Reviewed 7 October 2026
Who this is for
Field staff and managers who use the mobile app.
Before you begin
Sign in and open your assigned station while connected before going into an area with poor reception. Keep the app up to date.
1Prepare and work in the field
- Open the mobile app with your own account and confirm the organization and station. Load the information you need while online.
- Use the relevant task screen, for example Start shift, Close shift or a permitted delivery/expense form. Read required fields and units exactly as on the web.
- If a supported form offers offline saving, wait for its local confirmation and note that it is pending synchronization. Do not enter the same operation again on the web.
- Credit sales require an online authorization check. Restore connectivity and obtain authorization before dispensing on credit; a local note is not approval.
- Keep the device and its local data until pending operations have synchronized. Do not uninstall, clear storage or reset the app to fix a queue problem.
You know which records are synchronized and which remain only on the device.
2Reconnect and resolve pending work
- Restore a stable connection and open the app. Allow synchronization to run with the correct account.
- Open More, then Settings, then the synchronization queue and review failed items. Read the cause, such as changed source data, missing permission or a validation conflict.
- Correct or resolve only through the offered controls with your manager when necessary. If a save outcome is uncertain, first search the shared record history to avoid a duplicate.
- Confirm the final shift, delivery, expense or payment in its normal list and inspect its amounts. A disappeared warning alone does not prove the accounting result.
- Escalate unresolved items with operation type, local time and error text. Keep the device data intact until support confirms recovery.
Each field operation is accepted once or remains clearly identified for resolution.
A practical example
A closing reading saved during a network outage is still pending. Once connected, verify the shift is actually closed in the shared list before treating its cash as reconciled.
If something goes wrong
I can view a page offline but cannot submit
A cached page does not mean its action supports offline work. Follow the displayed requirement to reconnect.
A pending item fails after reconnection
Permissions or source data may have changed. Inspect the conflict, preserve evidence and avoid recreating the operation blindly.