Nine ways a new loyalty program dies in its first 90 days

Programs rarely die because the idea was wrong

Most new loyalty programs do not fail because customers dislike rewards. They fail on four or five operational details set in the first week and never revisited: a reward sitting too far away, staff who were never told the program exists, a QR code taped where nobody looks, and a first message that arrives at 11pm.

The useful part is that each of those failures leaves a fingerprint in your own numbers. What follows is a catalogue of nine, drawn from patterns that repeat across the 100+ shops running cards on Waya and the 5,000+ cards those shops have put into wallets. Each one gets the detection signal and the fix.

One thing to state plainly before the list. Waya has no POS integration and sends no SMS. Staff add stamps by scanning the customer's card on an ordinary phone, in a browser or the Waya merchant iOS app, and messages arrive as wallet notifications on the lock screen. So every failure below is operational, and you can fix all nine without touching your till.

None of this is Waya-specific either. The same nine patterns show up on Niqati, on Btaqa, and on a paper punch card in a drawer.

Mistakes 1 to 3: the math you set on day one

Mistake 1 is the reward nobody can reach. A barber sets 10 stamps, and his customers come every four weeks, so the reward is 10 months away. The signal: day 60 arrives, enrollments keep climbing, and your redemption count is still 0. The fix is to set the threshold so a normal regular reaches the reward in 4 to 6 weeks — three visits a week means 8 to 10 stamps, once a month means 4 or 5.

Mistake 2 is a reward worth less than the effort of collecting it. A 10% discount on a 22 SAR drink is 2.20 SAR after eight visits, which is not worth remembering. The signal: people enroll at the counter and never scan a second time, and when you ask five cardholders what the reward is, none of them can say. The fix is to give away the thing they already buy — a free drink, a free wash, a free cut — and to cost it out: if the reward costs you 12 SAR and it buys three extra visits at 25 SAR each, the trade works.

Mistake 3 is the wrong card type for the business. A pharmacy or a hardware store cannot fairly treat a 15 SAR purchase and a 400 SAR purchase as one stamp each. The signal: staff start improvising, two stamps for a big order and none for a small one, and the counts stop meaning anything. The fix is points or a balance card instead of stamps — Waya supports stamp, points, balance, and discount cards, and the cheapest week to change your mind is week one, before hundreds of cards exist.

Mistakes 4 to 6: the counter decides everything

Mistake 4 is the staff briefing that never happened. The owner builds the card at 1am, tells nobody, and the cashier first hears about it from a customer asking about "the stamp thing". The signal is easy to read: enrollments cluster on the shifts the owner works and fall to near zero on every other shift. Pull one week of new cards by day and shift and the pattern is unmistakable.

The fix takes ten minutes per shift. Write one sentence for staff to say, then have each person do one real enrollment and one real stamp on their own phone before they serve a customer with it. On the Growth plan you get 5 staff accounts, so each person scans under their own login and you can see who is actually asking.

Mistake 5 is the QR code in a place nobody looks. It ends up on the glass door at knee height, or behind the till facing the staff instead of the customer. The signal: a busy shop producing fewer than 5 new cards a week. The fix is to stand exactly where a customer stands, at their eye level, and check whether you can read the code — then put one on the counter facing out and a second where people wait, at the pickup counter, the barber's mirror, or on a table tent.

Mistake 6 is asking at the wrong second. The card gets offered after the payment terminal beeps, when the customer already has their bag and is turning to leave. The signal: staff keep reporting that people say no, and enrollment sits under 10% of tickets. The fix is to ask during the wait rather than after the payment, while the coffee is being made or the receipt prints, with the friction named out loud: "Want our card? It's free, it goes in your Apple Wallet, about ten seconds, no app."

Mistakes 7 to 9: after the card is in the wallet

Mistake 7 is the message that arrives at 11:40pm. A wallet notification on a late-night lock screen gets some people to delete the pass on the spot, and a deleted pass does not come back by itself. The signal: check the timestamps on your own sends first, then look for a dip in active cards in the days after each one. The fix is to send in hours when a person could act on the message — mid-afternoon to early evening for a cafe — and to give a reason, such as "two stamps left, valid this week". Passive branch-proximity reminders, configured on the Branches screen, take some of the timing guesswork off you; note that the address and Maps fields on the card itself are not the geofence.

Mistake 8 is the redemption that goes wrong. Someone finally reaches 10 stamps, holds up the pass, and the cashier says "I don't know anything about this." That is the most expensive minute in the whole program, because it is the minute the customer tells other people about. The signal: eligible customers pile up at the threshold while redemptions stay flat. The fix is a rehearsal — enroll on your own phone before launch, fill the card, redeem it, and show every staff member where the redeem action lives.

Mistake 9 is the dashboard nobody opens. The program runs for 90 days, the data accumulates, and no decision is ever made from it. The dashboard shows visits, redemptions, new versus returning customers, and which regulars have gone quiet, with win-back messaging from the same screen. The signal: the quiet list grows week over week and not one message has gone to it. The fix is ten minutes a week — and on the free plan, with 100 messages a month, spend them on the quiet list instead of messaging everyone.

A 90-day schedule that catches all nine

Days 1 to 7, watch enrollment rate per shift. Count new cards against tickets written on the same shift. If a shift writes 60 tickets and produces 3 cards, you are looking at mistakes 4, 5, or 6, and no change to the reward will fix it.

Days 8 to 30, watch median stamps per card. If most cards sit at exactly 1 stamp, customers enrolled once and nobody scanned them again, which points at the reward (mistakes 1 and 2) or at staff not scanning every visit. By day 30 you should also be able to name the week your first redemption will happen. If you cannot, your threshold is too far out.

Days 31 to 90, watch returning customers and the quiet list, because this is where the program either compounds or leaks. Here is the arithmetic with the assumptions written out: a shop writing 40 tickets a day, six days a week, sees about 960 tickets a month. If staff ask on half of them and one in three says yes, that is roughly 160 new cards in month one.

That number crosses the free plan's 100-customer cap inside the first month, which is a real decision rather than a detail. Stay free and stop enrolling at 100, or move to Growth at 85 SAR a month for unlimited customers and 5,000 messages. Either way, everyone already enrolled keeps their card and keeps collecting.