> 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/deactivating-your-doordash-storefront.md).

# Deactivating your DoorDash storefront

This article explains how to deactivate a DoorDash storefront through Atlas.

{% hint style="info" %} <mark style="background-color:$info;">This is a sub-article of</mark> [<mark style="color:blue;background-color:$info;">Deactivate a location</mark>](https://help.urbanpiper.com/business-manager/deactivate-a-location)
{% endhint %}

**How DoorDash deactivation works**

DoorDash deactivation is handled directly from the Hub in Atlas. Unlike other platforms, DoorDash deactivation cannot be initiated from the Deactivate Storefronts flow; it must be raised from within the location's Hub page.

Once you raise a deactivation request, UrbanPiper sends it to DoorDash immediately; no manual follow-up is needed from you or the UrbanPiper team. Once DoorDash approves the request on their end, the status is automatically updated in Atlas, and the location is marked as deactivated. UrbanPiper will stop processing orders for this location once this is done.

***

**Steps to deactivate a DoorDash storefront**

1. Log in to **Atlas** and go to the location you want to deactivate.
2. Open **Hub** for that location.<br>

   <figure><img src="https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2Fc7Ubo1Bmdv4J3Fy1G7BY%2Fimage.png?alt=media&amp;token=05201e7b-0c52-4393-83a9-e4e1b253c391" alt=""><figcaption></figcaption></figure>
3. Click the **⋯** icon next to DoorDash.
4. Select **Deactivate.**<br>

   <figure><img src="https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2FXygFBUqXM9KJ2AfbwjDT%2Fimage.png?alt=media&amp;token=d02f2519-9341-4fc3-9bbe-2dae22b50843" alt=""><figcaption></figcaption></figure>
5. Check the confirmation checkbox and click **Deactivate.**<br>

   <figure><img src="https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2FVwLdbgf3QRv6vLNOMBqr%2Fimage.png?alt=media&amp;token=cab54209-4c87-489b-9ac1-39cda0196583" alt=""><figcaption></figcaption></figure>

***

**What stops after deactivation is complete**

Once DoorDash approves the deactivation request and the location is marked as deactivated in Atlas:

* Order relay from DoorDash to your location will stop
* Catalogue updates, inventory control, and location status updates will no longer be processed by UrbanPiper for this location on DoorDash

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.


---

# 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/deactivating-your-doordash-storefront.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.
