> 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/types.md).

# Types

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

* Tools (category)
  * **Drills**
  * **Screwdrivers**
  * **Saws**
* Communication (category)
  * **Walkie Talkies**
  * **Phones**

**Expected to return**: Check this checkmark if the articles in this type are expected to return. Uncheck if they don't need to return, like tie wraps, or maybe fuel.

When adding types you are required to pick the "unit" and "Lease in other amount than 1". These values will be enforced for all the articles you load into this type.

Another thing you can add is text for documents that need to be signed before and/or after a lease starts of this stock type. This is a great addition to make sure you have a signed confirmation.


---

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