What is the Self-Checkout Connector (SCO)

The Self-Checkout Connector (SCO) is a middleware component that enables communication between LS Central and supported self-checkout (SCO) devices. It acts as a bridge between physical self-checkout terminals and LS Central Business Central (BC) Web Services, allowing transactions and device interactions to be processed consistently across different manufacturers and deployment models.

In addition to LS Central, SCO integrates with Hardware Station to handle payment processing and printing operations.

SCO abstracts device-specific behavior, authentication complexity, and hardware communication, providing a unified integration layer for self-checkout solutions.

Purpose of the Self-Checkout Connector

The primary purpose of SCO is to enable self-checkout devices to perform sales transactions in LS Central while minimizing direct integration complexity.

  • Enable self-checkout transactions in LS Central
  • Provide a standardized interface across device manufacturers
  • Support both on-premises and SaaS LS Central deployments
  • Integrate with Hardware Station for payments and printing
  • Allow partners to extend self-checkout behavior using Feature Flags

By centralizing this logic, SCO reduces the need for device vendors or partners to integrate directly with LS Central Web Services or hardware devices.

Supported Self-Checkout Devices

The Self-Checkout Connector supports the following self-checkout device types:

  • Diebold Nixdorf self-checkout devices
  • NCR self-checkout devices
  • Custom implementations using a plugin-based architecture

Supported functionality and available Feature Flags may vary by manufacturer. Manufacturer-specific behavior is documented separately.

Supported Deployment Models

SCO supports both LS Central deployment types. The deployment model determines how SCO authenticates with Business Central but does not change its functional capabilities.

  • On-premises
    Uses NavUserPass authentication and requires a Web Service Access Key for Basic HTTP authentication.
  • SaaS
    Uses Server-to-Server (S2S) OAuth authentication and requires an Azure AD application registration.

Installation Models

The Self-Checkout Connector can be installed using one of the following models:

  • 1–1 installation
    A single SCO instance is installed directly on a self-checkout device.
  • 1–N installation
    A single SCO instance is installed on a separate server and communicates with multiple self-checkout devices.

Both installation models are supported and selected based on customer architecture, performance, and operational requirements.

Integration with Hardware Station (HWST)

The Self-Checkout Connector integrates with Hardware Station (HWST), to perform hardware-related operations that cannot be handled directly by LS Central Web Services.

SCO communicates with Hardware Station when it needs to:

  • Process payments through EFT devices
  • Print receipts or other transaction documents

The EFT and printer devices used by SCO are defined and managed in Hardware Station.

For this reason, the Hardware Station URL is a required configuration value during SCO installation and setup.

Core Functional Capabilities

The Self-Checkout Connector enables self-checkout devices to perform the following high-level operations through LS Central Web Services:

  • Start and manage transactions
  • Add, modify, or void items and orders
  • Retrieve item, device, and terminal configuration
  • Handle staff logon and card entry
  • Print previous transactions
  • Apply business rules and restrictions using Feature Flags

A complete list of supported Web Service operations is provided in the functional reference section.

Version Compatibility

The Self-Checkout Connector must always match the LS Central major version it connects to.

For example, LS Central version 27 requires SCO version 27.

This compatibility requirement exists because SCO relies on LS Central Web Services that may change between versions.

The latest compatible SCO installers are available through the User Portal.

Extensibility Using Feature Flags

SCO supports Feature Flags defined in Business Central to control or extend self-checkout behavior.

Feature Flags can be associated with:

  • Items (for example, age-restricted sales)
  • Specific device types
  • The SCO connector itself

Some Feature Flags are generic, while others are manufacturer-specific. Supported Feature Flags are documented separately.