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

# Brands

The Brands feature allows venues to operate multiple distinct brands within a single physical location. This enables venues to sell different product categories under separate brand identities whilst managing everything from one central kitchen and POS system.

## What are Brands?

Brands are separate business identities that operate within the same venue. Each brand can have its own product range, distinct branding and visual identity, and separate online presence.

Each brand can have its own website where customers only see products assigned to that specific brand. Integration providers can list multiple brands from that same venue.

> **Example:**
>
> Consider a venue that operates:
>
> * Flame Pizza brand selling pizzas
> * Ice Café brand selling coffees and pastries
>
> Each brand appears as a separate restaurant to customers where customers can visit separate websites for each brand, seeing only the relevant products. However, both brands operate from the same kitchen using the same KDS.

Products can be assigned to show only in a specific brand or in multiple brands. This is done under the Product Overview tab under Brands, or during product creation.

[Creating a Product](https://docs.bossithq.com/menu/products/creating-a-product.md)


---

# 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.bossithq.com/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.
