> 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-management/create-warehouses.md).

# Create warehouses

Create the warehouses, sub-warehouses, and storage locations you use for Stock.

Create your warehouse structure before you add stock.

Go to **Items → Warehouses** to start.

### What a warehouse can represent

A warehouse can be:

* a main warehouse
* a sub-warehouse
* vehicle stock
* job site storage

### Good setup principles

Use clear names and codes from the start.

Keep the structure simple at first.

Add more locations later when your process is stable.

{% stepper %}
{% step %}

### Open Warehouses

Go to **Items → Warehouses**.
{% endstep %}

{% step %}

### Add a warehouse

Create a new warehouse and enter the main details.
{% endstep %}

{% step %}

### Name and code the warehouse

Use a name and code that your team recognizes immediately.
{% endstep %}

{% step %}

### Repeat for other locations

Add each warehouse, vehicle, or job site location you want to manage.
{% endstep %}
{% endstepper %}

### Frequently asked questions

<details>

<summary>Can I use more than one warehouse?</summary>

Yes.

Each warehouse keeps its own stock levels.

</details>

<details>

<summary>Should I create every possible location at once?</summary>

Not always.

Start with the locations you really use.

</details>

### Related topics

* [**Stock**](/marketplace-packages-and-power-ups/power-ups/stock-management.md)
* [**2BA**](/marketplace-packages-and-power-ups/power-ups/2ba.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/stock-management/create-warehouses.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.