Dynamics 365 Commerce for SMEs in 2026

What is Dynamics 365 Commerce?

Dynamics 365 Commerce is Microsoft's omnichannel retail solution, unifying back-office operations, in-store experiences, digital commerce (online stores) and call center channels into one platform for retailers. It sits in the Dynamics 365 family alongside Supply Chain Management, Finance, Customer Service and Sales, each licensed as its own module.

What makes Commerce different from a standalone webstore is the headless Commerce Scale Unit (CSU). The CSU is a commerce engine that powers all native Commerce channels (in-store POS, e-commerce and call center) and exposes commerce data and business logic through open APIs (Commerce Runtime, Retail Server). One engine, every channel, consistent pricing, inventory and promotions across them. That is the core architectural promise, and it is also why Commerce is heavier to implement than a SaaS storefront.

Microsoft positions Commerce for medium-to-large retail businesses with complex channel needs. That framing matters for SMEs reading this page, and we return to it in the SME-fit section below: for many smaller retailers, a lighter path (Business Central plus a connected webstore, or Odoo eCommerce) is the more honest answer.

• →Commerce headquarters (back-office) — configures products, employees, assortments, pricing and discounts, channels, workers, call center operations and statements.
• →Store Commerce app — the next-generation POS, unifying Modern POS and Cloud POS into a single cross-platform application with full offline support.
• →Digital commerce / e-commerce — the online storefront plus Site Builder for managing the digital storefront experience.
• →Call center — handles phone-order entry, customer service and order management as a first-class channel.
• →Headless Commerce Scale Unit (CSU) — the engine that powers every channel through open APIs, so business logic stays consistent across in-store, web and call-center.

Dynamics 365 Commerce pricing in 2026

Official Microsoft pricing for Dynamics 365 Commerce is $210.00 per user/month, paid yearly. This is the core Commerce licence covering omnichannel retail operations, and it reflects a recent increase from the previous $180/user/month that many third-party guides still cite. If you read a page quoting $180, it is stale.

Two licensing details matter for SMEs. First, e-Commerce is tenant-based, with tiers tied to transaction volume and Average Order Value bands, and includes Fraud Protection capacity, so the full online-store piece is not just a flat per-user fee. Second, store and frontline workers often use lower-cost Operations Device or Operations Activity licences rather than the full $210 Commerce seat, which materially changes the total cost for a retailer with many POS terminals.

The honest takeaway: budget the $210/user/month for back-office and management users, plan a separate tenant-based eCommerce tier for the online store, and use lower-cost device/activity licences for the store floor. A scoping call should model all three before you commit.

Dynamics 365 Commerce capabilities: online store, POS and channel management

Commerce is built around four pillars that share one commerce engine. Understanding what each pillar does, and that they all run on the same Commerce Scale Unit, is what separates a real omnichannel rollout from a disconnected set of tools.

The Store Commerce app is worth calling out specifically. It is the next-generation offering for physical stores, unifying Modern POS (MPOS) and Cloud POS (CPOS) into a single application with full offline support. In offline mode, POS devices automatically switch from the channel database to an offline SQL Server Express database if the Commerce Scale Unit is unavailable, so stores keep trading through network outages, then sync when connectivity returns.

• →Store Commerce app (POS) — unified MPOS + CPOS replacement with full offline support and automatic switch to an offline SQL Server Express database when the CSU is unreachable.
• →Online store / digital commerce — headless React-based storefront plus Site Builder for merchandising, content and digital experiences.
• →Merchandising and assortments — product information, catalogs, assortments and publishing managed in headquarters and pushed across channels.
• →Pricing and discounts — engine-based pricing, promotions, price adjustments and loyalty that run consistently across POS, web and call center.
• →Call center — phone-order entry, customer service, order management and returns as a native channel.
• →Channel management — configure and operate retail channels, stores, registers and workers from headquarters.

The headless Commerce Scale Unit: one engine, every channel

The Commerce Scale Unit is the technical reason Commerce can claim true omnichannel rather than just 'multiple channels'. The CSU hosts the Commerce Runtime and Retail Server, exposing commerce data and business logic through open APIs. Every native channel (in-store POS, the online storefront and the call center) talks to the same engine, so a price change, a promotion or an inventory update happens once and propagates everywhere.

That architecture also has implications SMEs should understand. On self-hosted Commerce Scale Unit deployments, online stores, e-commerce channels and Distributed Order Management (DOM) are not available; only POS, call center, merchandising, pricing/discounts and loyalty are supported. In practice this means the full omnichannel promise assumes a cloud-hosted CSU, which is the model almost all SME rollouts use.

• →Commerce Runtime + Retail Server — the API layer that exposes commerce data and business logic to every channel.
• →Cloud-hosted CSU — the default for SME rollouts; unlocks the full omnichannel set including the online storefront and DOM.
• →Self-hosted CSU — supports POS, call center, merchandising, pricing/discounts and loyalty, but not online stores or e-commerce channels.
• →One engine, one truth — pricing, promotions and inventory update once and propagate to every connected channel.

Where Shopify integration honestly sits

Many SME retailers already run Shopify as their online storefront and ask whether Dynamics 365 Commerce replaces it or works alongside it. The honest answer is: both are possible, but they are very different paths, and Microsoft's own connector has a specific scope that is easy to overestimate.

Microsoft ships a built-in Dynamics 365 Commerce connector for Shopify that synchronizes products, customers, orders, inventory and pricing between Business Central/Commerce and a Shopify store. It is designed to let a retailer keep a lighter Shopify front-end while running Dynamics as the system of record for finance, inventory and ERP. It is not the same as running Commerce's native headless e-commerce engine.

So the real decision for an SME is not 'Commerce vs Shopify' as if they were equivalent. It is: do you want one vendor's headless commerce engine running every channel (Commerce), or do you want a best-of-breed front-end (Shopify) connected to a Dynamics back-office (typically Business Central)? Flectic implements both Microsoft Dynamics 365 and Odoo, and we regularly help SMEs choose between these two patterns based on channel complexity, transaction volume and how much of the stack they want under one license.

• →Commerce native e-commerce — full headless storefront, one engine across POS, web and call center; heavier to implement.
• →Dynamics + Shopify connector — Shopify stays the front-end; Dynamics (usually Business Central) is the back-office system of record.
• →Decision driver — choose native Commerce when channel complexity and inventory-at-scale matter; choose Shopify + Dynamics when time-to-launch and front-end flexibility matter more.

When Commerce is overkill: Business Central plus a webstore

Dynamics 365 Commerce is built for retailers with multiple physical stores, complex assortments, call-center operations and a serious online channel. If you are an SME with one or two locations and a straightforward online store, the full Commerce licence and the CSU implementation effort are usually more than you need.

The lighter Microsoft path is Business Central plus a connected webstore. Business Central handles the ERP side (inventory, financials, purchasing) and integrates with a front-end like Shopify through the same Microsoft connector. For SMEs that want to stay fully in the Dynamics family but do not need Commerce's POS engine or headless storefront, this is typically the right answer.

The non-Microsoft path we also implement is Odoo eCommerce, which bundles ERP and a webstore in a single SME-priced stack. The point is not that one is universally better; it is that an honest SME scoping conversation should compare all three before committing to a $210/user/month Commerce rollout.

Is Dynamics 365 Commerce right for your SME?

Use this short checklist to decide whether Commerce, Business Central plus a webstore, or Odoo eCommerce is the better fit for your retail operation.

Commerce tends to fit when you have multiple physical stores or a call center, you need a unified POS-plus-web-plus-call-center engine, your assortment and promotion complexity is high, and your team can absorb an ERP-grade implementation. Business Central plus a webstore tends to fit when you have one or two locations, you mostly need ERP plus an online store, and you want lower per-user cost. Odoo eCommerce tends to fit when you want one SME-priced stack covering ERP and webstore together and you are not already committed to the Dynamics family.

If those lines are blurry, that is exactly what a scoping call is for. Flectic runs ERP readiness engagements across Canada, the UK and the US that map your channels, transaction volume and growth plan against all three options before anyone signs a licence.

• →Choose Commerce if — multi-store, call center, unified POS/web engine, high assortment complexity, ERP-grade implementation budget.
• →Choose Business Central + webstore if — one or two locations, ERP-first needs, lower per-user cost, Shopify-style front-end is acceptable.
• →Choose Odoo eCommerce if — single SME-priced stack, no existing Dynamics commitment, webstore and ERP under one roof.