Ellich has three different first-run paths. Use the path shown by the package or browser screen instead of entering owner credentials on every device.
Install POS / Store Edge first
The role-specific POS / Store Edge package creates the Main POS and local StoreHub anchor.
- Download the current POS / Store Edge package from the Ellich Station download page.
- Install and open it on the store's main Windows or Android POS device.
- On Verify the store owner, enter the owner email, password, and Ellich server URL.
- Confirm the tenant and store returned by owner verification.
- Choose MAIN POS / StoreHub server, give the station a recognizable name, and select Enable POS hub.
- Complete Diagnostics. Correct an unsupported display before continuing.
- Enter a six-digit staff PIN to open the assigned POS runtime.
Do not install a KDS, Kiosk, Customer Display, Operations Board, Table Order Kiosk, or Sub POS before the Main POS is running. Those installed roles require its LAN service.
Pair an installed secondary Station package
A role-specific secondary installer is already fixed to its device type. It does not ask for the store owner email, password, tenant ID, or an enrollment claim.
- Start the Main POS and connect both devices to the same trusted store LAN.
- Open the secondary package and select Find Main POS.
- Select the correct Main POS from the discovery list. If discovery is blocked, use Add POS by IP with the Main POS IPv4 address.
- Review the device name and role-specific assignment, such as a KDS prep profile or Kiosk layout.
- Submit the request. Approve the short request on the Main POS when prompted.
- Continue only when Diagnostics says the tenant and store are verified and the POS link is present.
Register cloud identity only is a support fallback, not a completed installation. The device cannot enter service until it is linked to a Main POS on the LAN.
Set up Mobile POS
Mobile POS is the exception to the LAN-anchor rule. Sign in with the owner account once to establish its cloud device session, store assignment, and payment capability. It may use Wi-Fi or cellular service and does not need to discover a Main POS. StoreHub printing is optional, but supported payment-provider capability is still required for card-present and offline payment behavior.
Pair a browser-based device
Use /device for browser-based secondary POS, Kiosk, KDS, display, signage, or printer identities. Select the role and device name, start enrollment, and approve the displayed user code in Admin → POS → Devices → Pair with user code. The browser stores its approved identity locally and redirects to the assigned role application.
The installed Station package and /device enrollment are different setup paths. Do not use a payment-terminal pairing code in the device enrollment field.
Verify before service
- The package, displayed role, tenant, store, station name, and assignment profile are correct.
- A secondary installed Station shows its Main POS link, not only a cloud identity.
- Display Diagnostics is supported or contains only an accepted recommendation.
- The device reaches its intended runtime and reports a fresh heartbeat.
- The smallest safe role test succeeds, such as one KDS test ticket or a controlled Kiosk order.
Never approve an unknown device request or share the owner password with a secondary-device installer.