Guides

LAN multi-till and terminal registration: how to manage

How multiple cashiers register on the store LAN, who approves, and how to recover credentials. Pairing and troubleshooting steps are in the article; capability bounds are on the kitchen and terminals feature page.

A new bar till shows pending approval. Open the manager app and go to Parameters → LAN multi POS / terminal registration — not the plugin market. If you can find the page, tell whether your account may approve, and let the till claim its own credential after approve, the extra till can open for service.

Catering POS LAN multi-till and terminal registration screen

What this page helps with / what not to assume

Helps you

Do not assume

Before expand or cutover, see the migration sample and limited pilot. Overview: Restaurant POS selection checklist.

Open the entry, then check if you can manage

  1. Open Parameters → LAN multi POS / terminal registration.
  2. Read the banners and buttons. If the page says read-only, or Pending approvals / Register / recover only warn when clicked, your account cannot manage — use an account that can, or ask an admin to grant rights, then Refresh.
  3. You should still be able to find the entry. If it is missing, confirm you are under Parameters, then Refresh. Do not assume the plugin market is required to open it.

When the till shows pending approval

  1. Start registration on the till (current UI: pending requests expire after about 15 minutes; if expired, start again on the till).
  2. In the manager app open Pending approvals (or Review requests), and check that the name, address, and version match that new till.
  3. Approve if correct; Reject if not, with a reason when asked.
  4. Approve only means consent to register. The till claims the one-time credential itself in the claim window. The manager does not claim it and never shows credential plaintext.
  5. If recovery approve is blocked because the terminal is missing or disabled: fix status on the terminal list and Save first — do not expect approve to re-enable a disabled till by itself.

Register / recover and the one-time pairing code

Two common paths — do not mix them up:

Credential recovery (terminal still exists, old credential broken): use Credential recovery or row Register / recover, bound to the original terminal. After approve, the till typically claims the new credential automatically; follow on-screen copy (often no restart required for recovery). The manager still does not receive plaintext.

Revoke only after you have a fallback

Before Revoke credential, confirm the shop still has another way to sign in or open. Revoke makes the old credential fail at once and does not mint a replacement. To bring the till back, return to Register / recover and issue a new one-time code using the device identity the till shows now.

Startup menu: set it after identity is approved

After the terminal identity is approved, set Startup menu on the list when the control is available. If it is unset or a plugin menu is unavailable, an in-house till can usually keep selling on the ordinary till menu — trust what your screen says. Do not promise the same fallback for every public ordering channel.

Quick checks

SymptomWhat to tryActions greyed out / cannot approveRead-only account? Switch to a managing account or get rights, then RefreshEntry not in the side menuLook under Parameters; do not search the plugin market; Refresh or confirm the right venue loginApproved, but till still cannot sign inDid the till claim inside the window? Manager approve ≠ credential already claimedRecovery will not approveIs the terminal still listed and not disabled? Bound to the original terminal?Pairing code expiredAbout 300 seconds, one shot; Generate pairing code againPending list empty while till still waitsPast ~15 minutes? Start the request again on the till

Firewall elevation and starting/stopping local services belong to the till’s own wizard, not to shell commands in the browser manager.

Back to the Restaurant POS selection checklist.