Scans is the record of every time one of your passes was scanned by your team. It's read-only - you don't edit it, you read it - and it answers the questions you actually ask after the fact: who came in, at which door, was their pass still good, and did it count.
Each scan lands here the moment it happens, whichever reader and method produced it.
The columns
| Column | What it tells you |
|---|---|
| Time | When the scan happened |
| Pass | Which customer's pass was scanned |
| Template | The template that pass came from |
| Reader | The reader it was scanned at - your front desk, entrance, etc. |
| Method | How it was scanned |
| Result | What happened |
| Used | Whether this scan consumed a use |
Reader is why setting up readers is worth it - it turns "someone scanned in" into "someone scanned in at the main entrance." See Readers & the Scanner app.
Method
How the pass was read:
QR- the app read the pass's barcode.Tap- the customer tapped their phone (NFC).Manual- a staff member entered or confirmed the scan by hand rather than reading a code.
Result - and what each one means
The result is the outcome of the scan. Anything other than Accepted means the pass wasn't honoured, and the column tells you why:
- Accepted - a valid scan. The pass was good and the customer is in.
- Already used - the pass had already been redeemed, or it was re-scanned too quickly. Common at a busy door where a code gets scanned twice in a second.
- Expired - the pass is past its expiry.
- Cancelled pass - the pass had been voided or deactivated.
- Not active - the pass has been removed from wallets, so there's nothing live to honour.
- Not recognised - the code didn't match any pass in your account. Usually a screenshot of someone else's code, a pass from a different system, or a damaged barcode.
A wall of Already used results at one reader usually isn't fraud - it's double-scanning. A minimum seconds between scans on the template fixes it. See Redemption & usage limits.
Filtering
The log can get long, so you can narrow it by:
- Result - e.g. show only Not recognised to investigate bad codes.
- Method - separate Tap from QR from Manual.
- Template - one product or campaign at a time.
- Reader - a single door or till.
Combine them to answer specific questions, like "every rejected scan at the front desk this weekend."
Scans and webhooks
Every scan also fires a pass.scanned webhook, so your own systems can react in real time - credit a visit, log an entry, trigger a message - without polling this page. The payload carries the pass and the outcome. See Webhooks.
Where to go next
- Readers & the Scanner app - where scans come from.
- Redemption & usage limits - control what a scan does.
- Webhooks - react to scans automatically.