Vefuno
Separating loyalty state from physical QR/NFC touchpoints while keeping reward progression and retention workflows consistent.
#01 The product
Vefuno is a web platform for cafés and similar merchants. It replaces a printed loyalty card with digital stamp and reward flows. Customers interact through QR, NFC, or a phone-wallet representation of the same card. Merchants configure the program and see it from a dashboard.
The product covers stamp-based loyalty, rewards, referrals, Google Review incentives, and reactivation. It does not own a separate truth for each channel. QR, NFC, and the wallet pass are ways to reach one loyalty state.
#02 Loyalty state
The model runs Merchant → Loyalty Program → Member → Stamp Events → Reward State → Wallet Representation → Retention Segments. Stamps are events. Reward progression is derived from those events. A scan or a tap does not own the balance.
Known program behavior includes a reward for both sides of a referral, an optional extra stamp after a Google review, and segments a merchant can act on: customers inactive for 30 days, customers one stamp away from a reward, new members, returning customers, total stamps, and redeemed rewards. Merchant presentation stays configurable without forking the progression rules.
#03 Engineering
Physical interaction stays interchangeable. QR and NFC are layers over the same stamp and reward state, so adding a touchpoint does not duplicate progression logic. Retention segments read those events — inactivity, proximity to a reward — instead of becoming a second system of record.
Wallet integration is a boundary around that state. Google Wallet Passes API access has been approved for Vefuno. That approval is not a claim that a production wallet launch is finished. Apple Wallet is part of the pass architecture, not a channel described here as production-complete.
$ ls ./screenshots
Want the full story behind this build?
POST /contact