Choose between Store Commerce app and Store Commerce for web

This article explains the key differences between the Store Commerce app and Store Commerce for web, and describes various factors that retailers that implement Dynamics 365 Commerce should consider to help them make the best choice for their requirements. It also gives implementers additional background, tips, and guidance for factors that they should consider when they deploy Dynamics 365 Commerce. By reviewing and following this guidance as part of the deployment process, implementers can avoid issues that might affect user satisfaction or performance.

Insights

Commerce provides a wide range of deployment and topology options. Therefore, retailers can choose the components and configuration that best meet their business and technology requirements. One aspect of implementation that requires careful consideration is the choice of a platform and form factor for the point of sale (POS) component.

POS platform and form factor considerations

Commerce supports the following POS options:

• Store Commerce for Microsoft Windows
• Store Commerce for iOS and Android
• Store Commerce for web, which supports the Microsoft Edge and Google Chrome browsers
• Store Commerce app for Microsoft Windows (MPOS will be deprecated in October 2023.)

In all cases, the POS (Store Commerce app and Store Commerce for web) shares the same core application code. This point is important for the following reasons:

• The user interface (UI) is consistent, regardless of the platform or form factor.
• Most of the functional capabilities are the same, regardless of the platform or form factor. However, there are some important differences. These differences are noted in this article.
• In each store, the POS variations can be combined and can run concurrently. For example, for its main registers, a retailer can use Store Commerce on computers that run Windows. However, the retailer can supplement those registers with browser-based terminals or mobile devices.
• Customizations and extensions can easily be used across platforms and form factors. Because the core application code is shared, most customizations can be implemented one time instead of multiple times.

Store Commerce app vs. Store Commerce for web

Although the Store Commerce app and Store Commerce for web are largely the same, there are some important differences that you must understand.

Store Commerce

Store Commerce is a desktop application that is installed and serviced on a device.

• Windows – The Store Commerce app for Windows contains all the application code, Commerce Runtime (CRT), and Hardware Station (HWS).
• iOS/Android – On these platforms, the application acts as a host for the Store Commerce for web application code. In other words, the application code comes from the Commerce Scale Unit (CSU). For more information, see Commerce Scale Unit overview.

Store Commerce for web

Because Store Commerce for web runs in a browser, the application isn't installed on the device. Instead, the browser accesses the application code from the Commerce Scale Unit (CSU). Therefore, Store Commerce for web can't directly access POS hardware or work in an offline state.

Store deployment considerations

In addition to a platform and form factor, retailers must also choose a deployment option at the store. The following table shows the configurations that are available for each POS option.

Commerce Scale Unit

The Commerce Scale Unit is a component that hosts the CRT. The CRT contains all the business logic that the POS uses, and it provides access to the channel database. While they are online, all POS clients in the store use the Commerce Scale Unit. The Commerce Scale Unit can be deployed either in the cloud or in the store.

Offline mode

Store Commerce for Windows supports offline mode. In offline mode, the POS can continue to process sales even if it's disconnected from the Commerce Scale Unit. It can then be synchronized with the channel database when connectivity is restored. Store Commerce uses its own embedded instance of the CRT and temporarily uses its own local data source (offline SQL Server database). For more information about offline functionality, see POS offline functionality.

POS peripheral/hardware considerations

Retailers must also consider how the POS will access devices and peripherals such as printers, cash drawers, and payment terminals. Hardware stations can be dedicated to a POS register or shared among the registers in a store.

For more information about hardware stations, see Configure and install Retail hardware station.

Implementation considerations

Consider the following information as you plan your POS implementation in your stores:

• Functional requirements – The core business processes and capabilities are the same, regardless of the platform, form factor, or deployment topology. Therefore, most retailers don't have to consider functional requirements when they plan their implementation.

• Connectivity – Network availability (wide area network [WAN] and local area network [LAN]) is a major factor that requires careful consideration. Any benefits that a zero-footprint, cloud-hosted solution brings in terms of cost and simplicity are lost if the system isn't available for business-critical processes.

  Unless the connectivity for a given device is very dependable and resilient, or unless a certain amount of downtime is acceptable to the retailer, we recommend one of the following options:

  • Use Store Commerce in Windows, and enable offline mode.
  • Deploy an on-premises Commerce Scale Unit.

  These two options aren't mutually exclusive. For the most reliable topology, retailers can deploy a local RSSU to reduce the dependency on internet connectivity or Azure availability, and they can also deploy POS registers where offline mode is enabled if there is an issue with the local server or network.

• Hardware devices/peripherals – One important aspect of a Retail POS system is its ability to use POS peripherals such as printers, cash drawers, and payment terminals. Although all the available POS options can use peripheral devices, only Store Commerce for Windows supports them directly. For all other applications, one or more hardware stations are required. Although this approach adds flexibility, additional components must be deployed, configured, and serviced.

• System requirements – The system requirements for the POS application vary. Be sure to check the latest information before you make your choice. For example, because Store Commerce for web runs in a browser, it supports a wider range of operating systems. For more information about system requirements, see System requirements for cloud deployments.

• Deployment and servicing – The complexity of the deployment and servicing requirements can vary, depending on the application and deployment choices. For example, for a cloud-hosted Store Commerce for web deployment, you don't have to install and update on every device. Therefore, this approach greatly reduces complexity and cost. However, if you deploy Store Commerce on every register and enable offline mode, and you also deploy shared hardware stations, you greatly increase the number of endpoints that must be managed.

• Web browser considerations - Popular web browser have the ability to put idle tabs to sleep to free up system resources, which can cause unexpected behavior when using Store Commerce for web. If you're using Store Commerce for web, we recommend that you disable this feature.