> For the complete documentation index, see [llms.txt](https://docs.brewfather.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brewfather.app/br/inventory.md). # Inventory The inventory is designed to be fully customizable, that means you can add, edit and delete everything. ### Deleting inventory items If you delete an item, you actually remove it from your personal list of ingredients. When organizing inventory stock amounts you don't want to delete items, you want to edit the inventory amount field (setting it to 0 indicates out of stock). If you accidentally delete an item you can add it back by either: 1. Add it back from a recipe where the ingredient have been used from recipe (preferrably), 2. Add it again filling in the info manually, 3. restore default data in the settings (warning: this will reset all in the given category). ### Track inventory usage You substract from inventory when you plan a batch, and actively check each ingredient to remove them from inventory. ![Items not in stock is marked with a red exclamation mark](https://559214094-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LEzhWP2LGeXaKgS2qr4%2F-LFvaUzXEj-UvLAX8VQp%2F-LFvaWyYxMHmTYDS9ruf%2Fimage.png?alt=media\&token=43b3b835-daba-4f08-84a5-44d921ebebed) --- # 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.brewfather.app/br/inventory.md?ask=&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.