> 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/stock-count.md).
# Stock Count
Stock counting is essential for identifying variances between theoretical usage (system calculations) and actual usage (physical counting).
## Creating a Stock Count
1. In the [**Admin Portal**](https://admin.gobossit.com/), navigate to **Stock** > **Counts**.
2. Click **Create new stock count.**
3. To add product(s), click:
1. **Add items** — Search for and select individual products to include in the count.
2. **Import from .csv** — Import stock count data.
3. **Add by category** — Add all products from a specific category (e.g., *Drinks*, *Pizza Toppings*) in one action.
4. **Add by stock lis**t — Add all products from a stock list.
4. Fill in the quantities counted for each product.
5. Click **Compare Stock**.
The system allows counting in different items for the same stock product. It automatically consolidates to total stock for the stock product.
> **Example**
>
> Coke Inventory
>
> * Count large deliveries: 9 cases (24 cans each)
> * Count remaining individual units: 3 cans
>
> This results in a total of 219 pieces of Coke.
---
# 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/stock/stock-count.md?ask=&goal=
```
`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.