> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/administration/settings/set-up-inventory-locations-and-suppliers.md).

# Set up inventory locations and suppliers

The purchase order template preview includes examples with full supplier and delivery details and with optional details omitted. Switching examples changes only the preview and does not edit or save the template.

Settings -> Inventory is also where you turn the Inventory module itself on or off. Switch **Enable inventory** and save; turning it off hides inventory across the app, but keeps your locations, suppliers, and stock so you can turn it back on anytime. This page stays reachable by permission alone even while Inventory is off, so an admin can always turn it back on.

Below the toggle, Inventory Locations is where you set up where stock lives and who you restock from. Under Inventory Locations you add the places that hold stock (a warehouse, a truck) and mark one as the default; the default can't be deleted, and deleting any other location transfers its inventory to the default.

Under Inventory and Purchase Order Suppliers (titled Inventory Suppliers while the module is off) you add the vendors you buy from. These locations and suppliers are then used when you track stock, reorder items, and send purchase orders.

While the module is on, the page ends with **Purchase Order Template**, the PDF attached when you email a purchase order to a supplier. Click any text on it to change the wording, use **Insert variable** to add details such as the supplier's contact name, or switch to **Edit code** for the layout - see [Changing what the PDF looks like](/field-operations/inventory/emailing-a-purchase-order-to-a-supplier.md#changing-what-the-pdf-looks-like).

![Inventory settings](https://3838208579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Flu1pgNH0CrkCPslG8suQ%2Fuploads%2Fgit-blob-09fb84920e8bc05d97a9da8a34579143a02ca125%2Fsettings-inventory.png?alt=media)

> **Where to find it:** Settings -> Inventory

## Related guides

* [Feature availability and setup](/getting-started/getting-started/feature-availability-and-setup.md)
* [Add or edit a pricebook item](/administration/settings/add-or-edit-a-pricebook-item.md)
* [Add the intake form to your website](/administration/settings/add-the-intake-form-to-your-website.md)
* [Automate task statuses with Task Automations](/administration/settings/automate-task-statuses-with-task-automations.md)
* [Build your intake form](/administration/settings/build-your-intake-form.md)
* [Bulk upload pricebook items from a spreadsheet](/administration/settings/bulk-upload-pricebook-items-from-a-spreadsheet.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://learn.withessential.com/administration/settings/set-up-inventory-locations-and-suppliers.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.