> For the complete documentation index, see [llms.txt](https://help.urbanpiper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.urbanpiper.com/business-manager/creating-a-new-location.md).

# Creating a new Location

{% embed url="<https://urbanpiper.portal.trainn.co/share/thL637P4WHKx06rv9C4zcQ>" %}

## How to Add a New Location

In this article, we will guide you through adding a new location on UrbanPiper.

1. **Log into your Atlas portal:** Begin by logging-in into your Atlas portal.
2. **Navigate to Locations:** Click on the 'Location' tab.
3. **Add a New Location:** Click on 'Add Location'.
4. **Select Number of Locations:** Choose the number of locations you want to create.
5. **Enter Location Details:** Fill in the details for the new location, including:
   * Name
   * Address
   * City
   * The contact number of the restaurant
   * Email address (if available)
6. **Proceed to Next Step:** Click 'Next' once all the details are entered.
7. **Multi-Brand Setup (Optional):** If applicable, associate the Brand with the location and click 'Next'.
8. **Catalog Options:** Choose to either copy the catalog from existing locations or skip to add it later.
9. **Select Platform or DSP:** Choose the platform or DSP with which you want to associate the location.
10. **Finish:** Click 'Finish' to add the location.

Your new location is now created.


---

# 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://help.urbanpiper.com/business-manager/creating-a-new-location.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.