Insights · Knowledge, not a service

Microsoft Dynamics 365 Commerce — omnichannel retail with headless commerce option.

The retail application of the former F&O suite. Stores + online on a single stack: Modern POS, Cloud POS, e-commerce platform with headless option, customer loyalty, self-service kiosk, store and online inventory in one consistent data model. For retail chains and multi-channel merchants from mid-market upward.

What is Dynamics 365 Commerce?

Retail ERP with a seamless store and online stack.

Microsoft Dynamics 365 Commerce is the cloud-based retail application of the former F&O suite. The app unites two worlds that have been separate in most retail setups until now: the brick-and-mortar business (with store registers, store master data, store promotions) and the digital business (e-commerce platform, online inventory, click & collect). Both run on the same backend and share master data, inventory and customer history.

At its core, Commerce has four functional layers: the retail backend (on the F&O codebase, identical to Supply Chain Management), channel management (store, online, call center, marketplace), the frontend components (Modern POS for store registers, Cloud POS for mobile devices, e-commerce frontend with storefront modules) and the cross-cutting services (customer loyalty, promotions, Customer Insights, AI-driven personalization).

One distinctive feature is the headless commerce option: by default, Microsoft ships its own React-based storefront with configurable modules. If you need a more individual online experience, you can replace this frontend with a custom frontend (Next.js, Nuxt, Hydrogen) and consume the approved Retail Server APIs. This architecture makes Commerce particularly attractive for brand-driven retailers building a distinctive online experience rather than a pre-configured standard layout.

We don't deliver Commerce ourselves — retail is a discipline of its own, with store rollouts, POS hardware integrations and, in many cases, 24/7 requirements that demand a dedicated retail team. But we know the topics well enough from projects we've lived through to place them in context — and to judge when Commerce fits and when a leaner solution like Shopify with Business Central integration would be the better choice.

Functional landscape

What Dynamics 365 Commerce typically covers.

The core disciplines — distilled to what actually gets discussed in retail implementations.

Modern POS & Cloud POS

Native store register application with offline capability (local database, automatic sync), hardware integration (receipt printers, slip printers, card readers, cash drawer), tax-free shopping, gift cards, manager override workflows.

E-commerce platform

Microsoft's own storefront with configurable modules (product page, cart, checkout, account area), SEO-compliant URL structure, server-side rendering, multi-site support for multiple brand webshops on one backend.

Headless commerce option

Retail Server APIs for full frontend decoupling. Custom storefronts on Next.js, Nuxt, Hydrogen or your own tech stacks. Ideal for brand-driven retailers who don't want to click their online experience together from modules.

Cross-channel inventory

Store and online inventory in one view. Click & collect, reserve-in-store, ship-from-store, endless aisle (online sale of store inventory), central planning across all channels.

Customer loyalty

Points and status systems, tier programs (silver, gold, platinum), birthday promotions, member pricing, customer master data consolidated across all channels. Integration with Customer Insights for a 360-degree view.

Promotions & pricing

Channel-specific promotions, time-limited campaigns, quantity discounts, mix & match, BOGO logic, coupon control. Pricing hierarchy with store, channel and customer conditions.

Self-service kiosk

Standalone ordering terminals in stores (e.g. for quick-service restaurants, larger fashion stores), with credit card or loyalty card payment, connection to store printers and inventory backend.

Store operations

Shift planning, end-of-day register reconciliation, store inventory counts, shift handovers, store orders to central warehouse, loss and shrinkage recording.

Industry and size profile

Who typically uses Commerce.

Commerce targets retail companies from mid-market upward, typically with:

  • Multiple stores (5+ locations) and simultaneous online presence
  • Multi-brand or multi-site strategies (multiple webshops on one backend)
  • High demands on the online experience (brand-driven fashion labels, furniture makers with their own retail channel, premium cosmetics)
  • Customer loyalty programs that connect store and online
  • Combination with Supply Chain Management to run store and online logistics from one stack

Typical profiles from the market:

  • Fashion and lifestyle retailers with 30–500 stores plus online shop
  • Furniture and home-interior houses with store + e-commerce + configurator
  • Sports and outdoor retailers with strong seasonal swings
  • Premium cosmetics and drugstore chains with a customer loyalty program
  • Quick-service restaurants with a self-service kiosk strategy

For smaller merchants or pure-play retailers without stores, Commerce is functionally oversized. If you need pure e-commerce without physical stores, Shopify, BigCommerce or commercetools combined with Business Central as the ERP backend is usually more economical.

Predecessor product & migration path

From AX Retail to the cloud.

Commerce has its roots in Microsoft Dynamics AX Retail, which was developed from AX 2009 onward as a specialized retail extension to the AX suite. AX Retail was one of the first retail ERPs at the time with native POS integration and an architecture that cleanly separated central master data from decentralized store operations.

With the cloud migration, AX Retail became part of Dynamics 365 for Operations, later Finance and Operations. In 2020 the retail discipline was spun out as its own app, Dynamics 365 Commerce — and in the following years was substantially expanded with the e-commerce frontend, headless option and customer loyalty functions.

Typical migration paths:

  • From AX Retail (on-prem) → Commerce Cloud: the most common path. The store rollout has to be re-planned because the POS frontend (Modern POS) is structured differently from the old Enterprise POS.
  • From classic retail solutions (e.g. NCR, GK Software, Futura, LS Retail) → Commerce: re-implementation. Data migration via standard tooling; custom POS customizations have to be rebuilt.
  • From Shopify, Magento, other e-commerce pure-plays → Commerce: only makes sense if stores and loyalty are being added. A pure e-commerce replacement rarely justifies Commerce.
  • From Business Central + Shopify integration → Commerce: when multi-channel complexity grows and store locations are added. Re-implement.

License costs & implementation reality

What you can honestly expect.

License costs (as of May 2026): Microsoft does not publish a self-service EUR list price for Dynamics 365 Commerce on the pricing page — pricing runs through Microsoft Sales / CSP channel. The typical license building blocks:

  • Dynamics 365 Commerce — full-user license for HQ, category manager, merchandiser (price on request)
  • Attach license — if Finance is already licensed, Commerce can be added as an attach license at a significantly lower price
  • POS device license — per store register (Modern POS or Cloud POS), price on request
  • E-commerce storefront — bandwidth and storage-based costs via Azure
  • Activity user — for store staff with limited access

Source: microsoft.com/en-us/dynamics-365/products/commerce/pricing — as of May 2026.

On top come hardware costs for stores: POS terminals, receipt printers, card readers, cash drawers, self-service kiosks. In a 50-store implementation, hardware alone quickly becomes a six-figure line item.

Implementation reality:

  • Duration: 12–24 months depending on store count and frontend complexity (headless takes longer)
  • Budget: seven figures, eight figures in larger retail implementations
  • Store rollout: phased with a pilot store, then waves of 5–20 stores per month
  • Risks: POS hardware compatibility, customer master consolidation across legacy channels, storefront performance under load
  • Headless commerce specifics: additional frontend team (Next.js, Nuxt), CDN strategy, A/B-testing setup

How we can help

Three clearly bounded contributions — even though we don't deliver Commerce ourselves.

Knowledge · not a service

1. Honest selection advisory

We give an independent read on whether Commerce is the right choice — or whether a leaner stack (Shopify + Business Central, commercetools + BC, or a custom frontend with Independent Engineering) fits more economically.

Knowledge · not a service

2. Referral to specialized partners

If Commerce is the right choice, we refer to F&O retail partners from our network — firms with POS rollout experience and a store operations methodology.

Service · what we deliver

3. Customer Engagement Apps & integration, if Commerce is running

If Commerce is already implemented: we deliver Customer Insights as a CDP layer, Customer Service for return and complaint processes, and integrate on the customer-engagement side with the Commerce world.

Frequently asked questions

What retail decision-makers want to know before the initial conversation.

What sets Dynamics 365 Commerce apart from Shopify or SAP Commerce Cloud?

Shopify is a pure e-commerce platform — quick to set up, but without deeply integrated store POS and without an ERP backend. SAP Commerce Cloud is an enterprise retail platform with a strong B2B focus. Dynamics 365 Commerce is Microsoft's answer for omnichannel retail with native store POS, integrated e-commerce frontend (or headless), customer loyalty and ERP backend in one stack. If you really want to run store and online from one data model, Commerce offers an architecturally clean setup.

Can I replace Microsoft's own frontend (headless commerce)?

Yes. Microsoft provides storefront modules for its own React-based frontend, but you can replace it with custom frontends on Next.js, Nuxt or Hydrogen. The backend APIs (Retail Server) are fully documented and approved for headless setups. Brand-driven retailers often choose this path to preserve their distinctive customer experience.

What does Dynamics 365 Commerce cost per user?

Microsoft does not publish a self-service EUR list price for Dynamics 365 Commerce — pricing runs through Microsoft Sales / CSP. Store staff with POS access are cheaper under a POS-specific license than the full-user license. Device costs (Modern POS, Cloud POS, self-service kiosk) come on top. Source: microsoft.com/en-us/dynamics-365/products/commerce/pricing — as of May 2026.

How does Commerce integrate with Customer Insights?

Commerce writes all customer events (POS purchases, online purchases, loyalty actions) to Dataverse. Customer Insights aggregates them into a consolidated customer profile and makes it available for marketing automation in Dynamics 365 Marketing or external channels. This is one of the strengths of the Microsoft stack — and an area where we can support you.

What about click & collect and ship-from-store?

Standard functionality in Commerce. Store and online inventory are held in a single view; online orders can be shipped from the nearest stocking location (store or central warehouse) or reserved for in-store pickup. The routing logic is configurable and can be combined with AI-driven optimizations from Intelligent Order Management.

Does arades deliver Microsoft Dynamics 365 Commerce?

No. We deliver Business Central and the Customer Engagement Apps. For Dynamics 365 Commerce we refer to specialized F&O retail partners. If Commerce is already running, we deliver the customer-engagement side (e.g. Customer Insights as a CDP) and the integration.

Is Commerce worth it for a pure B2B wholesale business?

Rarely. Commerce is B2C and omnichannel focused. For pure B2B businesses with customer-specific price lists, conditions and EDI processes, Supply Chain Management or Business Central combined with a B2B commerce solution (e.g. SAP Commerce Cloud, OroCommerce, a custom platform) is typically the better choice.

30-min initial conversation

Commerce question? We'll place it honestly.

Tell us about your retail situation. We'll give you an independent read — whether Commerce fits, whether a leaner stack is enough, or whether an F&O retail partner from our network fits you better.