Positions

Points expiry is usually a liability decision not an engagement one

Points expiry is usually a liability decision, not an engagement one. Programmes let points lapse primarily to remove unredeemed balances from the balance sheet; engagement effects are secondary and often accidental.

The argument

The register profiles 217 programmes across ten sectors. Of the 214 with known tier status, 112 run tiers. Airlines run tiers in 61 of 61 profiled programmes and hotels in 18 of 18, while grocery runs tiers in none of 18 and fuel in none of 12. If expiry were an engagement tool, its use should track the presence of engagement machinery. It does not: tiering varies wildly across these sectors, but the accounting pressure to limit outstanding points does not. The decision to expire points sits in the same financial logic regardless of tier count. That uniformity points to a common financial requirement, not a differentiated engagement tactic.

The financial requirement is balance-sheet management. Points issued but not redeemed are an outstanding obligation. Letting points lapse removes that obligation. The decision to have an expiry window is made by finance teams because it controls how much liability a programme carries. A grocery programme with no tiers and an airline programme with full tiering both face the same accounting pressure to stop unredeemed balances growing without limit. The engagement effect of a deadline is real but secondary: it is a by-product of the liability choice, not the reason for it.

Engagement tools are tuned to member behaviour. They are tested, segmented, and personalised. Expiry clauses are not. They sit in terms and conditions, written in legal language, with little variation across sectors. If expiry were primarily an engagement decision, programmes would run experiments on expiry length, test different lapsed-point messages, and change expiry rules based on redemption behaviour. Some do test the messaging around expiry, but the expiry window itself is set by liability forecasting, not by engagement optimisation. That is why the strongest reading of the clause is financial.

The strongest counter-argument

The strongest counter-argument is that expiry can drive real engagement. A member who knows points will lapse has a reason to return, redeem, and stay active. Expiry reminders often produce redemption spikes, and some programmes deliberately use short expiry periods as a behavioural nudge. If those engagement gains are large enough, a programme might choose expiry even if the liability benefit were zero. In that case, calling it usually a liability decision understates the role of deadline pressure in keeping members active.

What would change our mind

If a programme removed expiry entirely and its outstanding liability grew, while its active member rate and redemption rate improved beyond what the liability cost would predict, and other programmes then copied the removal for engagement reasons rather than accounting reasons, that would shift the evidence. The key observable is the decision sequence: a programme chooses to increase its liability while talking about member engagement, and competitors follow while accepting higher liability. That would show expiry is being used as a lever rather than as a bookkeeping device.

What follows if we are right

Run expiry as a finance decision first. Forecast breakage and liability with the finance team, set the expiry window to manage the balance sheet, and do not present it to members as a loyalty feature. Then treat the communication around expiry as the engagement layer: give clear reminders, offer redemption paths before the deadline, and design the final notice to be useful rather than threatening. That gives the programme the accounting benefit while preserving trust, and it stops loyalty managers from pretending that a liability write-off is a reward for loyalty.

Related