Prerequisites for the Self-Checkout Connector (SCO)
In this article
Prerequisites for the Self-Checkout Connector (SCO)
Internet Information Services (IIS)
Prerequisites for the Self-Checkout Connector (SCO)
Before installing and configuring the Self-Checkout Connector (SCO), ensure that the underlying system environment is ready. Meeting these prerequisites prevents installation failures and ensures SCO can communicate with LS Central and Hardware Station correctly.
Supported Operating Systems
SCO must be installed on a supported Windows operating system. Verify that the server or device hosting SCO meets LS Central and SCO minimum system requirements.
Internet Information Services (IIS)
SCO relies on IIS for web services communication. The SCO instance requires:
- The Web Server (IIS) role, with the following IIS features: World Wide Web Services, Static Content, Default Document, HTTP Errors, Request Filtering, and IIS Management Console.
- .NET Runtime 8 (x64) and ASP.NET Core Runtime 8 (x64).
- ASP.NET Core Module V2, which registers the connector with IIS. This is installed as part of the .NET Hosting Bundle, not as a standalone component.
Automatic Prerequisite Checks by the Installer
The SCO installer automatically detects whether the IIS role/features and the .NET Runtime, ASP.NET Core Runtime, and ASP.NET Core Module V2 are present, and can install whatever is missing on your behalf:
- By default, the installer's Install the missing components before installing the connector option is checked, which enables the missing IIS features and downloads and installs the .NET Hosting Bundle automatically.
- In an interactive install, if prerequisites are still missing when you continue, you are prompted to confirm before proceeding; the connector will not start until the missing components are installed.
- In a silent/unattended install, a failed prerequisite installation stops the setup entirely, since there is no one to prompt.
- The installer looks for an offline copy of the .NET Hosting Bundle in a Prerequisites folder next to the setup executable before attempting to download it - useful for offline or air-gapped installations.
Installing these components manually before running the SCO installer is optional but fully supported, for example to prepare an environment in advance or where the installer cannot reach the internet or install IIS features itself:
- Enable the Web Server (IIS) role and the features listed above using Windows Server Manager (Add Roles and Features) or the Turn Windows features on or off dialog.
- Download and run the .NET Hosting Bundle matching the SCO installer's required version - it installs the .NET Runtime, the ASP.NET Core Runtime, and the ASP.NET Core Module V2 together. The version required by the current SCO installer is available at https://builds.dotnet.microsoft.com/dotnet/aspnetcore/Runtime/8.0.30/dotnet-hosting-8.0.30-win.exe.
Network Connectivity
The SCO instance must be able to communicate with LS Central and Hardware Station over the network:
- Ensure proper IP addressing and DNS resolution between SCO, LS Central, and Hardware Station.
- Open required firewall ports for inbound and outbound traffic.
- Verify network reliability and latency, especially for 1–N installations.
Deployment Models
SCO supports two deployment models, which determine authentication methods and architecture:
- 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.
Authentication Requirements
SCO requires different authentication depending on the LS Central deployment type:
On-Premises Deployments
- NavUserPass instance configured in LS Central.
- Web Service Access Key for Basic HTTP authentication.
SaaS Deployments
- Server-to-Server (S2S) OAuth authentication via Azure AD application registration.
- Required OAuth fields: Tenant ID, Client ID, Client Secret, Scope, Authority Host, OAuth Version.
Hardware Station Availability
SCO communicates with Hardware Station (HWST) for EFT payments and printing operations. Ensure that:
- Hardware Station is installed and running.
- The SCO instance has network access to the Hardware Station URL.
- Required devices (EFT, printers) are configured in the associated Hardware Profile.
Version Compatibility
SCO must match the major version of LS Central it connects to:
- For example, LS Central version 27 requires SCO version 27.
- Installers compatible with each LS Central version are available through the User Portal.
Summary
Ensure the following before proceeding with SCO installation:
- Supported Windows operating system is in place.
- IIS is installed with required components enabled, or you are relying on the installer to detect and install them automatically.
- Network connectivity between SCO, LS Central, and Hardware Station is verified.
- Authentication for your deployment type (on-premises or SaaS) is ready.
- Hardware Station is available with configured EFT and printer devices.
- SCO version matches the LS Central major version.
After verifying these system prerequisites, proceed to configure Business Central and the SCO card settings as described in the Business Central Configuration Requirements for SCO topic.