> For the complete documentation index, see [llms.txt](https://docs.lidiacommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lidiacommerce.com/products/lidia-pim/pim-user-guide/inventory.md). # Inventory The **Inventory Management** section in the PIM system provides tools to manage and organize product-related inventory details, including **price lists** and variant pricing. *** ### **Price Lists** The **Price Lists** page displays all available pricing lists in the system and allows users to manage them efficiently. * Users can **view, edit, and delete** price lists. * Each price list contains **specific pricing details** for products and their variants. * Pricing lists are **categorized with unique codes** for easy identification. * Users can **filter, sort, and group** price lists based on various attributes. #### **Key Features:** * **List ID**: Unique identifier for each price list. * **Name**: The descriptive name of the price list. * **Code**: Short code representation of the price list. * **Status**: Indicates if the price list is **active** or inactive. --- # 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.lidiacommerce.com/products/lidia-pim/pim-user-guide/inventory.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.