Store Commerce app

This article explains how to set up and configure the Microsoft Dynamics 365 Commerce Store Commerce app for Windows. It applies to Dynamics 365 Commerce versions 10.0.25 and later.

The Dynamics 365 Commerce Store Commerce app is the next generation offering for physical stores. It unifies Modern point of sale (MPOS) and Cloud point of sale (CPOS) (referred to hereafter as Store Commerce for web) into a single application, providing deployment choices to retailers, helping improve performance, and offering superior application lifecycle management (ALM) while retaining all the functionality of MPOS and Store Commerce for web, including extensibility.

The Store Commerce app provides rich commerce functionality for first-line workers such as cashiers, sales associates, inventory associates, stock clerks, and store managers. It lets these workers perform commerce operations such cash-and-carry transactions, cash/shift management, customer engagement, assisted selling, clienteling, endless aisle, order processing/fulfillment, inventory management, and reporting.

The Store Commerce app is a Windows Presentation Foundation (WPF) shell application for Windows that uses the Microsoft Edge WebView2 control to render Store Commerce for web. Although Store Commerce for web can only run in a web browser, Store Commerce can run as a native Windows application like MPOS does, providing the benefits of both the the Store Commerce app and Store Commerce for web.

Store Commerce supports local hardware station and offline usage, and can be directly integrated with a payment terminal, printer, and cash drawer. It can use hardware devices without requiring that a shared hardware station be set up.

To render the user interface (UI), Store Commerce uses the Chromium engine instead of the Universal Windows Platform (UWP) app rendering framework. The Chromium engine has better rendering performance than the native JavaScript UWP app in Windows. The main difference between MPOS and Store Commerce is that Store Commerce uses the Chromium engine to render the app.

The Store Commerce app is also available for the Android and iOS platforms. For more information, see Store Commerce for mobile.

Benefits of Store Commerce

  • Application lifecycle management is simplified.
  • Extension or independent software vendor (ISV) code that is developed for the Store Commerce app or Store Commerce for web by using the Commerce software development kit (SDK) can be reused in Store Commerce with minimal changes.
  • The industry-standard developer experience uses Microsoft Visual Studio Code and GitHub.
  • Store Commerce provides the benefits of both MPOS and Store Commerce for web.
  • Performance is significantly improved.
  • POS and extension upgrades are simplified through the Commerce sealed installer framework.
  • Dedicated hardware station is supported.
  • Offline deployment is supported.

To review the capabilities of the Store Commerce app, see Store Commerce app capabilities.

Application lifecycle management

The Store Commerce app runs on Windows devices and can be downloaded from the Shared asset library in Microsoft Lifecycle Services (LCS). On the Shared asset library page, select Retail Self-service package as the asset type, and then find the file that ends with "Store Commerce." Be sure to select the version for the Commerce release that you're using (for example, 10.0.25 or 10.0.26).

Store Commerce deployment options

Store Commerce supports two types of deployment topologies:

  • In-app – All components are deployed locally. Offline mode and local Hardware Station (HWS) are supported.
  • Hybrid – Store Commerce renders the Cloud POS that is deployed in Commerce Scale Unit (CSU) and supports local Hardware Station. However, offline isn't supported.

There are no separate installers for the hybrid and in-app topologies. The deployment options are determined by the parameters that are passed during installation.

Store Commerce deployment options.

In-app deployment

For the in-app deployment option, the application content is locally deployed. Store Commerce then renders the application content from its local deployment. It doesn't retrieve the Cloud POS UI hosted in the Commerce Scale Unit (CSU).

To update the application content, run the latest version of the Store Commerce installer. The application content won't be updated if you update the CSU. Therefore, you can manage the updates at individual registers.

In-app deployment supports offline mode. During installation, pass the --installoffline parameter to deploy the offline database. In offline mode, the application won't be able to connect to CSU or Commerce headquarters, and will use the locally deployed CRT.


During the installation of Store Commerce, users can pass parameters to select either the hybrid option or the in-app option. The default option is in-app deployment.

Hybrid deployment

Store Commerce is a shell that connects to Headless Commerce and Commerce headquarters by using CSU in online mode. In hybrid mode, Store Commerce renders the Cloud POS UI that is hosted in the CSU. When the Store Commerce app is opened, it will prompt for the Cloud POS URL.

Active Store Commerce dialog box prompting for the Cloud POS URL.

To update Store Commerce, just update the CSU. Store Commerce will then automatically receive the update. Because updates are centrally managed in CSU, they don't have to be managed at individual registers. The Store Commerce application shell must still be updated separately by using the installer. For more information about how to update the CSU, see Apply updates and extensions to Commerce Scale Unit (cloud).

Store Commerce and MPOS parity

Store Commerce has full functional parity with MPOS. For more information about the different POS applications and topologies, see Choose between Store Commerce app and Store Commerce for web.

Hardware parity between MPOS and Store Commerce

The Store Commerce app does not support Universal Windows Platform (UWP) peripherals that are Point of Service devices. If you are currently using a Universal Serial Bus (USB) scanner or magnetic stripe reader in plug-and-play mode, you will need to install OLE for Retail POS (OPOS) drivers and configure these devices in your hardware profile so they work with the Store Commerce app. For more information about Store Commerce peripheral support, refer to the Commerce peripherals article.

For guidance on migrating from MPOS to Store Commerce, see Migrate Modern POS to Store Commerce.

Store Commerce and Store Commerce for web parity

Store Commerce has full functional parity with Store Commerce for web. In addition, Store Commerce supports dedicated hardware station and offline deployment.

MPOS and Hybrid app roadmap

The Store Commerce apps for Windows and mobile platforms are the next generation of POS applications for Dynamics 365 Commerce. Microsoft will deprecate MPOS and the Retail hybrid apps in October 2023, and recommends that you use Store Commerce or Store Commerce for web for all new deployments. Existing customers should plan to migrate MPOS to Store Commerce.

Comparison between Store Commerce and MPOS

Store Commerce MPOS
Operating environment Windows Windows
ALM Store Commerce is self-serviced by using LCS and Commerce headquarters. It's packaged and installed by using the Store Commerce installer, and Store Commerce for web is deployed through CSU. The Store Commerce app is self-serviced by using LCS and Commerce headquarters. It's packaged and installed by using the Store Commerce app installer.
Extensions Extensions are deployed to the CSU or installed by using the extension installer. Extensions are packaged with the Store Commerce app, or an independent extension package is used.
Support for offline mode Yes Yes
Support for local hardware station Yes, but does not support UWP peripherals that are Point of Service devices. For more information about Store Commerce peripheral support, refer the [Commerce peripherals](../ article. Yes
UI rendering engine The Chromium engine is used to render the UI. The UWP app rendering framework is used to render the UI.

Setup and installation


  • Windows 10 version 17763.0 or later (Pro, Enterprise, and Enterprise LTSC), Windows 11 (Pro, Enterprise, LTSC, and IOT Enterprise editions), or Windows Server 2019 (Standard, Essentials)
  • Microsoft Edge WebView2 (Use the Evergreen Standalone Installer.)
  • SQL Server Express, SQL Server Standard, or SQL Server Enterprise (required only for offline mode). For information on which SQL Server edition to use, see Commerce offline implementation and troubleshooting.
  • Dynamics 365 Commerce (Commerce headquarters and Cloud Scale Unit)
  • The .NET Framework version 4.7.2 or later. See Install the .NET Framework

Device setup in Commerce headquarters

For Store Commerce, a new application type that is named Store Commerce has been added on the Devices page (Retail and Commerce > Channel setup > POS setup > Devices). Select this application type when you create a device for Store Commerce.

If the Store Commerce application type doesn't appear on the drop-down menu, try to run the Initialize function from the General tab of the Commerce parameters page (Retail and Commerce > Headquarters setup > Parameters > Commerce parameters). Then refresh the page.

You must create a register and a device for Store Commerce. Then, before you activate the app, run the register job from the distribution schedule in Commerce headquarters. During device creation, set the Application type field to Store Commerce.

Device installation

Store Commerce can be downloaded from the LCS Shared asset library. On the Shared asset library page, select Retail Self-service package as the asset type, and then find the file that ends with Store Commerce. After the file has been downloaded, follow these steps to install the app.

  1. Go to the folder where you downloaded Store Commerce, and open PowerShell in administrator mode.
  2. In PowerShell, find the Store Commerce installer, and pass the install parameter to install the app. To install offline components, pass the --installoffline parameter. (For example, enter Store_Commerce Installer_exe_name install --installoffline.) If you want to enable debugging mode during installation, pass the --enablewebviewdevtools parameter.

Store Commerce installation parameters

You can also use the help command in PowerShell to find information about all the parameters. In PowerShell, find the Store Commerce installer, and then enter Store_Commerce Installer_exe_name help install.

Parameter Description
installoffline Deploys the offline database.
sqlservername Specifies the name of the SQL Server instance that Store Commerce uses in offline mode. If you don't specify this parameter, the installer will use a default instance.
skipsqlfulltextcheck Skips validation of the SQL Full-Text Search that is required for offline deployment.
trustsqlservercertificate Trusts the SQL Server certificate when a connection is established to SQL Server. To help avoid security risks, you should never use this argument for production deployments. By default, the SQL Server certificate isn't trusted.
enablewebviewdevtools Enables developer tools for Store Commerce. If you don't specify this parameter, developer tools will be enabled only if Windows Developer Mode is enabled.
retailserverurl Specifies the default Retail Server URL to use for Store Commerce. If you don't specify this parameter, the user will be prompted to enter the Retail Server URL during device activation.
useremoteappcontent Use the remote application content to download the Cloud POS UI that is hosted in CSU. By default, the local application content that is deployed with Store Commerce is used.
disableaadauthentication Disables the Azure Active Directory (Azure AD) authentication that is used by default during device authentication and use Retail authentication (Operation ID and PIN) to activate the device. This parameter is used for on-premises deployments that use Active Directory Federation Services (ADFS) authentication.
skipversioncheck Skips the validation during downgrade.
skipurlcheck Skips the validation of URLs that are passed to the installer.
logdirectorypath Specifies the path of the log's directory.
config Specifies the path of the configuration file that will be used as part of the installation.
verbosity The level of logging that is requested during installation. This value shouldn't typically be used.
help Shows parameter information.
version Shows information about the app version.

Activate Store Commerce

To activate Store Commerce after installation, follow these steps.

  1. On the Windows Start menu, search for Store Commerce, and then open the application.

    NOTE The Store Commerce app shouldn't be run with elevated privileges, and shouldn't be run from an account with elevated privileges.

  2. On the application's start page, if you select Remote app content as the deployment option, enter the Cloud POS URL, and then select Save. You can find the Cloud POS URL on the environment details page in LCS, or on the Channel profiles page in Commerce (Dynamics 365 Commerce > Channel setup > Channel profiles).
  3. Activate Store Commerce by following the steps in the POS activation guide.
  4. After activation is completed, sign in to the application by using an employee account.

Troubleshoot setup issues

For troubleshooting information, see Troubleshoot Store Commerce setup and installation issues.

Customize the app

Store Commerce can be customized by using the Commerce SDK. You can modify and create the POS user experience, enhance or modify out-of-box functionality, add validations, and add custom features. For more information, see Point of Sale (POS) extension overview, or review the samples on GitHub.

Hardware station extension

Store Commerce can be extended so that it's integrated with hardware devices. You can use the sample extension code that has been added in GitHub to generate Store Commerce hardware station extension packages. For more information, see Integrate the POS with a new hardware device.

Known issues with the Microsoft Edge WebView2 control

  • During activation, when prompted for entering the AAD password with multiple options, choose password. The other options might not work.

Additional Resources

Store Commerce app capabilities

Modernizing the Dynamics 365 Commerce in-store technology stack

Commerce SDK Tech Talk Series

Store Commerce Extensions Overview