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

# Warehouse management

Warehouse management: managing services in the warehouse, reserving them for groups, issuing them and moving them between warehouses.

**Path:** sidebar → **"Assets" → "Warehouse management"**

Warehouse management shows all services assigned to a **warehouse**, e.g. stock devices for new employees or returned devices that are to be issued again. A warehouse is a [location](/dokumentation/organization/locations.md) that is marked as a warehouse. In addition to your own warehouses, there can be a **supplier warehouse** in which the supplier keeps devices ready for the company.

The table corresponds to the [inventory list](/dokumentation/assets/inventory.md) with the additional column **"New product"**: it shows whether a service has never been in use. At the top you see the "Current costs" and "Forecast" of the warehouse stock.

## Bringing services into the warehouse

* In the inventory or on the detail page, choose **"Store service" → "Internal"**, or
* assign an active service to a warehouse via "Assignment details", or
* specify a warehouse as the target directly when [ordering](/dokumentation/procurement/order-requests-and-checkout.md) or [recording](/dokumentation/assets/inventory/record-and-import-inventory.md).

## Bulk actions

| Action                        | What happens                                                                                                                                                                           |
| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **"Reserve"**                 | Assigns services to a group (organizational unit), e.g. "Reserved for Sales" ("Reserve for group").                                                                                    |
| **"Request provision"**       | Issues services to an employee or location ("Select your delivery location"). Unsuitable services are deselected.                                                                      |
| **"Assign add-on"**           | Books add-ons for the selected services.                                                                                                                                               |
| **"Move service"**            | Moves services to another warehouse. From an internal warehouse, they are rebooked directly; from the supplier warehouse, provision is requested from the supplier. *(Administrators)* |
| **"Please confirm receipt."** | Confirms pending receipt confirmations. *(Administrators)*                                                                                                                             |

**Prerequisites for moving and issuing:** The services have the status "Ready for delivery" and no open approvals.

## Frequently asked questions

**How do I prepare devices for a new employee who starts in a few weeks?**

Order the device into a warehouse or reserve an existing warehouse device for the appropriate group. As soon as the employee has been created, use "Request provision" to request delivery to them.

**Why can't I issue a warehouse service?**

It does not have the status "Ready for delivery", or an approval is still open.


---

# 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/warehouse.md?ask=<question>&goal=<user_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.