> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/dokumentation/assets/inventory.md). # Inventory The inventory list: columns, search, filters, export, cost display and bulk actions for multiple services. **Path:** sidebar → **"Assets" → "Inventory"** ("My organization" view: **"My organization" → "Inventory"**) The inventory lists all of the company's services, including those that have been ordered and are still being delivered. Clicking a row opens the [detail page of the service](/dokumentation/assets/inventory/asset-details.md). Right-click to open it in a new tab or copy the link. Services with the status "Removed" or "Cancelled" and one-time purchased add-ons are **not shown**. ## Costs in the header * **"Current costs"**: ongoing monthly costs of the currently displayed (filtered) services. * **"Forecast"**: costs including changes that have already been requested or are upcoming. Both values adapt to the filters you set. This way you can see, for example, the costs of a location or a category. ## Columns Columns can be shown and hidden, sorted and filtered. Some are hidden by default. | Area | Columns | | ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Identification** | "Asset ID", "Preview image", "Service name" (chain icon = linked services), "Linked main service", "Inventory number" | | **Origin** | "Supplier", "Invoice issuer" | | **Assignment** | "Employee", "Email", "Departments", "Department/Company Name", "Location", "Address", "Warehouse", "Group (reservation)", "Service owner", "Cost center" | | **Features** | "Category", "Service Features", "Options", "Asset Features" (e.g. serial number, IMEI) | | **Costs and contract** | "Current costs", "One-time costs", "Offer type" (purchase, rent, mobile contract, leasing), "Remaining term", "Extension period", "Activation date", "Order date" | | **Status** | "Status", "Type" (open change: "Order", "Cancellation", "Call-off", "Change"), "Add-ons", "Note", "Confirmation" (receipt confirmation) | Administrators set up additional, company-specific columns under [Portal settings → "Additional table columns"](/dokumentation/settings/portal-settings.md#additional-table-columns). ## Search, filters and export The **search** finds services by service name, inventory number, invoice issuer, asset features (e.g. serial number or IMEI), employee name, department, location, asset ID, product features and booked options. With **export** you download the current table as an Excel file, including the additional columns. With large amounts of data, this may take a moment. How to set filters and save views is described in [The user interface](/dokumentation/getting-started/user-interface.md#tables-filters-and-views). ## Buttons above the table | Button | Function | | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | **"Record inventory"** | Manually create an asset that already exists → [Record and import inventory](/dokumentation/assets/inventory/record-and-import-inventory.md) | | **"Import"** | Import many assets via Excel → [Record and import inventory](/dokumentation/assets/inventory/record-and-import-inventory.md#importing-inventory-via-excel) | | **"Actions"** | Bulk actions for selected rows (see below) | ## Bulk actions Select one or more rows and choose under **"Actions"**: | Action | What happens | | ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **"Cancel"** | Creates a cancellation as an order request for each service (up to 100 services at once). Services that cannot be cancelled are listed with the reason. | | **"Assign add-on"** | Choose matching add-ons; they are created as an order request for each selected service. | | **"Store service"** | Return **"External"** (sent back to the supplier) or **"Internal"** (stored in one of your own warehouses). | | **"Move"** | Assign services to another employee, location, home office or warehouse. Optionally with receipt confirmation and adoption of the target's cost center. | | **"Request successor service"** | Request a new service for each selected service (same assignment) and define what happens to the old one: no action, return or cancellation. *(Administrators)* | | **"Update service owner"** | Set the responsible organizational unit ("Service owner"). | | **"Please confirm receipt."** | Confirm pending receipt confirmations in bulk. *(Administrators)* | | **"Request confirmation of receipt"** | Ask employees to confirm receipt. *(Administrators)* | Details on each action and its prerequisites: [Lifecycle actions](/dokumentation/assets/inventory/lifecycle-actions.md). --- # 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://hub.equipme.io/dokumentation/assets/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.