> For the complete documentation index, see [llms.txt](https://docs.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pakk.io/products-and-inventory/multi-location/items-batches-and-locations.md).

# Items, Batches and Locations

s you will already know, all stock control in Pakk is done through the ‘batch’ system. Multi-location inventory is achieved by assigning Locations to Batches.

* Items don’t have Locations assigned, only Batches do.
* When manually creating a new Batch, you can set a Location or leave the Batch as ‘Unlocated’ if you don’t want to track Location for that Batch or Item.
* Once a Batch has been created, you can’t change the Location simply by editing the Batch manually (you need use the ‘Relocate’ action, see below).
* Batches can only have a single Location, so stock within a single Batch cannot be split across multiple Locations. If you need to split out the stock of a Batch to multiple Locations, use multiple Batches.
* Once a located batch starts to get stock (either via a Stock Adjustment, Stock Transfer or Purchase Order), you will see the ‘Location Stock Levels’ for that Item start to reflect the different Locations at which stock (i.e. batches) are available.

\ <br>


---

# 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://docs.pakk.io/products-and-inventory/multi-location/items-batches-and-locations.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.