Path to live · Client platform
Launch a loyalty platform for your clients.
Build one shared installation for client businesses, then give each partner a restrained first program, its own staff workflow, and a clear operating boundary.
- Installation model
- One shared installation
- Business boundary
- Isolated partner businesses
- Primary layout
- Portal
Four-domain topology
Separate your service brand from the application.
Your agency or platform site explains the offer. The application domain carries every isolated partner workspace. A dedicated sending subdomain protects OTP operations, while staging gives you a place to rehearse upgrades and restore tests.
Root or marketing
yourplatform.com
The service website, sales material, and support entry point.
Application
app.yourplatform.com
One shared Reward Loyalty installation for all partner businesses.
Transactional email
mail.yourplatform.com
The authenticated identity for OTP and platform service mail.
Staging
staging-app.yourplatform.com
The private rehearsal copy for releases, backups, and configuration.
The three-domain license allowance covers production, staging, and test application domains. It does not turn one license into separate client installations.
Model decisions
Set the model before the screens.
These choices keep the setup coherent. The linked documentation carries the screen-level procedure after the operating decision is made.
Keep clients inside one shared installation
SaaS mode gives isolated partner businesses one platform to operate. Portal is primary when clients must not discover each other. Smart Wallet fits only a curated network where businesses are deliberately visible together.
Treat separate installations as another model
If you deploy a separate branded installation for each client, repeat the own-business setup for each one. The product and license boundary is different from one shared platform.
Start billing with an operator-owned process
Map plans and tiers to what you actually sell. Begin with manual billing, then add Stripe or PayPal when operational volume justifies the automation. Pricing and margins remain your decisions.
Define white-label at the platform boundary
White-label here means the shared application carries your platform name, logo, colors, and service relationship. Each partner still receives an isolated business workspace inside that one installation.
Inside Reward Loyalty
Operate partners from one installation.
The SaaS overview brings partner count, plan mix, registrations, and billing mode into one operator view. Each partner works inside its isolated business workspace.
Path to live
Nine milestones, in order.
Make the decision here, then open the owning documentation for the current screens. Do not skip the smoke test or the first restore proof.
-
1
Lay out your domains
Map the platform marketing domain, shared application domain, authenticated transactional-email subdomain, and staging domain. Keep HTTPS and DNS ownership clear before inviting the first client.
Open the procedure -
2
Choose your hosting
Choose for concurrent client counters, partner administration, campaigns, queues, backups, and scheduled work. MySQL/MariaDB is the production recommendation. SQLite is for evaluation, not a growing shared platform. Use the hosting hub for verified options and disclosed limits.
Open the procedure Open the hosting hub Download the compatibility checker -
3
Install and prove it
Install once, then complete the real smoke test inside the shared application. Keep the proof on staging before client onboarding.
- Sign in as the administrator
- Receive a real OTP email
- Credit a test member through a staff checkout
- Upload an image
-
4
Make email real
Connect transactional email from day one. Authenticate the platform sending domain with SPF, DKIM, and DMARC, monitor bounces and complaints, and prove a real OTP reaches an inbox. Do not build a client-access platform on host SMTP.
Open the procedure -
5
Shape the front door
Choose Portal as the primary layout when isolated partner businesses must not know about one another. Apply the platform name, logo, and color. Use Smart Wallet only when the product is intentionally a visible curated network.
Open the procedure Apply platform branding Compare separate installations -
6
Build your first program
Define plans and tiers from supported permissions, then launch each client with one loyalty mechanic and one worthwhile reward. Keep self-registration off while you create partners deliberately. Begin with manual billing, moving to Stripe or PayPal only when the operating case is clear.
Open the procedure Set up manual billing Review Stripe billing Review PayPal billing -
7
Bring in people
Create each partner account from administration, confirm its isolated business workspace, invite the client operator, and let that partner create the staff who work its counters. Add first members through the client business QR after the team can explain the program.
Open the procedure Set partner permissions Train client staff -
8
Launch at the counter
Give each client its own tested QR materials and staff scanning routine. Run the first real checkout for a member, confirm the credit appears, and keep a named escalation route for staff or partner questions.
Open the procedure Prepare staff scanning -
9
The first 30 days
Review members joining, repeat visits, first redeemed rewards, staff corrections, partner questions, billing status, and platform operations. Prove a backup restore, bring Health Center checks to green, and check updates. Loyalty compounds slowly, and that is normal.
Open the procedure Inspect Health Center Prove the operating checks