The rule: no scan happens, so no stamp happens
A no-show doesn't need a special rule inside Waya, because the mechanism already handles it correctly: a stamp or point is only ever added when a staff member scans the customer's card, and a no-show never reaches the counter to be scanned. Nothing is credited, and nothing needs to be manually reversed.
The confusion usually comes from booking systems that treat a confirmed appointment as a committed visit before it happens. If a car wash's booking flow shows the appointment as "done" the moment it's scheduled, staff can lose track of which bookings actually turned into a scanned wash.
Keep the two systems separate in your head: the booking calendar tracks intent, the Waya scan tracks the real visit. Only the second one should ever touch a customer's stamp count.
Where car washes actually get this wrong
The mistake isn't usually a customer getting a stamp they shouldn't have — Waya's scan-based model prevents that by design. The mistake is staff manually trying to "make it fair" for a no-show, for example promising a stamp next visit to make up for the missed slot, which creates an informal, undocumented exception nobody else on shift knows about.
- Booking marked "done" before the wash actually happens, confusing staff about what's real
- Staff informally promising make-up stamps that aren't tracked anywhere
- No shared rule for how a rescheduled (not cancelled) booking should be treated
- Confusing a no-show with a customer who showed up but wasn't scanned — the second one is the scanning-gap problem, not a no-show issue
A simple written rule removes the ambiguity
One line, agreed by every shift, is enough to stop the informal exceptions.
| Booking outcome | Stamp given? | What staff should do |
|---|---|---|
| Customer no-shows entirely | No | Nothing — no scan, no stamp, no manual note needed |
| Customer reschedules in advance | Only once wash happens | Scan at the new appointment, not the original slot |
| Customer shows up, staff forgets to scan | Should have been yes | This is a scanning gap — fix the habit, don't invent a stamp after the fact |
Put the rule in place in one short conversation
This doesn't need a policy document — a five-minute team conversation is enough to align everyone.
- State the rule plainly
A stamp only happens when the card is scanned at a completed wash — nothing else.
- Cover the reschedule case
Confirm the scan happens at whichever appointment the wash actually happens at.
- Ban informal make-ups
No promising extra stamps to compensate for a no-show; it isn't tracked and it isn't fair across shifts.
- Separate this from scanning gaps
Make sure staff know a forgotten scan on a real visit is a different problem with a different fix.
- Revisit after a month
Check whether no-shows are actually affecting your numbers or whether it was never really the issue.
No-shows rarely explain a low return rate on their own
If your return rate looks low, no-shows are usually a smaller factor than a genuine scanning gap. One Waya car wash traced its 7.5% return rate — well under the 24–27% typical range — to attendants not scanning real visits, not to unfulfilled bookings.
Keep bookings and card notifications on separate tracks
Booking reminders and Waya's wallet triggers do different jobs and shouldn't be merged. Use your booking system's own reminder for the appointment itself, and let Waya's wallet notifications — welcome, stamp added, reward redeemed, and the 14-day win-back trigger — handle loyalty specifically, sent only to the wallet lock screen, never by SMS.
Waya has no POS, till, or booking-system integration, so there's no automatic link between a booking status and a stamp — the scan at the counter is always the single source of truth, whether you're on the Free plan or a paid one. For the wider setup, see the car wash loyalty guide, and review Saudi customer data handling rules if you're storing booking details alongside loyalty data.
Frequently asked questions
Does a customer get a loyalty stamp if they no-show a booking?
No. A stamp only happens when a staff member scans the customer's card at a completed wash, so a no-show never touches the loyalty program at all — no manual reversal is needed.
What if a customer reschedules instead of no-showing?
The scan happens whenever the wash actually takes place, at the new appointment time. The original slot never generates a stamp on its own.
Should staff give a make-up stamp for a missed booking?
No — informal make-up stamps create undocumented exceptions that vary by shift. Keep the rule simple: a stamp only follows a scan at a real, completed wash.
Can no-shows explain a low overall return rate?
Usually not as much as a scanning gap does. One Waya car wash's low 7.5% return rate traced back to attendants not scanning real visits, not to unfulfilled bookings.
Is there any link between a booking system and Waya stamps?
No — Waya has no integration with booking or POS systems. The scan at the counter is the only thing that ever creates a stamp, regardless of what a booking calendar shows.