> 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-keeta-storefront.md).

# Deactivating your Keeta storefront

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

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

**How Keeta deactivation works**

To deactivate a Keeta storefront, you will need to complete the deactivation directly on the Keeta merchant portal. UrbanPiper initiates the deactivation request from Atlas, but the final step must be completed by you on the Keeta portal.

Keeta supports both brand-level and location-level deactivation from the portal — follow the steps below based on what you want to deactivate.

***

**Steps to deactivate a Keeta storefront**

**Deactivate all locations under a brand**

Use this if you want to deactivate all locations associated with a brand at once.

1. Log in to the [<mark style="color:blue;">**Keeta portal**</mark>](https://merchant.mykeeta.com/) using your merchant credentials.
2. Navigate to **API Management.**
3. Click **De-authorize** next to the UrbanPiper re-integration service provider name.<br>

   <figure><img src="https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2FB7Y58u4YmvjWTfHjKlVI%2Fimage.png?alt=media&amp;token=06e5a8a7-899b-454e-b6ee-d0f25430a52c" alt=""><figcaption></figcaption></figure>
4. Review the list of all locations associated with the brand.
5. Click **Submit** to complete the de-authorization.<br>

   <figure><img src="https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2FLmATW4anFWloWGEPvAmz%2Fimage.png?alt=media&amp;token=b32da404-1cf7-42b1-af7c-b1547c9ded9e" alt=""><figcaption></figcaption></figure>

\
**Deactivate a specific location**

Use this if you want to deactivate one or more specific locations without affecting the rest.

1. Log in to the **Keeta portal** using your merchant credentials.
2. Navigate to **API Management.**
3. Click **Edit** next to the UrbanPiper re-integration service provider name.<br>

   <figure><img src="https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2Frn8VjWaksnu26768yasp%2Fimage.png?alt=media&amp;token=e0e81ac1-d490-437a-8ac2-a000cd0a36d3" alt=""><figcaption></figcaption></figure>
4. Unselect the location(s) you want to deactivate.
5. Click **Save changes** to complete the de-authorization for the selected location(s).<br>

   <figure><img src="https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2FeC3DiY2YjEqmxBSvLINZ%2Fimage.png?alt=media&amp;token=71373007-b7fd-4bc3-a6a7-bbde373daa0a" alt=""><figcaption></figcaption></figure>

***

**What stops after deactivation is complete**

Once deactivation is complete on both Atlas and the Keeta portal:

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

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-keeta-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.
