Modern POS in Dynamics 365 Commerce

For retailers running Dynamics 365 Commerce, the in-store cash register is Modern POS (MPOS) — a Windows-based point-of-sale application that runs on store-level tills, handheld devices, and tablets, with full offline capability when connectivity drops. Understanding its architecture is essential for any retail implementation.

The architecture. Modern POS is a Universal Windows Platform app installed on Windows PCs, tablets, or handhelds. Each store runs a Retail Server (in-store or cloud-hosted) that proxies between MPOS and the head-office Commerce environment. The flow:

MPOS → Retail Server → Head Office (Commerce / F&O)

When the head office is unreachable, MPOS continues operating against the store database — a local SQLite copy synced from head office that holds the current product catalogue, prices, promotions, customer data, and inventory.

Offline mode. This is the differentiator. When the connection to the Retail Server drops:

• The till keeps ringing sales against the local database.
• Transactions queue locally for upload.
• Customer lookups, loyalty checks, and most operations work locally.
• Some operations (payment via online gateways, complex price overrides requiring approval) may pause.

When connectivity returns, queued transactions sync up to head office, and any pending downloads (new prices, new products, new customers) sync down. The pattern survives spotty connectivity, brief network outages, and even multi-day disruptions without losing transactions.

Channel data exchange. A scheduled service called Commerce Data Exchange (CDX) synchronises data between head office and stores in both directions:

• Down to store: product catalogue, prices, promotions, customers, gift cards.
• Up from store: transactions, inventory adjustments, time clock entries, customer registrations.

CDX runs on a configurable schedule per store; high-volume stores run more frequently.

Peripherals. Modern POS speaks to a wide range of retail hardware through the Hardware Station — a separate service running on the till that manages:

• Receipt printers.
• Barcode scanners.
• Cash drawers.
• Customer-facing displays.
• Payment terminals (chip-and-PIN, contactless, NFC).
• Scales (for weight-based goods).
• Magnetic stripe readers.
• Signature capture pads.

Hardware drivers are certified per device; the device-and-driver catalogue is published by Microsoft and the hardware OEMs.

Functions. The cashier experience covers:

• Transactions — scan or look up items, apply discounts (rule-based or manual with override approval), accept payment (any tender configured), produce receipt.
• Returns — with-receipt return (lookup posted transaction), no-receipt return (with manager override).
• Customer lookup and creation — at the till; ties transactions to loyalty.
• Gift cards — issue, top up, redeem.
• Loyalty — earn and redeem points inline.
• Order from store — create a sales order for items not in store; ship from another location or central warehouse.
• Pickup at store — fulfil online orders.
• Cash management — opening float, mid-shift counts, end-of-shift closeout, deposits.
• Time clock — staff clock in / out, with hours flowing to payroll.
• Reporting — basic in-store reports for managers.

Cloud POS. A parallel browser-based POS — Cloud POS — runs the same functionality in a web browser, suitable for tablets and lighter-weight terminals without the Windows installation overhead. Cloud POS has fewer offline capabilities (depends on internet for most operations).

Store Commerce app. A newer iteration of the in-store experience, designed for modern Android and iOS-friendly hardware, with an updated UI and clienteling features. Microsoft is investing in Store Commerce as the strategic direction; Modern POS remains supported but new builds increasingly start with Store Commerce.

Operational reality. Retail POS implementations are unforgiving — the till is the most-watched part of any retail operation. Pilot in one store before rolling out; train cashiers extensively; test offline scenarios deliberately before go-live.