> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/stock/set-stock-levels-per-warehouse.md).

# Set stock levels per warehouse

Stock levels are stored per item and per warehouse.

This means the same item can have different values in different locations.

### Stock values you can use

For each item in each warehouse, you can set:

* **Current stock**
* **Minimum stock**
* **Preferred stock**
* **Maximum stock**

### Why these values matter

These values help you:

* see what is available now
* know when to reorder
* restock to a target level
* avoid storing more than you want

### Good setup approach

Start with your most important items first.

Use real usage data when you set minimum and preferred levels.

Review the values regularly and adjust them over time.

### Frequently asked questions

<details>

<summary>Do I set stock levels once for the whole account?</summary>

No.

You set them per warehouse.

</details>

<details>

<summary>Why should I use minimum and preferred stock?</summary>

They help you see when to reorder and how far to restock.

</details>

<details>

<summary>Can one item have different values in different warehouses?</summary>

Yes.

That is a normal part of stock management.

</details>

### Related topics

* [**Stock**](/marketplace-packages-and-power-ups/power-ups/stock.md)
* [**OutSmart packages**](/marketplace-packages-and-power-ups/marketplace/outsmart-packages.md)
* [**Power-Ups**](/marketplace-packages-and-power-ups/power-ups.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/stock/set-stock-levels-per-warehouse.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.