Solution · Multi-business
One installation can serve many separate businesses.
Each partner operates its own programs and data inside one installation. The operator owns the shared infrastructure and administration.
- Shared layer
- Application and infrastructure
- Isolated layer
- Partner business data
- Member layer
- One account, separate programs
Short answer
Start with the operating model.
Reward Loyalty runs several partner businesses inside one installation. Each partner manages its own programs, staff, members, and reporting within the product’s scope, while the operator manages shared infrastructure and administration. Members use one account across participating businesses, but business program data remains separate.
Decision criteria
What the decision changes.
These choices affect configuration, staff work, economics, support, and the customer promise.
Tenant definition
Treat a partner as a business boundary, not as a casual label for each branch or department.
Operator responsibility
The installation owner controls shared configuration, plans, infrastructure, managers, and service health.
Member experience
One account reduces signup friction, while each business still presents and operates its own programs.
Architecture
Separate shared services from partner ownership.
The commercial service becomes easier to explain when each layer has one owner.
Platform operator
Owns the domain, platform identity, infrastructure, release process, plans, and cross-installation administration.
Partner
Owns its business settings, staff, programs, customers, activity, and reports within granted permissions.
Member
Uses one account and wallet, with program balances, passes, vouchers, and achievements shown per business.
Operations
Design the support and access model.
Multi-business software reduces duplicated infrastructure. It increases the importance of permission and incident discipline.
-
1
Define onboarding
Decide who creates a partner, which plan or permissions apply, and who verifies business settings.
-
2
Set manager scope
Grant only the administration needed for the portfolio or network the manager operates.
-
3
Test partner isolation
Use separate accounts to verify lists, exports, staff, programs, member relationships, and dashboard access.
-
4
Plan shared incidents
Mail, queues, scheduler, storage, or deployment problems can affect several businesses at once. Name the response owner.
Product and operating limits
Keep the recommendation inside the product boundary.
- Multi-tenant operation does not provide automated client billing, tax, contracts, onboarding service, or support staffing by itself.
- The shared wallet does not merge partner balances or let one partner inspect another partner’s customers and activity.
- One license covers one installation under the current license terms. Separate installations need separate licenses.
Implementation guides
Use current documentation for changing details.
Requirements, interfaces, settings, limits, and release behavior belong in the maintained product documentation.