The immediate consequence of a missed scan
When a barber forgets to scan the loyalty card, exactly one thing happens: nothing does. No stamp is added, no automatic message fires, and the customer’s wallet card looks identical to how it looked walking in — the visit simply doesn’t exist as far as the program is concerned.
Waya has no POS or till integration, so there’s no fallback that notices a payment and adds a stamp anyway. A stamp only exists if a staff member scans the customer’s QR on an ordinary phone, using the web dashboard or the Waya iOS app. Skip that one action and the visit is invisible to the loyalty program, even though it happened and was paid for.
Why a single missed scan snowballs
One missed scan rarely stays a single incident, because the customer has no way of knowing it happened — the card doesn’t show an error, it just doesn’t update. A client counting on their own memory ('I think I’m on stamp 4') will eventually disagree with the barber’s count, and the shop has no record to settle it, since the visit was never logged.
The trust cost is bigger than the missing stamp. A customer who feels shortchanged once on a loyalty count often disengages from the whole card rather than raising it — they just quietly stop mentioning it.
- No stamp recorded for the visit, even though it was paid for
- No welcome, stamp, or reward message fires, since those triggers key off the scan
- No record to resolve a disagreement over the customer’s stamp count
- The gap compounds silently — nothing flags a missed scan on its own
Before and after: a 3-chair shop over one month
One 3-chair shop tracked its scan rate against its ticket count for a month before and after making scanning a required checkout step rather than an optional one.
| Metric | Before | After |
|---|---|---|
| Tickets closed per week | ~180 | ~180 |
| Cards scanned per week | ~145 (≈80%) | ~176 (≈98%) |
| Customer disputes over stamp count | 4 in the month | 0 in the following month |
The fix: attach the scan to the ticket, not to memory
The fix is procedural, not technical: make scanning the last step of closing a ticket, done by whoever takes payment, every single time, rather than an extra step someone remembers when the shop is quiet. Give every chair barber the Cashier staff role from the staff accounts screen — it lets them add or deduct stamps and points directly — so nobody has to hand the phone to one designated person while a queue builds.
- Assign Cashier to every barber
Every chair should be able to scan, not just the till.
- Scan before handing back change
Make the scan the literal last motion of the transaction.
- Say the stamp count out loud
This catches a missed scan immediately, in front of the customer.
- Check the dashboard weekly
Compare scanned cards to tickets closed; a gap means a habit slipped.
A missed scan is not the same as a lapsed customer
It’s worth separating a missed scan from an actual lapsed customer, because the fix is completely different. A missed scan is a staff-side gap that shows up as a customer who seems inactive despite having visited. A genuinely lapsed customer hasn’t visited at all, which is what the 14-day win-back trigger is built to catch — checked daily, with a 30-day dedupe.
If your win-back messages are firing for people who insist they were just in the shop, the scan is the problem, not the trigger.
Plan around the Free plan while you fix the habit
Fixing a scanning habit costs nothing to test — Free is 0 SAR forever, no credit card, up to 100 customers and 100 messages a month, enough to run the before/after comparison above on a single chair before deciding whether to add branches or staff on Growth.
Frequently asked questions
What happens when a barber forgets to scan the loyalty card?
Nothing gets recorded — no stamp is added and no automatic message fires, because Waya has no POS or till integration and relies entirely on a staff member scanning the card. The visit happened and was paid for, but the loyalty program has no way to know that on its own.
Can a missed stamp be added later?
Yes — a Cashier or Branch Manager can add a stamp manually from the dashboard once the miss is noticed, but the fix that actually matters is making the scan a required last step of checkout so misses stop happening.
Why did our shop’s scan rate drop to about 80%?
Usually because scanning was treated as an optional extra step rather than part of closing the ticket. Attaching the scan to the payment motion itself, and giving every chair barber the Cashier role, is what raised one shop from roughly 80% to 98% scanned.
How do I tell a missed scan from a genuinely lapsed customer?
If a customer disputes a win-back message and says they were just in, that points to a missed scan on that visit, not a misfiring trigger. The 14-day win-back trigger only fires off actual scan history, so a gap in scanning looks identical to inactivity from the outside.
Does Waya flag a missed scan automatically?
No — there is no built-in alert for a skipped scan. The dashboard shows scans and enrollments, so a weekly comparison against tickets closed is the practical way to spot a gap before it becomes a pattern.