This feature introduces a dynamic, per‑session self-checkout (SCO) language change from a store‑configured list with no cashier intervention required. Stores control which languages are available, and screen layout labels for buttons and tabs can be localized for each language. The same runtime language change flow is also available on non‑SCO registers. Administrators can configure supported languages and customize UI labels for each language, ensuring a consistent and localized experience.

Target audience

Customers at self-checkout can select a preferred language at the start screen, or via the Change Session Language operation.
Store IT administrators can configure the allowed languages per store and turn the feature on or off.
Merchandisers and designers can localize button and tab text for each language using the POS layout designer.

How to enable and use the feature

To enable the feature in Commerce headquarters, go to the functionality profile. In the SCO section, under SCO Multi‑Language Enabled, set the option to On. The default value is Off.

Customer experience

When the feature is enabled, SCO can show a Welcome screen with language tiles that enable the language change flow.
Selecting a language tile updates all UI strings such as buttons, tabs, and labels to the selected language, and navigates to the cart view.
Alternatively, SCO can go directly to the cart view transaction screen, where the change language operation is accessed via the button grid to invoke the change language dialog for the transaction session.
If the feature is disabled or only one language exists, a single Start button is shown on the Welcome screen.
Customers can scan a product directly from the Welcome screen without having to select Start.
After a customer completes a transaction, the app reverts to the worker/store default language and automatically returns to the Welcome screen, or the cart view.

Data flow and synchronization

CDX/Channel: Secondary languages and the enablement flags are included in seed data and synchronized by running the 1070 job. The ChannelConfiguration and DeviceConfiguration properties expose values to the client.