Spa Dani & Stefi Club
Give every visit a place in the loyalty journey.
Loyalty // Service operations // QR cards
- Industry
- Wellness & customer loyalty
- Deployment Status
- Internal business application
- Technology Stack
- Next.jsReactTypeScriptTailwind CSSNeon PostgreSQLQR toolingPWA
The business dilemma
A service business needs shared rules for recording visits, applying benefits and reviewing redemptions, while giving staff and customers the appropriate view.
The implemented solution
A private, role-oriented loyalty workspace separates administration from the customer card experience and brings visit and benefit workflows together.
What the system accomplishes
Role-oriented access
Owner, administrator and customer routes support different responsibilities.
Customer management
Dedicated routes provide customer registration and lookup for staff.
Visit and cashback workflows
The application’s documented scope connects service visits with loyalty benefits.
Redemption handling
Separate workflows support benefit requests and administrative review.
Digital cards and QR
Customer card routes and QR tooling support registration, access and scanning within an installable application.
Architectural engineering
Role-based routes
Next.js routes separate administrative workflows from customer card views.
Server-side records
Server components, actions and route handlers connect application data to PostgreSQL.
Local sessions and PWA
Documented HTTP-only cookie sessions and installable application assets support the private workspace.
Scope & authentic evidence
Implementation scope covers a private loyalty workspace, role-specific routes, visit and benefit workflows, digital cards and PWA structure.
- The current manifest identifies a loyalty application with PostgreSQL and QR dependencies.
- Documentation describes a private PWA, local sessions and role-oriented workflows.
- Source inventory confirms administrative customer routes and a customer digital-card route.
- No private records, authenticated screens or operational data were accessed.
Operating boundaries
- The club is separate from the spa’s public marketing website and has no public demo link here.
- Database persistence, session security and real redemption behavior were not tested.
- Email, OAuth, recovery flows and business results are not claimed as live capabilities.
- Implementation scope is source-backed; sole authorship and a paid engagement are not established.