Running one loyalty program across several shops

What breaks when you open the second site

At one counter, a loyalty program runs on shared understanding. Everyone knows what counts as a qualifying visit because everyone was there when it was decided.

At two, that stops being true within weeks. The failures are consistent:

• The rule drifts. One shop stamps a takeaway coffee, the other does not. Neither is wrong; nobody wrote it down.
• The customer finds the seam. Someone earns at one site and tries to redeem at the other, and the answer depends on who is behind the counter.
• The weaker site disappears into the average. Business-wide totals look healthy while one location’s program has quietly stopped being offered.
• Staff permissions sprawl. Everyone ends up with access to everything because it was easier than deciding.

None of these are technical problems. They are decisions that a single site let you avoid making.

The four decisions

1. One card, or one per site?

Almost always one. A customer who visits two of your shops is your best kind of customer, and giving them two half-finished cards punishes exactly that behavior.

Run separate programs only when the sites are genuinely different businesses to the customer — a café and a wine bar under one company, with different rewards and different reasons to visit. Not when they are the same shop in two streets.

2. Where can a reward be redeemed?

Decide before someone asks. “Anywhere” is the right default and the one customers assume. If a reward can only be claimed at the site where it was earned, that is a rule, and it belongs on the card rather than in a conversation at the counter.

The cost of “anywhere” is that one site absorbs the reward cost for visits another site earned. Between your own shops that is bookkeeping, not a loss.

3. What counts as a qualifying visit, exactly?

Write it as one sentence that a new starter can apply without asking. Not “a purchase” — which purchase. Not “a visit” — including the one where they only bought a bottle of water?

The test: if two members of staff at different sites would answer differently, it is not written tightly enough yet.

4. Who can do what, at which site?

A manager at one shop does not need the ability to edit the program for all of them. Decide two things per person: which sites they work at, and which of the program’s controls they need.

Why per-site numbers matter more than the total

A combined figure hides the thing you most need to know: whether the program is actually being offered.

A location where staff have quietly stopped mentioning the card produces a stamp count that falls while the business-wide total stays flat, carried by the other sites. From the top-line dashboard, nothing appears wrong for months.

Three comparisons worth making regularly:

• Joins per site, relative to footfall. A site with similar traffic and a third of the joins has a counter problem, not a customer problem.
• Stamps per join. Low means people join and are never stamped again — the card is being offered but not used.
• Redemptions per site. Rewards earned but never claimed usually means staff are unsure how to confirm them.

Each one points at a specific, fixable thing, and none of them are visible in a single number.

Launching the program at a new site

Do not assume the second opening inherits the first one’s competence.

1. Write the rule down and put it where staff can see it, not only where customers can.
2. Give the site its own join poster so you can tell where a customer actually started.
3. Walk one full cycle before opening: join, stamp, earn, redeem. Do it as a customer would, on a phone, at the counter.
4. Check the numbers at two weeks, not at three months. The failure mode is silence, and silence looks fine from a distance.

Doing this in NeoLoyal

Outlets are the counters. They share the business’s card and customer list, so one program covers every site, while each outlet mints its own join code — which is what makes “where did this customer start” answerable rather than inferred.

Stamps and visits are attributed to the outlet that issued them, so the per-site comparisons above read directly off the dashboard instead of needing to be reconstructed.

Staff can be assigned to specific outlets or left unassigned for access to all of them, and permissions are set per person rather than inherited from a role — so a site manager can be given the program controls they need without gaining the ones they do not.

Closing a site deactivates it rather than deleting it, so the history attached to those stamps still reads back correctly afterwards.

How many outlets can run live at once depends on the plan; the free and Starter tiers cover a single counter.

The summary

Multi-site loyalty is not a harder version of single-site loyalty. It is the same program with the unwritten parts made explicit, because the shared understanding that carried it at one counter does not survive the second.

Write the rule, give each site its own front door, read the numbers apart, and decide who can touch what. The rest is the program you already had.