> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/admin/warehouse/location-zone/what-is-a-location-zone.md).

# What is a Location Zone?

Warehouses can be divided into zones to help manage their operations, especially the large ones. They can be separated based on the inventory stored, picking methods, or any other way that best suits a business’s workflow.

### Creating a Location Zone

To create a location zone, you have to specify the name and description for the zone and then select the store for which the zone is being created. 

{% hint style="info" %}
*To create a location zone, go to Menu > Admin > Warehouse > Location Zone* 
{% endhint %}

**Location Zone Fields**

<table><thead><tr><th width="222">Field</th><th>Description</th></tr></thead><tbody><tr><td>Zone Name</td><td>Specify the name of the zone in this field.</td></tr><tr><td>Store</td><td>Select the store for which you want to create the zone.</td></tr><tr><td>Description</td><td>Enter the description for the location zone.</td></tr></tbody></table>

After filling in the details, click on "Save" to create the location zone.&#x20;

All the zones created in the system are listed in the "Location Zone Centre".


---

# 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.xorosoft.com/xoroerp-1/admin/warehouse/location-zone/what-is-a-location-zone.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.