- Joined
- Jul 11, 2008
- Messages
- 2,855
- Reaction score
- 198
- Points
- 63
A second brand usually begins as a commercial decision. A different audience, a different product angle, a different name over the door. The technical work behind it is narrower than most planning documents assume, and it divides into two parts: what the new brand inherits from the existing operation, and what has to be created for it from the start.
Where that division falls depends on whether the platform treats a brand as a separate deployment or as a configuration layer inside one system. The difference surfaces in every task that follows, from reporting to content updates, which makes it a practical criterion when selecting an iGaming solution provider. Soft2Bet builds the second case: shared platform services sit underneath, and brand-level settings sit on top, so partners administer several brands from one back office.
Source: https://www.magnific.com/free-photo...0b-e000-4dfd-8498-c74422a7db70&query=software
The account layer carries over in the same way. PAM (Player Account Management) holds records for each brand separately, while the administration screens, verification steps, and account status handling are one system. A support request for the second brand is worked in the same interface, with the same tools, by the same people who handle the first.
Reporting inherits its structure. The views built for the first brand exist for the second on day one, which means reporting produces usable output from the opening week.
Content selection is the second piece of per-brand work. The catalogue is shared, but which titles appear, how the lobby is grouped, and what sits on the front screen are decisions made separately for each brand.
Then there is configuration: languages, availability by market, support hours, and the settings that control what is offered where. None of this is development work. It is setup, and on a platform built for several brands it is done through the back office without a release.
A multi-brand back office typically handles:
The first is whether brand separation is a configuration setting or a second installation. A second installation means a second set of updates, a second integration surface, and manual reconciliation between two sets of numbers.
The second is whether a change deploys once or repeatedly. If a fix to a shared component has to be applied to each brand in turn, the cost of every future release multiplies by the number of brands.
The third is whether reporting consolidates natively. Combining figures by hand is workable with two brands and becomes the main obstacle with more.
All three are answerable before any commitment. An operator considering a second brand can put them to a provider during evaluation and receive a specific answer.
Where that division falls depends on whether the platform treats a brand as a separate deployment or as a configuration layer inside one system. The difference surfaces in every task that follows, from reporting to content updates, which makes it a practical criterion when selecting an iGaming solution provider. Soft2Bet builds the second case: shared platform services sit underneath, and brand-level settings sit on top, so partners administer several brands from one back office.
Source: https://www.magnific.com/free-photo...0b-e000-4dfd-8498-c74422a7db70&query=software
What the Second Brand Inherits
The heaviest technical work is already done, and content integrations are the clearest example. Once a game supplier is connected to the platform, the titles it delivers become available to any brand running on that platform. The second brand selects from the existing catalogue and skips the integration work entirely.The account layer carries over in the same way. PAM (Player Account Management) holds records for each brand separately, while the administration screens, verification steps, and account status handling are one system. A support request for the second brand is worked in the same interface, with the same tools, by the same people who handle the first.
Reporting inherits its structure. The views built for the first brand exist for the second on day one, which means reporting produces usable output from the opening week.
What Has to Be Built Each Time
Everything the player sees is brand-specific by design. The frontend carries the theme, the navigation, the lobby arrangement, and the interface copy. Two brands on the same platform can look nothing alike, and in most cases that is the reason for launching the second one.Content selection is the second piece of per-brand work. The catalogue is shared, but which titles appear, how the lobby is grouped, and what sits on the front screen are decisions made separately for each brand.
Then there is configuration: languages, availability by market, support hours, and the settings that control what is offered where. None of this is development work. It is setup, and on a platform built for several brands it is done through the back office without a release.
How the Back Office Changes
Running two brands changes the shape of daily administration more than the volume of it. Reporting needs two views at once: the brand on its own and the operation as a whole. Permissions need scoping, because staff working on one brand rarely need access to another. Support requests need to arrive already identified by brand.A multi-brand back office typically handles:
- reporting that separates brand-level output from the combined picture
- permissions set per brand, so each person sees only what they administer
- support requests routed by the brand they came from
- content changes applied to one brand or pushed to several at once
- market settings configured once and reused wherever they apply
What to Check Before the Second Brand Is on the Roadmap
Three questions separate a platform that will carry a second brand from one that needs work first.The first is whether brand separation is a configuration setting or a second installation. A second installation means a second set of updates, a second integration surface, and manual reconciliation between two sets of numbers.
The second is whether a change deploys once or repeatedly. If a fix to a shared component has to be applied to each brand in turn, the cost of every future release multiplies by the number of brands.
The third is whether reporting consolidates natively. Combining figures by hand is workable with two brands and becomes the main obstacle with more.
All three are answerable before any commitment. An operator considering a second brand can put them to a provider during evaluation and receive a specific answer.
