Dynamics 365 Commerce: What Retail Leaders Should Know in 2026
Dynamics 365 Commerce is Microsoft’s unified commerce platform for midsized to large-enterprise retailers and B2B sellers, running stores, web, call center and back office on one commerce engine. Microsoft’s pricing page lists it at $210 per user per month in 2026, and its Copilot features are real but narrow. For hands-on help with this, explore our Microsoft 365 migration.
Picture a shopper who orders a jacket online for store pickup, only to find the associate cannot see her order because the web system syncs overnight (a composite scenario, not a client story). This guide covers what Dynamics 365 Commerce includes in October 2026, how its unified commerce design supports omnichannel retail, and what a license costs. If you are weighing Dynamics 365 implementation services or deciding whether to buy at all, you also get a fit score, a risk list and a readiness checklist.
What Dynamics 365 Commerce Is in 2026
Dynamics 365 Commerce is Microsoft’s unified commerce platform for midsized to large-enterprise retailers and B2B sellers. It combines a back-office application, a point of sale app, an e-commerce storefront, call center tools and a headless commerce engine. Its back office shares a web experience and data stores with Dynamics 365 Finance and Supply Chain Management.
Older articles and many buyers still say Dynamics 365 for retail. Microsoft now documents and sells Dynamics 365 Commerce, and its product page targets midsized to large-enterprise customers.
The same pricing, order management and inventory visibility sit behind the point of sale, the website and the call center. That is what unified commerce means in practice, and it is how Dynamics 365 Commerce serves omnichannel retail.
Dynamics 365 Commerce moves fast. Version 10.0.47 reached self-update availability in March 2026 and auto-update in April. Version 10.0.48 followed in June and July, and 10.0.49 reached self-update availability in September and auto-update in October, per Microsoft’s release notes. If you want a partner for this work, see our Microsoft solutions.
The pressure behind unified commerce is real. The US Census Bureau reported that e-commerce made up 17.1% of total US retail sales (seasonally adjusted) in the second quarter of 2026, or $340.2 billion. Online is no longer a side channel, but most retail sales still happen elsewhere.
How Unified Commerce Architecture Works
Dynamics 365 Commerce runs on a hub and spoke design. Head office is the hub. Distributed Commerce Scale Units (CSUs) are the spokes, and each hosts the headless engine behind unified commerce. Microsoft’s architecture overview calls the CSU the central integration point for all commerce business logic. Read next: Microsoft 365 Copilot vs ChatGPT.
The Unified Commerce Pieces in Plain Terms
- Dynamics 365 Commerce headquarters: the back-office app for products, pricing, employees and processes.
- Store Commerce app: the point of sale for Windows, iOS, Android and macOS, with offline support in the in-app deployment.
- E-commerce storefront and site builder: a React.js storefront plus a visual authoring tool for marketers.
- Commerce Scale Unit: the engine for pricing, order management, inventory visibility and customer logic. Partners and custom apps call the same engine.
Choosing an In-Store Point of Sale Topology
A Commerce Scale Unit comes as a Microsoft-managed cloud service or as a self-hosted unit inside the store, and one Dynamics 365 Commerce environment can mix both. In our experience, self-hosting suits poor connectivity but adds monitoring and update work.
The trade-off is concrete. The Store Commerce point of sale app supports mass deployment, but offline it cannot run cross-terminal shift and transaction operations. A self-hosted scale unit keeps those running during a headquarters outage, but it does not support mass deployment. Pick per store format, not once for the whole chain.
Microsoft lists Microsoft Dataverse and Azure Data Lake Storage as the unified data components for cross-app scenarios and analytics. Plan that path early. Our enterprise system integration services work usually starts at exactly this seam.
Omnichannel Retail Capabilities Compared
Omnichannel retail in Dynamics 365 Commerce rests on six working areas: point of sale, e-commerce, call center, pricing and promotions, inventory visibility and order management. The table shows what each does and the catch to know before you sign.
| Area | What Dynamics 365 Commerce does | Watch for |
| Point of sale | Store Commerce, the point of sale app, handles cash and carry, assisted selling, clienteling, endless aisle, customer orders and returns. Version 10.0.48 adds nonreturnable items and payment profiles per register. | Older MPOS apps were deprecated in October 2023, so plan migration. |
| E-commerce | React storefront, site builder, B2B multi-outlet buying (10.0.47), Adyen payment link and QR code. | The Adyen link and QR code need the Adyen connector. |
| Call center | Call center tools handle assisted omnichannel retail orders and payments. | From 10.0.48, payment authorizations cannot be edited from the call center. |
| Pricing and promotions | One pricing engine for store, web and call center, which unified commerce needs. Unified pricing adds custom attributes and rule simulation. | Migrate legacy setups deliberately. Microsoft describes an automated migration script. |
| Inventory visibility | Channel-level inventory visibility, plus cross legal entity lookup in point of sale (10.0.47). | Availability is an estimate between syncs, not a live count. |
| Order management | Distributed order management in Dynamics 365 Commerce applies profiles and rules to source orders. Version 10.0.48 adds cross legal entity fulfillment. | Rules and profiles take real design time. |
Inventory Visibility Is an Estimate, Not a Promise
Microsoft’s documentation says availability shown in point of sale, the e-commerce APIs and headquarters might not be 100% accurate in real time, because Commerce uses multiple servers and databases and syncs channel transactions to headquarters after the fact. Treat inventory visibility as a managed estimate.
That matters for Dynamics 365 Commerce promises such as buy online, pick up in store. Set a safety buffer on fast movers in Dynamics 365 Commerce and audit inventory visibility after close. For the operational side of order management, see our guide on omnichannel order management challenges.
Unified Pricing and Promotions
Pricing is where Dynamics 365 Commerce projects for omnichannel retail quietly break. Dynamics 365 Commerce uses one pricing engine across channels, so a promotion built once applies at the point of sale, online and in the call center. That is the core promise of unified commerce.
Microsoft’s 2025 wave 2 release plan describes unified pricing with custom attributes for customers and products, an automated migration script, and attribute-based pricing models you can configure, simulate and approve. Treat your current trade agreements as a migration project, not a toggle.
Copilot and AI Features Available Today
Dynamics 365 Commerce Copilot features today are narrow and practical: product copy in site builder, customer and report insights in the point of sale app, merchandising and statement summaries in headquarters. Two AI previews for developers sit alongside them: a Commerce MCP server and AI extension skills. Here is what each does.
| Feature | What it does | Status and limits |
| Copilot in site builder | Drafts product detail page copy from name, attributes and price, with tone and audience controls. | Generally available since March 2024; 23+ locales. |
| Customer insights by Copilot | Shows preferred categories, RFM analysis, lifetime value, icebreakers and recommendations in the point of sale app. | English only. Needs a Dataverse link and specific versions. |
| Store report insights | Writes natural-language summaries of Store Commerce reports. | English only. Needs a cloud Commerce Scale Unit. |
| Merchandising insights | Flags missing data, duplicates, price misconfigurations and catalog mismatches per channel. | Off by default. Batch jobs run every 24 hours. |
| Statement posting summaries | Summarizes stuck transactions and risky returns or overrides. | On by default in headquarters. |
| Dynamics 365 Commerce MCP server | A Microsoft-managed Model Context Protocol (MCP) endpoint on the Commerce Scale Unit. Its preview tools cover product search, store inventory, cart, checkout link and delivery options for AI agents. | Public preview, per Microsoft’s June 29 and September 23, 2026 posts. |
| AI extension skills (10.0.49) | Add Commerce extensibility knowledge to command-line AI coding assistants, so developers can scaffold point of sale and commerce runtime extensions from a plain-language brief. | Public preview, per Microsoft’s September 30, 2026 post. Developers still review the generated code. |
Microsoft’s Copilot pages warn that AI-generated content might be incorrect. Run these Dynamics 365 Commerce features as pilots with a named owner, not unattended automation. A good first pilot is merchandising insights, because the output is a fix list your catalog team can check against the data. Read next: Dynamics 365 AI and Real-Time Data.
Microsoft says its roadmap through March 2027 holds “continued enhancements to core experiences with AI,” without naming features. Buy against what you can switch on in a sandbox this month.
How It Fits With Finance and Supply Chain
Dynamics 365 Commerce shares a platform, web experience and data stores with Dynamics 365 Finance and Supply Chain Management, because all back-office capabilities are built on the same web experience and data stores. Microsoft’s architecture article describes Finance as offering an integrated experience for managing store and e-commerce financial statements alongside the rest of your operations.
That tight fit is the selling point of Dynamics 365 Commerce for anyone already on the finance and operations stack: store financials, unified commerce, point of sale and order management share one platform.
Business Central is a different animal. Microsoft describes it as a business management solution for small and mid-sized organizations, with a Shopify connector that synchronizes customers and orders. For a handful of stores plus a Shopify site, Dynamics 365 Commerce is probably more platform than you need.
If you run a non-Microsoft ERP, the question flips. The commerce engine is a single integration point for partner channels, so Dynamics 365 Commerce can be adopted without replacing every system, but you own the integration to your finance system. Budget for that before you compare license lines.
Dynamics 365 Commerce License Costs
Dynamics 365 Commerce is licensed per user, with two optional tenant-level add-ons. Microsoft’s pricing page lists the core license at $210 per user per month, the e-Commerce add-on at $4,000 per tenant per month and the Headless add-on at $4,200 per tenant per month, all billed yearly.
Microsoft states that prices are for informational purposes only and can vary by currency, country and region. Treat these Dynamics 365 Commerce figures as a planning floor, not a quote.
What the License Does Not Cover
- Partner services: discovery, configuration, data migration, point of sale extensions and integrations. This is often the larger line.
- Hardware and payments: registers, scanners, printers, terminals and your payment processor fees.
- Base license rules: which other Dynamics 365 licenses your design needs alongside Dynamics 365 Commerce. Get your partner to confirm them in writing.
- Environments and support: sandbox and production environments, plus a support plan.
You can try Dynamics 365 Commerce free for 30 days through Microsoft’s trial, with demo data and no customization. Microsoft says organizations with 250 or more Dynamics 365 users might be interested in a volume licensing agreement. Others can work with a Cloud Solution Provider partner.
Dynamics 365 Commerce vs Shopify and Salesforce
Choose Dynamics 365 Commerce when your stores, ERP and online channel must share one set of inventory visibility, pricing and order management rules. Choose Shopify or Salesforce when the storefront is the center of gravity and the back office is settled. Either way, test inventory visibility and order management first.
Shopify’s point of sale page says connecting in-store and online sales helps you keep inventory, payments and customers in sync, and that you can integrate your existing inventory and order management systems. Its Plus page says you can plug in existing systems through APIs, though it names no ERP. Those are vendor claims describing a storefront-first model of omnichannel retail. In our experience, Salesforce Commerce Cloud sits in the same storefront-first camp.
| Your situation | Lean toward |
| Dozens or hundreds of stores, ERP-driven finance, shared inventory visibility and unified commerce goals | Dynamics 365 Commerce |
| Mostly direct-to-consumer, a few stores, fast launch needed | Shopify Plus |
| Existing Salesforce CRM and a digital-first brand | Salesforce Commerce Cloud |
| B2B account buying with credit limits on the finance system | Dynamics 365 Commerce |
| Small team with no Dynamics skills in-house or at a partner | Storefront-first platform |
Plenty of retailers run a storefront platform for the web and Dynamics for stores and finance. The cost is a second pricing and inventory visibility sync to maintain, the very problem unified commerce is meant to remove.
A Five-Signal Fit Score for Dynamics 365 Commerce
This is Techverx practitioner judgment, not sourced data. Score each signal 0 (no), 1 (partly) or 2 (clearly yes). The total tells you whether to pursue Dynamics 365 Commerce, pilot it, or look elsewhere for omnichannel retail.
- Shared stock: stores, web and fulfillment nodes must draw on one inventory visibility pool for omnichannel retail.
- Finance gravity: you run, or will run, Dynamics 365 Finance or Supply Chain Management.
- Assisted and B2B selling: associates, call center agents or account buyers need orders, credit and quotes in one place.
- Store complexity: multiple legal entities, tax regimes, offline needs or payment hardware that off-the-shelf point of sale struggles with.
- Delivery capacity: you have a partner or team that can build and maintain Commerce extensions and run a multi-quarter program.
A score of 8 to 10 is a strong fit. A score of 5 to 7 deserves a scoped pilot in one region or banner. Under 5, a storefront-first platform with a lighter point of sale will usually reach value faster. Be strict on signal five, which buyers tend to inflate.
Implementation Risks to Plan For
Most Dynamics 365 Commerce projects stumble on integration and data, not point of sale features. These failure modes are worth designing around, and each is grounded in Microsoft’s documentation.
- Sync jobs as a hidden dependency: point of sale settings reach registers through distribution jobs such as 1070 (channel configuration), and Copilot merchandising insights run as batch jobs every 24 hours. Monitor them like production services.
- Customization creep: every point of sale or storefront extension to Dynamics 365 Commerce raises upgrade cost. Microsoft’s release list shows several versions a year, and extensions must keep pace.
- Inventory visibility trust: shoppers see estimates. Agree buffers and a store-level audit rhythm before go-live.
- Pricing migration: moving legacy trade agreements to unified pricing for omnichannel retail needs testing against real baskets.
- AI prerequisites: Copilot needs a Dataverse link, specific versions and, in some regions, cross-region data movement. Point of sale Copilot features are English only.
- Topology surprises: self-hosted scale units add monitoring work, and the offline in-app setup requires SQL Server on the register.
- Partner dependence: if one consultant holds all the Dynamics 365 Commerce configuration knowledge, your first upgrade will hurt.
If you are weighing wider ERP change at the same time, our ERP implementation services team can help separate what belongs in this program from what can wait.
A Dynamics 365 Commerce Readiness Checklist
Run this list before you sign a statement of work. If you cannot tick seven of ten, spend a quarter on groundwork first.
- Written Dynamics 365 Commerce scope for which channels go live in phase one, and which do not.
- Clean product, category and attribute data for omnichannel retail, with an owner per field.
- A pricing inventory for unified commerce: every trade agreement, discount and loyalty rule documented.
- A store connectivity survey that decides cloud or self-hosted scale units per format.
- Payment processor and terminal plan for the point of sale, including the Adyen connector decision.
- Integration map for ERP, warehouse, tax, loyalty, order management and marketing systems.
- Named business owners for inventory visibility, pricing and order management rules.
- A sandbox plan using the Dynamics 365 Commerce trial or a partner demo with your real data.
- A budget that covers partner services, hardware and the first year of Dynamics 365 Commerce upgrades.
- A go-live rehearsal covering offline selling at the point of sale, returns and order edits.
What to Do This Quarter
Score yourself on the five signals, trial Dynamics 365 Commerce for 30 days, and prove one omnichannel retail scenario, such as buy online and pick up in store for ten stores with agreed inventory visibility buffers. Ask your partner for the exact Dynamics 365 Commerce version, the license prerequisites and the Copilot features they would switch on first.
The Bottom Line
Dynamics 365 Commerce earns its place when stores, ERP and online must act as one business. It is heavy for a storefront-first brand, and the Dynamics 365 Commerce AI features are useful but narrow. Decide on inventory visibility, pricing and order management, not on the demo.
