Dynamics 365 Commerce is licensed across three user types in 2026: full users at $180/user/month list price (base, first user of the application), attach users at $30/user/month list price (second-and-subsequent users of any other D365 app who add Commerce), and Team Members at $8/user/month list (read-mostly access). POS terminals are licensed separately as Device licences at $75/device/month, and e-commerce channels (online storefronts) are licensed through the Commerce Scale Unit add-on rather than per-user. The biggest commercial fact for Commerce buyers in 2026: most retail enterprises deploy Commerce alongside D365 Finance, Supply Chain Management, and Customer Service — making the Attach pricing structure the largest licence-cost lever in the deployment. Customers who buy Commerce as a full user across the entire user population, rather than as an Attach licence on D365 Finance / SCM full users, routinely overpay by 4–6× for users whose primary application is not Commerce.
The three Commerce user-type SKUs
Dynamics 365 Commerce licensing in 2026 follows the broader D365 user-type model: a Base user licence for the first qualified user of an application, Attach licences at materially lower price for the second-and-subsequent applications used by the same user, and Team Member licences for read-mostly access. Commerce-specific pricing:
| User type | 2026 list price | Functional scope | When to use |
|---|---|---|---|
| Commerce (Base) | ~$180/user/month | Full Commerce + POS + merchandising + pricing | Users whose primary application is Commerce |
| Commerce (Attach) | ~$30/user/month | Same functional scope as Base | Users whose Base is Finance / SCM / Customer Service |
| Team Members | ~$8/user/month | Read-mostly; limited write to ~10 entities | Headcount needing visibility without execution |
| Device licence | ~$75/device/month | POS terminal full functionality | Per-terminal POS deployment |
| Activity licence | ~$50/user/month | Time-clock and shift activities | Hourly retail staff |
The Base vs Attach decision is the largest cost lever. A user whose primary D365 application is Finance ($210 Base) and who additionally needs Commerce should hold a Commerce Attach at $30, not a Commerce Base at $180. Customers who default everyone to Base across all applications pay $390 instead of $240 for that combined user — $150/month/user/year × thousands of users compounds quickly.
POS terminals: Device licensing vs User licensing
Retail point-of-sale terminals can be licensed two ways in Commerce: per-User (Activity licence at $50/user/month) or per-Device ($75/device/month). The decision is economic: Activity licensing makes sense for terminals with a dedicated 1:1 user assignment; Device licensing makes sense for shared-station terminals where multiple users authenticate to the same physical device through a shift pattern.
A typical retail store with 4 POS terminals and 12 cashiers across 3 shifts: Device licensing = 4 × $75 = $300/month; Activity licensing = 12 × $50 = $600/month. Device licensing wins for shared-station topologies, which is the typical retail-store deployment. The Activity option is the right choice for terminals tied to a specific named cashier (e.g., back-office customer-service stations).
The audit trap: D365 Commerce Device licences are sometimes ordered alongside Activity licences for the same terminal under the assumption that both are needed. The correct entitlement is one or the other, not both.
Commerce Scale Unit and e-commerce channels
The Commerce Scale Unit is the deployment-tier SKU that powers the e-commerce online channel, the in-store retail server, and the Call Centre channel. Commerce Scale Unit is licensed per environment ($1,200–$3,500/month depending on tier) and is required for any production deployment of the Commerce channels. The Scale Unit cost is separate from the per-user licensing.
The procurement consideration: many Commerce deployments require multiple Scale Units (production, staging, integration, disaster-recovery) and the total Scale Unit cost can match the per-user licensing for smaller deployments. We routinely see customers over-provision Scale Unit count or pay for unnecessary tiers on lower environments.
Team Member entitlement and the audit trap
Team Member at $8/user/month is the most common over-used SKU in D365 deployments — including Commerce. The Team Member entitlement is bounded: read access to most entities, write access to ~10 specific entities (timecards, expenses, etc.), and explicitly excluded from production POS, sales order creation, customer-record creation, inventory adjustment, and most operational functions.
The audit trap: customers deploy Team Member licences to retail-store staff and configure operational access through custom security roles. Microsoft Verification routinely surfaces the violation — the technical access works but the licence does not permit it. The recovery cost is the difference between Team Member and the correct entitlement (Activity, Attach, or Base) multiplied by the user population and the audit lookback period.
EA negotiation levers for Dynamics 365 Commerce
- Base-vs-Attach audit at user level. Every Commerce user should be audited against the user’s primary D365 application. If the primary is Finance, SCM, or Customer Service, Commerce should be Attach not Base.
- POS Device-vs-Activity SKU correction. Shared-station POS topologies belong on Device licences; named-user terminals belong on Activity. Audit the deployment against the topology before renewal.
- Team Member entitlement audit. Audit all Team Member assignments against actual usage patterns — Team Members performing operational functions create audit exposure that compounds.
- Scale Unit right-sizing. Lower-environment Scale Units (dev, staging, integration) rarely need production-tier sizing. The default LSP quote tends to oversize.
- Hardware refresh timing alignment. POS hardware refresh cycles are the leverage point for Device licence count rationalisation — bundle the Commerce renewal with the hardware cycle to capture the right device count.
- Commerce Scale Unit MACC application. Commerce Scale Unit consumption is Azure-backed and applies to MACC commit. Capture in MACC sizing rather than letting it land outside.
Anonymised case study: $890K Commerce renewal reduction
A 4,200-store specialty retailer deployed D365 Commerce alongside D365 Finance and D365 SCM across the corporate function. Total D365 user population: 6,200, of which 4,400 were retail-store staff and 1,800 were corporate users. The LSP-proposed renewal: 1,800 corporate users on D365 Finance Base + Commerce Base + SCM Base ($580/user/month combined), 4,400 retail-store staff on Commerce Base ($180/user/month), 14,000 POS Activity licences across the store estate at $50/user/month. We audited. Base-vs-Attach correction: 1,800 corporate users restructured to Finance Base + SCM Attach + Commerce Attach — combined $270 instead of $580, $670K annualised reduction. Retail-store Base-to-Activity correction: 4,400 staff moved to Activity licensing aligned to actual operational functions, $115K annualised reduction. POS Device licensing: 14,000 Activity licences replaced with 4,800 Device licences across 4,200 stores (1.14 terminals avg), $105K annualised reduction. Scale Unit right-sizing: 3 lower-environment Scale Units downshifted from production tier, $24K annualised reduction. Combined annualised Commerce renewal reduction: $890K against the LSP proposal.
D365 Commerce is one of the highest-overpayment areas we see in Dynamics 365 renewals, primarily because the Base-vs-Attach structure is poorly understood at procurement time. Pair the Commerce audit with the broader 2026 EA tier-collapse landscape, the license-optimization tooling that drives the user-level audit, and the license-optimization advisory that translates the audit into renewal economics.