> 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/classes/admin/warehouse/moving-items-within-the-warehouse.md).

# Moving items within the warehouse

{% hint style="info" %}
Walkthrough goes here.
{% endhint %}

Moving an item changes where it is recorded, nothing else. Stock levels stay the same, nothing is ordered, nothing is consumed. You are lining the record up with reality.

Mechanically it works like reassigning a device from one person to another. The only difference is that both sides of the move are locations rather than people.

The usual reasons are an inventory check, a reorganised storage area, or spare monitors sitting in one city while another office needs them.

It is worth doing promptly, because everything downstream trusts this data. Reservations, provisioning requests and stock checks during approval all assume the recorded location is the real one.

### Read more

{% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/HYzVkSCDvZgxGVyD1XKr" %}
[Warehouse management](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/assets/warehouse-management)
{% endcontent-ref %}

### Next

When someone leaves, their equipment comes back through here: [Offboarding employees](/classes/admin/offboarding-employees.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/classes/admin/warehouse/moving-items-within-the-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.