Loyalty

4.5 out of 57 sold

A loyalty scheme where the customer list is yours. Points on somebody else’s platform are their asset, not yours, and they end when the contract does.

From$449

Open the preview Request a quote

Function: 22
User types: 1
Platform: iOS & Android

React Native
TypeScript
PostgreSQL
Expo

Inside the app

What it does out of the box

22 connected functions on one schema across 1 user type. Everything below is in the template before a line of customisation.

Card
Stamps or points, whichever you run, with progress to the next reward stated as a number rather than implied by a graphic.
Scan to collect
A code the till scans. No phone numbers read aloud in a queue, no app for the staff to learn.
Rewards
What is available, what it costs and any restriction, written plainly. A reward with hidden conditions is a complaint waiting at the counter.
Expiry
Shown well before it happens, and never as a surprise. Expiring points quietly is how schemes lose the customers they were meant to keep.
History
Every collection and redemption with date and place, so a dispute at the till takes ten seconds.
Offline at the till
The code works without a signal and reconciles afterwards. Queues do not wait for connectivity.

User types

One user type, and no confusion.

The staff side is a scan at the till rather than an app, so there is one user type here. A scheme that needs explaining at the counter costs more in service time than it earns in return visits.

Customer
3 of 3 screens
The only user
Collects, sees what they have earned and redeems it. One user type, because a loyalty scheme the customer cannot understand in five seconds is a loyalty scheme nobody uses.
Preview as the customer
- Stamps or points, whichever you run
- Rewards with the rule stated plainly
- Scan at the counter to collect
- Expiry shown well before it happens
- Works without a signal at the till

The limits

What this is not.

The same list we give for every app in the catalogue, because the fastest way to a bad project is a promise made in a meeting that nobody wrote down.

It does not process payments
It records collection and redemption. Money moves through your existing till and payment provider.
It is not a marketing platform
It holds the list and the balance. Campaign sending is a fitted-build addition or an integration with what you already use.
It will not fix a bad offer
If the reward is not worth collecting, better software will not help. We will say so at scoping rather than after launch.
Consumer and data rules are yours
Terms, expiry law and data protection where you trade remain your responsibility. We build to the rules you confirm apply.

Questions

Questions, answered plainly.

If yours is not here, ask it on the call rather than guessing from a pricing page.

Not covered here?

Ask a consultant directly. No form to fill in first, and no follow-up sequence.

Book a consultant All questions

Stamps or points?

Either, configured at scoping. Stamps suit a single repeated purchase, points suit a varied basket. Running both at once usually confuses everybody, so we would push back on it.

What happens to balances if we stop using it?

They stay in your database, because it is your database. That is the difference from a rented scheme, where the balances and the list end with the contract.

Does the staff need an app?

No. The till scans a code the customer shows. Adding another device to a counter mid-service is how schemes stop being used.

Do I get the source code?

Yes, on the same terms as every app here. No licence key, nothing that calls home.