QR ticket scanning software for controlled operators.
Nox-Tickets is QR ticket scanning software: clear scan outcomes, scanner device approval, offline queuing, and event reporting.
It is shaped for operators who need more than a generic QR scanner app — visible device state, staff roles, and operational reporting rather than a public self-serve ticket marketplace.
Available now and currently running for 1 PaaS client; early enough for direct implementation support and proven enough to run real event operations.
Public list pricing is available on the pricing page; this page describes the QR-scanning workflow in more depth.
Audience
What the product is shaped for
Verified product screenshots
Screenshots from the current Nox-Tickets admin surfaces. These are the same surfaces you would see on the day of the event.
Admin sign-in screen in the current browser surface.
Mobile admin sign-in for scanner operators.Hardware is separate. White-label implementation starts from ₹75,000; unusually large usage is quoted based on the agreed operating scope.
- Rollout scoping and device review (first week)
- Project, ride groups, and device approval (week 2)
- Live event with on-call support (event day)
- Post-event scan outcome review (week 4)
Event scope, devices, and deployment support are confirmed in writing before any rollout invoice.
Process
- Rollout scoping. We review the event scope, expected attendance, gate count, and the device inventory you plan to use.
- Project setup. We configure the project, ride or entry groups, ticket batches, and scanner device approvals before the event.
- Live event. We support the event day with a runbook, on-call coverage, and the operational dashboard for live visibility.
- Post-event review. We review scan outcomes, rejection reasons, device reports, and offline sync so the next event is tighter.
What is and is not in scope
- In scope: QR validation with clear outcomes, scanner device approval, staff roles with ride-group permissions, offline queuing, post-event reporting.
- Out of scope: a generic QR scanner app, public self-serve ticket marketplace, or a universal offline-resilience guarantee before rollout validation.
- Public list pricing applies within the published limits; custom usage, hardware, and implementation are confirmed before onboarding.
Frequently asked questions
Can it detect duplicate scans?
Yes. Duplicate-scan outcomes are part of the product workflow, with clear labels for valid, duplicate, expired, invalid, and wrong-group scans.
Can devices be approved or rejected for scanning?
Yes. Scanner device approval is part of the operational workflow and is configured during rollout scoping.
Does offline scanning queue scans?
Offline queuing is part of the current scope. Conflict handling and reconciliation depend on the device and sync workflow and are tested during rollout onboarding.
Is Nox-Tickets available for public events?
Yes. Nox-Tickets is available now and currently runs for one PaaS client. It is operator infrastructure, not a public ticket marketplace.
What devices can run the scanner?
Nox-Tickets is being tested on supported Android scanner devices. Device registration, approval, Android version, and camera performance are checked during rollout onboarding rather than promised as a universal hardware guarantee.
How does Nox-Tickets handle wrong-group scans?
Wrong-group scans are handled as a distinct outcome with a clear operator message. Staff permissions and ride-group configuration are part of the rollout setup.
Can operators override a scan outcome?
Yes. Supervisor overrides are part of the operational workflow and are recorded in the audit trail so overrides are reviewable.
Book a consultation
Tell us the workflow you run today. We will confirm whether this is a sensible fit and what to do next.