> 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/configure-pos-and-store-manager/inventory-and-purchasing/setting-up-inventory-rules.md).

# Inventory rules

This topic describes how to configure inventory rules. These include cost update method to use when receiving POs and whether to include landed cost in the cost calculation.

1. Click **File** | **Configuration**.
2. Click the **Inventory Rules** tab.
3. (Optional) Select inventory rules for the store, e.g., whether to update item cost when receiving purchase orders, whether to include landed cost, and what price to display in POS.

<details>

<summary><img src="https://2921455087-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2FpopbobAPoZyocahbnRhK%2FMORE%20INFO.png?alt=media&amp;token=b6405f3b-3d08-43d4-8bb4-9e98e4de32b3" alt="" data-size="original"></summary>

<table><thead><tr><th valign="top">Option</th><th valign="top">Field</th><th valign="top">Description</th></tr></thead><tbody><tr><td valign="top">Cost Update Method</td><td valign="top">None</td><td valign="top">Store Manager can automatically update the cost of items received through purchase orders or inventory transfers. Select this option if you do not want to change existing costs when items are received.</td></tr><tr><td valign="top"></td><td valign="top">Last Cost</td><td valign="top">Select this option if you want Store Manager to automatically update the cost of items based on the item cost on the most recent purchase order.</td></tr><tr><td valign="top"></td><td valign="top">Weighted Average</td><td valign="top">Select this option if you want Store Manager to automatically update the cost of items based on the average cost of all in stock (existing) and new units, e.g., you have 2 units in stock @ $10/ea. and 20 new units just arrived at $12/ea. for a total of $260. The weighted average cost ($260/22 units) is $11.82.</td></tr><tr><td valign="top">Landed Cost</td><td valign="top">Use landed cost when receiving merchandise</td><td valign="top">Select this option if you want to use landed cost, e.g., include tax, shipping, tax on shipping, and invoice discounts in the cost of each item received.</td></tr><tr><td valign="top"></td><td valign="top">Default Cost Distribution Method</td><td valign="top">Select the default cost distribution method (Quantity, Value, or Manual) that you want Store Manager to use to calculate the landed cost. Refer to <a href="/store-manager/configure-pos-and-store-manager/inventory-and-purchasing/calculating-landed-cost.md"><strong>Landed cost</strong></a> for more information about the calculations used for landed cost.</td></tr><tr><td valign="top">Price Calculation</td><td valign="top">Use Minimum Price</td><td valign="top">Store Manager analyses discount, level, sale, and buydown prices for the item and calculates the lowest price for the item.</td></tr><tr><td valign="top"></td><td valign="top">Use Level if it exists. Otherwise use minimum.</td><td valign="top">Store Manager calculates the price of the item based on the defined price level. If the price level does not exist, it uses the minimum price.</td></tr><tr><td valign="top"></td><td valign="top">Prioritize in order of: quantity discount, level, sale, then buydown</td><td valign="top">Store Manager calculates the quantity discount price. If no quantity discount exists, it uses the price level. If no price level exists, it uses the sale price. If no sale price exists, it uses the buydown price.</td></tr></tbody></table>

</details>

4. 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/configure-pos-and-store-manager/inventory-and-purchasing/setting-up-inventory-rules.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.
