Four earning axes in a hotel loyalty programme
Spend is useful, but it is not the only signal for a hotel loyalty programme. One guest stays many nights on an agreed rate, another returns several times, and a third uses services across departments. Four axes let the hotel describe these actions separately. The examples below are design options, not implementation results or a promise of more repeat bookings.
Monetary: spend by category
This axis covers eligible room, restaurant, spa and other spending when the data is available and included in programme rules. Each category can have its own earning rule based on the economics of that service. Define eligible payments and how discounts, cancellations and refunds are handled.
Volume: amount of accommodation
Count room-nights separately from the bill. For example, a long stay at a corporate rate can be recognised without relying on spend alone. Keep nights and visits distinct: one multi-night trip is not several trips.
Frequency: repeat visits
This axis recognises completed stays within a period or time since the previous visit. Test the threshold against the hotel's own data. Crediting a repeat visit does not itself show that the programme caused it.
Engagement: actions beyond purchases
Completing a preference profile, answering a survey or making a verified referral can be recognised separately if the hotel may collect and verify those events. Each action needs a source, duplicate-credit protection and a reversal process. Credit for a review should not depend on a positive rating.
Earning and tier progression
The four axes describe what earns recognition or points. Tier qualification can use separate thresholds for spend, nights, visits or a combination. An OR rule allows several routes to a tier; an AND rule requires several conditions together. These are design options, not universal thresholds or a claim that every project has a ready-made feature.
Check before launch
- Agree the event for each axis: booking, payment, completed stay or verified action.
- Check data sources, guest identity, credit timing and duplicate events.
- Test cancellations, refunds and manual corrections with sample cases.
- Compare expected reward and operating costs with the hotel's own data.
Measure actual effects after launch and account for other reasons guest behaviour may change. Discuss your project's rules and data →
