SuperBluOrange can scope a multi-brand configuration around your group structure and rollout plan. Bring the existing brands and the next planned launch into the same design discussion.
Map what is shared and what stays separate
| Area | Group decision | Boundary to verify |
|---|---|---|
| Player accounts | One identity service or independent accounts | Which operator may access and use each record? |
| Wallets | Shared balance or separate balances | Which entity owes the player and how are transfers reconciled? |
| Suppliers | Group procurement or brand-specific agreements | Which catalog and payment routes are approved for each brand? |
| Content and promotions | Shared templates with local variants | Which market and language can receive each published offer? |
| Administration | Central team with scoped local roles | Which records and settings can each role read or change? |
| Reporting | Consolidated view with entity-level detail | Can totals be traced to the underlying business and transaction? |
Use a separate row for every entity and brand in the implementation brief. Record exceptions explicitly rather than relying on a default inherited from the first launch.
Make inheritance visible before enabling it
A shared rule can reduce repeated configuration, but a mistake can affect more brands. Define which settings are centrally controlled, which may be overridden and what happens when the group default changes.
For example, a promotion intended for one market should not become visible across all brands because they share a template. Preview the affected brands, require the appropriate approval and retain the previous version. Apply the same reasoning to payment routing and staff permissions.
Accept the configuration with an isolation test
- Create a brand-specific staff role and demonstrate that it cannot access another brand's player records.
- Change one local setting and verify both the intended effect and the absence of an unintended group change.
- Produce a consolidated report, then reconcile its components to the individual entity records.
Test an incident affecting one brand: who receives the alert, which services can remain available and how the restriction is removed. These are proposed acceptance scenarios; their implementation belongs in the agreed scope.
Plan the second rollout as carefully as the first
Agree how a new brand obtains approved suppliers, content, permissions and reporting. Include the operational cost of local support and governance alongside any shared technology saving. If an existing brand is moving onto the group platform, scope its migration separately.
Discuss your brand and entity structure. Include the systems you want to share and the separations the business must preserve.