The Best Loyalty Program in Saudi Arabia: How to Choose, and What It Costs

The seven criteria that actually decide it

Feature lists are close to useless when comparing loyalty products, because every vendor lists the same twenty things and the differences hide in how each one behaves on a busy Thursday. These seven questions separate the options far faster:

1. Does your customer have to install anything? This determines your join rate more than any other factor, and it is binary rather than a matter of degree.
2. Where do your sales actually happen? In a shop, online, or both. A tool built for e-commerce checkout will be awkward at a physical till, and the reverse is equally true.
3. Is the price published? Not whether it is cheap — whether you can find it without a sales call.
4. Is Arabic native or translated? Ask to see a real card on a real phone in Arabic.
5. Can you export your member list? The list outlives the vendor. Make sure it can leave with you.
6. What happens at branch two? Even if you have one location today, ask now; retrofitting is painful.
7. Who fixes it when Apple changes something? Wallet formats change. Somebody has to keep up, and if that somebody is you, factor it in.

The five approaches, compared

Nearly every loyalty option sold in Saudi Arabia falls into one of five categories. Comparing categories rather than brands is more durable, because vendors come and go while the trade-offs stay put.

The row that surprises people is the marketplace app. If your business is a Salla or Zid store, a loyalty add-on inside that platform integrates cleanly with online checkout and is the sensible choice for online orders. What it generally does not do is work well at a physical counter, because it was designed around a web basket rather than a queue. Businesses with both need to be honest about which side carries more revenue.

The POS-bundled row carries a subtler trade-off. Operationally it is the simplest option — one system, one screen, one supplier — but it welds your loyalty programme to your point-of-sale contract. Changing POS vendor later means rebuilding the programme and, in some cases, losing the history that made it valuable.

How much does a loyalty program cost in Saudi Arabia?

This is the question the existing Arabic results answer worst, largely because most vendors do not publish a price. Here is what is actually discoverable, with the caveat that anything not published by the vendor is left blank rather than guessed at.

Two of those rows deserve elaboration.

Custom development is priced wrong in most people's heads. A software house quoting 15,000 to 50,000 SAR is quoting version one. The recurring expense arrives afterwards, and it is not optional: Apple and Google both revise their wallet pass formats, iOS and Android ship yearly, and a system nobody is actively maintaining eventually stops issuing passes on new devices. A platform spreads that engineering across every customer it has; a bespoke build makes you the only one paying for it.

"Contact us for pricing" is a commercial model, not a scandal. It lets a vendor quote each business according to size and budget, and it is entirely normal in enterprise software. But it costs you time and makes genuine comparison hard, so ask early and ask for everything: setup, monthly, per branch, per customer, and any percentage of transactions.

Does your customer have to install anything?

If you take one thing from this page, take this. Every loyalty programme has a join step, and the join step is where almost all of them fail.

Ask a customer at a busy counter to download an app, wait for it, create an account, verify a code and then earn their first point, and you will lose most of them. Worse, you pay that toll on every new customer, forever — it is not a launch cost, it is a permanent tax on acquisition. The customers who do install are disproportionately the ones who were already loyal, which means you have spent effort rewarding behaviour you already had.

A wallet pass sidesteps the problem instead of optimising it. The wallet is already on the phone; joining is one QR scan and a few seconds, with no account and no permissions requested. And because the pass lives in the app people open to pay for things, your card reappears in front of them at the moment they are deciding where to spend — a placement no standalone app can buy.

The mechanics of how a pass is built, and how Apple's format differs from Google's, are covered on our digital loyalty cards page.

Arabic and RTL, done properly

Every vendor selling into the Kingdom says it supports Arabic. The claim is nearly meaningless on its own, because there is a wide gap between a translated dashboard and a product that was built right-to-left.

The dashboard matters least — you are the only one who sees it, and you will learn your way around a mediocre one. What matters is everything your customer touches: the wallet pass itself, the join screen, the notification text, dates and numbers. Those are seen constantly, by people who will judge your business by them.

Three questions cut through the claim quickly:

• Can I see a real Arabic card on a real phone, not a mockup?
• Do notifications arrive in Arabic, with correct text direction on the lock screen?
• Is the customer-facing join page right-to-left, or an English layout with Arabic words in it?

Ask for a live example rather than a screenshot. A vendor who has genuinely done the work can produce one in a minute; a vendor who has run their English product through a translation layer will offer you a demo call instead.

Who owns your customer list

The rewards are the mechanism. The member list is the asset — and it is the thing that still has value in three years when you have changed your offer twice.

Get clear answers to three questions before you start collecting anything:

• Can you export it? In a usable format, on demand, without a support ticket or a fee.
• Does the vendor market to your customers? Some platforms build a consumer-side audience from merchant data. That may be acceptable to you, but you should be choosing it rather than discovering it.
• How is the data protected? Your data and your customers' data should stay protected by whichever platform you pick. A programme that asks for the minimum, states plainly what it does with it, and requests no device permissions is easier to run and easier to defend.

Our own position on data handling is set out on the security page. Whatever you choose, get the answer in writing before the list exists rather than after.

Choosing by industry

The general answer only gets you so far; the mechanic that fits a barber is wrong for a restaurant. We have worked the numbers through separately for eleven kinds of business, each with its own visit cycle and margin structure:

• Cafés — short cycles and a repeating product; stamps almost always win.
• Restaurants — widely varying bills, which points and cashback handle better.
• Salons and barbershops — long gaps between visits, so short cards.
• Car washes — bulk purchases, where multi-stamp visits matter.
• Gyms — retention is about attendance, not spend.
• Retail stores — mixed baskets and thinner margins.
• Clinics and hospitals — recall matters more than rewards.
• Flower shops and pet stores — occasion-driven and habit-driven respectively.

If you would rather start from the mechanic than the industry, the five options are laid out side by side on our loyalty cards page, and the broader strategy behind running one is on the customer loyalty program guide.

Five mistakes that kill a programme in month two

Most failed loyalty programmes were not beaten by a competitor; they were configured badly at the start and quietly abandoned. These five account for the large majority:

1. A reward too far away. Multiply your visit gap by your goal. If the reward is more than about three months out, nobody is chasing it and every stamp you gave was wasted.
2. Choosing the mechanic before doing the arithmetic. A buy-five card costs roughly 5% on café margins and closer to 15% on thin retail margins. Same card, different business, very different bill.
3. No launch push. A programme nobody knows about does nothing. The QR needs to be where people wait, and staff need one sentence to say.
4. Staff who were never briefed. The counter is the whole distribution channel. If the cashier does not mention it, the programme does not exist.
5. Changing the rules in week two. Give it sixty days before you touch anything, or you will never know whether it worked.

Where Niqati fits

We build the fifth category — a wallet-pass platform — so treat this section as what it is: our own case, stated plainly so you can weigh it against the criteria above rather than take it on faith.

Niqati issues loyalty cards in your branding directly into Apple Wallet and Google Wallet, with nothing for your customer to install. It runs five reward mechanics — points per riyal, points per visit, stamps with a goal you set from three to nine, cashback, and manual awards — with lock-screen notifications, per-branch reporting, staff permissions, and an Arabic-first interface on both the merchant and customer side. Pricing is published: a permanently free plan, Pro at 49.99 SAR per month, and Enterprise for chains needing the API and POS integrations.

Where we are not the right answer: if you sell entirely online through a marketplace store, an add-on inside that platform will integrate with your checkout more tightly than we do. If you are a large chain already deeply committed to a POS vendor with its own loyalty module, the operational simplicity of one system may outweigh what you give up. And if loyalty is itself your product, you should be building rather than buying.

For everyone else — physical shops, cafés, salons, clinics, multi-branch retail — the wallet-pass approach removes the join problem that sinks most programmes, and you can test that claim in about ten minutes without speaking to anybody.

Frequently asked questions

Written by the Niqati team, who build one of the options compared above — stated openly so you can weigh it accordingly. Last reviewed 14 August 2026. Third-party figures are those the vendors or the market publish openly and were accurate at the date of review; where a vendor does not publish a price we have said so rather than estimate. Niqati's own prices are our published rates.