QR codes and scanning
Offline scanning
Distinguish pending operations from server-confirmed records.
Sign in and load needed data while online first. Offline scanning uses available cached data; it does not automatically cache every record in the organization. Saved moves wait in a device queue owned by that account.
Eligible operations retry when connectivity returns. An expired session requires the same account to sign in; permanent rejection or permission errors may need action. Check sent, pending and rejected states rather than treating queued items as completed. Clearing browser data can delete the local queue.
Contents imports, photo deliveries and persistent count sessions require online saving. Contents product codes are not in the offline cache.