> 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/releases/old/3-10-8.md).

# 3.10.8

Release Date: June 20, 2022

## **Store Manager**

### Child item cost is updated when a purchase order or transfer in containing parent item is received

Starting with release 3.10.8, when a purchase order or transfer in that contains a parent item is marked as received, if the store uses a **Cost Update Method** (Last Cost, Weighted Average, or Landed Cost) to calculate item cost, the item cost for both the parent and child items are updated. Prior to release 3.10.8 only the item cost of the parent item was updated.

The **Cost Update Method** is selected under **File** | **Configuration** on the **Inventory Rules** tab. If a Cost Update Method is selected, the formula used to update the item cost of a child item is **\[new cost of parent item] / \[child item quantity]**. The new cost of the parent or child item displays in the **Cost** field on **General** tab of the Item screen. The quantity of the child item displays in the **Child Quantity** field on the **Special** tab of the Item screen.


---

# 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/releases/old/3-10-8.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.
