Tools and providers
Part of Multi-site loyalty software: a procurement checklist
Multi-site loyalty software: a procurement checklist
A practical checklist for UK multi-site retailers using loyalty software, covering branch needs, EPOS checks, cost modelling, data responsibilities and a pilot.
What to take away
- Judge multi-location loyalty software per site, not per brand. Redemption rules, staff training and reporting all change from branch to branch.
- Map the platform against your real EPOS estate. A clean integration with one till system says nothing about the older tills in half your shops.
- Put per-site fees, onboarding and transaction charges into one three-year cost model before you compare licences.
- Settle data purposes and controller roles in writing, because points balances and referral links are personal data under the ICO's rules.
- Pilot in three branches with different footfall, then extend site by site.
Start with the site list, not the feature grid
Most loyalty platform comparisons assume one shop and one till. A regional chain with twenty branches, two older EPOS systems and a separate ecommerce site is a different purchase. Write down each location, its till software, its connectivity and its opening hours before you book a demo.
Site list before demos
- Each location and branch
- Till software per site
- Connectivity per site
- Opening hours per branch
- Per-branch reward thresholds
Sites selling identical products can behave nothing alike. A town centre branch with heavy footfall and a retail park unit with baskets twice the size need different reward thresholds. Ask which settings can be varied per branch without a support ticket.
Office for National Statistics retail industry data gives you a neutral way to sanity-check sector turnover before you forecast redemption costs. Use the published retail industry statistics for the market view, and your own site figures for the forecast.
Before you shortlist vendors, compare how each channel behaves. Our piece on comparing loyalty and referral channels sets out who sends, who shares and who hosts, which decides what the platform has to report per site.
Test the EPOS integrations against your tills
Integration is where multi-site rollouts stall. Ask for named EPOS integrations and version numbers, then compare that list with your own estate line by line.
Integration checks and evidence
Check
- Per-site configuration
- Settings that differ by location
- EPOS coverage
- Named integrations with versions
- Offline behaviour
- Documented offline queue duration
- Staff permissions
- Role templates plus audit trail
- Reporting
- Sample three-site pilot reports
- Exit route
- Data export and wind-down terms
Evidence to request
- Per-site configuration
- EPOS coverage
- Offline behaviour
- Staff permissions
- Reporting
- Exit route
A platform that reads orders from one till system but ignores the rest creates manual work at the counter. Staff will not chase points on a busy Saturday.
Use a decision table before demos.
Test the EPOS integrations
| Check | Why it decides the shortlist | Evidence to request |
|---|---|---|
| Per-site configuration | Reward thresholds and opening hours vary by branch | A written list of settings that can differ by location |
| EPOS coverage | Unsupported tills force manual entry at the counter | Named integrations with version numbers and release dates |
| Offline behaviour | A dropped connection loses accrual and goodwill | Documented offline queue and how long it holds |
| Staff permissions | Refunds and goodwill points need approval limits | Role templates per site plus an audit trail |
| Reporting | Head office needs site margin, not just sign-ups | Sample reports for a three-site pilot |
| Exit route | Points balances and referral records must survive a change | Contract terms for data export and wind-down |
Price the whole estate, not the headline licence
Work through these steps with each shortlisted vendor:
- Ask for a written quote covering every site you intend to onboard, not a pilot price for one shop.
- Split one-off costs from recurring ones. Hardware, data migration and staff training belong in year one.
- Model transaction fees on your busiest site as well as your quietest. If a vendor charges 4p per redemption, a flagship with 30,000 redemptions a month costs £1,200 a month on these illustrative figures.
- Check the exit before you sign. Ask how points balances, referral records and reporting history leave with you.
- Add internal time. Counter staff, area managers and finance all spend hours on reconciliation in the first quarter.
Per-site fees and redemption costs decide the total, so build the model before anyone sends a proposal.
Agree the data rules before the pilot
Points balances, referral links and purchase histories are personal data. The ICO's UK GDPR guidance expects a lawful basis and defined purposes before collection starts, so write those down per scheme.
Franchise models split responsibilities further. Decide whether the franchisor or each franchisee is the controller, record the processor terms, and keep the answer in the contract rather than in an email.
Reward terms are consumer promises too. The Competition and Markets Authority is the regulator for pricing and consumer protection questions across UK retail, so treat reward conditions as promises you will be held to.
Referral tracking adds a second layer. Our guide to GDPR-compliant referral tracking covers what to log and how to answer a subject access request.
Common questions
Can one loyalty platform run several brands in a group?
Usually yes, but check whether each brand is a separate account with its own data. Sharing customer records across brands needs a stated purpose and a lawful basis, not a tick box.
How many sites justify multi-location loyalty software?
There is no fixed threshold. The usual trigger is inconsistent reward handling or reporting head office cannot reconcile, which tends to appear between three and ten branches.
What should a multi-site pilot measure?
Pick three branches with different footfall and track accrual rate, redemption cost per site and staff time at the till. Agree the exit criteria before the pilot starts.
Does a franchise loyalty platform need separate terms?
If franchisees are separate businesses, yes. Set out the controller for customer data, the funding of rewards and the complaints route, and align it with the franchise agreement.
