A scan doesn't have to do anything beyond confirming the pass is valid. But often you want it to count - a single-use voucher that burns after one scan, a coupon good for three visits, a membership that scans forever. That behaviour is set per template, in its Scanning section.
The three settings
On a pass template's Scanning section:
- Limit uses (redeem on scan) - the master switch. Turn this on to make scans redeem the pass; leave it off and scanning only checks the customer in.
- Max uses (blank = unlimited) - how many accepted scans the pass allows.
- Minimum seconds between scans (optional) - a throttle against accidental double-scans.
How redemption behaves
With a finite max uses, each accepted scan consumes one use. When a pass hits its cap, PocketPass marks it used - that's the redeemed status - and pushes the change straight to the customer's wallet, so their phone reflects that it's spent. See Pass statuses and lifecycle.
Leave max uses blank and the pass is unlimited: it can always be scanned and never caps out. That's what you want for a membership card, a season pass, or anything a customer presents on every visit.
Redemption and check-in aren't opposites. An unlimited pass still records every scan in the scan log - you just never run out of uses. Turning Limit uses off simply means no scan ever marks the pass spent.
Stopping double-scans
Minimum seconds between scans guards against the same pass being read twice in quick succession - a code scanned as the customer walks up and again as they step through. A re-scan inside that window is rejected as Already used rather than quietly eating a second use.
Set it to a few seconds for a busy entrance. It costs nothing on a pass that's genuinely scanned once.
Overriding per pass
These settings are the template's default, but you can override them on an individual pass. Give one VIP unlimited uses on a template that's otherwise capped at one, or extend a specific customer's voucher - without touching everyone else's.
Undoing a scan
Mistakes happen - a staff member scans the wrong customer, or redeems a pass they shouldn't have. Staff can undo a scan. That:
- refunds the use, so the pass isn't out of pocket, and
- un-voids the pass if that scan was the one that capped it out - flipping it back from
redeemedso the customer can use it again.
Undo is the safety net that makes redemption safe to hand to front-line staff.
Redemption pushes real changes to the customer's wallet. A pass that hits its cap shows as spent on their phone within moments - so decide max uses deliberately before you start issuing, and lean on undo rather than editing statuses by hand when a scan was a mistake.
Where to go next
- The scan log - see every scan and its result.
- Pass statuses and lifecycle - where
redeemedsits. - Pass templates overview - where the Scanning section lives.