> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/store-manager/manage-inventory/manage-offline-inventory/moving-item-to-offline-inventory.md).

# Move an item to offline inventory

This topic describes how to move an item to offline inventory.

1. Click **Inventory/Purchasing**.
2. Click **Offline Inventory**.
3. Click **New**.
4. Click in the **Find** field and search for the item.
5. Select the item and click **OK**.
6. (Optional) If you store requires reason codes for inventory changes, click the browse icon beside the **Reason Code** field, select a reason for moving the item to offline inventory, and click **OK**.
7. In the **Comment** field, enter any additional comments about why you are moving the item to offline inventory.
8. In the **Quantity** field, enter the number of items you want to move to offline inventory.

{% hint style="info" %}
If the item is serialized, the **Quantity** field is disabled.
{% endhint %}

9. (Optional) If the item is serialized:
   1. Click **New**.
   2. Select the serial number or serial numbers.
   3. Click **Save And Close**.

{% hint style="success" %}
Click **All** to select all serial numbers in the list, or press **Shift** and **click and drag** to select a range of serial numbers.
{% endhint %}

10. Click **Save And Close**. The item is moved to offline inventory in the quantity you specified.


---

# 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://docs.rmhpos.com/store-manager/manage-inventory/manage-offline-inventory/moving-item-to-offline-inventory.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.