Ten questions to ask a loyalty software vendor

The short answer

Ten questions decide whether loyalty software will still be running in your shop a year from now, and none of them are on a feature list. They cover joining, stamping, cheating, exporting, non-payment, price growth, message metering, multiple sites, staff permissions and rule changes.

Ask all ten before you buy. Three of them, the export format, the price shape and what happens if you stop paying, cannot be renegotiated later, because by then your customer list and every balance live inside the product you are trying to leave.

The checklist

Work down the column on the left. The column on the right is what disqualifies a vendor rather than what disappoints you.

	Ask this	An answer that should end the conversation
1	Can a customer join without installing an app?	“They just download our app, it takes a second”
2	Can the person on shift issue a stamp without the owner?	“The owner approves them in the dashboard”
3	What stops a customer stamping their own card?	“Customers are honest, it’s never been an issue”
4	Can I export my customer list and balances, and in what format?	“You can request an export from support”
5	What happens to the data if I stop paying?	“The account is closed after the grace period”
6	How does the price change as customers grow?	“It’s just pennies per member”
7	Are messages metered separately?	“Emails are credits, they’re very cheap”
8	Are balances shared across my sites?	“Each location gets its own program”
9	What can a staff member do and not do?	“Everyone gets a login to the dashboard”
10	Can I change the reward without breaking cards already out?	“You’d just start a new program”

1. Can a customer join without installing an app?

Every step between “I’ll have that” and “I’m on the card” loses a share of the people offered it, and those steps are paid at the busiest minute of the transaction. A store search, a download, an account and a first open is four chances to be told no by someone with a queue behind them.

A bad answer sounds like the install being described as trivial. It is trivial for the person who built it. Ask instead for the number of people who scanned the poster and finished, and if the vendor does not measure that, they are not measuring the thing that decides whether you get a program at all.

2. Can the person on shift validate a stamp without the owner?

A loyalty program is used by whoever happens to be working at 8:15 on a Saturday. If a stamp needs the owner’s login, the program runs only on the shifts the owner works, and everyone else quietly stops offering it.

A bad answer sounds like approval living in the owner’s dashboard, or a single shared account that everybody uses. Both mean the same thing in practice: nobody is accountable for a stamp, and nobody on shift is confident enough to hand over a reward.

3. What stops a customer stamping their own card?

If the customer can advance their own balance, the count stops being evidence and becomes a self-reported number. That matters most on the day someone presents a full card you have no record of filling.

A bad answer sounds like an appeal to honesty, or a QR code taped to the counter that anybody can scan repeatedly. Ask what specifically prevents a second stamp in the same visit, and who has to be present for a stamp to exist. There should be a person in that answer.

4. Can you export your customer list and balances, and in what format?

Ask before you have a list worth exporting. The useful version of this question has a file format in it, because “yes, you can export” and “yes, you can download a CSV containing every customer, their contact details, their current balance and their redemption history” are different promises.

A bad answer sounds like an export you have to request from support. That is not an export, it is a favor, and favors stop when the relationship does.

5. What happens to the data if you stop paying?

There are three possible answers and they are very far apart. The account can drop to a free tier and keep serving existing cardholders. It can freeze, so nobody can be stamped and nobody can redeem. Or it can be deleted after a grace period.

The version that punishes your customers for your billing is the one to avoid, because they did nothing and they will not read a billing notice. There is more on how free tiers behave at their limits in what free actually buys you.

A bad answer sounds like vagueness about the grace period, or a closure that takes the balances with it. Get this one in writing.

6. How does the price change as customers grow?

The pricing shape matters more than the headline number, because two of the common shapes bill you for succeeding. Per-member pricing rises with every person who joins. A percentage of transactions is a permanent charge on revenue you would have taken anyway.

Do the arithmetic at the customer count you are aiming for, not the one you have. A tool that is cheap at 40 customers and unaffordable at 400 has priced you out of your own goal. The four line items in a loyalty budget are worked through in what a loyalty program actually costs.

A bad answer sounds like a per-member rate quoted as a small number without a total attached. Multiply it yourself, in front of them.

7. Are messages metered separately?

A loyalty program builds a list, and the list is where the second invoice lives. Email and SMS have a real delivery cost, so metering them is honest, but it has to be visible before you build a habit of sending.

Find out the allowance on the tier you would actually buy, what an extra message costs, and whether an automated sequence draws from the same meter. A tool that sends four automated messages per customer per month is spending your allowance without a decision from you.

A bad answer sounds like “credits”, with no exchange rate and no monthly allowance named.

8. Are balances shared across your sites?

If you have a second site, or intend to, this is the question that separates one program from several. Customers assume a stamp earned at your High Street shop counts at the station one. A tool that duplicates the program per location produces an argument at a counter, in front of other customers, within the first month.

Also ask whether reporting can still separate the sites. Shared balances and separate numbers are both needed, and some tools give you one or the other. The practical detail is in running one program across several shops.

A bad answer sounds like each location getting its own program, described as flexibility.

9. What can a staff member do, and what can they not do?

Roles are the difference between giving a new starter the stamp button and giving them your customer list. The permissions worth asking about individually are issuing stamps, confirming redemptions, adjusting a balance by hand, seeing customer contact details, changing the program rules, and sending messages.

Ask what an invite looks like too, and whether it expires. A staff account that outlives the staff member is a real exposure, and it is the most common one in small businesses because nobody remembers to revoke it. Who on your team can do what breaks the same question down by role.

A bad answer sounds like one login for the whole shop, or “everyone gets the dashboard”.

10. Can the reward rules change without invalidating cards in circulation?

You will change the reward. The target will be wrong, or the coffee price will move, and the question is what happens to the eleven people who are seven stamps into the old version.

There are two acceptable answers. Existing cards keep the terms they were issued under until they are completed, or every card is migrated and each holder is told. There is one unacceptable answer, which is that the change resets progress silently.

A bad answer sounds like being told to start a new program. That is the vendor describing a limitation as a workflow, and you will be the one explaining it at the counter.

What to do with the answers

Six of the ten can be checked yourself in a trial. Numbers 1, 2, 3, 8, 9 and 10 are all observable: join your own program on your own phone, have your newest staff member issue a stamp with no training, try to stamp yourself twice, and change the reward on day ten to see what happens to a card already in circulation.

The other four are answers you should hold in writing before you start, because they describe what happens after the relationship ends. Send this, verbatim, and keep the reply:

What format is the customer export in, and does it include balances and redemption history? What happens to our data and our customers’ balances if we stop paying? What is the total monthly price at 500 customers? Are marketing messages metered, and what is included at that tier?

NeoLoyal is one of the tools this list is meant to be used on, which is a reason to check its answers against the ten rather than to take the list on trust. The categories these questions apply differently to are in loyalty software, apps and card apps compared, and the wider evaluation sits in how to choose loyalty program software.