The number one mistake: no named scan owner before doors open
The single most common launch-week mistake is going live without deciding, in advance, exactly who scans the card at every visit. Without a named owner, the scan quietly becomes optional the first time the queue gets long, and by week two nobody remembers it was ever supposed to be consistent.
This is exactly what happened at scale in one Waya car wash's case: 67 cards enrolled, but only about 7.5% of customers were credited with a second visit — well under the 24–27% norm — because the scan habit was never locked down from day one.
Everything else in this list matters, but this one alone accounts for most of a shaky first week.
Five more mistakes that show up in week one
Beyond the scanning habit, a handful of smaller oversights compound quickly during launch week specifically, because there's no established routine yet to fall back on.
- No stamp threshold decided before launch — cashiers guess differently and customers get inconsistent answers
- Triggers (welcome, stamp added, reward, win-back) never turned on, so the program feels silent even when it's technically live
- QR poster only placed at the till, missed by customers who pay by app or don't linger at the register
- Only one staff account created, so the scan bottlenecks on a single person's schedule
- No plan for what happens past the Free plan's 100-customer mark, causing a scramble mid-launch
What each mistake actually costs you
None of these are catastrophic on their own, but stacked together in the same week they compound.
| Mistake | Visible symptom | Fix timing |
|---|---|---|
| No named scan owner | Return rate stalls near single digits | Fix before launch, not after |
| Threshold undecided | Inconsistent answers to customers | Decide on day 1 |
| Triggers off | Program feels dead despite active enrollment | Turn on during setup |
| Poster only at till | Lower enrollment than expected | Add a second spot by day 2 |
A tighter launch-week sequence
This is a compressed version of a full launch plan, focused specifically on avoiding the mistakes above.
- Day 1: decide the threshold and name the scanner
Pick the stamp count for a free wash and assign the scan to one role, in writing, before anything goes live.
- Day 2: turn on all four triggers
Write and enable welcome, stamp-added, reward-redeemed, and win-back messages together, not one at a time later.
- Day 3: print two posters, not one
Place a QR code at the till and at a second high-visibility spot, like where keys are handed back.
- Day 4: add every staff member who might scan
Give every relevant attendant Cashier access so scanning never bottlenecks on one person's shift.
- Day 5: rehearse the scan under a real queue
Run it during an actual busy period, not a quiet test run, to confirm the habit holds under pressure.
- Days 6–7: check the numbers daily
Compare scans to car volume every day this first week, since small gaps are easiest to fix before they become habits.
Why launch week specifically matters more than later weeks
Habits set in week one tend to persist, for better or worse — staff who scan consistently from day one keep doing it, and staff who learn the scan is optional rarely un-learn that. That's why the fixes above are front-loaded into the first week rather than spread out.
All of this fits inside the Free plan
None of the launch-week fixes above require paying anything — Free covers up to 100 customers, 1 stamp card, 1 branch, and 100 messages a month at 0 SAR, which is enough to launch cleanly and test the whole sequence before deciding on Growth.
Keep Waya's limits in view during launch week: no POS or till integration, so scanning is always a manual step, and no SMS — every trigger and campaign reaches customers through the wallet lock screen only. For the full setup beyond launch week, see the car wash loyalty guide, and get every relevant attendant onto staff accounts before day one.
Frequently asked questions
What's the single biggest mistake car washes make when launching a loyalty program?
Not naming, in advance, exactly who is responsible for scanning the card at every visit. Without that decision made before launch, the scan quickly becomes optional and the habit never sets properly.
How does this connect to the 67-card, 7.5% return rate case?
That case is the clearest example of what happens when the scan habit isn't locked down early — 67 enrolled cards but only about a 7.5% two-visit return rate, well under the 24–27% typical range.
Should triggers be turned on before or after launch?
Before. Write and enable the welcome, stamp-added, reward-redeemed, and win-back messages during setup, not as an afterthought once the card is already live.
Is one QR poster at the till enough for launch?
Often not — customers who pay by app or don't linger at the register can miss it. A second poster at a high-visibility spot, like where keys are returned, improves enrollment.
Can a full launch fit inside the Free plan?
Yes. Free covers up to 100 customers, 1 stamp card, 1 branch, and 100 messages a month at 0 SAR, which is enough to launch cleanly and test every step of the sequence before considering Growth.