Configuring NCR Devices for SCO

This topic explains how to configure the Self-Checkout Connector (SCO) to work with NCR self-checkout devices in Business Central, including SCO card setup, terminals, and NCR Device Types. Installation of the NCR Connector app itself is documented separately.

Related Topics

NCR Integration Overview

NCR self-checkout devices integrate with SCO through an intermediate application called NCR Connector. The NCR Connector acts as a bridge between the NCR POS environment and SCO, translating POS events into SCO-compatible requests and responses.

How It Works

  1. The NCR POS client sends events (for example, item scans) as XML messages to the NCR PipeServer.
  2. PipeServer forwards these XML messages to the NCR Connector.
  3. NCR Connector sends the requests to SCO over HTTP.
  4. SCO processes the request using LS Central Web Services.
  5. XML responses are returned through NCR Connector → PipeServer → NCR POS, updating the UI.

This architecture allows SCO to remain independent of NCR’s internal POS protocols while maintaining real-time communication.

Step 1: Create or Verify Self-Checkout Device Types

Each NCR terminal must be associated with a Self-Checkout Device Type in Business Central. This links terminals to manufacturer, host, port, and device-specific configuration.

  1. Open the Self-Checkout Device Type list in BC.
  2. Verify that a Device Type exists for each NCR terminal.
  3. Required fields for each Device Type:
    • Device Type – Unique code for the NCR device.
    • Description – Descriptive name.
    • Brand – NCR.
    • Tender Type Mapping Profile – Optional, if tender type IDs differ.

Step 2: Configure the SCO Card

1. Open the Self-Checkout Connector card in Business Central.

2. Configure the following fields:

  • Store ID – Store where NCR devices are installed.
  • Hardware Profile – Required; defines EFT and printer devices used by NCR terminals.
  • Staff ID – Staff user with Self-Checkout User = Yes.
  • Terminals Table – Add each terminal to communicate with this SCO instance:
    • All terminals must reference an NCR Device Type.
    • 1–1 installation: Only one terminal.
    • 1–N installation: Multiple terminals are allowed; each should have its own NCR Device Type.
    • Hardware Profile can be assigned per terminal or inherited from the SCO card.

Step 3: Verify Hardware Profiles

Ensure each terminal’s Hardware Profile points to the correct EFT and printer devices in Hardware Station. Terminals can inherit the SCO card’s Hardware Profile if not set individually.

Step 4: Testing NCR Terminals

  1. Start the SCO connector from the SCO Management Portal.
  2. Confirm all terminals are listed as Connected and Online.
  3. Perform a test transaction on each NCR terminal to verify full communication with SCO and LS Central.

Example: Item Scan Flow

The following example shows a simplified XML message sent from an NCR POS device when an item is scanned, and the corresponding responses returned by SCO.

Request from NCR POS (via PipeServer): 

			<message msgid="b1" name="Item">
			<fields>
			<field name="UPC" ftype="string">50000</field>
			<field name="Scanned" ftype="int">0</field>
			<field name="LabelData" ftype="string">50000</field>
			<field name="PicklistEntry" ftype="int">0</field>
			</fields>
			</message>

Response from SCO: 

			<message name="ItemSold" msgid="b2">
			<fields>
			<field name="Description" ftype="string">Briefcase, leather</field>
			<field name="ItemNumber" ftype="int">10000</field>
			<field name="IsZeroWeight" ftype="int">0</field>
			<field name="RequiresSecurityBagging" ftype="int">4</field>
			<field name="UPC" ftype="string">50000</field>
			<field name="Price" ftype="int">10000</field>
			<field name="Age" ftype="int">-1</field>
			<field name="Quantity" ftype="int">1</field>
			</fields>
			</message>

			<message name="Totals" msgid="b2">
			<fields>
			<field name="TotalAmount" ftype="int">10000</field>
			<field name="TaxAmountA" ftype="int">0</field>
			<field name="BalanceDue" ftype="int">8000</field>
			<field name="ItemCount" ftype="int">1</field>
			<field name="DiscountAmount" ftype="int">0</field>
			</fields>
			</message>

The exact message structure and supported fields depend on the NCR configuration and NCR Connector implementation.

Notes

  • All terminals in a single SCO instance must be NCR devices.
  • 1–N installations require multiple Device Types, one per terminal.
  • The NCR Connector is required for communication with NCR devices; installation details are in the Installing the NCR Connector topic.
  • PipeServer must be running and reachable by NCR Connector and SCO for communication.
  • XML messages shown in this topic are for illustration purposes only and are handled internally by NCR POS and NCR Connector.

See Also