Skip to main content
The Tapp management mobile app registers the current installation as a shop device after a valid sign-in and shop selection. Registration lets Tapp identify the device for POS targeting, status, and terminal behavior.

​
Who can do this?

Owners and Managers and Staff can use the parts described here. Store-wide management of other devices remains limited to Owners and Managers; self-service for the current device and read-only list access have different scopes. API authorization is authoritative.

​
Where

Sign in to the Management Native App and select a shop. Registration runs automatically after the app has confirmed the access token; there is no separate manual Register button.

​
Steps

  1. Install and open the official Management Native App on the team device.
  2. Sign in with an Owner, Manager, or Staff account that belongs to the intended shop.
  3. Select that shop and wait while personal account data validates the session.
  4. Allow the app to obtain its installation identifier. Tapp creates or updates the device for that installation and shop; if no name is supplied, the service creates one from the user name.
  5. Open device settings to confirm the current device appears. Bring the app to the foreground later to send a fresh heartbeat.

​
Platform notes

Registration is self-service for an authenticated user and is keyed by installation ID plus shop ID, so the same installation can be updated rather than duplicated. The native app matches its installation against the user’s devices and stores the current device ID locally. Web Admin does not register the browser as a team device through this flow.

​
Market notes

The workflow is identical for GB and DE. Platform is recorded as iOS or Android and is independent of shop language or market. Payment capability still depends on device hardware, OS, user settings, and shop payment settings.

​
Troubleshooting

If the device does not appear, confirm sign-in, selected shop, network access, and that the app completed user-info loading. Reopen the app to trigger another foreground heartbeat. Do not repeatedly reinstall first, because a changed installation ID can create a different device identity; capture logs and ask support after checking the list.