Loyalty program rules: the edge cases to decide first
The questions a loyalty program answers badly when you improvise them at the till, refunds, duplicate signups, repricing, and what happens if you close.
On this page
- What happens when someone returns an item after redeeming a reward?
- Does staff get to use the card themselves?
- What do you do about a customer who joined twice?
- Can you change what a reward costs once people already have stamps?
- Should a stamp or a reward expire?
- What happens to member data if you close, sell, or move the business?
- Frequently asked questions
- Where to go next
A customer redeems a free coffee, then asks for a refund on the paid drink underneath it. Someone shows up with two phones and two passes for the same card. A regular insists they had eight stamps on a card you have no record of. None of these happen often, but each one happens eventually, and the worst time to decide the rule is at the till, in front of the customer it affects.
Moving off a paper stamp card without losing regulars covers the single most common version of this, a disputed stamp count during a changeover. This is the rest of the list: the decisions worth making once, in writing, before the first edge case forces an answer on the spot.
Key takeaways
- Decide these rules before the first edge case, not during it. A policy made calmly in advance is more generous and more consistent than one improvised under pressure.
- Write the rule down somewhere every staff member can see it, the same reasoning that makes a till line work for enrollment in the first place.
- Most of these decisions favor the customer over the ledger. The cost of being slightly too generous is almost always smaller than the cost of a regular who feels cheated.
- A few of these are not business judgment calls at all. Data deletion requests are a legal right, not a courtesy.
What happens when someone returns an item after redeeming a reward?
Decide the rule before the first return, not during it: when a customer redeems a reward and then returns the paid item next to it, the reward does not get clawed back. Reversing a stamp or a free item after the fact reads as punitive no matter how it is phrased, and the margin at stake is small compared to the goodwill lost by chasing it.
The cleaner fix sits earlier in the flow: hold the redemption until the transaction is final, rather than letting a reward get redeemed and the item returned inside the same visit. That removes the situation for most returns without ever having to claw anything back. For the rare case where someone returns days later, treat the reward as already spent, exactly as you would treat a discount that was already applied at the till.
Does staff get to use the card themselves?
Yes, with one adjustment: separate a staff discount from loyalty stamps. If staff buy at a reduced price, stamping that purchase at full value distorts your own numbers and, more importantly, looks like you are running two sets of rules. Either staff purchases do not earn stamps, or they earn at the same rate as anyone else paying the same discounted price. Pick one and apply it consistently, because the inconsistency is what a team actually notices, not the generosity of either option.
Loyalty program metrics is worth checking against this decision: if a handful of staff accounts show up near the top of your most-active-member list, that is usually staff purchases inflating the numbers rather than a genuine engaged regular, and worth excluding before you draw a conclusion from the data.
What do you do about a customer who joined twice?
This is more common than it sounds. Usually it is a customer who lost track of having already joined and scanned the join code again on a second phone, or a couple sharing one device that ends up registering two passes. Passumo flags this automatically: when two passes for the same card end up registered on the same phone, the newer one is marked as a likely duplicate on your customer list, without moving or merging any stamps between them.
That last part is deliberate. Automatically combining two accounts’ stamp counts assumes the two passes are definitely the same person and definitely should be merged, and neither assumption is safe to make without asking.
The decision that is actually yours is what to do once you notice a flagged duplicate. Either let it sit, since most customers never notice they have two low-stamp accounts instead of one higher one, or have a quiet word next time they are in and consolidate it by hand. Neither choice needs a policy beyond “don’t fix what nobody has complained about.”
Can you change what a reward costs once people already have stamps?
Yes, and the honest version of this decision is about timing, not whether you are allowed to. If you make a reward cheaper, apply it to everyone immediately: nobody objects to a card becoming easier to fill. If you make it more expensive, existing members should finish their current card at the old price. A customer who is six stamps into a ten-stamp card should not discover, on stamp seven, that the goal just moved to twelve.
On Passumo, repricing a reward updates every member’s wallet pass automatically, so there’s no manual step where some passes show the old number and some show the new one. The business decision, who the new price applies to and from when, still has to be made by you. How many stamps should a card have? is the decision to get right before launch, so repricing becomes a rare correction rather than a recurring fix.
Should a stamp or a reward expire?
Most independent shops are better off without an expiry date on stamps themselves. A dormant member who comes back after a year and finds their stamps intact is a win either way; one who finds them wiped has a reason to feel the card was never really theirs, over a decision that saved you almost nothing.
A reward that has already been earned and sits unredeemed is a different question, and reasonable shops land on both sides of it. If you do set an expiry, put it on the earned reward rather than the stamps that built it, and be upfront about the date at the moment it is earned, not buried in terms the customer never reads. If an expiry term matters enough to enforce, it is worth a few minutes with a solicitor or your local trading-standards guidance, since what counts as a fair, clearly communicated term is a legal question, not a product setting.
What happens to member data if you close, sell, or move the business?
This is the one item on this list that is not a judgment call. UK GDPR gives every customer a right to erasure, and if someone asks you to delete their data, you generally have one month to act on it (Information Commissioner’s Office, “Right to erasure”). That obligation does not pause because the business is winding down, changing hands, or merging into another site. Getting opt-in: consent people actually complete covers the permission side of holding customer data in the first place; closing or selling is the other end of the same responsibility.
If you are selling the business, decide before the sale, not during handover, whether the new owner inherits the existing member list or starts fresh. Either is defensible, but it needs to be in the sale conversation, not discovered by a regular who gets a message from a business they thought had closed.
Frequently asked questions
What if a customer claims a stamp count you have no record of? Round in their favor, the same rule as during a paper-to-digital switch. The cost of crediting a guessed stamp too generously is a few pence of margin; the cost of arguing about it in front of other customers is a regular who stops coming back.
Can one person use two different loyalty cards from the same business, one per site? Treat it as a separate decision from the duplicate case above. A customer visiting two locations of the same business on purpose is not the error scenario a flagged duplicate is built to catch, and the right answer depends on whether you run the two sites as one program or two, which is a bigger decision than anything on this list.
Should a family be allowed to share one card? Most shops let this happen informally rather than policing it, and that is a reasonable default. The reward math assumes one card per regular visitor, so a shared card fills faster, which costs you a little margin in exchange for not having an awkward conversation with a family that has been coming in for years.
Does a referral reward need its own rule? Yes, the same repricing logic applies: if you change what a referral earns, honor the old terms for anyone who already referred someone under them. Changing the reward after someone has already done the work of bringing a friend in is the version of this that feels worst to the customer.
Who should actually make these calls, the owner or whoever is on shift? Decide the rule once, in writing, and let whoever is on shift apply it. How to get your staff to actually sign people up makes the same case for enrollment: a written rule that survives staff turnover beats a judgment call that depends on who happens to be working.
Where to go next
Most of these edge cases are really the same decision applied to a different situation: favor the customer, write the rule down once, and let the system do the rest. The complete guide to digital loyalty cards covers the setup decisions that come before any of these, and loyalty program metrics covers what to watch once the program is running and these rules are already in place.
Source: Information Commissioner’s Office, “Right to erasure”, UK GDPR guidance, retrieved October 27, 2026.
