What is the difference compared with a white-label loyalty SaaS such as Antavo, LoyaltyLion or Yotpo?
White-label loyalty platforms go live quickly and handle generic mechanics well (points, tiers, a rewards catalogue). They hit their limits at three points. First, industry-specific logic: a hotel chain offering room upgrades as a reward, a supermarket with dynamic personal pricing, a sports club with season-ticket bonuses. There you end up working against the tool instead of with it. Second, integrations with a non-standard till, a proprietary e-commerce stack or your own CDP, where adapter work becomes expensive and fragile. Third, price as you grow: active-user fees stack up quickly once adoption picks up, exactly when you are succeeding. Custom development costs more at the start and less in the long run, and you keep ownership of both the data and the mechanics. We will also tell you honestly when a white-label solution is enough. If your formula is a fairly standard points/rewards flow with no exotic integrations, it can be a perfectly good first step.
Native or cross-platform: what do you recommend?
It depends on the mechanics and your internal capacity. For relatively standard loyalty flows (points, tiers, redemption, push), Flutter or React Native works very well and gives you simultaneous releases on iOS and Android from a single codebase. For apps that make heavy use of the hardware (Apple Wallet passes, advanced push segmentation via OS features, NFC redemption at the till, complex animations that carry the brand feel), we increasingly choose native: Swift for iOS, Kotlin for Android. We advise case by case. We can deliver both, and do both well.
How do you handle POS and till integration?
We integrate with all the major POS systems in the Netherlands and internationally: Lightspeed, Tally Pay, Untill, Vectron, MplusKASSA, Storyous, Toast, Square, Adyen POS stacks and proprietary POS systems via a custom middleware. The integration can work in two directions: awarding points on purchase (event-driven, with the POS pushing a purchase event to the loyalty backend) and redemption (points or a voucher are redeemed at payment, validated against the loyalty backend). For chains with several POS types, we build an abstraction layer so marketing doesn't need to know which location runs on which system.
How do you handle GDPR and profiling?
Loyalty inevitably touches on profiling: you process purchase behaviour, location and possibly health-or-lifestyle signals to make personal offers. That falls under the GDPR and, in most cases, under the ePrivacy regime for push notifications. We build an opt-in flow that holds up legally, a granular consent model (you can collect points without receiving personalised offers) and a data vault set-up in which sensitive attributes are kept separate from operational data. We include a DPIA as standard on broader CDP projects. For sectors with additional requirements (healthcare, financial), we deliver the extra controls, such as pseudonymisation, retention policies or geo-fencing of data.
How do you prevent loyalty fraud and self-referrals?
Loyalty programmes are an attractive target for abuse: multiple accounts per person, referrals to yourself, hacked accounts draining points, bots simulating activations. We build in a fraud layer with device fingerprinting, behavioural pattern detection (too many actions in too short a time), email and phone number validation, and heuristics that only validate referrals after a completed purchase with payment method attribution. Suspicious cases go to a review queue for your team. For larger programmes, we also integrate with an external fraud tool where it makes sense.
What about gift vouchers and the Dutch Gift Voucher Act?
If rewards are issued in the form of gift vouchers, you come into contact with the Dutch Gift Voucher Act (extended validity since 2023, at least two years for new vouchers). Voucher rewards and closed-loop credits are also subject to specific rules on loss, expiry date, labelling and exchange for cash. We make sure the redemption flow complies, and for larger programmes we have the legal check carried out explicitly by a specialist, so there are no surprises later, such as a first discussion with a regulator or a redemption request that goes worse than expected.
Does the app work offline?
For collecting and viewing points and for the rewards catalogue, working offline is generally not critical, because the transaction happens at the till, not in the app. For in-store redemption, we have built an offline-friendly flow for a number of clients: the app caches balances and redemption tokens locally and syncs as soon as a connection is available again. This matters in shops with poor mobile coverage or in hospitality venues in old buildings.
Can you also provide Apple Wallet and Google Wallet cards?
Yes, for many clients we also deliver the loyalty card as a pass for Apple Wallet and Google Wallet, with live balance updates, geolocation triggers ("you're near a location, you have 240 points") and polished brand presentation. That lowers the barrier to having the card to hand and helps with in-store redemption because customers don't have to open their email first. Alongside the mobile app, the wallet pass makes your programme more accessible to the group that doesn't open the app every day.
How do you see the link with our marketing automation?
A loyalty app provides the data and the direct push/in-app layer, while your marketing automation platform (Klaviyo, Mailchimp, Braze, Salesforce Marketing Cloud, Bloomreach) handles email and cross-channel orchestration. We connect them with events in both directions: the loyalty backend sends events to the automation platform (tier upgrade, first redemption, dormant customer), and the automation platform sends segments and triggers back to launch push campaigns in the app. That way, marketing doesn't have to manage two separate campaigns for a single customer moment.
How do you measure whether the programme works?
We set up reporting on activation (what percentage of customers have an account), engagement (open rate, sessions, redemptions per month), incremental revenue per tier (do members spend more than non-members, corrected for selection bias), and the financial liability of outstanding points, a liability that sits on your balance sheet. For more mature programmes, we also build in A/B tests on offers, push frequency and redemption curves, so you know not only whether the programme works but also which variant works best for which segment.
Who owns the code and data?
You do. We hand over the complete source code, schemas, build pipelines and deployment scripts. The data lives in your cloud or with a hosting partner of your choice. If you later want to continue with another agency, or take over in-house, you can: there is no technical lock-in. We earn our money from good work that lasts, not from clients who are stuck with us.
What determines the cost of a loyalty app?
The biggest cost drivers are the complexity of the mechanics (just points and rewards, or also tiers, challenges, referrals and gamification), the number of integrations (POS, e-commerce, CDP, marketing automation, ERP, finance), the degree of personalisation (static vs. real-time based on behaviour), and whether the programme needs to work across multiple brands or formats. Native versus cross-platform and the amount of brand-specific motion design also play a part. We work in sprints with fixed sprint budgets, so there are no surprises and you can steer scope sprint by sprint.
How long until we can go live?
A first working version with points, a simple rewards catalogue and push notifications can be on TestFlight and the Google Play internal track within a few sprints. For a full platform with tiers, gamification, referrals, CDP integration and POS integration across multiple locations, we plan a programme of several sprints. We often roll out in phases, so a first cohort of customers can start while we keep building. That gives us feedback we can act on straight away for the wider launch.