Most UAE small businesses should not build a branded loyalty app. That is the honest answer, and it belongs before the price list rather than buried after it.
The reason is not cost. It is frequency. An app has to earn permanent space on a phone, and a customer who visits your cafe twice a month will not keep one installed to collect stamps. Many will download it for the sign-up bonus, use it once, and delete it the next time storage runs low. You will then be paying to maintain software that a shrinking number of people open.
This guide covers what a loyalty programme actually needs, the ladder of options from a free feature you may already own up to a full branded app, what each costs, and the point where building an app becomes a reasonable decision rather than a vanity one.
Should you build a loyalty app? Start with frequency
Before any technology decision, answer one question honestly: how often does a typical customer buy from you?
If the answer is weekly or more, and the app would do real work beyond holding points, an app is worth discussing. Ordering ahead, paying at the table, booking a slot, tracking a delivery. In that case the loyalty layer is a feature of an app that would exist anyway.
If the answer is monthly, or it varies, or most of your customers are passing trade, an app is the wrong tool. Not a cheaper app. Not a better designed app. The wrong tool. No amount of design fixes a customer who has no reason to open it between visits.
Apple's own behaviour is a useful reality check here. Apple runs a process that can flag apps which have not been updated in a long time and attract very few downloads, giving the developer a window to update before removal [1]. Low-engagement apps are a known problem that the platform itself manages against. A loyalty app for one shop is a strong candidate to become one.
Loyalty programme options in the UAE, cheapest first
There are five practical routes to a loyalty programme in the UAE: a POS loyalty feature, a wallet pass or digital stamp card, a dedicated loyalty platform, loyalty inside an app you are building anyway, and a standalone branded app. Work down the list and stop at the first one that solves your problem.
1. A loyalty feature inside the point of sale you already run. This is the cheapest option and most businesses skip past it. Loyverse publishes its core point of sale as free with the loyalty programme included rather than sold separately [2]. Square lists loyalty as a feature inside one of its paid plan tiers [3]. If your till already has this, turning it on costs an afternoon. The customer gives a phone number at checkout and that is the entire enrolment.
2. A digital stamp card or wallet pass. Apple documents a store card pass type built specifically for loyalty cards, discount cards, points cards, and gift cards, issued and updated through its PassKit framework [4]. Google provides an equivalent loyalty object in the Google Wallet API, with a documented flow for adding a card to a customer's wallet [5]. In both cases the customer installs nothing new, because the wallet app is already on the phone. Adding a pass is a tap or a QR scan at the till.
One useful detail. Apple's guidance is that pass notifications should be reserved for meaningful changes to the pass itself, such as an updated balance or an expiring offer, rather than general marketing [6]. That is a sensible discipline whichever channel you use.
3. A dedicated loyalty platform. These plug into an existing till or online store and handle points, rewards, and referrals. Published vendor pricing on the Shopify app marketplace, for example, starts with a free tier at low order volumes and rises through monthly subscription tiers as volume grows [7]. Worth it when your POS genuinely cannot do what you need, and not before.
4. Loyalty as a feature inside an app you are already building. If you are building a commerce or ordering app anyway, adding a points programme starts from around AED 4,000. Our e-commerce app cost guide covers where that sits inside a wider build. This is the most common sensible place for loyalty to live.
5. A branded standalone loyalty app. A focused first version starts from around AED 15,000, plus maintenance from around AED 500 a month. That sits above the AED 10,000 MVP floor in our mobile app development cost guide, because a loyalty app is not just screens. It needs an account system, a points ledger that reconciles, and a connection back to the till before it does anything a paper stamp card cannot. This is the option most readers should skip, and the rest of this guide explains why.
Final pricing depends on scope.
What a loyalty programme costs in the UAE
| Route | Cost |
|---|---|
| Loyalty feature already inside your POS | Often free or a small monthly add-on [2][3] |
| Wallet pass programme | No Apple or Google issuance fee found; cost sits with the pass platform [8] |
| Dedicated loyalty platform | Free at low volume, then monthly tiers [7] |
| Loyalty feature added to an app or POS you run | From around AED 4,000 for a points programme |
| Branded standalone loyalty app, first version | From around AED 15,000 |
| App maintenance, if you build a native app | From around AED 500 a month, or 15 to 25 percent of build cost a year |
| Apple Developer Program | Currently 99 US dollars a year [9] |
| Google Play developer account | Currently 25 US dollars, one time [10] |
A loyalty programme can cost nothing if your POS already includes the feature, from around AED 4,000 as a points feature in an existing app, or from around AED 15,000 as a branded app, and two notes on that table matter. The store fees look like the running cost of an app and they are not. Ninety-nine dollars a year is trivial. The real recurring cost is maintenance, because every native app needs work each year to stay compatible with new operating system versions and changing store requirements, as our app maintenance guide sets out. That obligation does not shrink because the app only holds points.
Second, neither Apple nor Google publishes a fee specifically for issuing a wallet pass, and Google's own Wallet API help pages do not address pricing [8]. The cost of a pass programme is whatever your pass platform charges. Do not assume it is free, but do assume it is far below a build.
If you do decide to build, our mobile app development cost guide and app design cost guide cover the wider budget. Final pricing depends on scope.
When building a loyalty app is the right call
A branded loyalty app is worth building only when all four of the following are true:
- Customers buy weekly or more often, not monthly.
- The app does transactional work: ordering ahead, paying, booking, delivery tracking.
- You have multiple locations, so the app solves a real problem that a single till cannot.
- Someone owns the app as a job, not as a side task, and the maintenance budget exists.
If all four are true, build it, and treat loyalty as one feature inside it rather than the reason for it. If only the last one is true, you have a budget looking for a project.
Enrolment is where most programmes die
Whatever you build, the moment that decides its fate is the twenty seconds at the till when a customer is asked to join.
Every extra step in that moment costs you people who would otherwise have signed up. A phone number typed by the cashier is one step. A QR code the customer scans is one step. Downloading an app, creating an account, verifying an email, and logging in is four steps, and each one happens while a queue builds behind them. That is not a design problem you can solve with a better onboarding screen. It is a structural cost of choosing an app.
So work backwards from the till. Decide what you want the customer to physically do, time it, and then pick the technology that supports it. If the answer is a scan or a phone number, you do not need an app. If you genuinely cannot deliver the programme without an installed app, that is a real signal, and it usually means the app is doing something else useful too.
Three practical things matter more here than the software choice. First, the prompt has to sit where staff cannot miss it, not three screens into a checkout flow. Second, staff need one short scripted line, agreed and repeated, rather than being left to improvise. Third, somebody has to look at enrolments per branch every week, because a programme with no owner quietly stops being mentioned within a month.
None of that costs money. It is also the part that most often separates a programme that works from an identical one that does not.
Stamps or points: picking the mechanic
Choose stamps where every purchase costs about the same, points where basket sizes vary, and remember the technology matters less than the reward maths.
Stamps suit a business where the core purchase costs about the same every time. A coffee, a wash, a cut. Buy nine, get the tenth free, and nobody has to do arithmetic.
Points suit varied basket sizes, because they scale with spend rather than counting visits. Most restaurants and most retail are points businesses.
Cashback as store credit is the easiest to model against margin, because the cost is a fixed percentage you choose.
Tiers unlock better rewards as spend rises. They need enough customers at each level for the levels to mean anything, so they suit multi-location retail more than a single cafe.
Whichever you pick, the reward has to be big enough that someone changes behaviour to reach it, and small enough that redeeming it does not erase the margin on the visits that earned it. Work that out from your own numbers first. Then measure repeat visit rate among enrolled customers over a few months, not sign-ups. Sign-ups are easy to inflate and tell you nothing. Our analytics and BI guide covers getting that reporting in place.
Be sceptical of the return figures you will find online. Almost every percentage published about loyalty programme returns comes from a company selling loyalty software, and we are not going to repeat numbers we cannot stand behind.
Points are a liability, so plan the expiry
Unredeemed points are not free revenue. They are generally treated as an obligation sitting on your books rather than income, until they are redeemed or until redemption becomes unlikely. We are not accountants, and the exact treatment under the standards your company reports on is your accountant's call, so ask them how to record the outstanding balance before you design the expiry. A programme with no expiry accumulates a balance that never clears.
That is why most programmes set an expiry, usually tied to inactivity rather than a fixed date, so regulars are not punished. There is no UAE standard period. It is your decision, it must be written into your programme terms plainly, and your accountant should tell you how to record the outstanding balance.
VAT is the other question people guess at, and it should not be guessed at. The Federal Tax Authority publishes VAT guidance and public clarifications covering business promotions and vouchers [11]. Treatment can differ depending on whether your programme awards points as a discount, issues vouchers, or gives an item away with no cash paid. Because the design changes the answer, confirm your specific programme with a VAT-registered accountant and check the Federal Tax Authority's published guidance directly rather than relying on a general rule.
Consent, data, and marketing rules in the UAE
A loyalty programme collects a phone number and ties it to what someone buys, which makes it a personal data programme that needs consent.
That is processing personal data under the UAE Personal Data Protection Law, Federal Decree-Law No. 45 of 2021, which took effect on 2 January 2022 and requires a lawful basis for handling personal data, normally the individual's consent [12]. It also gives people rights to correct their data and to restrict processing. Some free zones operate their own data protection regimes, so confirm which one covers your licence. Our PDPL compliance guide goes into the detail.
Marketing consent is separate, and this is where programmes get into trouble. Handing over a number to collect stamps is not agreement to receive promotional messages. UAE Consumer Protection Law, Federal Law No. 15 of 2020, requires suppliers to protect consumer data and gives consumers the right to accept or refuse marketing campaigns [13]. The UAE also issued telemarketing regulations by Cabinet Resolution in 2024, with a scope written broadly enough to cover marketing calls, text messages, and marketing messages sent through apps [14]. Separately, the Telecommunications and Digital Government Regulatory Authority operates a national Do Not Call Registry that lets residents opt out of telemarketing contact [15].
The practical version, which does not depend on any detail we cannot verify:
- Take marketing consent as a separate, explicit opt-in at sign-up, not bundled into joining.
- Keep a record of who consented and when.
- Make the opt-out obvious and free to use.
- Keep transactional messages about someone's own balance separate from promotional blasts.
- Check the current rules on the regulator's own site before running a campaign.
If your messaging channel is WhatsApp, which it usually is in this market, the same consent logic applies. Our WhatsApp Business API guide covers what that costs to set up properly.
Real client stories
The cafe that did not need an app. A single-location speciality cafe came to us wanting a branded app with points, push notifications, and a pre-order feature. We went through their till data. Average customer visited around twice a month and the pre-order demand was a handful of regulars who already messaged the owner directly. The honest recommendation was a wallet pass stamp card and a scripted line for the baristas. They spent a fraction of the budget and kept the rest for a second site. We would rather lose the build than sell a project the numbers did not support.
The retailer whose programme nobody mentioned. A multi-store retail client had a working points programme inside their POS and almost no enrolments. The technology was fine. Nobody at the till was bringing it up, and the prompt was buried three screens into the checkout flow. The fix was mostly operational: move the prompt, write one line for staff, and report enrolment by store each week so branch managers could see their own number. No new software.
The ordering app where loyalty belonged. A delivery-heavy food business was already building an ordering app because customers ordered several times a week and the phone-order process was breaking down. Loyalty went in as one feature inside that build rather than as its own product. That is the shape that works. The app justified itself on ordering, and points made the customers who already opened it weekly open it a little more.
How SKIMBOX approaches loyalty
We start with your transaction data rather than a demo, because visit frequency decides the answer before anything else does. We will tell you when the right build is no build, and we will point you at the feature already sitting unused inside your point of sale if that is the honest recommendation. When an app is justified, we scope loyalty as one feature inside something that does real work, set the consent and expiry rules up properly at the start, and put the reporting in place so you can see repeat visit rate rather than sign-up counts.
A loyalty feature added to an existing app or point of sale starts from around AED 4,000 for a points programme. A branded standalone loyalty app starts from around AED 15,000 for a focused first version, with maintenance from around AED 500 a month, or budget 15 to 25 percent of build cost a year. Final pricing depends on scope.
See our app development services and product engineering services, or contact us to talk through which rung of the ladder fits your business [16].
References
[1] Apple Developer - App Store Improvements process for apps not recently updated. developer.apple.com/support/app-store-improvements/
[2] Loyverse - Pricing, showing the free point of sale plan with the loyalty programme included. loyverse.com/pricing
[3] Square - Loyalty product page, showing loyalty as a feature within a paid plan tier. squareup.com/us/en/software/loyalty
[4] Apple Developer - Wallet, store card pass type for loyalty, discount, points, and gift cards. developer.apple.com/wallet/
[5] Google for Developers - Google Wallet loyalty cards and the add to Google Wallet flow. developers.google.com/wallet/retail/loyalty-cards/overview/add-to-google-wallet-flow
[6] Apple Developer - Human Interface Guidelines, Wallet, on pass notifications. developer.apple.com/design/human-interface-guidelines/wallet
[7] Shopify App Store - Smile.io listing, showing published vendor pricing tiers by order volume. apps.shopify.com/smile-io
[8] Google for Developers - Google Wallet API FAQ, which does not publish pass issuance pricing. developers.google.com/wallet/docs/faq
[9] Apple Developer - Apple Developer Program enrollment and annual fee. developer.apple.com/programs/enroll/
[10] Google Play Console Help - Developer account registration fee. support.google.com/googleplay/android-developer/answer/6112435
[11] Federal Tax Authority, UAE - VAT guides, references, and public clarifications. tax.gov.ae/en/taxes/vat/guides.references.aspx
[12] U.AE Official UAE Government Portal - Data protection laws, Federal Decree-Law No. 45 of 2021. u.ae/en/about-the-uae/digital-uae/data/data-protection-laws
[13] U.AE Official UAE Government Portal - Consumer protection, Federal Law No. 15 of 2020. u.ae/en/information-and-services/justice-safety-and-the-law/consumer-protection
[14] UAE Legislation Portal - Cabinet Resolution No. 56 of 2024 concerning the Telemarketing Regulations. uaelegislation.gov.ae/en/legislations/2519
[15] TDRA - Telecommunications and Digital Government Regulatory Authority, regulator of the Do Not Call Registry. tdra.gov.ae/en/
[16] SKIMBOX - App and product engineering services for UAE businesses, 2026. skimbox.co
