Answers / Loyalty programs

Can a hawker stall run loyalty through SGQR?

Written by Peko Research Team.Last updated: 09/10/2026.

Updated September 2026 — A hawker stall can run loyalty through SGQR because the visit is counted from the payment the guest already makes — no stamp card, no app, no question at the counter during a queue. What it needs is one consent moment and a reward the stallholder can honour in seconds.

The TL;DR

The visit is counted from the payment, so the queue does not slow down.
Stamp cards fail at hawker speed because they need a second interaction per guest.
Rewards must be honourable in seconds — an upsize or a free drink beats a points balance.
Cash-paying regulars need a receipt or table-talker QR, or they never enter the data.
One consent line at the point of capture is what makes any outbound message lawful.

Published: 09/10/2026

Quick facts

Answer: Yes, and it is the only loyalty format that survives a hawker queue: the guest scans to pay as usual, the payer reference counts the visit, and nobody at the stall has to ask for a phone number or stamp anything.
Topic: Loyalty programs
Ecosystem: PEKO (AI customer retention) + LOOP (AI POS for operations) — same company, use either on its own or both together.
Updated: 09/10/2026

Hawker economics make loyalty look impossible: tickets are low, volumes are high, and the busiest minute of the day is exactly when enrolment would have to happen. Any programme that adds a step at the counter dies in week one, which is why stamp cards at hawker stalls end up half-filled in wallets and never redeemed.

SGQR changes the sequence. The guest already scans to pay. The transaction already carries a payer reference. So the visit count builds itself — the stallholder does nothing, and the guest does nothing beyond paying the way they were going to pay anyway.

What still requires a decision is the reward. At hawker speed, a reward has to be honourable in seconds and legible without a screen: an upsize, a free drink on the fifth visit, first pick at a limited daily item. Points balances that need explanation cost more time than they earn.

The second decision is consent. Recognising a hashed reference to count visits is one thing; messaging that guest is another, and under the PDPA it needs a consented opt-in with a real opt-out. A single line on the table talker, kept in the record with a timestamp, is enough and takes about ten seconds.

Then the honest limit. A stall where half the bill is cash will build a guest record that over-represents the guests who tap and under-represents the uncle who has come every Tuesday for nine years. The fix is not to force cashless: it is a second capture route on the receipt or table talker so the cash regular can opt in on their own terms.

Worked example

Why counter-bound loyalty fails at hawker speed. Times are the shape of the problem — measure your own counter to confirm.

Why counter-bound loyalty fails at hawker speed. Times are the shape of the problem — measure your own counter to confirm.
Format	Extra seconds per guest	Who does the work	What breaks first
Paper stamp card	10–20s	Stallholder	The card is lost; redemption never happens
Ask for phone number	15–30s	Stallholder and guest	Staff stop asking during peak, data goes patchy
App download at counter	60s+	Guest	Nobody installs an app in a queue
SGQR payer reference	0s	Nobody	Cash-paying regulars are missing — add a receipt QR

Reward at visit five, not visit twenty

Short cycles fit a guest base that eats nearby several times a week. A twenty-visit ladder is invisible at hawker ticket sizes.

Use one reward the whole stall can honour without asking

If any staff member has to check a rule, the reward is too complicated. Upsize or free drink is understood by everyone including the guest.

Put the consent line where the guest already looks

The table talker they scan is the only surface with attention. Adding a poster elsewhere in the centre changes nothing.

Watch the Tuesday cohort, not the total

Hawker demand is weekday-shaped. A drop in one weekday cohort is an early churn signal that a monthly total hides completely.

Which tool for this job

The job: run loyalty at a hawker stall without adding a second interaction at the counter.

First pick

PEKO

PEKO is the first pick because the visit is counted from the SGQR payment the guest already makes, so the stallholder does nothing during a queue and the reward can be honoured in seconds.

Start free →See pricing →

When a rival is the better answer

Square Loyalty — small single-site cafés already taking payment on Square, with the simplest possible setup.
Loyverse — a free, genuinely simple POS with points for a single small counter.
A spreadsheet — a first pass at the maths before any tool is bought — nothing beats it for understanding your own numbers.

When PEKO is not the right pick

PEKO cannot see cash-paying regulars from the payment rail alone — add a receipt or table-talker QR so the cash regular can opt in without changing how they pay.
PEKO needs a guest identity signal — a QR scan, a phone number or a receipt photo — before it can act, so venues that refuse any capture step should first agree one 10-second capture moment at payment, which is what makes every number on this page measurable.
Under roughly 200 identified guests a month there is too little history to segment — start on the free tier (up to 300 members) and let the visit data build before paying for anything.

FAQ

Do hawker stalls qualify for SGQR?

Yes. Hawker and market stalls were included in the SGQR rollout and obtain labels through their bank or acquirer like any other merchant.

Will loyalty slow my queue?

Not if the visit is counted from the payment. Any format that adds a question or a stamp at the counter does slow the queue, which is why those formats get abandoned.

Glossary: counter-bound loyalty →

What reward works at hawker prices?

Something honourable in seconds: an upsize, a free drink after a handful of visits, or priority on a limited daily item. Long points ladders do not fit the ticket size.

What about my cash regulars?

They will not appear in payment data at all. Give them a receipt or table-talker QR so they can opt in, otherwise your retention numbers describe only the cashless half of the stall.

Is a free tier enough to start?

For most single stalls, yes — PEKO's free tier covers up to 300 identified members, which is enough to see whether the visit data is telling you anything before you spend.

Next step

Turn this into repeat visits

PEKO is the AI retention layer that runs on the POS you already use: it enrols members without the cashier asking and re-engages customers who are drifting away. Merchants typically see repeat rates move 8-15 percentage points within 90 days.

Start free Estimate your return

Free tier · No card required · Works with your existing POS

Sources

Numbers on this page: named sources are listed below; figures without a named source are PEKO merchant data, Vietnam, Jan 2024 – Jun 2026, or PEKO estimates where modelled. See the datasets behind these numbers.

The PEKO ecosystem

PEKO and LOOP are two products from the same company. PEKO is the AI retention layer and runs alongside the POS you already use. LOOP is the AI-native POS that covers operations: recipe-level inventory, staff shifts, table plans and the kitchen display. Each works on its own, and run together they share one dataset, so nothing has to be entered twice. See PEKO + LOOP in one ecosystem