> 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/menu/products/creating-a-product.md).

# Creating a Product

1. In the [**Admin Portal**](https://admin.gobossit.com/), navigate to **Menu** > **Products**.
2. Click **Add product.**
3. Configure the details:
   1. **Name** — Name of the product for internal reports and POS
   2. **External Name** — Name of product visible to customers online & on integrations.
   3. **KDS Ticker Name** — Used in the KDS bottom bar for reference

      [KDS Bottom Bar](https://docs.bossithq.com/pos/kitchen-display-system-kds/kds-bottom-bar.md)
   4. **Printing name** — Name of product on receipt.
   5. **Department** — Assign to appropriate department(s) for POS and Kiosk
   6. **Online department** — Assign to appropriate department(s) for Web and App
   7. **Brands —** Assign which brand(s) the product belongs to
   8. **PLU —** Automatically generated value (can be manually changed)
   9. **Product type** — Regular, Detailed, Meal, Combo, or Splittable
   10. **Price type**
       * **Fixed** — Product pricing is the same all the time.
       * **Variable —** Product pricing allows variation depending time or day.
   11. **Sold individually** — Whether item appears in product lists (Turn off for toppings that shouldn't be sold alone)
   12. **Active?** — Toggle availability
4. Click **Create**.


---

# 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/menu/products/creating-a-product.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.
