Skip to Content
📘Help ManualRS POSDevice Initialization

Device Initialization

1 Introduction

Through this manual, you can learn about POS device activation and deactivation, as well as system upgrades, covering the entire process including POS terminal activation, Local Server configuration, and system version upgrades.

2 Device Activation and Deactivation

2.1 POS Device Activation

💡

Key Terms：

Local Server: A store-level core server that needs to be registered before terminal devices (POS, KDS, etc.) can connect to it.

Terminal: Devices like cashier POS and handheld ordering devices that need to be activated and bound to a Local Server for use.

Activation Code: Obtained from the BO end (Operation Center → Devices → Local Site) to verify store identity and authorization.

2.1.1 Core Activation Process

Mode 1: Local Server Activation—First-time Store Deployment

  • Step 1: Select Work Mode

    • After the new device starts, select【Work in server mode】to enter the activation code entry page

  • Step 2: Enter Activation Code for Verification

    • Enter the activation code obtained from BO and click【Confirm】
    • If the activation code is invalid, a prompt “Invalid activation code” appears, and you need to obtain the correct activation code again.
    • If a Local Server already exists in the store, a prompt “The store already has a Local Server installed, please select Terminal mode” appears, and you need to switch to【Terminal mode】.

  • Step 3: Complete Registration and Activation

    • The system automatically registers the Local Server to the cloud and synchronizes by downloading basic store data (such as menu items and tables)
    • After successful activation, “Server is activated Successfully” is displayed, and it automatically jumps to the terminal login page after 3 seconds (or click【Start working】to enter immediately).

Mode 2: Terminal Activation—Adding New Cashier Device

  • Step 1: Service Discovery and Connection

    • Select【Work in terminal mode】,and the system automatically searches for Local Servers on the local network
      • If there is only one Local Server, it connects directly.
      • If there are multiple Local Servers, select the target device from the list (e.g., “XX Store - 192.168.1.121”).
      • If not found, manually enter the Local Server’s IP address (obtained from【Settings-About】on the activated main POS).

  • Step 2: Enter Activation Code to Bind

    • After a successful connection, enter the activation code, and upon verification, start activating the terminal.
    • If the activation code does not match the Local Server’s store, a “Invalid activation code” prompt appears, and store information needs to be checked.

  • Step 3: Activation Complete

    • “Terminal is activated Successfully” is displayed, and then it jumps to the employee login page (enter PIN to use).

2.2 Device Deactivation

2.2.1 Local Server Deactivation (Store Relocation / Decommissioning)

  • Step 1: Deactivation Initiated by BO:

    • The administrator logs into the BO end → Devices → Local Site, locates the target Local Server, and clicks【Archive】.

  • Local Server Handling Logic:

    • If the Local Server is online: All terminal connections are immediately disconnected (POS indicates “Local service unbound”), unsynchronized bills and clock-in data are uploaded, and it automatically enters the reactivation process.
    • If the Local Server is offline: Upon the next restart, the【Archived】status is detected, and it directly enters the activation process (a new activation code needs to be entered).

2.2.2 Terminal Deactivation (Device Replacement)

  • Step 1: Archiving via BO:

    • At the BO end → Devices → Local Site, locate the target terminal (e.g., “POS - Cashier 1”) and click 【Archive】.

  • Step 2: Terminal Response:

    • After receiving the deactivation notice, the terminal prompts “Site has been unbound or archived.”
    • Click【Got it】to enter the reactivation process (need to rebind to Local Server and enter activation code).

3 System Upgrade Operations

💡

Key Terms：

Regular Upgrade: You can choose【Upgrade Now】or【Upgrade Later】,without mandatory restrictions on usage

Mandatory Upgrade: Must be completed within 3 days; after this period, only "Upgrade Now" is displayed, and the system cannot be used normally

Rollback: If issues occur after an upgrade, you can revert to the previous stable version

3.1 Core Upgrade Process

3.1.1 Automatic Detection and Prompt

  • Step 1: Upgrade Package Detection

    • The POS system automatically checks for cloud upgrade packages every 30 minutes. When a new version is available:
      • The top displays version number + “New” label (e.g., “v1.0.4 New”).
      • A popup prompts “New version found,” displaying upgrade content (e.g., “Optimized ordering interaction, fixed printing bug”).

  • Step 2: Choose the Timing for Upgrade

    • Click【Upgrade Now】: The system automatically exits the current program, downloads and installs the upgrade package (wait 2-5 minutes, do not turn off power).
    • Click【Upgrade Later】: The popup closes, and the “New” label remains at the top for manual upgrade later.

3.1.2 Mandatory Upgrade

  • Countdown Reminder: The mandatory upgrade popup shows “Upgrade must be completed within 3 days,” decreasing by one day each day.
  • Handling Overdue: After the countdown ends, the popup only displays “Upgrade Now.” Clicking it forces program exit for upgrade; POS cannot be used until the upgrade is complete.

3.1.3 Version Rollback

  • Step 1: Access Version Management

    • Click【Settings → About → Version History】to view the historical version list (showing current and previous versions).

  • Step 2: Rollback Operation

    • Find the version to rollback (e.g., “v1.0.2.15”) and click【Restore】.
    • A popup prompts, “Confirm rollback to this version,” click【Confirm】.
    • If the local installation package for the version is available, rollback directly; if not, it automatically downloads and rolls back (requires internet connection).

4 FAQs

4.1 Activation Exception Handling

  1. Issue: Activation Code Indicates “Invalid”
  • Solution:
    • Step 1: Log into the BO end → Devices → Local Site to confirm the activation code matches the store ID
    • Step 2: Check if the activation code has expired (check validity in BO)
    • Step 3: Regenerate the activation code and re-enter it
  1. Issue: Local Server Not Found
  • Solution:
    • Step 1: Confirm the Local Server is powered on and connected to the network (Ethernet/Wi-Fi is working)
    • Step 2: Check whether the terminal and Local Server are in the same local network
    • Step 3: Manually enter the Local Server’s IP address (query from main POS)
  1. Issue: Activation Indicates “Insufficient License”
  • Solution:
    • Step 1: Contact the service provider or BO administrator to increase the store device authorization count
    • Step 2: Archive idle devices to release licenses and reactivate

4.2 Upgrade Exception Handling

  1. Issue: Upgrade Package Download Fails
  • Solution:
    • Step 1: Check network connection (switch to stable Wi-Fi or Ethernet)
    • Step 2: Enter the About page and click【Check for new version】to re-trigger download
    • Step 3: If it fails multiple times, contact technical support for an offline upgrade package
  1. Issue: Cannot Start After Upgrade
  • Solution:
    • Step 1: Restart the device; if it still fails, press and hold the power button for 10 seconds to force restart
    • Step 2: Enter the version rollback page and revert to the previous stable version
    • Step 3: Contact technical support to troubleshoot system compatibility issues
  1. Issue: Client and Local Server Version Mismatch
  • Solution:
    • Step 1: Upgrade the Local Server first (administrator logs into main POS to complete upgrade)
    • Step 2: Client re-detects version and completes synchronization after upgrade prompt
  1. Issue: Local Server Needs Reactivation After Restart
  • Solution:
    • Step 1: Check if the Local Server is mistakenly archived in BO (if archived, unarchive it)
    • Step 2: Re-enter the activation code to complete secondary activation
    • Step 3: Contact technical support to check if cloud authorization has expired
  1. Issue: Terminal Connection to Local Server Indicates “Service Unavailable”
  • Solution:
    • Step 1: Confirm the Local Server is powered on and connected to the network
    • Step 2: Check if the terminal IP is in the same subnet as the Local Server (modify terminal Wi-Fi/Ethernet configuration)
    • Step 3: Restart the Local Server’s network service
  1. Issue: Some Functions Unusable After Upgrade
  • Solution:
    • Step 1: Enter the version rollback page and revert to the stable version before the upgrade
    • Step 2: Record the issue (e.g., “Cannot add menu items”) and report it to technical support for fixing
    • Step 3: Wait for the next version to update and upgrade again
  1. Issue: Mandatory Upgrade Countdown Ends but Cannot Upgrade
  • Solution:
    • Step 1: Check device storage space (at least 500MB must be free, delete unnecessary files)
    • Step 2: Switch to store-specific network (avoid public network throttling)
    • Step 3: Download an offline upgrade package and install it manually
Last updated on:
Business SettingsDecoration Management