|
How this guide was prepared. Last updated October 2026. Brandmovers is itself a loyalty program provider; the criteria below apply to any provider, Brandmovers included. The guide draws on Brandmovers' experience designing and running loyalty programs. It also draws on AICPA guidance on SOC reports, the PCI Security Standards Council and California's privacy law, each checked at its source. This is general information, not legal advice. |
A loyalty program provider is a company that supplies the technology, and often the strategy, rewards fulfillment and day-to-day management, that a brand uses to run a loyalty program. Providers range from self-serve software platforms to full-service partners that design and operate the program on the brand's behalf.
Most brands that launch a loyalty program decide early whether to build or buy a loyalty platform. Those that buy then face a harder question: which provider. Feature lists look similar from the outside, so the useful work is asking each provider to prove what it claims against the program the brand actually plans to run. This guide covers eight considerations, what to ask under each, what proof to request and the red flags to watch for, followed by a summary table and a short process for running the evaluation.
|
Define the program's goals, the member behaviors it should change, the program structure and any industry rules first, so every provider is judged against the same requirements.
Write down what the program is for, such as more frequent purchases, purchases in a particular channel, better customer data or retention of at-risk customers, and the measure that will show it is working. Then note the structure the program needs (points, tiers, paid membership, rebates or a mix), the channels members will use and any industry rules that limit rewards, such as those for alcohol, tobacco, financial services or healthcare.
Even a rough list of must-have and nice-to-have requirements makes demos comparable. Without it, each provider shows its strongest features rather than the ones the program needs.
Red flag: a provider that proposes a solution before asking about goals, members or constraints.
The capabilities that matter are the ones the program needs at launch and in its second and third years: flexible earning rules, channel coverage, data and reporting, and integrations.
Ask each provider to show, not describe:
Proof to request: a live demo of two or three of the brand's own scenarios and integration documentation. If a needed feature is only on the roadmap, ask whether its delivery date can be written into the contract.
Red flag: a demo that only uses the provider's prepared example program.
Look for a reward catalog and fulfillment model that fits the program's members and budget, with simple redemption and clear handling of reward costs.
Red flag: reward costs or fulfillment fees that are not itemized in the proposal.
Ask for evidence: a recent SOC 2 report and who issued it, PCI DSS scope where payment cards are involved, privacy contract terms and specific fraud controls.
SOC 2 reports. A SOC 2 examination reports on a service organization's controls "relevant to security, availability, processing integrity, confidentiality, or privacy" (AICPA). Ask for the most recent report, usually under a nondisclosure agreement, and check which areas it covers, the dates it covers and any issues the auditor noted. Check who performed the examination, too. SOC reports are assurance reports issued by CPAs; the AICPA notes that "CPAs can use the AICPA's various SOC offerings to provide assurance reports" (AICPA), so confirm the report comes from a licensed CPA firm.
Payment cards. PCI DSS is aimed at "entities that store, process, or transmit cardholder data (CHD) and/or sensitive authentication data (SAD) or could impact the security of the cardholder data environment (CDE)" (PCI Security Standards Council). If the program takes fees, links cards or pays cash back to cards, ask which parts of the provider's service are in scope, which payment processors it relies on, and for evidence of compliance from each.
Privacy contracts. Under California law, a business that discloses personal information to a service provider for a business purpose must have an agreement that, among other things, "specifies that the personal information is sold or disclosed by the business only for limited and specified purposes," obligates the provider to comply with the law, and lets the business take steps to stop and remediate unauthorized use (Cal. Civ. Code 1798.100). If the provider is a service provider under the law, the contract must also prohibit it from selling or sharing the data, using it outside the contract's purposes, or combining it with personal information from other sources, except as the law permits (Cal. Civ. Code 1798.140). These duties apply to brands that meet the law's definition of a business. Ask whether the provider's standard contract covers these terms, and check the privacy laws of the other states where members live. This is general information, not legal advice.
Fraud controls. Ask which controls the platform uses against duplicate accounts, account takeover, receipt or offer abuse and points theft, and who reviews flagged activity.
Red flag: a provider that describes itself as compliant but will not share a report under NDA, or its contract terms, once it is shortlisted.
Expect a member experience that is simple to join and use, personalization based on member behavior, and communication tools that reach members in the channels they use.
Proof to request: the member journey on a phone, from enrollment to first redemption.
Red flag: personalization that cannot be tested against a control group.
Match the support model to how much the brand's own team will run: self-serve platforms need less, full-service programs need named people, regular reviews and clear service levels.
Red flag: a senior team in the sales process that does not appear in the delivery plan.
Compare total cost over the full contract term, including build, platform, rewards, fulfillment and service fees, and agree data ownership and exit terms before signing.
Pricing models differ. Some providers charge a build fee plus a platform fee, others a subscription, a per-member fee or a share of reward spend, and some itemize integrations, reporting or support as extras. Put every proposal into the same format, over the same term, using the brand's own member and redemption forecasts. For example, a proposal with a lower platform fee and a per-member fee can cost more by the final year than a flat subscription if membership grows as forecast, so run every proposal through the same forecast and note where the costs cross. The loyalty platform buyer's guide covers how costs differ across self-serve, enterprise and full-service providers.
Then check the contract terms that matter at the end of the relationship: who owns member data, in what format it can be exported, how points balances and history transfer, and what notice and fees apply to leaving.
Red flag: a low first-year price with large increases or unclear fees in later years.
Check results the provider can show for programs like the brand's, and talk to current clients of similar size and complexity.
Red flag: references only from clients much larger or smaller than the brand. A provider new to the brand's industry is not ruled out, but it should show how it will handle that industry's rules.
Use the table to keep each provider's evaluation focused on evidence rather than claims.
|
Consideration |
What good looks like |
Evidence to request |
Red flag |
|---|---|---|---|
|
Goals and requirements |
Provider asks about goals, members and constraints first |
Discovery questions in the first meeting |
A solution before any questions |
|
Platform capabilities |
Rules, channels, data and integrations the program needs now and later |
Demo of the brand's own scenarios; integration documentation |
Demo only of a prepared example |
|
Rewards and fulfillment |
Relevant catalog, simple redemption, itemized costs |
Catalog sample; redemption walkthrough; fee schedule |
Reward and fulfillment fees not itemized |
|
Security, privacy and fraud |
Current SOC 2 report, PCI DSS scope where relevant, compliant contract terms |
Report under NDA; contract terms; fraud control list |
Claims of compliance without documents |
|
Member experience |
Simple enrollment and redemption on a phone; testable personalization |
Mobile journey from enrollment to redemption |
Personalization that cannot be tested |
|
Service and support |
Named team, service levels and review schedule |
Delivery team list; service level terms |
Sales team absent from delivery |
|
Costs and contract |
Total cost over the term; clear data and exit terms |
Proposal in a common format; data export and exit terms |
Low year one, unclear later fees |
|
Track record |
Results with figures and context; similar clients |
Case studies; reference calls |
No similar references |
Shortlist three to five providers against the requirements, send the same questions to each, score the answers on agreed weights, then confirm the leader with demos and reference calls.
Choosing a loyalty program provider comes down to evidence, weighted by what the program needs most: a small self-serve program and a full-service enterprise program will not rank these eight considerations the same way. Define the program first, ask every provider the same questions, request proof for each claim, check security and privacy with documents, compare total cost over the contract term, agree data ownership and exit terms, and speak to clients like the brand before deciding.
|
Evaluating loyalty program providers? Brandmovers designs, builds and runs loyalty programs for consumer and B2B brands, and can walk through each of these considerations for your program. Request a demo to talk through your requirements with the Brandmovers team. |