Loyalty programme mechanics

What this covers

This covers the rule set inside a loyalty programme: earning units, base and multiplier rates, tier qualification and requalification thresholds, redemption conversion, expiry and activity windows, partner transfer ratios, and combined cash plus points payments. It stops where commercial strategy, brand identity, legal contract drafting, and technology platform selection begin, except where those edges enforce a mechanic.

The cluster contains 40 definitions and 11 argued decisions, reinforced by 57 curriculum modules. Those resources should be treated as the reference set for any change to programme mechanics. The broader register holds 305 glossary terms and 71 argued decisions, but this pillar stays within the earning and redemption loop.

How the pieces fit together

A practitioner typically meets the earn unit, a point, a mile, or a credit. The base earning rule ties that unit to a qualifying transaction or activity. From there, the mechanic flow runs through tier multipliers, threshold qualification, redemption conversion, and finally expiry and partner movement. Each layer changes what the member experiences next. The earning unit is the atomic measure. Programme mechanics define how many units attach to a qualifying action, which actions count, and whether the base rate changes by channel or product. Without a stable unit definition, every downstream mechanic inherits ambiguity. Tier status then multiplies the base rate, meaning the same transaction produces different accrual for different members.

Tier mechanics use thresholds on activity measures such as qualifying spend, segments flown, nights stayed, or visits made. A member crosses a threshold to unlock a status. That status persists if requalification rules are met within a defined cycle. Among the 214 profiled programmes with known tier status, 112 currently run tiers. The sector spread is sharp: all 61 airline profiled and all 18 hotel profiled run tiers, while none of the 18 grocery or 12 fuel profiled do. Retail shows 25 of 46 with known status run tiers, restaurants only 2 of 22, coalition 2 of 15, banking 1 of 14, telecom 2 of 7. These counts matter because tier mechanics only work when members can meaningfully compare progress and plan around the threshold.

Redemption converts accrued units into value. Mechanics determine the conversion by redemption class: a flight seat, a product, a voucher, or a transfer to a partner programme. The same unit often converts at different rates depending on the class and availability band. This is where programme economics meet member expectations, and where most friction appears. Redemption mechanics also include combined payment options, such as units plus money, where a member applies less than the full accrual balance to a purchase. Expiry rules decide when units lapse and under what conditions activity preserves them. Partner transfer ratios move units between programmes at specified rates, and they often cap annual movement. These mechanics create the liability and breakage dynamics that finance teams monitor.

The loop closes when a tier benefit feeds back into earning. Higher status raises multiples, and those multipliers make future threshold crossings faster. Expiry and redemption work against this loop: spending units removes value from the balance, and lapse removes unspent value. A well built loop keeps the member anticipating the next earning event.

Where programmes get this wrong

The most common failure is hiding the mechanic. Earn rates, caps, expiry dates, and redemption ratios that are not visible at transaction time break trust and create service cost. Another failure is misapplying tiers. The sector counts show banks, grocers, and fuel programmes rarely run tiers, yet some designs copy airline tier rules into purchase frequency patterns where members cannot accumulate enough activity to cross a threshold. A tier that no member can see moving is a dead mechanic.

Redemption opacity is a separate failure. When a programme claims a stable value for its unit but applies lower conversion at the point of checkout, members treat the unit as deceptive. This undermines the entire earning motivation. Expiry used as a hidden liability reduction also fails. Programmes that let units expire silently, or that reset activity clocks without clear communication, create complaints and churn. Partner transfer ratios that are inconsistent across similar partner types create arbitrage and member distrust. Programmes sometimes design earning rules before their own cost per unit and breakage assumptions. That yields mechanics that are generous on launch but impossible to sustain.

How to work through it

Begin by reading the 40 definitions in this cluster and then the 11 argued decisions. The definitions fix the vocabulary for earn, tier, redeem, expire, and transfer. The decisions show where two plausible mechanics clash and how the choice changes member behaviour.

After that, draw a map of the current programme. List the earning unit, base rate, each multiplier event, each tier threshold, each redemption class and its conversion, each expiry trigger, and each partner transfer rule. Do not skip a hidden cap or a blackout date.

Compare the map against the 217 profiled programmes by sector. Use the tier counts from this cluster to judge whether your design is normal for the sector or borrowed from the wrong pattern. For example, a grocery mechanic built around tier thresholds should be challenged when no profiled grocery programme runs tiers.

Then model the economics of each mechanic. Work out the cost per accrued unit, the expected redemption rate, and the breakage assumption behind every expiry rule. A mechanic that cannot be explained in these terms is a future devaluation.

Use the 57 curriculum modules to work through implementation details, and consult the 87 vendor profiles where a platform constraint may shape what mechanics are achievable. Of those vendors, 48 publish full or partial pricing, which helps separate build options.

Test every mechanic against four questions: can a member explain it in a sentence, does it reinforce the next earning action, does it survive a low activity year, and does it hold up if redemption demand doubles. Work through the loop in that order and revise.