Increase repeat purchases with rewards merchants can control.
VowRewards helps merchants issue VOWR rewards, review QR redemptions, monitor customer loyalty, and keep settlement work visible from one premium merchant workspace.
A loyalty operating system, not a points page.
The platform is designed for store teams, merchant owners, customer support, and finance reviewers who need clear decisions instead of scattered spreadsheets.
Increase repeat visits
Reward customers after purchase, bring them back through wallet-visible value, and measure the return journey from scan to redemption.
Control every campaign
Create reward rules, budget caps, store eligibility, and approval states before VOWR rewards are issued.
See settlement risk early
Track redemptions, flagged transactions, and finance batches before merchant settlement decisions are made.
From purchase to return visit.
VOWR rewards make the customer's next action visible while giving the merchant control over approval, fulfilment, and reporting.
Purchase
A customer buys in-store, online, or at an approved merchant location.
Earn
The merchant submits a reward request tied to campaign rules and purchase evidence.
Wallet
Approved VOWR rewards appear in the customer wallet with campaign context.
Redeem
The customer scans a QR code or presents wallet proof for redemption review.
Return
The merchant measures repeat behavior, campaign ROI, and next best reward offers.
Metrics investors and merchants can understand.
These are sample metrics from the demo portal, labelled clearly until production data is connected.
Demo metric showing repeat purchase lift tracked inside merchant analytics.
Sample scan volume across earn and redeem journeys.
Demo approved reward issuance with backend approval guardrails.
Sample finance queue value awaiting merchant review.
Launch reward campaigns that match merchant goals.
Each campaign can be shaped around acquisition, retention, or reactivation while preserving budget and approval controls.
Buy and Earn
Issue 10 VOWR for every R100 spent, capped by store and campaign budget.
Repeat Visit Bonus
Reward a second visit within 30 days and track conversion by location.
Weekend Recovery
Boost low-traffic trading windows with double rewards and approval checks.
Reward movement stays governed.
The product is designed so merchant teams can work quickly without moving funds or token value from the frontend.
Approval workflow
Reward requests move through pending, approved, rejected, flagged, processing, and completed states.
Role-aware portal
Owner, operator, reviewer, support, and admin roles are modelled for production RBAC.
Treasury guardrails
No frontend-only fund movement. Token and settlement actions remain backend-approved.
Audit-ready data
Status transitions, support tickets, and admin decisions are prepared for audit logging.
What is ready today.
These readiness signals describe the current software surface, not live market traction.
Onboarding, campaigns, transactions, redemptions, settlements, analytics, support, and roles.
Merchants, campaigns, reward requests, redemptions, settlements, transactions, support.
Afrihost MySQL schema includes merchant users, locations, rewards, settlements, and audit logs.
Backend contracts are prepared for production integration.
The current API safely returns mock responses when database variables are missing, and switches to MySQL when DB_* configuration is present.
/api/merchantsRead merchant onboarding records
/api/campaignsCreate campaign drafts
/api/reward-requestsSubmit reward issuance requests
/api/redemptionsUpdate redemption status
/api/database/statusCheck Afrihost MySQL reachability
