> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/implementation-guide/plan-and-foundations/multi-brand-and-wallets.md).

# Multi-brand Programmes and Wallets

Running several brands in one programme: one member profile, a wallet per brand, and labels that keep each brand's campaigns and rewards apart.

When one company runs loyalty for several brands, the first decision is whether members are shared.

| If…                                                              | Then                                                                                                              |
| ---------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| Each brand has its own members, currency or legal entity         | **Separate tenants**, one per brand. Nothing is shared; each tenant is set up on its own.                         |
| A consumer can belong to several brands and you want one profile | **One tenant**, with a wallet per brand and labels that scope campaigns and rewards to a brand — described below. |

## One tenant, several brands

<figure><img src="https://226878483-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ4Fuoa1PTF0DrNTgjzJu%2Fuploads%2Fgit-blob-34884e0b76a75e76709f0c096b92b483e74b31e8%2Fig-multi-brand-model.png?alt=media" alt="One member profile branches into Brand A and Brand B. For each brand: an opt-in flag, campaigns and challenges labelled with the brand, a brand wallet the campaigns earn into, and rewards labelled with the brand that are paid from that wallet." width="469"><figcaption><p>One member, a wallet and a set of campaigns and rewards per brand</p></figcaption></figure>

| What                   | How it's modelled                                                                                                                                                                                                                               |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Separate balances      | One [wallet](https://help.openloyalty.io/members-and-activity/wallets) per brand (e.g. `brand_a`, `brand_b`), each with its own expiry and pending rules.                                                                                       |
| Brand membership       | A [custom field](https://help.openloyalty.io/integrations-and-data-exchange/custom-fields) for the opt-in and its date, plus a [label](https://help.openloyalty.io/faq/custom-attributes) such as `brand_a_opt_in = true` that rules can check. |
| Brand-specific earning | Every campaign and challenge carries a label `brand = brand_a`, a condition that the member has opted in to that brand, and an effect that adds units to that brand's wallet.                                                                   |
| Brand-specific rewards | Every reward, fortune wheel and badge carries the same `brand` label; rewards are [paid from](https://help.openloyalty.io/rewards-redemption/rewards/reward-list/creating-reward) that brand's wallet.                                          |
| Brand on every event   | Custom events include a `brand` field in their [schema](https://help.openloyalty.io/members-and-activity/custom-events/custom-event-schemas), so one event type can serve both brands.                                                          |

### Joining a second brand later

When a member who belongs to Brand A joins Brand B, update the opt-in custom field and label — either with `PATCH /member/{member}` (labels and custom fields only) or with a full GET → merge → PUT (see [Member identity](https://help.openloyalty.io/implementation-guide/plan-and-foundations/member-identity.md)).

### Reading data per brand

* **Balances and points history** — filter by wallet: `walletType:code=brand_a`.
* **Campaigns, challenges and rewards to show** — filter by the brand label, e.g. `labels=(brand;brand_a)`.

{% hint style="warning" %}
Several label filters in one list query are combined with **OR**, not AND: `labels=(brand;brand_a),(audience;new)` returns items that match either label. To narrow a list by more than one dimension, use one combined label per use case (e.g. `brand_a_new = true`) or filter the rest in the integration layer.
{% endhint %}

## Checklist

* [ ] It's decided whether members are shared between brands (one tenant) or not (separate tenants).
* [ ] Each brand has its own wallet, with its expiry and pending rules agreed.
* [ ] The opt-in custom field and label exist for every brand and are set at registration.
* [ ] Every campaign, challenge, reward, fortune wheel and badge has a `brand` label — none is left unlabelled.
* [ ] Every earning rule checks the brand opt-in and adds units to the right wallet.
* [ ] Every reward is paid from its brand's wallet.
* [ ] Front ends filter balances by wallet and lists by brand label.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.openloyalty.io/implementation-guide/plan-and-foundations/multi-brand-and-wallets.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
