pass.qrtick.com/presentation
Platform overview
Physical access,member-ready
QRTick Pass (Member Access OS) ties together digital and physical credentials: staff run the gym from the cloud, members use passes and tags at the door, and readers can operate attended or unattended—without ripping out your existing billing story.
What you get
One platform for operators who need reliable check-in, clear audit trails, and optional wallet-grade experiences—without a bespoke hardware project on day one.
Authoritative access
Passes, NFC tags, and entry logs stay aligned with your facility roster and policies.
Readers that scale
From a simple USB wedge at the desk to Pi-class readers and wallet tap—same data model.
Staff & member UX
Portal for operators, member flows for join and wallet, and staff views where you need eyes on the gate.
Audit-friendly
Entry events and hardware signals support compliance conversations and day-two operations.
Groups & institutions
Bulk groups, leads, and facility-scoped roles map to how real gyms and venues run.
API-first ingest
Structured gate ingest lets devices post taps; the portal remains the coordination layer.
How it fits together
Think in three layers: cloud control plane, gate edge, and member credentials—all sharing one source of truth per facility.
- 01
Cloud — QRTick Pass
Facilities, members, passes, billing-adjacent configuration, reporting.
- 02
Edge — readers & optional Pi
NFC/VAS ingest, Shelly-style unlock when configured, local staff dashboards where deployed.
- 03
Credential — wallet + tags
Apple / Google Wallet and physical UIDs converge on the same roster rules.
Where people live in the product
Operators & staff
Portal administration, memberships, approvals, access points, gate modes, and exports—typically behind sign-in at your branded host.
Open dashboardMembers & guests
Facility directories, join flows, uploads where required, and wallet passes—all scoped to each venue's policy.
Routed from your public facility links
Live-ish demos
These illustrate principles; production decisions still run through your configured APIs and env secrets.
Ready to operationalize?
Stand up a facility, attach readers using the ingest contract, then tune gate modes for how your desk actually works.