What is the difference between a white-label loyalty SaaS like Antavo, LoyaltyLion or Yotpo?
White-label loyalty platforms are quick to launch and good at general mechanics (points, tiers, a rewards catalogue). They reach their limits in three places. First, with industry-specific logic: a hotel chain with room upgrades as a reward, a supermarket with dynamic personalised pricing, a sports club with season-ticket bonuses. There you need to build around the tool rather than with it. Second, with integrations involving an unusual till system, your own e-commerce stack or your own CDP: adapter work becomes expensive and fragile. Third, with pricing as you grow: active-user fees add up quickly once adoption takes off, exactly when you're succeeding. Custom development costs more at the start and less in the long run, and you retain ownership of the data and the mechanics. To be honest, a white-label solution is sometimes sufficient: if your scheme has a fairly standard points and rewards flow and 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 in-house capabilities. For relatively standard loyalty flows (points, tiers, redemption, push), Flutter or React Native work very well and deliver simultaneous releases on iOS and Android from a single codebase. For apps where you do a lot with 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 either approach, and both do well.
How do you handle POS and till integration?
We integrate with all the common point-of-sale 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 layer. The integration works in two directions: awarding points at purchase (event-driven, where the till pushes a purchase event to the loyalty backend) and redemption (points or a voucher are redeemed at payment, with validation against the loyalty backend). For chains running several POS types, we build an abstraction layer so marketing doesn't need to know which branch runs on which system.
How do you deal with GDPR and profiling?
Loyalty inherently involves profiling: you process purchasing behaviour, location and possibly health or lifestyle signals to make personalised offers. That falls under the GDPR and, in most cases, under the ePrivacy rules for push notifications. We build an opt-in flow that is legally sound, a granular consent model (you can collect points without receiving personalised offers), and a data vault setup in which sensitive attributes are kept separate from operational data. We carry out a DPIA as standard on broader CDP projects. For sectors with additional requirements (healthcare, finance), we provide 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 that drain points, and 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 once a purchase has been completed and attributed to a payment method. Suspicious cases go to a review queue for your team. For larger programmes, we also integrate an external fraud tool where it fits.
What about gift cards and the Dutch Gift Card Act (Cadeaubonwet)?
If rewards are issued as gift vouchers, you need to be aware of the Dutch Gift Voucher Act (Cadeaubonwet), which has extended validity since 2023, with a minimum of two years for new vouchers. Voucher-based rewards and closed-loop credits also carry specific rules around loss, expiry dates, disclosure and cashing out for money. We make sure the redemption flow complies with these rules and, for larger programmes, we arrange a formal legal review with a specialist. That way there are no surprises when a regulator raises questions or a redemption request goes less smoothly than expected.
Does the app work offline?
For collecting and viewing points and the rewards catalogue, working offline is usually not critical, since the transaction happens at the till, not in the app. For in-store redemption, we have built an offline-friendly flow for several clients: the app caches balances and redemption tokens locally and synchronises once a connection is restored. This matters most in shops with poor mobile coverage and in hospitality venues in older buildings.
Can you also supply 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 branch and have 240 points") and attractive brand presentation. This lowers the barrier to keeping the card at hand and helps with in-store redemption, as customers don't first need to open their email. Alongside the mobile app, the wallet pass makes your programme more accessible to those who don't open the app every day.
How do you see the connection with our marketing automation?
A loyalty app supplies the data and the direct push and 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, lapsed customer), and the automation platform sends segments and triggers back to activate 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 is working?
We set up reporting on activation (what percentage of customers have an account), engagement (open rate, sessions, redemptions per month), incremental revenue per tier (whether members spend more than non-members, corrected for selection bias), and the financial liability of outstanding points, which 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 full 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 move on to another agency, or take development in-house, that is possible, as there is no technical lock-in. We earn our keep through good work that keeps clients, not by keeping clients locked in.
What determines the cost of a loyalty app?
The biggest cost drivers are the complexity of the mechanics (points and rewards only, or also tiers, challenges, referrals and gamification), the number of integrations (till systems, e-commerce, CDP, marketing automation, ERP, finance), the degree of personalisation (static versus real-time based on behaviour), and whether the programme needs to work across multiple brands or formats. Native versus cross-platform development and the extent of brand-specific motion design also play a role. We work in sprints with fixed sprint budgets, so there are no surprises and you can steer scope sprint by sprint.
How long before we can go live?
A first working version with points, a simple rewards catalogue and push notifications can be live on TestFlight and in the Google Play internal track within a few sprints. A full platform with tiers, gamification, referrals, CDP integration and POS integration across multiple branches is a multi-sprint project. We often roll out in phases, so an initial cohort of customers can start while we continue building. That gives us feedback we act on directly before the wider launch.