Skip to content
ENS.EG

A Customer Loyalty App: When to Build It, How the Rules Work, What to Launch First

31 Oct 2026

A stamp card is enough for one branch and one rule. An app is worth building when you have several branches or staff can grant points with no trace. This guide covers rules, fraud and staff override, with no invented redemption figures.

An owner asks for a points app because the paper card gets lost, because a second branch does not know the customer of the first, or because a cashier hands over a free item for a familiar face. Those are different problems. The first may still be a plastic card the staff trust. The second and the third need a ledger that does not live in the till drawer. Start from the problem that is costing you, not from the look of an app in an ad.

The app is a loyalty program the customer opens to see a balance, and the cashier opens to confirm a sale. It is not a store and it is not a menu. If the sale itself is still a notebook, points on top of the notebook will break at the first argument. The event that earns points has to be an invoice you recognise: a number, an amount, a branch and an employee.

When a card is enough

  • One branch, staff who know the regulars, and one stamp per visit.
  • The reward is a single clear item, such as a drink after a number of visits you write down and keep.
  • You do not need to message the customer between visits, and you do not need a report of who stopped coming.
  • Arguments are rare because the manager stands at the same till.
  • You have no plan for a second branch in the coming months that will ask for this customer balance.

When the app is the tool

Build the app when the customer moves between branches, when the rule differs by product, or when you want a grant of points to leave a trace the manager can see. A phone in the customer hand is more reliable than a card left at home, provided identity is a mobile number or a live code on the screen. A saved photo of an old code is not proof. The cashier sees the code change, or searches the mobile number stored on the invoice.

Write the points rule before any screen is designed. How many points per pound, or one point per visit regardless of the amount. Whether points expire, and who sets the period. What can be redeemed: a named item, or a discount with a floor. Whether points and an existing offer may sit on the same invoice. Those four decisions are the product. Leaving them until after programming means the screen is rebuilt. We do not publish a redemption rate here, and we do not claim that customers redeem at any particular pace. That is measured from your own ledger after go-live, not from a sales line.

Fraud you should name up front

  • A customer shows a photo of a code that belongs to another person, instead of the live screen.
  • A staff mobile number collects points from customer invoices onto a personal account.
  • A cashier posts points with no matching invoice in the till.
  • A redemption is followed by a voided invoice, and the item still leaves the shop.
  • One manager code known to the whole shift, so override becomes the habit.

Each case is closed by a visible rule. A photo of a code is refused when the screen must be live. Points attach to an invoice number, and a manual grant needs a higher permission. A void after redemption either returns the points or blocks the void until a manager reviews it. A shared code is replaced by a code per manager, and the name is stored with the reason. The app does not stop a determined person if the invoice itself is fake. It makes the fake visible on a report the owner can open.

Staff override

Sometimes a manager should grant courtesy points when a customer waited too long or received a faulty item. Keep that button away from the ordinary cashier. Leave it with a manager code, and require a reason from a short list: delay, defect, an agreed compensation. The log stores who granted the points, when, and on which invoice. Without that log the exception becomes the rule and the points stop meaning anything. Courtesy should not be a silent path.

The first release worth shipping identifies the customer by mobile number, runs one earn rule and one reward, shows the balance to the cashier before the invoice closes, and records a manager override with a written reason. Tiers, a birthday gift and push campaigns come after a sample of invoices matches the points balance for two weeks. A daily notification before the balance is trustworthy trains the customer to ignore the app.

What to leave out at the start

Do not open with a long prize catalogue or with every payment method. Start with the channel that produces most invoices today, even if that channel is the branch till. If a slice of sales still happens on WhatsApp with no invoice, agree this in writing: those sales do not earn points until they enter the same ledger. A silent WhatsApp exception brings the fraud back through another door.

Who this decision is for

The decision shows up in retail more than in other trades: clothing, a small multi-branch grocery, a café with more than one address. A clinic and a school have a different relationship with the visitor, and purchase points are not their tool. If you sell repeatedly from a branch, the question is card or ledger. If you sell once a year, the app is a cost with no weekly use.

The customer app is built as mobile app design and development. The retail setting, branches and online selling, is retail and ecommerce.

Describe the branch count, the earn rule you want now, and whether staff grant points by hand, from start your project. The WhatsApp button at the bottom of the page is the place to send a photo of the current card, or the sentence the cashier already says to the customer.

Have an idea or a system that needs building?

Tell us about your project in three short steps. We will review it and contact you to agree on the next step.

Start a project