Dynamics 365 Commerce is a Microsoft business application that helps organizations manage and unify all aspects of their retail, e-commerce, and customer engagement operations in one integrated platform.
Here’s a breakdown of what it does
Overview
Microsoft Dynamics 365 Commerce is part of the Dynamics 365 suite and builds on the capabilities of Dynamics 365 Retail.
It enables businesses to deliver personalized, omnichannel shopping experiences — whether customers are buying online, in-store, or through call centers.
Key Features
- E-Commerce Platform
- Create and manage a custom-branded online store.
- Integrates seamlessly with back-office systems (inventory, pricing, promotions).
- Provides AI-driven recommendations and personalized product suggestions.
- Create and manage a custom-branded online store.
- Point of Sale (POS)
- Modern, cloud-connected POS for in-store transactions.
- Works online or offline, supporting cashiers and self-checkout.
- Supports mobile devices, allowing associates to assist customers anywhere in the store.
- Modern, cloud-connected POS for in-store transactions.
- Omnichannel Management
- Unified view of customers, products, inventory, and orders.
- Customers can buy online, pick up in-store (BOPIS), or return anywhere.
- Ensures consistent pricing and promotions across all channels.
- Unified view of customers, products, inventory, and orders.
- Customer Engagement
- Built-in AI tools for customer insights and loyalty programs.
- Personalized shopping experiences based on browsing and purchase history.
- Built-in AI tools for customer insights and loyalty programs.
- Back Office Integration
- Integrates with Dynamics 365 Finance and Supply Chain Management.
- Streamlines operations — from procurement and inventory to fulfillment and accounting.
- Integrates with Dynamics 365 Finance and Supply Chain Management.
- Content Management
- Includes a visual page builder for websites.
- Marketers can easily create product pages, promotions, and campaigns without coding.
- Includes a visual page builder for websites.
Who Uses It
- Retailers (fashion, electronics, grocery, etc.)
- E-commerce businesses
- Consumer goods companies
- Any organization wanting to unify online and in-store sales under one system.
Example Use Case
A clothing retailer uses D365 Commerce to:
- Run their website and in-store POS systems.
- Sync inventory across stores and the online shop.
- Offer “buy online, return in-store.”
- Track customer preferences for targeted marketing.
Can you create a diagram that visually explains how D365 Commerce connects the online store, POS, and back office?
Here is a more detailed explanation of that architecture diagram and how Dynamics 365 Commerce “plugs together” various components.
Architecture Layers & Components
Below is a breakdown of the major layers and components you’ll typically see in a D365 Commerce architecture (as represented in the image):
| Layer / Component | Role & Responsibilities |
| Web Storefront / Online Channel | This is the public-facing website or web store. It handles routing, authentication, content, and displays the UI to the customer. |
| Commerce Platform / Core Services | Core services that handle commerce logic — catalog, pricing, promotions, shopping cart, order processing, etc. |
| Data Actions / APIs | A data abstraction layer that allows for aggregating, batching, and calling connected services (e.g. catalog service, inventory service). |
| Extensions / Modules / Custom Logic | Allows partners or customers to extend functionality (custom modules, themes, business logic) without modifying the core. |
| Back Office / Headquarters Systems | Includes retail headquarters, master data management, ERP, financials, inventory, supply chain, etc. |
| Point of Sale (POS) / Physical Store Systems | The in-store checkout systems, mobile POS devices, self-checkout, etc. |
| Integration / External Services | Integrations to payment gateways, external data sources, third-party systems (loyalty, shipping, etc.). |
Request Flow (How it works end-to-end)
Here’s a simplified step-by-step of what happens when a user browses or places an order:
- User Request
A customer requests a page (e.g. product details) via their browser or mobile app. - Platform Layer
The request is received by the Commerce platform which handles authentication, routing, locale detection, etc. - Hydrated Page Object
The platform generates a “hydrated page object” — a composition of page configuration and data from various services through “data actions.” - Data Actions / Aggregation
The system may call multiple services (catalog, pricing, inventory, etc.) via data actions. It can batch, cache, or deduplicate underlying service calls. - Rendering (Server-Side + Client-Side)
A React application (running on Node.js) receives the view model, renders HTML, and sends it to the client. On the client side, React takes over to handle interactivity. - Interactions & Updates
When the user interacts (e.g. “Add to cart”), further APIs / data actions are invoked to handle those operations (cart updates, inventory check, etc.). - Order Processing & Back End
When checkout happens, the order is processed, integrated with headquarters systems (ERP, inventory, fulfillment), payments are authorized, etc. - POS / Store Sync
Inventory, pricing, and order information sync with in-store systems so that in-store and online channels share a unified view.