Retail Modern POS (MPOS) architecture
This topic applies to Dynamics 365 for Retail and Dynamics 365 for Finance and Operations.
This topic describes the POS topology.
Retail Modern POS topology
Users of Retail Modern Point of Sale (POS) can perform various retail tasks on supported laptops, tablets, and phones. These tasks include processing sales transactions, viewing customer orders, managing daily operations and inventory, and viewing role-based reports. Both Retail POS and Cloud POS are available in Microsoft Dynamics 365 for Retail. The Cloud POS is a hosted version of the POS app. Both the POS clients don't perform business functions or data processing. All business functions are provided by Retail Server. Retail Modern POS and Cloud POS clients can communicate with Retail Servers that are deployed in the cloud. Retail Modern POS client can also communicate with peripheral devices, such as cash drawers, credit card readers, and printers, by using Hardware Station. Hardware Station must be deployed in your store, and all Retail Modern POS clients can connect to the same Hardware Station. The following diagram shows the high-level topology.
Retail Modern POS architecture
The view, view-controller, and devices layers depend on the operating system (for example, Windows RT) that you plan to deploy Retail Modern POS on. The other layers are independent of the operating system. These layers use TypeScript classes and modules to implement Retail Modern POS functionality such as workflows and entities. The following diagram shows the Retail Modern POS technical architecture.
Cloud POS and Retail Modern POS architecture
Cloud POS is a hosted version of Retail Modern POS, and varies only in the way that it is rendered on specific devices or in specific browsers. Additionally, Retail Modern POS supports offline mode and therefore a local CRT. Other native peripheral support is also specific to Retail Modern POS.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.