Skip to main content
Resources & navigation
Installers & station setup

Pair a browser device with a user code

Last updated 2026-08-072 min read

Use /device enrollment, approve the user code in Admin, and understand what the browser stores after approval.

On this page

Use /device to register a browser-based secondary device. This flow is separate from role-specific Station installers and from payment-reader pairing.

Start enrollment on the device

  1. Open the correct Ellich server URL followed by /device on the physical device.
  2. Select the device role and enter a recognizable device name.
  3. Confirm the tenant when the screen requests it. An installed Main POS should use installer activation instead of this browser flow.
  4. Start enrollment.
  5. Keep the page open while it shows the short user code and QR code. The device polls for approval and the code expires if approval takes too long.

Approve in Admin

  1. Sign in to the correct tenant in Ellich Admin.
  2. Open POS → Devices.
  3. In Pair with user code or Approve pairing, enter the code exactly as shown on the device.
  4. Confirm the device name, role, and location before selecting Approve enrollment.
  5. Return to the device. After approval, it stores the device ID, role, tenant, server, and registration time locally, then opens the assigned role application.

Do not enter a Square or other payment-terminal pairing code here. Payment reader registration uses the Payments device workflow, not /device enrollment.

If approval does not complete

  • Confirm Admin and the device use the same tenant and server.
  • Confirm the code has not expired. Select Start over and request a new code when necessary.
  • Leave the enrollment page open until approval completes.
  • If the server asks the device to slow down, wait; polling continues automatically.
  • If the device was already registered, it normally redirects to its saved role instead of showing a new code.

Unregister this browser

Open Device settings on /device and select Unregister this device. This clears the browser's local device identity, so it must be paired again. Removing a row from the Admin active fleet is a separate administrative action; perform both sides when permanently retiring or moving the physical device.