Outlook
Part of Loyalty marketing outlook for England as rewards schemes face a reset
Loyalty software planning: three areas to review
Loyalty software planning for England teams: review member value, referral and data duties, delivery skills and platform fit, then set clear review triggers.
What to take away
- Recent change has shifted loyalty software planning away from headline mechanics towards proof: consent records, earn and burn clarity and referral disclosures now carry more weight than another rewards gimmick.
- The planning areas worth testing for 2027 in England are measurable value per member, tighter data and safety duties, and skills gaps that decide which tools a team can actually run.
- Treat every vendor claim as a hypothesis to test against your own baseline, not as a forecast you adopt wholesale.
- Use Ofcom and ICO guidance to check regulatory scope and marketing duties, then set review triggers so a change in rules or platform terms forces a rewrite of the plan.
Three planning areas for England teams to assess
1. Measure value per member, not just enrolment volume
Enrolment is cheap to grow and easy to game. Boards increasingly ask what each member returns once rewards, service and platform costs are deducted.
The £400 a month here is an example budget, not a market price or vendor quote. Separate software from rewards in your model; build the cost model first, then ask shortlisted suppliers for current quotes and assess whether the expected repeat-purchase margin supports the spend.
Start with the reporting you already hold. If margin per member cannot be produced from existing data, the first project for 2027 is a measurement fix rather than another campaign.
2. Check referral features against safety and data duties
Referral mechanics that let members post, comment or share into community spaces do not, by themselves, establish that a loyalty provider is within the Online Safety Act 2023. The Act covers regulated user-to-user and search services; Ofcom is the regulator. The government's Online Safety Act explainer sets out the scope of those duties. Check whether the service—not merely the referral campaign—falls in scope before assigning compliance work.
The ICO's Direct Marketing Guidance, alongside the Privacy and Electronic Communications Regulations 2003 (PECR) and the UK GDPR, gives teams a specific basis for reviewing marketing controls. Check PECR's consent rules and any applicable soft opt-in for electronic marketing; record consent and withdrawals where consent is the UK GDPR lawful basis. Review retention rules alongside those controls.
Map where member content can be seen by strangers, then decide whether moderation capacity exists in-house. Referral flows that stay inside private messaging sit in a different category from public feeds.
3. Match platform choice to delivery skills
Match platform choice to the roles needed to run it. A loyalty or CRM manager can own journey configuration, a CRM or marketing operations specialist can manage test sends, an analyst can report member value and referral performance, and an engineer or integration lead can handle data connections. If one person covers several roles, name that responsibility before choosing a platform tier.
Skills gaps show up in delivery rather than in demos. Ask which named person configures journeys, runs test sends and reads the reporting each month, then buy the tier that matches that answer.
Examples to investigate include LoyaltyLion, Yotpo Loyalty & Referrals and Voucherify. They are shortlist candidates, not recommendations or a feature comparison: confirm current UK fit, integration needs and pricing directly with each supplier.
Turn the three planning areas into a review process
Score the three areas against evidence, cost and reversibility
A planning area is only actionable if you can tie it to a number you already hold. Score each one on three tests: is there named evidence, what does it cost to act, and how hard is it to reverse? Record each test as a pass, gap or unknown. Use your own baseline and agreed business target for margin, conversion and cost per member; do not treat a single benchmark as universal.
Write the evidence column before you meet a vendor. If a supplier cannot point to the number their feature moves, that gap is your answer.
Score each trend against evidence, cost and reversibility
| Trend | Evidence to gather | Typical cost driver | Review trigger |
|---|---|---|---|
| Value per member | Margin per member after rewards | Reporting and analytics time | Margin falls two quarters running |
| Safety and data duties | Referral flow mapped to duties | Consent and moderation work | New guidance or platform terms |
| Skills and delivery | Named owner per platform module | Training days and backfill | Key person leaves or role changes |
| Measurement quality | Baseline before any change | Data engineering effort | Source data changes upstream |
Set review triggers instead of annual rewrites
Annual planning cycles are too slow for rules and platform terms that move mid-year. Name the person who watches each trigger and the date they report.
This turns a static plan into a short set of checks, keeping the wider outlook document current. Record the owner, evidence and next review date beside each trigger so the plan changes when the underlying facts do.
Common questions
Which planning areas belong in a 2027 plan and which are noise?
Keep areas you can tie to a number you already report, such as margin per member or referral conversion. Park the rest on a watchlist with a named owner. If nobody can say what would change their mind, it is noise.
Does this list cover Scotland, Wales and Northern Ireland?
The online safety and data duties cited here apply across the UK, so the compliance points hold throughout. Commercial factors such as local competition and staffing differ by nation, so check those against your own trading area.
How often should the list be refreshed?
Review it when a named trigger fires, and otherwise at least twice a year. Guidance pages and platform terms change without warning, so a fixed calendar date is a backstop, not the main mechanism.
Can a small team act on all of this?
No, and it should not try. Pick the two areas with the clearest evidence and the lowest reversal cost, deliver those, then revisit the table once results are in.
