> For the complete documentation index, see [llms.txt](https://manual.firstresonance.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.firstresonance.io/plans-and-autoplan/location-constraints.md).
# Location constraints
A simple, yet powerful method for constraining which inventory locations can feed a plan
### Overview
Each plan allows for configuring location constraints. The location constraint has two options:
1. An operator - either "in" or "not in"
2. A list of locations
When the constraint is defined, only inventory meeting that constraint can be allocated to the plan. The selected locations include all of their hierarchy, meaning that all child locations are also considered.
### Location constraints for site planning (distribution requirements planning)
Let's say that you have two sites: one in California and one in Massachusetts. If you are building different products at both sites, you can ensure only material physically located at the site is allocated to the plan. In this case, the setup would like something like the below:
* Plan 1
* Part A (made in California)
* Location constraint: "In California"
* Plan 2
* Part B (made in Massachusetts)
* Location constraint: "In Massachusetts"
Only Plan 1 will consume inventory located in California locations and only Plan 2 will consume inventory located in Massachusetts locations.
---
# 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://manual.firstresonance.io/plans-and-autoplan/location-constraints.md?ask=&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.
