SCO Connector Administration Portal

Configure SCO connection and device settings.
Monitor the status of connected terminals and services.
Validate SCO configuration and detect missing or incorrect settings.
Access and download detailed log files for troubleshooting.
Download a support package with logs and system information to send to support.

The connector version is shown in the top right corner of every portal page.

Quick Start Workflow

Open the portal by navigating to localhost:8077 in a web browser. If a different Site Port was entered during installation, use that port instead.
Verify the Setup tab configuration (Manufacturer, SCO server, Hardware Station).
Validate terminal connections using the Status Overview tab.
Check terminal service status under Terminal Status.
Review logs if errors or warnings are detected.

Setup

The Setup tab is where you review and change the main settings for the SCO Connector, such as connection info, authentication, plugin path, and telemetry. The Manufacturer is shown for reference but cannot be changed here.

After making changes, click Save. The connector must restart for the changes to take effect, so the portal asks whether to restart it now.
For detailed device setup, see:

Configuration	Description
Manufacturer	The manufacturer the connector is configured for. This ensures SCO loads the correct communication plugin and Feature Flags. The field is read-only: the manufacturer is chosen during installation, and to use a different manufacturer you must install SCO again and select it in the installer.
Default URL	Main endpoint for LS Central Web Services. Copy from the Web Service Setup card in BC. Ensure the URL ends with `/Codeunit`. This is the same value entered as LS Central Base Endpoint in the installer.
Hardware Station URL	Base URL of the Hardware Station, used for both the REST API and SignalR communication. This is the same value entered as Hardware Station Base URL in the installer.
Authentication Type	Basic (On-Prem) for on-premises deployments or OAuth2 (SaaS) for SaaS deployments. The fields below change depending on the selection.
User Name	Basic (On-Prem) only. The user used to log onto LS Central web services.
Password	Basic (On-Prem) only. Password for the above user. Leave blank to keep the existing password.
OAuth Client ID, OAuth Client Secret, Tenant ID, Scope, OAuth Version, Authority Host	OAuth2 (SaaS) only. The server-to-server (S2S) OAuth values from the Azure AD application registration. OAuth Version can be v2.0 or v1.0. Leave OAuth Client Secret blank to keep the existing secret.
Token	Unique token for this SCO Connector. See SCO Connector card.
Store ID	The store where the SCO Connector runs.
Plugin Folder Path	Folder containing custom POS plugin DLLs. Visible only if Manufacturer = Custom. SCO automatically detects and loads assemblies from this folder at startup.

When Authentication Type is set to OAuth2 (SaaS), the Authentication section shows the OAuth fields instead of user name and password:

Telemetry

Starting with SCO version 29, the Setup tab includes telemetry settings that control whether the connector reports logs, traces, and metrics to Application Insights. Only the on/off switch for this feature is also exposed in the installer wizard (see Telemetry Settings); the settings below are only available here, after installation.

Setting	Description
Enable Telemetry	Forwards logs, traces, and metrics to the shared LS Retail Application Insights resource. The connection to this resource is built into the connector and cannot be viewed or changed. Disabled by default. Only errors and above are forwarded as logs; traces and metrics are always captured in full when enabled.
Retailer ID	Unique identifier for your organization, used to filter telemetry by partner in the LS Retail portal.
Share with LS Retail	Category checkboxes - Transactions, Payments, Printing, Metrics - selecting which categories are forwarded to the shared LS Retail resource. When Enable Partner Telemetry is off, LS Retail receives all categories regardless of this selection.
Enable Partner Telemetry	Sends a full, unfiltered copy of all SCO traces and metrics to your own Application Insights resource, in addition to whatever is shared with LS Retail. Disabled by default.
Partner Connection String	The Application Insights connection string for your own resource (for example, `InstrumentationKey=...;IngestionEndpoint=...;LiveEndpoint=...`). Only used when Enable Partner Telemetry is on.

The category selection only controls what LS Retail receives - it never limits what your own Application Insights resource receives:

If Enable Partner Telemetry is off, or no Partner Connection String is set, LS Retail receives all categories regardless of the checkboxes.
If Enable Partner Telemetry is on but no categories are checked, LS Retail receives nothing from that SCO instance.
Your own Application Insights resource, when configured, always receives all SCO traces and metrics unfiltered.

Download Support Package

The Download Support Package button at the bottom of the Setup tab collects the information support typically needs to troubleshoot an SCO installation into a single ZIP file.

On the Setup tab, click Download Support Package.
In the Download support package dialog, select a Start date and an End date. The dates limit which logs and Event Viewer entries are included.
Click Download.

The file is named SupportPackage_<start date>_<end date>.zip (for example, SupportPackage_20260922_20260929.zip) and contains:

File	Content
SCO log files	The SCO connector log files (`.txt`) from the selected date range.
EventViewerLogs.txt	Warning and error entries from the Windows Application event log within the selected date range.
ScoSettings.db	A copy of the connector's settings database.
RegistryData.txt	Values of the NCR SCOT `SocketServerInfo` registry key, used by NCR devices. The file states that the key was not found when it does not exist on the machine.
SystemInformation.txt	Windows version, machine name, current user, and CPU and memory details.
SystemEnvironmentVariables.txt, UserEnvironmentVariables.txt	The system-level and user-level environment variables of the machine.

Only the most recent support package is kept on the machine; building a new one deletes earlier ZIP files. The package includes the settings database and environment variables, which may contain environment-specific or sensitive values, so review its content before sharing it outside your organization.

Status Overview

The portal validates the SCO configuration received from LS Central and reports missing or incorrect settings.

Example messages: "No tender types configured for SCO device".
These same validations occur at SCO startup and are written to the logs.

Terminal Status

Displays the status of each SCO terminal, including Connected, Online, or Stopped.

Log Viewer

Access logs via Utilities → Logs.
Filter by date or log type: General or Error.
Logs can be downloaded or viewed in the portal.
Tip: Large logs may only be available for download.

Troubleshooting Tips

Issue	Possible Cause	Solution
Terminal not connecting	Incorrect Hardware Profile or Device Type	Check SCO card and terminal assignment
Plugin DLL not loaded	Incorrect PluginFolderPath or missing DLLs	Verify DLLs are in correct folder and restart SCO
Error in logs: "Invalid Token"	Token mismatch in BC SCO card	Ensure SCO card Token field matches connector
No tender types configured	Tender types not assigned in BC SCO card	Assign tender types to SCO in BC

Next Steps

Verify terminal connections and SCO service status.
Check logs for errors or warnings.
Ensure SCO is properly configured for the selected Manufacturer and Device Type.