How many paid washes should come before a free wash on a stamp card?

The short answer: six is the common default, ten is the conservative choice

Six paid washes before a free one is the most common car wash stamp threshold, working out to roughly a 14% effective discount and completing in about two months for a customer visiting every 10-14 days. A ten-wash threshold cuts that discount to about 9% but takes noticeably longer to complete, which can cost some of the motivation a shorter cycle provides.

There's no single correct answer — it's a trade-off between margin protection and how motivating the reward feels, and the right choice depends on how often your customers actually visit.

Comparing thresholds side by side

The three most common thresholds trade off in a predictable pattern: a lower number completes faster and discounts more, a higher number protects margin but takes longer to pay off.

Choosing a threshold for your own visit cycle

Four steps turn your own visit data, rather than a generic default, into a threshold you can commit to.

1. Estimate your typical visit gap

   Car wash customers commonly return every 10-14 days; adjust based on your own dashboard data.

2. Pick a discount level you can afford

   9-14% is a workable range for most flat-price washes without eating too much margin.

3. Match the threshold to that discount

   Higher thresholds lower the effective discount but stretch out the time to reward.

4. Set it once and keep it consistent

   Tell every cashier the same number so nobody at the till is improvising a different threshold.

Why a shorter threshold often wins for car washes

Car wash visits are frequent enough that a 6-stamp card completes inside two to three months for a regular customer, which is short enough to stay motivating without disappearing into the background of daily life. A 10-stamp threshold, while cheaper per free wash, risks losing the customer's attention before they ever reach it — especially if their visit cadence slows during a quiet season.

This is different from a barbershop's roughly 3-week cycle or a salon's more irregular one; a car wash threshold should be set against its own visit rhythm, not borrowed from another vertical.

What changes if pricing isn't uniform

Everything above assumes a flat ticket price. Once pricing varies by vehicle size or service tier, the threshold question changes shape entirely, and a fixed stamp count stops being the right tool — the same logic that means subscription customers don't need a stamp card at all.

• Uniform flat pricing across all washes → a stamp card with a fixed threshold works cleanly
• Tiered pricing by vehicle size or service → a points card tied to riyals spent handles the variation a stamp card can't
• Mixed pay-per-wash and subscription customers → run the stamp card for pay-per-wash customers only
• Seasonal add-ons like interior detailing → track separately from the base wash stamp count

Testing a threshold on the Free plan before committing

The Free plan lets you run a real stamp threshold with up to 100 customers and 1 stamp card at 0 SAR, which is enough to see whether a 6-stamp cycle feels right before locking in a design. If most customers are stalling around stamp 3 or 4 without progressing, that's a sign the threshold or the visit cadence assumption needs adjusting before moving to Growth.

A scanning caveat that applies to every threshold

Whatever threshold you pick, it only works if every visit gets scanned — Waya has no POS or till integration, so a staff member scans the customer's card on an ordinary phone each time. A customer's stamp count that silently stalls because of a missed scan looks identical, from the customer's side, to a threshold that's set too high, so rule out scanning gaps before concluding the threshold itself is wrong.