> For the complete documentation index, see [llms.txt](https://help.urbanpiper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.urbanpiper.com/store-manager/prime-web/86ing-an-item-or-modifier.md). # 86'ing an item or modifier {% embed url="" %} In this guide, we will learn how to manage stock using Prime Order Tracker. This involves managing the stock of items or modifiers efficiently. ### Step 1: Access Stock Control * Navigate to the **Stock Control** section. * Here, all items will be listed. ### Step 2: Toggle Item Availability * To turn off an item, simply toggle off the button next to it. * Ensure to save the changes made. ### Step 3: Manage Stock Across Locations * Use the Stock Control feature to manage stock across different locations. * View all in-stock and out-of-stock items at once. * Filter items category-wise for more specific control. ### Step 4: Control Modifier Stock * Navigate to the modifier section to control the stock of modifiers. * Toggle the top button and hit Save to switch off the particular item or modifier on the aggregator's UI. ### Step 5: Verify Changes * Go to the **Live Orders** section. * Access the **Logs** to verify if the item was successfully turned off. Thank you for using Prime Order Tracker to manage your stock efficiently. --- # 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://help.urbanpiper.com/store-manager/prime-web/86ing-an-item-or-modifier.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.