📄Important Bepoz Programs

Overview

Many core bepoz applications operate as background services or integration layers that interact directly with the operating system, network resources, hardware devices, and other applications. Many of these components must be able to start automatically, communicate across services, write to protected directories, and maintain persistent connections without being restricted by Windows user-level permissions.

Program icons that display the blue/yellow shield overlay indicate that the executable is configured to always run as Administrator. This is intentional and required. Running these applications with elevated privileges ensures reliable startup, uninterrupted service operation, and consistent communication between POS terminals, servers, peripherals, and third-party systems. Without Administrator access, these services may fail to start, lose connectivity, or behave unpredictably—resulting in issues such as POS terminals dropping offline, integrations failing, or printing and API services stopping unexpectedly.

As a rule, any bepoz executable marked with the Administrator shield should not have this setting removed or bypassed. These applications are designed to operate with elevated permissions to maintain system stability and must always be allowed to run as Administrator.

Smart Controller (smartcontrol.exe) The Smart Controller is the core service and central communication hub of the bepoz system. All system components rely on it, including SmartPOS, Smart API Host, BackOffice services, and other supporting executables. It manages and routes data across the entire environment, tracking software activity and coordinating communication between servers, POS tills, and integrated systems. In multi-venue environments, the Smart Controller is responsible for distributing updates and synchronising data across locations. If the Smart Controller is not running, system-wide communication stops: POS terminals fall back to Offline (Standalone) Mode, API services cannot process requests, and integrations are unable to exchange data. In practical terms, it is the beating heart of the bepoz platform.
Smart Print (smartprint32.exe) Smart Print controls the activation and management of printers within the bepoz system. It must be running on the workstation or POS device to which a printer is attached, either physically (serial/USB) or virtually (network printers). Without Smart Print running, printing functions will not operate.
CA Link (calink.exe) CA Link provides the connection between the bepoz system and an external Gaming or Membership system. It must be running to enable communication between the POS and the gaming database, allowing member information to be retrieved successfully at the POS.
RMS Server (rmsserver.exe) RMS Server is the integration service that links bepoz with a room charge reservation system. It is primarily used with Basic RMS or Advanced Cloud deployments to support room charge functionality.
Reservation Link (reslink.exe) Reservation Link connects bepoz to supported hotel property management systems (PMS), enabling live communication between the POS and the hotel’s reservation and billing platform. This allows charges made at the POS (such as food, beverage, or retail sales) to be posted directly to a guest’s room folio. A common example of this integration is with Oracle Hospitality OPERA. Reservation Link must be running for room and folio information to be exchanged in real time.
SmartPOS (smartpos.exe) SmartPOS is the primary point-of-sale application used by Operators (staff) on till hardware. It is the foundation for selling within the bepoz system, handling day-to-day operations such as sales, refunds, and order processing. In most environments, no transactions can occur without SmartPOS running on a dedicated device.
BackOffice (backoffice.exe) BackOffice is the main administrative application for the bepoz system. It is used to configure the system, maintain data, manage inventory and pricing, and run reports. All system setup and ongoing management tasks are performed through BackOffice.
Kitchen Management System - KMS (kdslink.exe) The Kitchen Management System (KMS) Link communicates SmartPOS sales information to the kitchen display system. It ensures orders entered at the POS are sent to kitchen screens in real time for preparation. While the executable name remains kdslink.exe, the system is now referred to as KMS.
SmartAPI Host (smartapihost.exe) The Smart API Host listens for and processes API requests from external systems such as MobilePOS devices and self-ordering kiosks. It runs locally on a server (often the same server as smartcontrol.exe, though in some cases a dedicated server is required). Its role is to receive these API calls and pass the information into the bepoz system so it can be processed and acted upon.