> 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/update-on-hand-quantities-with-parent-child-relationships/setting-up-parent-child-relationships.md).

# Configure parent-child relationships between items

This topic describes how to configure parent-child relationships between items.

Parent items contain a set quantity of child items, e.g., a case (parent item) of 24 bottles of water (child items). When the on hand quantity of the child item is zero, the parent item can be opened up to add the child items to the quantity on hand. This topic describes all steps required to set up parent-child relationships between items in RMH.

## (Optional) Configure purchase order options for child items

1. Click **Setup**.
2. Expand **Inventory/Purchasing**.
3. Click **Order Setting**.
4. Select **Child Reorder**.
5. Click **Save And Close**.

## Configure parent-child relationships between items

{% hint style="info" %}
You must add both the parent and child items to the store database before you can create a parent-child relationship between them.
{% endhint %}

1. Click **Merchandising**.
2. Click **Items**.
3. Double-click the child item to open it.
4. On the **Special** tab, do the following:
   1. Click the browse icon next to the **Parent item** field and select the parent item.
   2. In the **Child quantity** field, enter the quantity of child items within the parent item.
5. Click **Save And Close**.


---

# 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/update-on-hand-quantities-with-parent-child-relationships/setting-up-parent-child-relationships.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.