Guides
Tiers and status
Tiers and status segment members into named levels with persistent recognition, benefits, and qualification rules. Airlines and hotels run them almost universally, while grocery and fuel rarely do. A sound design sets few, clearly separated levels, delivers benefits at the point of recognition, and plans downgrades before they happen. It ties recognition to member value and behaviour, not to points balances alone.
What this covers
Tiers and status cover the named levels a loyalty scheme assigns to customers, the rules for entering and holding each level, and the recognition members receive while they hold it. This includes qualification windows, upgrade and downgrade transitions, status matches and extensions. It excludes points currency, reward catalogues, coalition currency conversion, payment card linkage and liability accounting unless those tools directly set tier entry thresholds or trigger a status change. The site holds 305 glossary terms in total, with 20 definitions and 9 argued decisions in this cluster.
How the pieces fit together
A member typically begins at a base level granted automatically on joining. The operator then sets a qualification window, commonly one year, and names the activities that count: flights taken, hotel nights stayed, retail spend or visits, or a blend of spend and engagement. The sector pattern in the register is uneven: all 61 profiled airlines and all 18 profiled hotels run tiers, whereas none of the 18 profiled grocery businesses or 12 profiled fuel businesses do.
Once a customer crosses a threshold, the record carries a tier label, and that label converts into operational benefits at the point of service. Priority boarding, late checkout, free delivery, dedicated support and bonus earning all depend on the front line seeing the level instantly and acting without the customer having to ask. A back office that stores status but does not surface it turns recognition into a hidden admin field.
Requalification repeats the cycle after the window closes. Operators may keep the same bar, raise it, lower it, or grant a soft landing when the customer misses. Downgrade protection and status extension belong to this transition stage, not to a separate feature. Status match and challenge offers sit here too, as they move someone into a tier through an outside proof of value rather than the standard qualification path.
Of the register's 217 profiled programmes, tier status is known for 214, and 112 run tiers. Retail shows 25 running among 46 known-status schemes, restaurants 2 of 22, coalitions 2 of 15, banking 1 of 14, and telecom 2 of 7. This uneven distribution reflects different purchase cycles and recognition needs across sectors.
Where programmes get this wrong
A recurring mistake is publishing too many levels and then weakening the differences between them. When two adjacent tiers differ only by a small points multiplier or a rarely used coupon, the status structure loses meaning and members stop aiming for the next step. That failure happens before any communication problem.
Another common error is setting thresholds from last year's revenue alone, with no weight on purchase frequency, margin or non-buying behaviour. A single large buyer who visits once may land in the same level as a weekly low-margin shopper, even though their future value and churn risk are very different. The 9 argued decisions in this cluster often turn on precisely these cut-off disputes.
Operational neglect is often the hardest failure to reverse. A customer qualifies for a level, but store staff, call centre agents and website sessions do not reflect it. The promised benefit either is missing or must be requested. This breaks the recognition loop and converts a loyalty asset into a source of complaints.
How to work through it
- Start with the data already in the membership system. Map current value, visit frequency, recency and non-purchase actions before looking at competitor tiers. The audit should name the moments where a member currently feels recognised and the moments where recognition fails.
- State the behavioural objective in one sentence. Decide whether the level is meant to keep high-value customers, increase share of wallet, lift visit frequency or reduce churn. Write that objective down before choosing thresholds or benefits. This prevents copying a structure from a different purchase cycle.
- Set the number of levels so each one carries at least one distinct benefit and one visible recognition event. Use a qualification window that matches how often the customer actually buys. The register's 57 curriculum modules walk through this sequence from data to tier count.
- Test candidate thresholds against the previous year of real behaviour. Rank members by value and frequency, then simulate where each would have landed. This shows whether a level is too easy, too hard or reachable only by a tiny group. The cluster's 9 argued decisions provide worked examples of threshold choices.
- Design benefits, downgrade protection and status match rules at the same time. A benefit is only useful if the operational system exposes it to employees in real time. Decide what happens when a customer fails requalification and write the soft landing before the first downgrade occurs. Status match offers need a value check, not an open door.
- Choose vendors from the register's 87 profiled suppliers, split across 26 ecommerce-smb, 19 enterprise, 18 composable-api, 17 vertical-specialist and 7 agency-services, with 48 publishing full or partial pricing. Confirm that the platform can record qualification events, expose status at every touchpoint and manage tier transitions without manual work.
- Run a pilot with a subset of members before full rollout. Track recognition at the point of service, benefit redemption, complaint volume and movement between levels. Adjust thresholds or benefits based on observed behaviour, then expand to the whole base and revisit the model at least once per requalification cycle.