SaveMate

The problem

Online cashback had to feel like a consumer brand (SaveMate and other white-labels) while remaining one codebase. Visitors arrive from different countries, languages, and partner domains. Auth, claims, and engagement had to survive that.

Approach

1. 01

   Next.js App Router with /[region]/[lang] routing and CloudFront country headers mapped to the right market.

2. 02

   White-label via x-appwl: per-brand chrome, configuration, and legal surfaces without a fork per tenant.

3. 03

   Member lifecycle: register, activate, payment methods, transactions, favorites, raffles, refer-a-friend, and missing cashback verification.

4. 04

   PWA + Firebase + MoEngage for installability and lifecycle messaging.

Outcome

A production cashback portal that can be re-skinned for partners, geo-routed at the edge, and operated as a PWA — the web counterpart to the CLO mobile stack.

Tenant and geography as architecture

Middleware is the product. JWT cookies gate private routes; viewer country selects region and language; white-label headers swap brand identity. That is how one Next.js app serves multiple consumer brands without collapsing into a configuration nightmare.

The shopping loop

Merchants, categories, search, hot deals, double cashback, and VIP rewards are the front of the funnel. The back of the funnel is where cashback products usually fail: claims, payment methods, transaction history, and support. Those screens were treated as first-class, not admin afterthoughts.