> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/using-peakcommerce/products-and-bundles/product-brands.md).

# Product Brands

If you sell under more than one brand, every rate plan in your catalog carries the brand it's sold under. That brand decides which brand's portal shows the subscription, which brand's payment page and gateway collect for it, and where its revenue is reported.

Open it from **Product Catalog → Brands**.

## How a rate plan gets its brand

| Level              | What you do                                                                                                                                                                                                                                                          |
| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Billing system** | Link each brand to the billing system it bills in, on the brand's page in **Settings → Brands**. If only one brand bills in a billing system (for example a Stripe account per brand), every product from it takes that brand automatically. There's nothing to tag. |
| **Product**        | In a billing system shared by several brands, give each product its brand. The product's brand fills in every rate plan under it.                                                                                                                                    |
| **Rate plan**      | When one product spans brands, set the rate plans that belong to another brand individually. A rate plan set individually keeps its brand when the product's brand changes.                                                                                          |

**Example:** one product, *Marketing plans*, has five rate plans: three for Brand A and two for Brand B. Set the product to Brand A, which fills in all five, then set the two Brand B plans individually.

New products and rate plans from a catalog sync fill in the same way: a new rate plan takes its product's brand, and a new product from a single-brand billing system takes that brand.

## Assign brands in bulk

1. Filter the list by name or SKU, billing system, category or product set.
2. Tick the products (or tick the header to select every one shown).
3. Choose a brand and select **Preview**. The preview shows how many rate plans will change and how many are set individually and won't.
4. Select **Apply**.

If the catalog changed after you previewed (for example a sync added plans), **Apply** is refused and you're asked to preview again, so nothing changes that you haven't seen counted.

**Suggestions.** When a product's name contains exactly one brand's name, the list offers that brand as a suggestion. It's only a suggestion: select it to see the preview, and nothing changes until you apply.

A brand can only go on products from the billing system it bills in. If a brand isn't linked to a billing system yet, link it first on its page in **Settings → Brands**.

## Product sets show the brand; they don't set it

In the product-set editor each item shows its rate plan's brand, read from the catalog. Change it here, in the catalog. A product set can include rate plans from several brands (for example a set your support team uses).

## Who can change this

Viewing needs **Products: Read**; assigning brands needs **Products: Update**. Every change is recorded in the audit log.


---

# 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://docs.peakcommerce.com/product/using-peakcommerce/products-and-bundles/product-brands.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.