Skip to main content
Disabling a shop is a consequential Owner-only action. Tapp soft-deactivates the selected shop, removes it from the normal active shop list, and switches the Admin App to another active shop.

​
Who can do this?

Owners can use this workflow with the scope described here. Write access is checked for the currently selected shop. Backend authorization is authoritative; entering a route directly does not expand a role.

​
Where

Open Settings for the intended shop and scroll to Disable shop. The action is disabled when this is your only active shop.

​
Steps

  1. Check the shop name in the sidebar and page before opening the action.
  2. Ensure at least one other active shop exists and that any operational work in the current shop is complete.
  3. Choose Disable shop and read the confirmation, which names the selected shop.
  4. Choose the red confirmation action only when the target is correct. Cancel or click outside the dialog to stop.
  5. Wait while Tapp refreshes the active shop list and selects another shop. Verify the destination before continuing.

​
Platform notes

The backend requires Owner access and performs a soft deactivation rather than a client-side hide. The /store/my list then excludes the inactive shop. The UI also blocks the last active shop, and the API can return a LAST_ACTIVE_STORE error if the condition changed concurrently.

​
Market notes

The product action exists for GB and DE. Disabling a shop is not documented as canceling platform billing, settling balances, completing fiscal duties, ending provider agreements, or deleting retained records. Handle those obligations separately with the appropriate owner and reviewer.

​
Troubleshooting

If the button is disabled, add or retain another active shop; do not bypass the safeguard. If the API reports the last active store, refresh the list. For any other error, stop before repeating, record the target shop and message, and ask @sebestil to review the state.