Check guests in, even with no signal.
Meridian Guide reads the ticket QR with the phone camera, gives the guide a boarding decision on the spot, and writes to the same record the desk is watching. When the signal drops, the scan queues and syncs when it returns.
The headcount at the desk is the headcount on the bus
Every ticket carries a QR code — one document per passenger, ready to hand out or print. The guide points the camera, the app reads it and a boarding decision comes back immediately. Hard rejects stop at the door; the fraud rules accept the guest and raise a flag for the office instead, because arguing with a guest at the coach door is not the guide's job.
The scan is what the rest of the system reads. An active ticket left unscanned on a departure that has already run is a no-show, and that is exactly how the per-departure P&L counts one — a single definition, computed in a single place, so the guide's screen and the margin report cannot disagree.
QR scanning from the camera
The ticket QR is read through the phone camera in the browser — no dedicated scanner hardware, no separate check-in app to install.
Offline-first
A scan taken with no signal is queued with an idempotency key and replayed when the connection returns. The same scan arriving twice is still one scan.
Accept and flag, not block
Hard rejects short-circuit at the door. Everything else is accepted with the flag going to the office as an audit signal, so the coach leaves on time.
One definition of a no-show
The scan record is what the P&L reads to count no-shows, so operations and reporting are reading the same fact rather than two versions of it.
The rest of the operation
See it on your own operation.
No open signup — a short manual review, then a demo populated for your region.