Prepare ticket control for locations where connectivity is unreliable. Offline operation depends on the app, downloaded data and the synchronisation procedure configured for your installation.
Load the relevant departure and ticket data while the device is connected. Check that the required journey is available on the device before beginning offline control.
The useful question is what information is already on the device. A ticket issued after disconnection or a scan on another offline device may not yet be known locally. Staff need an agreed response for those cases and a reconciliation step when the connection returns. Offline preparation and supported behaviour must be confirmed for the app and installation in use.
A disconnected device cannot immediately receive every later booking change or another device’s scan. Define how staff handle newly issued tickets, amendments and a ticket presented at separate control points.
Synchronise after offline use and check that the central records reflect the work performed. Test a connection loss and recovery on the intended devices before relying on the workflow in service.
Use the iOS app for ticket sales and control, and the Android app for ticket control.
Explore Mobile Ticket Sales & Control
Use ticket scanning to check an issued ticket at the point where it is presented.
Explore Ticket Validation
Connect counter sales, booking corrections and ticket control at the ferry terminal.
Explore Ferry Terminal SoftwareTell us how offline ticket scanning fits into your operation and which part you want to improve. We’ll review the relevant workflow and the scope of your setup with you.
