> 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/deactivate-a-location.md).
# Deactivate a Location
How to deactivate a store location from one or all Delivery Service Platforms
### Overview
If a location is permanently closed, no longer in use, or you want to stop receiving orders from a specific platform, you can deactivate it directly from Atlas. This takes the location offline and stops all UrbanPiper services for that location on the selected platform(s).
**NOTE**: You will stop being billed for this location from the next billing cycle. For the current month in which you initiated the deactivation, you will still be billed for any orders processed during that month.
{% hint style="info" %}
**When to use this:** Use this flow to **permanently deactivate** one or more locations from one or more connected DSPs. This flow is intended for permanent closures and should not be used for temporary deactivations or pauses.
{% endhint %}
***
#### Not every platform deactivates the same way
The outcome of your deactivation request depends on the platform. Review the following before you confirm:
**⚡ Deactivates instantly**\
UrbanPiper sends the deactivation request as soon as you confirm, and the platform processes it immediately. Orders will stop flowing to this location once done; nothing more for you to do.
**📨 We raise the request — deactivation takes 3-5 days**\
UrbanPiper raises the deactivation request with the platform on your behalf. Orders will continue to flow in the meantime. The platform typically processes this within 3-5 days. If deactivation is not completed within that window, UrbanPiper will stop processing orders for the selected location(s) and platform(s) within 7 days of your confirmation. You may need to follow up directly with the platform to ensure deactivation is completed on their end.
**🔗 We deactivate, but you need to act on the platform portal too**\
UrbanPiper initiates the deactivation, but you will also need to raise a deactivation request directly on the platform's portal to complete the process. Orders will continue to flow in the meantime until this is done. UrbanPiper will stop processing orders for the selected location(s) within 7 days of your confirmation regardless.
The flow will show you which category your selected platform falls into before you confirm.
***
#### Steps to deactivate a location
1. Log in to **Atlas.**
2. Go to **Settings → Platforms**
3. Click **Deactivate storefronts** in the top right corner (preferred for bulk location(s) platform(s) deactivation).
4. On the **Deactivate storefronts** screen, select your brand from the dropdown. If you manage multiple brands, make sure you select the correct one.
Under **Select Platforms and Locations**, choose the location(s) and platform(s) you want to deactivate. You can select one or more locations and platforms, then click **Continue** to proceed with the deactivation process.
\
**Alternatively**, if you want to deactivate a single storefront, you can also do this directly from its activation screen. Select the platform from the Platforms list, find the storefront, click **View Details**, and then click **Deactivate Storefront** in the top right.
5. If any of the selected storefronts have missing details required by the platform for deactivation, you will see a screen flagging these gaps. Fill in the required details for each storefront listed before proceeding — storefronts with missing details will be left out of the request if not filled in.
6. Once all details are in place, select a reason for deactivation from the dropdown.
7. Review the storefronts listed under **Review your storefronts for deactivation** — this shows you exactly which locations and platforms will be affected. Click on Confirm deactivation request.
8. Review the process preview — this shows you how each platform handles deactivation (instant, 3-5 days, or portal action required).
9. Confirm your request — once submitted, you will see a confirmation: **Deactivation request has been raised.**
**Note:** Storefronts that are not live are skipped automatically and will not appear in your selection.
> 💡 Want to[ ](#user-content-fn-1)[^1]deactivate all storefronts for all brands at once? You can [**Cancel your subscription**](https://help.urbanpiper.com/business-manager/cancel-your-subscription) instead — the option is shown on the selection screen itself.
***
#### What happens after deactivation
Once you submit your deactivation request, here is what happens next:
**UrbanPiper sends the deactivation request to the platform**\
As soon as you confirm, UrbanPiper automatically raises the deactivation request with the selected platform(s) on your behalf. You do not need to follow up with us — it is handled from our end.
**Orders keep flowing until deactivation is complete**\
Your storefront will continue to receive and relay orders while the deactivation is being processed. Orders will only stop once the platform completes deactivation on their end, or after 7 days from the date you confirmed — whichever happens first.
**What stops after deactivation is complete**\
Once your storefront is fully deactivated on a platform, the following services stop for that storefront on that platform:
* Order relay
* Catalogue updates
* Inventory control
* Location status updates
***
#### **Billing adjustment**
Billing for a deactivated storefront works as follows:
* **Current month:** Billing applies to this storefront for any orders processed in the current month — regardless of when in the month the deactivation was confirmed. No partial adjustments are made for the current month.
* **From the next billing cycle onwards:** Once the storefront is deactivated, it will be removed from your active location count, and you will no longer be charged for it going forward.
[^1]:
---
# 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/deactivate-a-location.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.
