Skip to main content
Switching shops changes the active shop context used by navigation, orders, notifications, settings, and other store-scoped screens. Use the persistent shop switcher rather than changing a URL by hand.

​
Who can do this?

Owners and Managers and Staff can use this workflow. Permission is always evaluated for the selected shop. A role without write access cannot bypass the restriction by opening a route directly; API authorization remains authoritative.

​
Where

Use the shop name and avatar at the bottom of the Management Admin App sidebar. On Shop overview, Owners and Managers can also use the arrow beside the displayed shop when more than one manageable shop exists.

​
Steps

  1. Finish or save work with unsaved changes before switching.
  2. Open the shop switcher and identify the destination by name, logo or initial, and address.
  3. Select the destination. Tapp updates the active store and store-scoped data.
  4. Verify the shop name before making the next operational change.

​
Platform notes

The web app persists the selected shop locally and reloads queries that depend on its ID. An unsaved-changes guard can interrupt a switch so you can stay and save or deliberately continue. Staff may switch among shops in which they have Staff membership, even though Shop overview editing itself is limited to Owner and Manager memberships.

​
Market notes

The behavior is shared by GB and DE. Currency, dates, language defaults, payment options, and compliance screens can change with the destination shop’s market; switching the interface language alone does not switch shops.

​
Troubleshooting

If a shop is missing, confirm that your account still has an active role in it and refresh the store list. If a switch appears to revert, resolve the unsaved-changes prompt. Never continue editing until the sidebar and page both show the intended shop.