QR operations layer
One scan.The whole context.
A QR code in Rhlah is not a link to a page. It is a signed pointer to a record, and what it shows depends on who scanned it and what they are permitted to know.
- Travellers assigned
- Documents complete
- Payment schedule met
- Supplier confirmations
- Transport assigned
Capabilities
What this engine doesand what it does not.
Each capability below carries its real status. Anything marked planned is modelled in the platform and not yet operating.
Signed pointers
Tokens are signed and stored as hashes, so a code cannot be forged or read from the database.
Seventeen object types
Pilgrim, group, booking, journey, voucher, resource, task and more resolve through one scanner.
Role-aware resolution
The same code shows an operator, a guide and a pilgrim different, permitted levels of detail.
Atomic actions
Check-in, voucher redemption and single-use claims execute once, with idempotent results.
Recorded scans
Every scan is recorded with its outcome, including refusals and why they happened.
Offline-resilient scanning
Field check-in queues while the network is unavailable and reconciles on reconnect.
Printed badge production
Batch badge and wristband generation for groups is planned, not built.
Connected by design
Nothing here works alone.
This engine is authoritative for its own domain and reads everything else from the engine that owns it.
Operations
Field teams scan to check in pilgrims and confirm resources on the ground.
Sourcing
Meal vouchers are redeemed here, exactly once, against the issuing plan.
Journey
Scans move journey milestones from expected to evidenced.
Identity
Resolution is scoped to the organisation and the scanner's permissions.
Ready to run your business differently?
See how Rhlah can fit your Hajj & Umrah operation.
