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

# Inventory - Categories

What do you have?

This page shows you an overview of all the stock categories in your event. On the left side you have a list of those categories. Click one of then to show the stock types.

On the top left of the page there is a search field. Use this to find an article fast using the article [bar/QR code](https://docs.eventication.com/event/stock/inventory-categories/types/articles.md).

Adding a new category asks you for a name. Optionally you can add an image to the category to create a visual indicator.

The stock inventory exists of a 3 layer system.

### Categories

A stock category is a grouping of what kind of stock this is. Some examples of our events:

* Access Scanners
* Communication
* Vehicles
* Tools
* Office supplies
* Electronics

### [Types](https://docs.eventication.com/event/stock/inventory-categories/types.md)

Stock types are a grouping of the same kind of articles. For example:

* Tools (category)
  * Drills
  * Screwdrivers
  * Saws
* Communication (category)
  * Walkie Talkies
  * Phones
* Vehicles (category)
  * Artist vans
  * Manitu's
  * Forklifts

### [Articles](https://docs.eventication.com/event/stock/inventory-categories/types/articles.md)

An article is the actual hardware like a hammer, or the keys to a car.


---

# 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.eventication.com/event/stock/inventory-categories.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.
