A little help, when you need it

Keep the shift moving.

Installation guidance, connection checks, and a clear way to report a problem with Carry Demo.

Installing on Android

Open the download page on your Android device, download the available APK, and open the file. Follow Android’s installation prompts. Install only the build linked from this site. The download page includes a SHA-256 checksum when one is supplied with the release.

If installation fails, include your Android version, device model, app version, and the exact error when reporting it. Carry Demo is a separate app from a future production release.

Installing on iPhone or iPad

The download page shows a TestFlight or App Store link only when a signed iOS release is available. While Apple signing and distribution are pending, open the web app in your browser to explore the sample workspace.

Connecting to ERPNext

Start with sample data to check that the app opens correctly. To connect your own workspace, you need your ERPNext service URL, valid credentials, appropriate permissions, and the matching Cash & Carry backend extension. Ask your ERPNext administrator to confirm those details and device access to the service. A server running only on a computer’s localhost is not automatically reachable from a phone.

If the app stops or a job is waiting

1. Reopen the app and check the current workspace and connection status.
2. Review the job queue before entering the same operation again. Pending work can be saved locally and may still need to sync.
3. If an operation needs manager review, resolve it in the manager workspace or with your administrator.
4. Before clearing app storage or resetting data, preserve any unsynced work you need. Clearing storage can remove it.

If invoice reading is unavailable

Keep the saved receipt draft and photos. Check your connection and try again later if the service is busy. Native demo devices may need provisioning for Firebase App Check. Use synthetic or sanitized invoice images and review all extracted lines before confirming.

What to include in a report

• The app version, device or browser version, and whether you were using sample data or a connected workspace.
• The job you were doing, the steps that led to the problem, and the exact error text.
• A redacted screenshot if it helps explain the problem.