Customer engagement / loyalty
Rewards Engagement Platform
PerkUP—ASP.NET Core 6 JWT API over SQL Server, React admin, and Flutter apps for customers, vendors, and admins.
The challenge
Growth and vendor networks needed structured perk catalogs and multi-role clients—not ad-hoc coupon spreadsheets—while staying honest about what loyalty ledger features are still missing. Without a coherent customer engagement / loyalty foundation, Rewards Engagement Platform stakeholders faced fragmented tools, slow handoffs, and limited visibility—classic failure modes Tekvers designs against.
The solution
Rewards Engagement Platform: PerkUP—ASP.NET Core 6 JWT API over SQL Server, React admin, and Flutter apps for customers, vendors, and admins. Multi-client loyalty catalog operable from one API. Tekvers delivered a maintainable customer engagement / loyalty system for Rewards Engagement Platform using ASP.NET Core 6, EF Core, SQL Server, ADO.NET/SqlClient, with phased rollout, operator workflows, and documentation suited to long-term ownership.
Approach
Shared API, multiple clients
Twelve controllers covering auth, users, roles/permissions/modules CRUD APIs, perks/perk types, menus, geography.
Role strings + metadata tables
UserType strings (Admin/Customer/Vendor) drive UX; Roles/Permissions/Modules tables exist; junction controllers and admin UIs for RBAC metadata are absent; no runtime permission checks beyond JWT presence.
Engagement UX without ledger overclaim
Customer QR display + vendor scanner/confirmation screens; no redemption transaction API.
Deliverables
- ▸ASP.NET Core 6 JWT API + Swagger in Development
- ▸React admin CRUD for users, perks, perk types, menus, geography
- ▸Flutter admin, customer, and vendor apps (primary paths)
- ▸Domain: Perks, PerkTypes, Menus/MenuItems, Countries/Cities/Areas/Addresses, Users
- ▸Roles/Permissions/Modules CRUD APIs (metadata)
- ▸Explicit non-features: points wallet, redemption history, Hangfire jobs, maps/push shipping features, microservices
Outcomes
- ▸Multi-client loyalty catalog operable from one API
- ▸Vendor menu + customer offer browsing with QR handoff UX
- ▸Clear roadmap items (RBAC enforcement, redemption ledger) called out in docs
Impact
Operators configure perks and menus across web and mobile—without Tekvers inventing wallet balances or background-job architecture the running code does not include.
Tech stack
Want something similar?
I build production systems like Rewards Engagement Platform—from architecture through launch. Tell me what you need.
Contact me →