> For the complete documentation index, see [llms.txt](https://nomadia-docs.gitbook.io/products/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nomadia-docs.gitbook.io/products/import-and-data-setup/create-a-depot.md).
# Create a Depot
## 1. Creating and Managing Depots
A Depot is essentially a location—a warehouse, service center, or hub—that you need to manage for scheduling and resource allocation. By following this guide, you will learn exactly how to create these important locations efficiently and accurately.
## 2. Initial Configuration
To begin managing or creating a Depot, follow these steps:
1. Access the **TourSolver web application**. Click on **Configuration**
2. From the **Actions menu**, click **Manage Depots**
## 3. Understanding Depot Details
When you create a new Depot, you will fill out details across three main sections: General, Planning, and Quantity. Each section controls a different aspect of how the Depot functions within your scheduling and resource planning.
### A. General Section
This section handles the basic identification and core rules for your Depot.
Field/Constraint
Purpose/Benefit
Name
Identifying label for the Depot.
Address
Physical location of the Depot.
Constraints
Rules that govern how the Depot operates, such as Assign Resources, Explore Resources, or Availability.
### B. Planning Section
This section defines when the Depot is operational.
* You can specify the opening days.
* You can set the opening time.
* You can set the specific start and end time.
* You have the option to edit multiple opening days from this location.
### C. Quantity Section
This section defines the capacity and inventory available at the location.
* You will edit the initial quantity.
* You can define the available space.
## 4. Creating a New Depot
The most common task is adding a brand new Depot. This requires moving through the three detailed sections described above.
### Adding a New Depot
1. From the **Actions menu**, click **Add**.
**In the General section, enter the required basic information.**
2. Input the **Name** and **Address**.
**Edit the scheduling details.**
3. Click on **Planning**
4. Adjust the **opening days** and **opening time**.
5. Define the **start** and **end** time
**Tip** : You can also edit multiple opening days from this screen to save time when setting complex schedules.
6. To add or edit quantity details, click the **plus** symbol located at the bottom right corner.
**Update the inventory details.**
7. Edit the **initial quantity**.
8. Click **Add**
9. Depot has been created successfully
## 5. Productivity Tips
To manage your Depots efficiently, especially if you have à large number of locations to configure, leverage the bulk action tools.
## 6. Bulk Import or Export Depots
You can easily manage multiple Depot entries at once using the import and export functions.
1. On the main Depot management screen, click the **Actions** menu.
2. Click on **Export** to download the file.
3. Click **Import**, then select Browse Excel to choose a file and import it, or simply drag and drop your file into the upload area.
**Tip**: Using the Export feature first can be helpful if you want to create a template to correctly format the data before performing a bulk Import of new Depots.
---
# 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://nomadia-docs.gitbook.io/products/import-and-data-setup/create-a-depot.md?ask=&goal=
```
`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.