Good people.
Going further.

Why the customer program stalls without the staff half

Loyalty programs are designed around the customer: the earn rate, the reward, the member page. Whether any of it works is decided by a sentence someone says at the counter, while a queue forms and a card reader waits.

That sentence is real work and invisible work at once. In week one it happens because it is new. In week two it happens on the shifts the owner works. In week three it quietly stops, and nothing in the dashboard explains why — enrolments flatten and the program looks like it failed.

Usually it did not. The ask stopped. A well-built customer loyalty program and an unmanaged counter are two systems, and only one is measured. The staff half decides whether the customer half gets a fair test.

What a counter can actually prove

Three things happen at a till that Rewardfinity credits without anyone filling in a form. Each is credited to the staff scanner key signed in on the web counter page at the moment it happens:

• Visits punched. Which key was signed in when the stamp went on the card.
• Purchases recorded. Which key rang the purchase through the counter page.
• Redemptions handled. Which key processed the reward, a fair proxy for who explained it.

Credit follows the key, not the face behind it. Give each person their own scanner key from the owner's dashboard; two people sharing one key share one count, and the software cannot split it afterwards. Scans made in the paired Staff app do not count toward the staff wheel today — the web counter page is the surface that earns.

Enrolment is the obvious fourth, and it is the one to be careful about. A signup is not credited to staff today, so a scheme built on "who signed the most people up" cannot be settled from the record — it would come down to memory, which is the thing you were trying to escape. The same goes for add-ons: attaching a second item to a ticket is a real skill, and it is not something the counter credits here. Count the three that are keyed instead. They sit either side of the ask, close enough to reward the behaviour without inventing a number.

You still need a denominator, and it does not come out of the software: Rewardfinity stores no hours or shift data. Take hours worked, or transactions served, from the rota you already keep. Without one you are ranking the roster rather than the people on it.

A counter cannot prove the attempt that failed or how warmly the offer was made. Those belong in a conversation, not a scoreboard. The set is narrow on purpose: a number staff can dispute will be disputed. Credit has to be captured as the action happens, which is why in-store loyalty and staff credit are one build, not two.

A target is not a mechanic

Leaderboards alone go stale for a structural reason. Once the ranking settles, the person on top is safe and everyone below can see the gap. Both ends stop competing. A leaderboard is a display; pair it with something each person earns on their own count.

Fairness across shift length, day mix, and part-timers

Raw totals reward the rota, not the person. A full-timer out-counts a twelve-hour-a-week student every month, and Saturday sees more customers than a wet Tuesday. Rank on totals and the part-timers disengage first. The fix is arithmetic you do with your own rota: divide credited actions by hours worked, or by transactions served, before comparing anyone.

Per-transaction normalization is stricter again: it removes the quiet-shift penalty as well as the short-shift one. Simplest of all is to skip comparison — which is how the staff wheel works: everyone earns on the same per-action threshold, independently, and nobody's spin depends on anyone else's count.

Recognition, compensation, and what an incentive cannot fix

Recognition is small, frequent, and tied to a specific action. Compensation is what someone is owed for turning up, and it is contractual. Blurring them is how these schemes become resented: once a reward is counted on as income, it is a variable wage without the protections.

The honest note: an incentive does not fix an understaffed rota. If two people cover a three-person shift, asking them to also pitch the program is asking tired people to do more for a prize. Incentives make an easy thing habitual, not a hard thing possible.

Three ways small businesses run this

Most shops land in one of three places. The differences show up in who gets credit, and in whether anything happens when the owner is out.

How the Rewardfinity staff wheel works

Those three counter actions, credited to a scanner key, convert into spins on a staff-facing wheel. The owner sets one number — earnEvery, how many credited actions buy a spin, from 1 to 1,000 — and the allowance is arithmetic you can check by hand:

spins available = floor(counter actions on this scanner key ÷ earnEvery) − spins this key has taken on this wheel

Two properties to know before you announce it. The count is all-time: actions recorded before the wheel existed still count, so a new staff wheel opens with spins already earned — the key above would start a fresh wheel with 4. And there is no monthly reset. A new scanner key starts from zero. The wheel's start and end dates control when spins can be taken, not which actions count.

The prize table is yours, and so is the handover: the product records the win and the owner fulfils it, so cost is bounded by what you put on the wheel rather than by how good the month was. A points prize on a staff wheel is treated as an item to hand over, not a balance. Staff sign in to the web counter page with the key you issue, on the device already at the counter — covered under staff devices. Plan boundaries move as packaging changes, so check pricing first.