How do I calculate my barbershop real repeat-client rate?

Count clients who returned two or more times, not total stamps handed out

A barbershop's real repeat-client rate is the share of enrolled customers who returned and were scanned on two or more separate occasions — not the total number of stamps given out, which can overcount if a barber double-taps a scan, and not raw visit count, which overweights a handful of very frequent regulars. For a shop with 140 enrolled clients and 36 who genuinely returned twice or more, that's a 26% repeat rate, right in the typical 24–27% range for barbershops and salons on Waya.

Getting the counting method right matters because the wrong method can make an identical shop look dramatically better or worse than it actually is, and comparing your number against the 24–27% benchmark only works if you're measuring the same thing.

The three ways a shop can miscount, and how to avoid each

Most counting mistakes come from confusing a related but different number for the one that actually matters.

• Counting total stamps instead of distinct returning clients — a client who visited five times counts once toward the repeat rate, not five times
• Counting a single visit with an accidental double-scan as two separate visits — check the dashboard's activity log for same-day duplicate scans, not just the running stamp total
• Measuring too early in the cycle — a client enrolled ten days ago on a roughly 3-week cycle hasn't had a fair chance to return yet
• Including customers who never redeemed the welcome trigger — enrolled-but-inactive clients should count in the denominator, not be quietly dropped to inflate the rate

The worked example

Here's the full calculation for a 140-client shop, laid out the same way the dashboard's customer profile view presents it.

Where to find this on the dashboard

The customer profile view on the Waya dashboard tracks visits, redemptions, new versus returning status, and quiet regulars directly, which means the 36-out-of-140 calculation above doesn't need a spreadsheet — it's a filter, not a manual count.

Check this monthly rather than daily. A daily check catches too much noise from clients mid-cycle who simply haven't had their second visit yet; a monthly check, aligned roughly to two haircut cycles at the 3-week rhythm, gives a number that's actually comparable month over month.

What to do once you have a trustworthy number

A repeat rate meaningfully below 24% is worth investigating as a scanning-discipline issue before assuming the reward or the shop itself is the problem — one Waya car wash saw only about 7.5% precisely because staff weren't scanning every visit, not because customers were uninterested.

A rate at or above 27%, on the high end of the typical range, is a sign the win-back trigger and QR placement are both working — worth documenting what's being done right so it survives a staff change or a new chair barber joining. The trigger itself is doing quiet work behind that number: "Overdue for a cut? Your chair's waiting."

Run the count for your own shop

Follow the same five checks that produced the 26% figure above, using your own dashboard rather than the 140-client example.

1. Step 1: pull total enrolled clients

   Use the dashboard's customer list as your denominator, not an estimate.

2. Step 2: filter for two-or-more visits

   Use the customer profile view to isolate real repeat clients as your numerator.

3. Step 3: check for same-day duplicate scans

   Scan the activity log for accidental double-taps that could inflate the numerator artificially.

4. Step 4: exclude clients enrolled in the last two weeks

   They haven't had a fair chance to return yet on a typical 3-week cycle.

5. Step 5: divide and compare to the 24–27% benchmark

   A result well outside that range points to a measurement or scanning issue worth investigating first.

The limits behind an accurate count

Every number in this calculation depends on consistent, accurate scanning — Waya has no POS or till integration, so a visit only exists in the dashboard because a barber recorded it by hand on an ordinary phone. Inconsistent scanning doesn't just lower your real repeat rate; it corrupts the count itself, making even the miscounting fixes above less useful.

There's no SMS on any plan, only wallet lock-screen messages, and the Android merchant app is in closed testing, so staff on Android record scans through the web dashboard rather than a native app — none of which changes the counting method, but all of which affects how reliably the underlying data gets recorded in the first place.