> 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/brands-in-the-admin-portal/adding-a-new-brand.md).

# Adding a New Brand

1. In the [**Admin Portal**](https://admin.gobossit.com/), navigate to **Menu** > **Brands**.
2. Click **Add brand**.
3. Enter the details:
   1. **Name** — The name of the brand
   2. **Generic Name** — Used for menu or product sync between venues; identifies items that share the same name.
   3. **Short Name** — The name of the brand displayed in the POS brand selection dropdown.
   4. **Venue Group Brand** — The group it belongs to.
   5. **Address** — The venue’s address displayed on customer receipts.
   6. **Phone** — The contact number displayed on customer receipts.
   7. **Image** — The image displayed on the online venue list.
   8. **Receipt Image** — The image or logo displayed on customer receipts.
   9. **Active?** — Indicates whether the brand is currently active or not.
4. Click **Create**.

{% hint style="warning" %}
Only users with this permission can access brands: **"User can access brands"**
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bossithq.com/brands/brands-in-the-admin-portal/adding-a-new-brand.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.