Program Status
| Setting | Behavior |
|---|---|
| Enabled | Eligible events and admin adjustments can affect loyalty balances. Customer-facing loyalty endpoints return loyalty data for authenticated consumers. |
| Disabled | The program is paused. Keep customer-facing UI prepared to handle unavailable loyalty data. |
Expiration Policy
The dashboard supports three policies.| Policy | Configuration | Customer-visible behavior |
|---|---|---|
| None | No month value required. | Points do not expire. |
| Fixed | Set the number of months after earning. | Points expire based on the earning bucket after the configured number of months. Redemptions or deductions consume older expiring points first at a conceptual level. |
| Inactivity | Set the number of months without qualifying activity. | Points expire when the customer has no earning or redemption activity for the configured period. Earning or redeeming points resets the customer activity window. |
Limits
Each limit is optional. Leave the field empty when you do not want that configured limit.| Limit | Meaning |
|---|---|
| Maximum balance | Maximum current balance a customer can hold. |
| Daily earn cap | Maximum points a customer can earn in a day. |
| Monthly earn cap | Maximum points a customer can earn in a month. |
Public Copy Guidelines
- Say whether points expire and what the customer can do to keep or use them.
- Show upcoming expirations when your UI needs to prompt action.
- Avoid promising points for events you have set to
0. - If a queue uses loyalty-biased admission, avoid precise numeric queue positions and use qualitative progress language.
- If a draw uses loyalty-biased selection, avoid promising a fixed chance or guaranteed outcome.
- Keep reward terms aligned with your own legal and support policies.