A no-show never enters the loyalty program in the first place
A barbershop handles a walk-in no-show simply by not scanning anything, because Waya only counts a visit when a staff member scans the customer’s card — there’s no booking integration to reconcile against, so a client who books and never arrives leaves zero trace in the loyalty data. That’s the correct behavior, not a gap to patch.
This matters because many shops that also take appointments alongside walk-ins assume their booking software and their loyalty numbers should match up. They won’t, and they don’t need to — the two systems are tracking different things. Bookings track intent to arrive; Waya tracks who actually got a stamp.
Where the confusion actually comes from
The worry usually starts when a merchant compares a booking list to the Waya dashboard and finds fewer enrolled or active customers than expected. The gap is nearly always no-shows, cancellations, or walk-ins who never made it to the front desk to scan — not a data-sync issue, because there is no data sync between a booking tool and Waya.
- A booked client who never shows generates no stamp, no message, no dashboard entry
- A walk-in who’s turned away for a full queue also generates nothing, correctly
- Only a completed, scanned visit ever enters the loyalty data
- There is no POS or till integration to reconcile against, by design
Before and after: stop reconciling two systems that were never meant to match
One shop spent weeks trying to explain a gap between its appointment book and its Waya enrollment count before realizing the two numbers were never supposed to agree.
| Before | After | |
|---|---|---|
| Weekly reconciliation effort | Manually comparing bookings to Waya enrollments | Stopped — treated as unrelated systems |
| Source of loyalty truth | Assumed to be the appointment book | Correctly treated as the scan log only |
| Win-back trigger targeting | Manually excluded no-shows (incorrectly) | Left alone — it already only reads scans |
Let the win-back trigger do its actual job
Waya’s win-back trigger fires after 14 days of inactivity based purely on the last scanned visit, checked daily with a 30-day dedupe. It has no concept of a booking or a no-show, and it doesn’t need one — a client who genuinely hasn’t been scanned in 14 days is exactly who the trigger is designed to reach, regardless of how many appointments they may or may not have missed.
A short, direct message works well here: "Haven’t seen you in a couple of weeks — your chair’s ready."
Set up the program without waiting on booking data
Because loyalty and bookings are unrelated in Waya, there’s no setup step that depends on your appointment system at all — every shop, walk-in-only or hybrid, follows the same steps.
- Build the stamp card
Pick a 6-stamp threshold matched to uniform per-cut pricing.
- Print the QR poster
Place it at the counter, independent of any booking flow.
- Scan only completed visits
A no-show or a turned-away walk-in never gets scanned — that is correct.
- Turn on welcome and win-back
Both fire off actual scan history, unaffected by booking data.
Waya’s limits worth knowing here
There’s no POS or till integration and no way to import a booking system’s no-show list, since a stamp only exists when a staff member scans the card on an ordinary phone. There’s also no SMS — wallet lock-screen messages only — and the Android merchant app is in closed testing. Handling customer data correctly still matters even without a booking sync, so review Saudi PDPL rules on customer data if you’re combining sources at all.
If you're setting this up for the first time rather than fixing an existing mix-up, the barbershop launch guide covers the full week-one sequence, booking system or not.
Frequently asked questions
How does a barbershop handle loyalty when walk-in clients do not show?
It doesn’t need to handle it specially — Waya only records a visit when a staff member scans the card, so a no-show never enters the loyalty program at all. There’s no booking integration to reconcile, so the two systems simply track different things by design.
Why don’t my booking numbers match my Waya enrollment numbers?
They are not meant to match. Bookings track intent to arrive; Waya only counts a scanned, completed visit. No-shows, cancellations, and turned-away walk-ins all show up as zero in Waya, which is expected.
Does the win-back trigger need to exclude no-shows manually?
No configuration is needed — the 14-day win-back trigger only reads actual scan history, so it never counted no-shows in the first place. It fires purely off the last time a customer was scanned.
Can I import my booking system's no-show list into Waya?
There’s no integration for that, and no bulk import either — Waya has none on any plan. A no-show list has no meaningful use inside the loyalty program anyway, since a no-show never generates a stamp to begin with.
Does a turned-away walk-in count against my loyalty numbers?
No. A walk-in who leaves without being seen never gets scanned, so nothing about them is recorded — the same as a no-show. Only a completed, scanned visit enters the loyalty data.