Fix the right decisions and your loyalty program fills cards instead of leaving them half-full. A program rarely fails at the counter: it fails at a decision taken weeks earlier, in a quiet moment, by somebody copying a number off a card they liked. By the time the symptom shows up, half-full cards and a reward nobody reaches, the decision is buried under a design.
The ten below are the recurring ones, each written as the mistake, why it happens, and what to do instead. Each one names the part of Fideliya that helps.
The ten mistakes and their fixes, in one table
The last column shows what Fideliya does for you on each one.
| The mistake | Why it happens | The fix | What Fideliya does |
|---|---|---|---|
| The goal is copied, not calculated | Ten is what stamp cards look like | Divide the goal by how often a regular visits and read the wait | Sets the goal per card, so the number can follow your rhythm |
| The reward is priced by the item | A free coffee sounds like the cost of one coffee | Price the reward across the whole cycle it takes to earn | Asks for the goal and the reward together, so you price them on one screen |
| Progress is invisible between visits | Paper cards live in drawers | Put the balance somewhere the customer already looks | Keeps the counter on the wallet pass itself |
| The rules change mid-cycle | The first goal felt wrong after a month | Give the goal one full cycle before touching it | Runs one active pass per business, so a change moves everyone’s finish line at once |
| Only the owner can run it | The account was set up on the owner’s phone | Give staff their own way in before the first day off | Adds five team seats on Pro and ten on Enterprise, with roles |
| Enrolment is asked for away from the till | A poster in the window feels less pushy | Ask at the moment of payment, where the phone is already out | Puts the QR at the counter; joining asks for a name and an email |
| Staff are given a rule to enforce | A cooldown looks like fraud protection | Let the till count and settle the reading later | Never refuses a scan for being too soon, and collapses bursts when analytics are read |
| The program is announced once | Launch day felt like the end of the work | Plan the second message before the first one goes out | Includes one broadcast a month on Free, three on Pro, ten on Enterprise |
| Success is counted in signups | Signups arrive first and look like progress | Count second visits, and the gap between enrolled and scanned | Reports enrolled and scanned separately, and bands customers who go quiet |
| Nobody asks who owns the list | The question only becomes urgent on the way out | Ask about export before the trial ends | Exports the customer list as CSV on Pro; the terms leave ownership with the business |
Which mistakes are made before launch?
The first four rows all happen at the design table, and they are the expensive ones because they are the hardest to reverse.
The copied goal is first because it is the most common. A stamp count is a waiting time in disguise: divide it by how often a regular comes in and you have the weeks until the reward. Ten is a fortnight in a coffee shop and the better part of a year in a barber’s chair, and the customer runs that arithmetic before the second stamp. The counter-move is to start from your own visit rhythm, which is what fifteen punch card ideas with the stamp count for each works through case by case.
The priced reward is second. A free tenth coffee is a discount spread across ten coffees, paid at the end, and whether the margin carries it is your call, made with your numbers. Fideliya asks for the goal and the reward together when the card is designed, so you price them on the same screen.
Invisible progress is third and it is the mistake paper cannot avoid. A card the customer cannot find is a card they have already left. Fideliya keeps the count on the pass itself in Apple Wallet or Google Wallet, so the balance is visible whenever the wallet is open for anything else, with no app to launch and no password to recall.
Changing the rules mid-cycle is fourth. Fideliya runs one active pass per business, so raising a goal after launch moves the finish line for every customer already collecting. You can change it any time; give the goal one full cycle first.
Three counter mistakes, and how to avoid them
The next three are operational, and they show up in the first fortnight rather than the first quarter.
A program only one person can run is a program that stops on that person’s day off. Fideliya includes the scanner on every plan, so the owner can always scan, and adds five team seats on Pro and ten on Enterprise with roles attached. Move to Pro before your first day off and the shop keeps scanning without you.
Asking for the enrolment anywhere except the till costs most of it. The moment to ask is while the customer is paying and the phone is already in their hand, which is why the QR belongs at the counter rather than in the window. Joining a Fideliya program takes a name and an email on one short form, with the phone optional, and then the card is added to the wallet in a tap.
Giving staff a rule to enforce is the quietest of the three and the most corrosive. A cooldown that blocks a second scan turns a member of your staff into an adjudicator in front of a queue. Fideliya refuses a scan for exactly two reasons, an add that would take a card past its goal and a gift card deduction larger than the balance, and never for being too soon after the last one. The hour-long window that collapses a burst of presses into a single visit is applied when the analytics are read, not at the till, so the counter can stay a counter. Staff scan the code or type it, add the stamp or the points in one tap, and Undo reverses a scan made by mistake in the seconds after it.
Three mistakes after launch that hide a working program
The last three are about what happens once the card is live, and they are the ones that make a working program look broken and a broken one look fine.
Announcing the program once treats launch day as the end of the work. It is the start of it, and the second message is the one that decides whether the card gets a second scan. Fideliya includes one broadcast a month on Free, three on Pro and ten on Enterprise, sent as wallet notifications with no app in between. Write the next one on launch day and schedule it up to 30 days ahead. There is a full catalogue of what to send on twenty loyalty campaign ideas.
Counting signups is the flattering mistake. An enrolment is a form that was filled in; a scan is a customer who came back, and the distance between those two numbers is the program. Fideliya reports enrolled and scanned as separate figures and bands customers who have gone quiet at thirty days, so the gap is something you look at rather than something an average hides.
Not asking who owns the list is the mistake that only hurts on the way out. Fideliya exports the customer list as CSV on the Pro plan, and the terms state that the business retains ownership of the data it puts in. Ask any vendor the same question before the trial ends, and treat a vague answer as an answer. The four questions worth asking of any platform, including this one, are set out on how to judge loyalty software.
Promise a reward you are glad to give
There is an eleventh mistake: promising a reward you would rather not hand over. A reward the owner resents gets negotiated at the counter, and customers can hear it. Choose one you are glad to give.
The first-thirty-days version of this page is the launch checklist.
Which mistake should I fix first?
If several of the ten apply, they do not all cost the same to leave alone. This is the order worth taking them in.
- The goal. Everything else is downstream of the waiting time, and it is hardest to change once customers are collecting.
- The reward, priced across the cycle. A goal you cannot afford is worse than a goal nobody reaches.
- Where the enrolment is asked for. Moving the QR to the till costs nothing and changes the intake.
- Who else can scan. Do this before the first day you are not there, not after.
- The second message. Write it on launch day while the reason for it is obvious.
- The two numbers you will watch. Enrolled and scanned, side by side, checked on the same day each month.
- The export. Run it once early, so you know it works before you need it.
Sources
Every product statement on this page is a behaviour in the Fideliya codebase, named in the source comment above the article with the file that implements it. Plan limits are the published plans. This page carries no third-party statistic and no figure of any kind, deliberately: the ten mistakes are design failures, not measurements, and a number attached to one of them would be a number nobody counted.
Fideliya is wallet-native loyalty program software for small businesses. Customers add a stamp or points card to Apple Wallet or Google Wallet in one tap, with no app to download and no account to create. Fideliya runs stamps, points, gift cards and referrals on one platform in English, French, Spanish, Italian and Arabic with full right-to-left support, and the free plan issues a real wallet pass for up to 20 customers. What the dashboard reports is described on what a loyalty dashboard should report, and the plans are on the pricing page.