The earning rate
Decide how much spending earns a point, and how many points a bill can earn. Those are numbers you write, not constants of the system.
Changeable at any time
Your points should work the way you wrote them, not the way the software decided. This page covers every setting Looplet actually has — the earning rate, expiry, caps per bill and per day, staff permissions, and a history you can audit.
No card requiredNo POS to buyNothing for the customer to install
These six live on the same screen the shop uses to run its programme. None of them needs the Looplet team to configure it, and none is locked behind a plan.
Decide how much spending earns a point, and how many points a bill can earn. Those are numbers you write, not constants of the system.
Changeable at any time
Three options: never expire, expire after a number of days or months you set, or expire across the whole shop at the end of next year.
A commitment you define
The most points a single bill can earn, which is what stops a mistyped figure or points exceeding what was actually sold.
The counter screen says when it applies
The most one customer can collect in a day, so a single bill or a misuse cannot turn into a large block of points.
Works with the cap per bill
Permissions per role and per branch: a cashier does what a cashier should, and editing the rules stays with the owner.
Branches and staff according to your plan
Every issue of points records who did it, at which branch, for how much, and under which rule at the time. It can be read back later.
Visible in the dashboard
The numbers in these three examples are illustrations of what a rule set looks like, not defaults the system applies and not the price of any plan — your shop writes its own.
Small bills, frequent visits: points should flow steadily rather than arrive in a lump.
Bigger bills, less often: points a customer has not spent should not vanish before they come back.
The unit is a visit, not an amount, and the customer should return within half a year.
Points already issued are a promise the shop made. Changing the earning rate or the expiry therefore applies to the next bill only — it never reaches back and edits what a customer already received, and each record still shows the rate that was actually applied. If a customer asks why last month's bill earned that many points, the answer is in the system, not in a cashier's memory.
The caps per bill and per day work with that history. The first layer stops the mistakes that happen most — a digit typed wrong, an amount entered twice — by limiting the maximum; the counter screen tells staff when the cap has trimmed the entry. The second layer is the trail: every movement of points records who did it, at which branch, when, for how much and under which rule.
Staff permissions are part of the same story. A cashier can issue points but cannot edit the rules, an owner sees every branch, and adding a branch or inviting a staff member are separate actions rather than side effects of some setting.
All of this runs on your own shop's data. Consent is enforced before the first point is issued, and customers can view, correct or delete their own data from the privacy screen — a commitment under the privacy notice (PDPA) published on this site.
The legal detail is in the privacy notice and the terms of service
All three happen in a browser, on the phone or tablet the shop already has, with nothing to install before the first bill earns points.
Open a merchant account, name the shop, and add the branch that will issue points. A branch is where points are recorded, so it comes before the first rule.
Set the earning rate, the expiry and the caps per bill and per day, then invite staff with permissions per role.
The customer opens a mobile browser, scans a QR code or gives a phone number, and the points are on their card immediately with nothing installed.
Still deciding on a plan? See the prices and what every shop gets or go back to the customer's screen while collecting points
Nothing changes. A rule applies to points issued after the edit; points a customer already holds stay under the rule that was in force at the time, and each record still shows the rate that was actually applied. Editing a rule never makes anyone's balance jump or disappear.
It depends on whether you want points to be a liability or an incentive to come back sooner. All three options live on one screen: never expire (points behave like the customer's property), expire after a number of days or months (a nudge to return within a window), or expire at the end of next year (one sweep for the whole shop, easy to audit). You can change it later, and it never applies backwards.
There are two layers. The first is the cap: points per bill and per customer per day are limited to what you set, and the counter screen warns staff when an entry exceeds it. The second is the record: every movement of points shows who did it, at which branch, under which rule, and it can be read back later.
No. A phone, tablet or computer the shop already has is enough. With a camera you can scan QR codes at the counter; without one, look members up by phone number. The customer installs nothing either — it runs in a browser on iPhone and Android.
Your shop's. Member records and points history are not pooled with other shops. Consent is enforced before points are issued, and customers can view, correct or delete their own data and withdraw consent from the privacy screen, under the published privacy notice (PDPA).
Open a merchant account, set the rate and expiry you choose, and let customers collect points in a browser within five minutes.