BC Extension for SCO

In this article

Overview

Installing and Publishing the BC Extension

Standalone Use of the BC Extension

See also

The BC Extension is the AL extension that adds Self-Checkout Connector (SCO) functionality to LS Central. It is a separate artifact from the SCO Connector installer, and it must be installed and published in Business Central before you configure or install the SCO Connector.

Overview

The BC Extension and the SCO Connector are two distinct components that are downloaded and deployed separately:

  • The BC Extension is published into LS Central and adds the objects, pages, and web services that SCO depends on, including the Self-Checkout Connector card.
  • The SCO Connector (also called the SCO installer or SCO service) is a separate application deployed on a server or device, which communicates with LS Central web services through the BC Extension.

The Self-Checkout Connector card does not exist in Business Central until the BC Extension has been installed and published. All Business Central configuration for SCO, including card setup, hardware profiles, and tender type mapping, depends on the BC Extension being available first.

Installing and Publishing the BC Extension

Before configuring Business Central for SCO, install and publish the BC Extension:

  • Download the BC Extension from the Self-Checkout Connector product page on the LS Retail Partner Portal, or from the LS Central product page by scrolling to Self-Checkout Connector for LS Central.
  • Install and publish the extension in your Business Central environment, matching the extension version to your LS Central major version.
  • Confirm the extension is published before proceeding to the Business Central configuration steps.

Once the BC Extension is published, continue with Business Central Configuration Requirements for SCO.

Standalone Use of the BC Extension

The BC Extension can also be used on its own, without installing the SCO Connector. In this scenario, a partner integrates directly with the web services exposed by the BC Extension, rather than routing communication through the SCO Connector.

This standalone approach is intended for partners who want to build their own integration against the Business Central web services surface instead of using the SCO Connector as the communication layer.

  • The BC Extension is still a prerequisite in this case, as it is what exposes the web services that a standalone integration calls.

See also