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

# Creating a Stock Product

1. In the [**Admin Portal**](https://admin.gobossit.com/), go to the **group** level.
2. Navigate to **Stock > Products**.
3. Click **Add Stock Product**.
4. Enter the details:
   1. **Name** — Identifier of the stock product (e.g., Chips)
   2. **Unit** — Base measurement unit
   3. **Stock Category** — Optional grouping for organisation
   4. **Price type**
      1. **Fixed** — Price has to be manually updated.
      2. **Dynamic** — Price will automatically update based on supplier orders.
      3. **Notify Price Change** — A price change notification will be created based on supplier orders, which can then be approved or rejected.
   5. **Current unit cost** — Base cost for one unit of measurement
   6. **Reorder quantity** — Stock level at which reordering should occur
   7. **VAT, %** — Applicable VAT rate


---

# 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/stock/creating-a-stock-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.
