Dynamics 365 Commerce — Pricing, Plans & What's Included

Dynamics 365 Commerce for Commercial customers is the commercial-market licensing offer for Microsoft Dynamics 365 Commerce, because the source listing includes a full Dynamics 365 Commerce SKU and a separate Attach SKU for qualifying Dynamics 365 base-offer scenarios. It is intended for standard business purchasing, not Government, Charity, or Education purchasing paths.

The full Dynamics 365 Commerce Commercial SKU gives you the listed Commerce license offer for commercial purchasing, because it is the standalone Commerce SKU in the source pack. The source pack does not specify the unit of measure, assignment model, or detailed feature entitlements, so those should be confirmed before relying on user, device, store, or capacity assumptions.

Dynamics 365 Commerce Commercial licensing does not include a qualifying Dynamics 365 base offer for Attach eligibility, because the Attach SKU requires that qualifying base offer separately. It also should not be assumed to include trial access, other Microsoft products, implementation services, data migration, custom integrations, store hardware, payment terminals, third-party payment processing, or unlisted Commerce capacity unless those are separately confirmed or purchased.

The full Dynamics 365 Commerce SKU is the primary Commerce license option, while the Attach SKU is only for customers that already meet Microsoft’s qualifying Dynamics 365 base-offer requirement. Do not choose the Attach SKU unless eligibility is confirmed, because using Attach without the required base offer can create a licensing compliance issue.

You qualify for the Dynamics 365 Commerce Attach SKU only if you have a current Microsoft-approved qualifying Dynamics 365 base offer, because Attach licensing depends on an eligible base license. The source pack does not list the qualifying base offers, so IT Partner should verify the current Microsoft eligibility rules before you order.

No trial SKU is listed for the full Dynamics 365 Commerce or Attach SKUs in the source pack, because those Commercial entries are paid license options. The September catalog does show trial-tagged entries for the new Headless Import and Headless Orchestration SKUs, and if your project requires broader evaluation access, confirm with IT Partner whether Microsoft has a separate trial, sandbox, or evaluation path available outside this specific CSP listing.

The September catalog adds Dynamics 365 Commerce Headless Import and Headless Orchestration SKUs, each paired with a separate overage SKU. Per the catalog descriptions, Headless Import enables importing completed retail/commerce transactions from external systems into Dynamics 365 Commerce for downstream processing and fulfillment, while Headless Orchestration enables custom commerce experiences and integrations that use Commerce services across the shopping journey, including product discovery, cart management, pricing, promotions, and checkout; both base tiers include an initial transaction capacity entitlement, and the overage SKUs provide additional capacity beyond it. Headless commerce generally refers to using the Commerce engine through APIs without the Microsoft-built storefront, but the source pack does not define included capacity amounts, metering rules, or the unit of measure, so confirm the current Microsoft licensing guidance and prerequisites with IT Partner before ordering.

Dynamics 365 Commerce Commercial is listed with one-month, one-year, and three-year term options, because the source pack includes those commitment periods. Billing choices vary by term: one-month is listed with monthly billing, one-year is listed with annual or monthly billing, and three-year is listed with annual, monthly, or triennial billing.

No, monthly billing is not always the same as a month-to-month commitment, because the source pack separately lists monthly billing on fixed one-year and three-year terms. A one-month term provides the shortest commitment, while monthly billing on a longer term spreads payment across that fixed commitment.

You can typically add licenses during a CSP subscription term, because Microsoft commercial subscription programs generally allow increases during the active term. Reductions are usually more restricted after the short cancellation window and are commonly handled at renewal, so confirm the current CSP New Commerce rules for the exact subscription before placing the order.

Cancellation rules depend on the CSP term and Microsoft’s current New Commerce policy, because fixed-term subscriptions normally have a limited cancellation window and then run through the committed term. Renewal is typically managed at the subscription renewal date, where you can reassess quantity, term, billing frequency, and whether full or Attach licensing is still appropriate.

A switch from the full SKU to the Attach SKU should only be made after confirming Attach eligibility, because the Attach SKU requires a qualifying Dynamics 365 base offer. In practice, SKU changes are usually planned around renewal or a subscription change event, so IT Partner should review timing and eligibility before any change.

Do not assume Microsoft Teams is included with Dynamics 365 Commerce, because the source pack lists Commerce SKUs only and does not list Teams entitlements. If your retail or commerce rollout needs Teams for collaboration, meetings, chat, or frontline workflows, license Teams through an eligible Microsoft 365 or Teams offer as applicable.

Do not assume Copilot rights are included with this Dynamics 365 Commerce Commercial listing, because the source pack does not list Copilot as an included entitlement or add-on. Copilot availability can depend on the specific Microsoft product, region, tenant settings, data configuration, and separate licensing, so confirm current Microsoft Copilot requirements before including it in scope.

Do not assume POS devices, store hardware, or payment terminals are included, because the source pack only lists Dynamics 365 Commerce license SKUs and does not list hardware or payment-device entitlements. Store devices, peripherals, payment gateways, payment processing, and third-party integrations should be scoped and licensed separately where required.

Do not rely on unverified capacity assumptions, because the source pack does not specify e-commerce capacity, transaction capacity, Commerce Scale Unit requirements, or environment-level limits. Before final architecture or budget approval, confirm Microsoft’s current Commerce entitlements and any add-on or capacity requirements with IT Partner.

Dynamics 365 Commerce is a Microsoft cloud business application, so security and compliance depend on both Microsoft’s service controls and your tenant configuration. You should confirm data residency, role design, identity controls, audit needs, integrations, and industry compliance requirements before deployment, because the source pack does not define those operational settings.

No, this page is for the Commercial offer, because the source pack lists Commercial, Charity, and Education segments but does not list Government availability. Organizations requiring GCC, GCC High, DoD, or government-specific residency and compliance should not buy the Commercial SKU without confirming the correct government licensing path.

A nonprofit can buy Commercial licensing if it chooses to purchase commercially, but nonprofit eligibility and grant-related purchasing are separate because Charity is a distinct segment in the source pack. If your organization may qualify for nonprofit pricing, grants, or charity-specific terms, verify eligibility before buying the Commercial offer.

Schools should not assume the Commercial SKU is the right purchasing path, because Education is a separate segment from Commercial in the source pack. Student, faculty, and institutional licensing rules can differ from standard business licensing, so education buyers should confirm the Education offer and eligibility before ordering.

A CSP partner transfer can usually be planned without moving your Microsoft tenant or application data, because the service remains in the same Microsoft cloud tenant when the transfer is handled correctly. To avoid downtime or a subscription lapse, IT Partner should coordinate the transfer timing, subscription replacement or acceptance steps, renewal dates, and any price or service differences before the change.