Quick answer
Redesign an existing loyalty programme by separating future earning rules from rewards customers have already accumulated. First identify the problem, record current balances and decide how existing members move through the change. Then configure and test the new offer. This guide focuses on changing an active programme; it is different from simply replacing paper cards with digital ones.
Identify the smallest change that solves the problem
Write one measurable complaint about the current programme. Perhaps the reward is rarely redeemed, staff cannot explain the earning rule, or one benefit costs more to supply than expected. Those problems call for different responses. A new logo and a larger reward do not automatically resolve any of them.
Review a sample of customer journeys from joining to earning to redeeming. Ask staff which step causes repeated questions. If customers can earn but cannot find a suitable redemption occasion, reducing the threshold may be less helpful than changing the benefit. Keep useful parts of the existing experience rather than resetting everything at once.
Snapshot balances before changing settings
Create a dated, secured record of member identifiers, available credit, progress toward a reward, relevant expiry dates and outstanding exceptions. Use exports or supported reporting available in your system and confirm the record can be interpreted. A screenshot of the headline total cannot restore an individual member’s balance.
Assign one person to reconcile the snapshot against test profiles. Avoid editing live earning rules while another team is exporting balances. Note the cutover time and how transactions occurring during that window will be handled. The objective is a reproducible before-and-after record, not an additional marketing database.
Choose a transition rule customers can understand
Possible approaches include preserving existing credit while applying the new rate to future purchases, honouring old rewards for a stated transition period, or retaining the old programme for existing members until a defined event. These are editorial design options. They must be reviewed against your terms, relevant requirements and the capabilities of your actual system.
Consider an illustrative café changing from ten qualifying visits to eight. A member with six visits should receive a clear explanation of what those six mean after launch. A spend-based programme changing its redemption value presents a different problem. Do not hide either decision behind “we have improved your rewards.” Show an ordinary account example and the effective date.
Test members at different stages
Use profiles with zero progress, nearly complete progress, an unused earned reward and an unresolved correction. Include a customer who reaches a threshold immediately before the cutover. Record the expected outcome for each profile before the software is changed; otherwise it is easy to accept whatever result happens to appear.
Test a purchase immediately before and immediately after launch. Check the staff screen, customer card, transaction history and any automated messages. If one card is replaced by another, verify the supported restoration or transfer process with the provider. Do not assume a visual redesign automatically preserves balances, status and expiry behaviour.
Explain the change in three short messages
Use a before-launch notice explaining the change and what stays usable, a launch-day message naming the effective rule, and a follow-up answering the most common questions. Mastercard’s reboot guide advises clear communication and staff preparation when programmes change. Its general guidance supports the communication principle; the specific checklist here is our operating proposal.
Give the team a customer-friendly example and an escalation route. Staff should know what to say when a member’s displayed balance differs from the snapshot. Invite customers to report a problem and explain when a response is expected. Avoid asking the person to enrol again as a substitute for investigating a missing balance.
Establish a rollback and review point
Decide in advance what would pause the rollout: widespread duplicate credit, balances not matching, or redemption failing at a participating location. Keep the old configuration record and identify who can restore it through a supported method. Never promise an instant rollback unless the provider has confirmed it can be done.
After launch, review completed redemptions, support questions, corrections and reward cost. Compare similar trading periods and consider other changes in the business. More member revenue alone does not prove the redesigned programme created additional profit. Read the ROI guide for a more careful measurement approach.
Where Boomerangme fits
Boomerangme documents stamp and cashback formats. Explore Boomerangme to investigate which suits the new rule, with your balance and transition checklist ready. Confirm existing-member handling before changing a live template. Product settings are a tool for the plan, not a substitute for the plan.
Quick questions
Should I delete the old programme first?
Prepare the transition record and supported handling method first. Deleting a programme before reconciling member progress makes the change harder to verify.
Can I keep old balances and change future earning?
That is a sensible design option to investigate, but technical support depends on your system and configuration. Test it rather than assuming it.
What should the launch notice explain?
Explain the effective date, future earning rule, existing credit treatment, redemption conditions and where a member can ask for help.
Sources & further reading
- Mastercard loyalty reboot guidePrimary guidance on programme-change communication and staff preparation.
- Boomerangme stamp guideOfficial card settings, not automatic migration assurance.
- Boomerangme cashback guideOfficial earning and expiry settings; transition methods need verification.
Sources reviewed .
Numerical examples are illustrative unless a cited source states otherwise.
