OneXEOS
Blog detail

Blog detail

Loyalty Program Software for Cafe Chains in Vietnam

Getting started

How a Vietnam cafe chain can pick loyalty software: shared member accounts across branches, reward costing, fraud controls, a pilot plan and metrics.

Loyalty Program Software for Cafe Chains in Vietnam

A regular who buys a flat white every morning at your first branch walks into your newest branch on Saturday and asks to redeem a free drink. The barista cannot see the balance. The customer shrugs, pays, and quietly stops caring about your stamps. Loyalty software for a cafe chain earns its keep when it does three things: it recognises one customer across every branch, it applies one set of earning and redemption rules at the counter without slowing the queue, and it shows you what the programme costs against the repeat visits it creates. This guide walks through how to judge those three things, cost your rewards, run a pilot and measure the result.

Key points before you shop

  • A chain needs one member identity and one balance shared across branches. Paper stamp cards cannot do that.
  • Unredeemed points are a liability you will eventually pay. Good software lets you see the total at any time.
  • Simple rules a barista can explain in one breath beat clever rules nobody remembers.
  • Pilot in a few branches with your real menu and real staff before you roll out.

What changes when a single shop becomes a chain

In one shop, the owner knows the regulars by name and a punch card does the job. Once you operate several outlets, three problems appear. First, customers stop being recognised from branch to branch, so progress toward a reward gets split into small, unfinished piles and the programme feels stingy. Second, each manager improvises: an extra stamp here, a free upgrade there. Reward costs drift, and head office cannot explain why one branch gives away more than another. Third, you lose the ability to answer plain questions such as how many customers return within a month and whether members spend more per visit than walk-ins.

Software fixes this by moving the customer record and the points ledger to a central place, with each till simply reading and writing to it. That makes loyalty closely tied to your point of sale and your customer data rather than a standalone gadget. If you want to see how a customer relationship application sits inside the OneXEOS suite, read about the CRM application and compare it with what your chain needs.

Choose the mechanism before you choose the tool

Software should follow the design of the programme, not the other way round. Four mechanisms cover most cafe chains.

MechanismWorks well whenWatch out for
Points per amount spentOrder values vary a lot and you want to reward spendYou must track the outstanding balance and set expiry
Stamp per drink, free item after NOne signature product dominates salesAwkward with a wide menu, easy to game with the cheapest item
Spend-based tiersA group of heavy users is worth keepingNeeds a few months of data to set sensible thresholds
Targeted offersYou want to pull customers into quiet hoursCan slide into permanent discounting if unchecked

For a young chain, one mechanism run well for a few months is usually better than three layered at once. When you add a second mechanism, decide whether the two stack, and set a ceiling.

A five-part scorecard for evaluating software

Score each vendor from 1 to 5 on the following, and write down the evidence behind every score.

1. Customer identity

Ask how a member is identified: phone number, card, QR code, or something else. Then ask the awkward questions. What happens when two branches create duplicate profiles for one phone number? How do you merge them, and do the points survive the merge? What if a customer changes number? If merging needs a developer to edit the database, expect pain within the first quarter.

2. Rule engine

Can you set different earning rates by product group or branch, exclude discounted items, set an expiry window, and cap redemptions per day? A chain usually has high-margin drinks and low-margin combos; your rules need to protect the second group without confusing the customer.

3. Fit with the till

Is the points balance shown and updated on the same screen the cashier already uses, or is it a separate step? When an order is voided or refunded, do the points reverse automatically? A step that is optional during a rush will be skipped.

4. Controls and audit trail

Who may add points by hand, edit balances or delete profiles? Is every change logged with a user and time? This protects you from both internal abuse and disputes with customers.

5. Reporting and data portability

Look for outstanding points, redemption rate, repeat-visit rate and member revenue by branch. Also confirm you can export your member data. If you cannot take your data with you, switching vendors later becomes very costly.

Costing your rewards: a worked example

Treat every reward as a cost of sales. The basic formula is:

Reward cost as a share of spend = cost of the reward item ÷ spend needed to earn it, adjusted for the share of points actually redeemed.

The figures below are assumptions made up to illustrate the arithmetic. They are not market prices or promised outcomes. Replace them with your own.

  1. Assume the rule is 1 point per 1,000 VND spent, and 100 points buy one free drink.
  2. The customer must therefore spend 100,000 VND to earn the drink.
  3. Assume the free drink sells for 45,000 VND and costs 15,000 VND in ingredients and packaging.
  4. Reward cost at ingredient cost: 15,000 ÷ 100,000 = 15% of that customer's spend.
  5. Assume only 70% of issued points are ever redeemed because some expire or are forgotten. Expected cost: 15% × 70% = 10.5% of member spend.
  6. If your gross margin on drinks is 65% (an assumption), the margin after rewards is roughly 54.5% on member spend. The real question is whether members visit often enough, or spend enough more, to make up the difference.

You can run the same sum for a stamp card or a tier. Change the inputs, and test a pessimistic case where 95% of points are redeemed. If the programme only works when half the points disappear, it is fragile.

Pilot design: prove it before you scale

Do not rely on a vendor demo. Build a small test from your own operation.

  1. Pick two or three branches of different types, for example an office-district shop with a morning rush and a residential shop busiest in the evening.
  2. Write 20 to 30 test cases: new sign-up, existing member from another branch, redemption, refunded order, voided order, mistyped phone number, customer who forgot their number, a manager adjustment.
  3. Let your own cashiers run them without the vendor standing nearby, and time each transaction.
  4. Reconcile at end of day. Do points issued match qualifying sales? Do points redeemed match rewards handed out?
  5. Export the member list and the ledger, and open the files. This is the cheapest portability test you will ever run.

If you already run branches on a unified restaurant and cafe system, it helps to read how café and bubble-tea management software is described, so you can map each test case to the applications you would actually use.

Fraud and leakage in a cafe setting

Loyalty schemes leak in small, repeated ways. Typical patterns:

  • A staff member enters their own phone number to collect points on sales made to customers without a card.
  • Points stay on the account after the sale is refunded.
  • Rewards are handed out on a promise that the balance will be corrected later.
  • One person registers several profiles to claim a welcome gift repeatedly.

Design around these rather than around suspicion. Restrict manual adjustments to managers, cap redemptions per profile per day, require the customer to confirm a redemption through a code or a scan, and review an exceptions report weekly. When you shortlist products, ask which report surfaces accounts with unusual earning patterns.

You are also collecting phone numbers and purchase history. Tell customers plainly what you use the data for and have a process for deletion or correction requests. This is general information, not legal advice; for your exact obligations around personal data, consult a qualified adviser.

Metrics that decide whether to keep, tweak or stop

  • Member attach rate: the share of transactions linked to a member. If it is low, look at counter workflow before you blame the offer.
  • Visit frequency: average visits per month for members versus non-members.
  • Average ticket: member order value versus non-member order value.
  • Redemption rate and outstanding points: your liability and a read on how attractive the rewards are.
  • Member revenue by branch: shows which sites sign people up well and which need retraining.

Reading the numbers: a short scenario

Imagine a branch with 1,000 weekly transactions where 400 are linked to members, a 40% attach rate, against an internal target of 60%. Before touching the reward rules, the manager watches the evening shift and notices cashiers skip the phone-number prompt when the queue builds. The fix is operational: let customers scan a code while they wait for their drink, and set an attach-rate target per shift. The figures here are illustrative; measure your own.

Tying loyalty into chain operations

A loyalty ledger that lives apart from sales data will eventually disagree with your reports. Prefer a set-up where member revenue and ordinary revenue come from the same source. Also check how prices and menus that differ by branch interact with earning rules. Operators weighing centralised control over many outlets can look at the page on multi-branch restaurant and café chain software to see which applications are in scope.

Finally, name an owner. Marketing sets the rules, operations enforces them at the counter, and finance tracks the outstanding-points liability. Without a clear owner, branches start bending rules and the programme loses consistency.

Common mistakes

  • Buying on feature count rather than on whether a cashier can use it at peak.
  • Launching with rewards that are too generous and being unable to pull them back.
  • Forgetting points expiry, so the liability keeps growing.
  • Letting each branch invent its own rules.
  • Skipping the data-export test.
  • Training managers but not the part-time baristas who actually ask customers to join.
  • Counting sign-ups instead of repeat visits.

Frequently asked questions

Do two branches justify loyalty software?

If customers move between them and you want shared rewards, yes, a central ledger is worth having. If the branches are far apart and customers rarely overlap, start simple but pick a tool that can grow with you.

Points per amount spent or stamps per drink?

Points suit varied menus and price levels; stamps are easier to explain when one product dominates. Simulate both on last week's receipts and compare reward cost.

Do we need a branded customer app?

Not at the start. Many chains begin with a phone number or a QR code at the counter. An app starts to make sense once you have a steady member base and plans for pre-ordering or personalised offers. Ask for the ongoing cost before committing.

Should points expire?

Set a reasonable window based on how often your customers actually visit, and state it clearly at sign-up. Open-ended points create an open-ended liability. For the legal wording of programme terms, ask a professional.

How do we know the programme pays for itself?

Compare members with non-members on visit frequency and ticket size, then subtract the reward cost calculated with the formula above. If the gap stays positive over several months, it is working.

Next steps

  1. Write down no more than five earning and redemption rules, and cost them with your own margins.
  2. Prepare 20 to 30 real test cases from your counters.
  3. Ask two or three vendors to run those cases and score them on the five-part scorecard.
  4. Pilot in two branches for a few weeks, tracking the five metrics and reconciling daily.
  5. Roll out to the whole chain only when the pilot numbers are steady and the cashiers are comfortable.
POSCRMInventoryKDSStaffReportsAI Menu

Ready to upgrade the operating system for your business?

You are ready to upgrade the operating system for your business in about 5 minutes. You create an account, pick your industry and switch on the apps you need, with the core plan free forever. No credit card and no long-term contract. You can add a branch at any point. Everything you turn on shares the same 1 data layer.

Loyalty Program Software for Cafe Chains in Vietnam