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 attributes to a named person without anyone filling in a form:
- Visits punched. Who was on the counter when the stamp went on the card.
- Purchases recorded. Who rang the sale through the counter surface, and for how much.
- Redemptions handled. Who processed the reward, a fair proxy for who explained it.
Enrolment is the obvious fourth, and it is the one to be careful about. A signup is not credited to a staff member 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 line to a ticket is a real skill, and it is not something the counter attributes to a person 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: hours worked, or transactions served, taken 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. Attribution has to be captured as the action happens, by whoever is signed in on the shared device — which is why in-store loyalty and staff attribution are one build, not two.
A target is not a mechanic
A target
"Twenty signups this month." It states an outcome. It does not say what happens at nineteen, who checks, or when the reward arrives. Most schemes in small shops are only this, on a whiteboard, decaying at the speed of the owner's attention.
A mechanic
A rule that turns a countable action into a reward automatically, on a budget the owner sets once. It runs on the shifts the owner is absent. It answers the nineteen question before it is asked.
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: divide attributed actions by hours worked, or by transactions served, before comparing anyone.
Two staff, same month
Assumptions: A works 62 hours and records 47 attributed counter actions. B works 24 hours and records 22.
Raw totals: A leads 47 to 22. Per hour: A is 47 ÷ 62 = 0.76, B is 22 ÷ 24 = 0.92. On the normalized rate, B leads.
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 — give everyone the same per-action threshold and let each person earn independently.
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.
| Question | Spreadsheet or paper tally | POS team reporting | Purpose-built staff mechanic |
|---|---|---|---|
| Who gets credit | Reconstructed later, from memory | Whoever was signed into the till | The person attached to the action when it happened |
| Reward delivery | The owner remembers, or does not | Usually none — reporting only | An allowance the staff member draws down |
| Shift fairness | Manual, and argued about | Raw totals favour long shifts | Per hour, per transaction, or no ranking at all |
| Owner effort | Recurring, every week | Low, but reading is not rewarding | Set the rate and prizes once |
| Where it fails | The first genuinely busy week | Staff see totals and nothing follows | Prizes set too low to be worth chasing |
How Rewardfinity runs it
Those three counter actions are attributed to the staff member who performed them and convert into spins on a staff-facing wheel. The owner sets one number — how many attributed actions buy a spin — and the allowance is arithmetic you can check by hand:
spins available = floor(staff counter actions ÷ earnEvery) − spins already taken
Working the allowance
Assumptions: earnEvery is 10. A staff member has 47 attributed actions and has taken 3 spins.
floor(47 ÷ 10) = 4 earned. 4 − 3 = 1 available now. The fifth appears at 50 actions. Nothing accrues invisibly, nothing is owed retrospectively.
The prize table is yours, so cost is bounded by what you put on it rather than by how good the month was. It runs on the shared device the counter already uses, covered under staff devices. Staff gift cards are Coming Soon — the merchant features under gift cards are customer-facing, so hand any card-based staff reward over outside the software for now. Plan boundaries move as packaging changes, so check pricing first.
Questions owners ask about staff incentives
What is staff incentive software?
Software that attributes counter actions to individual staff members and converts those actions into a reward the person can claim. It differs from bonus and payroll tools in what it measures: visits punched, purchases recorded and redemptions handled at the till, not annual objectives. It runs on the device already at the counter.
How do you track which staff member served a customer?
The person is identified as the action happens, not reconstructed afterwards. Whoever is signed in to the counter surface when a visit is punched, a purchase is recorded or a reward is redeemed receives the credit, and the record is kept per person. Enrolment is the exception worth stating plainly: a signup is not attributed to a staff member today, so do not build the scheme on it. Tallies written up from memory are where manual schemes break, because the disputed cases are always the busy shifts nobody remembers clearly.
Do leaderboards actually motivate counter staff?
For a few weeks. A leaderboard stops working once the ranking settles: the person on top is safe, everyone else can see they will not close the gap, and the middle disengages. A leaderboard is a display, not a mechanic. Pair it with something each person earns on their own count.
How do you make staff incentives fair for part-time workers?
Compare rates, not totals. A forty-hour week out-counts a twelve-hour week every time, and weekend shifts see more customers than quiet weekday ones. Divide each person's attributed actions by hours worked, or by transactions served, before comparing anyone. Simpler still, drop comparison: give everyone the same per-action threshold and let each earn independently.
Can you reward staff with gift cards?
Staff gift cards are Coming Soon in Rewardfinity, so that reward cannot be run inside the product today. What ships now is a staff-facing spin wheel with prizes the owner defines and an allowance calculated from attributed counter actions. If a gift card is essential, plan to hand it over outside the software until the staff version ships.
Are staff incentives the same as a pay rise?
No, and treating them as interchangeable causes problems. An incentive is recognition attached to a specific action, usually small and frequent. Compensation is what someone is owed for turning up. If the base rate is wrong or the rota is short-staffed, an incentive will not repair it — it asks tired people to do more for a prize.
Set the rate, set the prizes, leave it running.
Decide what counts as an action, and how many buy a spin, before you announce anything.