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

eCommerce is a non-core Dynamics 365 Commerce component listing, because it represents selectable Dynamics 365 Commerce Cloud Scale Unit tiers and a separate Ratings and Reviews option. For Commercial buyers, the live selector determines whether you are purchasing Basic, Standard, Premium, or Ratings and Reviews.

Only the selected Dynamics 365 Commerce component SKU is included, because this catalog item is sold as separate component options. If you select a Cloud Scale Unit SKU, you receive that Basic, Standard, or Premium scale-unit option; if you select Ratings and Reviews, you receive that separate component under its listed term and billing schedule.

Implementation work is not included, because this CSP SKU only covers the selected Microsoft component. Storefront design, solution architecture, data migration, integrations, managed services, and any licenses not represented by the selected SKU must be scoped and purchased separately if needed.

Basic, Standard, and Premium are separate Cloud Scale Unit SKUs, because Microsoft sells them as distinct scale-unit tiers. The exact functional and capacity differences should be confirmed against current Microsoft guidance and your Commerce architecture before purchase, especially for production eCommerce workloads.

No, Ratings and Reviews is a separate listed option, because the source catalog shows it as its own Dynamics 365 Commerce Ratings and Reviews SKU. If your deployment requires ratings and reviews functionality, confirm that requirement and select that component separately if eligible.

You may need other Dynamics 365 Commerce base, user, environment, or tenant prerequisites, because this listing covers only the selected scale-unit or Ratings and Reviews component. IT Partner should verify your current Dynamics 365 licensing and deployment plan before you buy to avoid purchasing a component that cannot be used on its own.

No, this eCommerce listing does not include Teams or Copilot licenses, because it is a Dynamics 365 Commerce component catalog item rather than a Microsoft 365 or Copilot plan. Any Teams, Copilot, Power Platform, or Dynamics add-ons required for your users or implementation must be licensed separately.

No, the source catalog does not show a trial for this Commercial eCommerce product. Buyers should validate fit through licensing review, deployment planning, or a Dynamics 365 Commerce assessment rather than relying on a trial SKU.

Commercial options include monthly commitment for Basic, Standard, Premium, and Ratings and Reviews, because those options appear in the catalog. Basic, Standard, and Premium scale-unit SKUs also have annual and three-year commitment options with monthly, annual, or triennial billing depending on the selected term; Ratings and Reviews appears only as a monthly Commercial option in the source catalog.

No, billing frequency and commitment length are different, because some annual and three-year commitments can be paid monthly while still committing for the longer term. In the source catalog, monthly-billed annual and three-year scale-unit commitments have higher catalog totals than equivalent annual- or triennial-billed options, so confirm the live CSP offer before purchasing.

Possibly, but it must be verified, because Basic, Standard, and Premium are separate Commerce Scale Unit SKUs and changes are subject to Microsoft CSP eligibility and subscription rules. Treat a tier change as a licensing and deployment decision, not just a seat-count adjustment.

Not necessarily, because this product is measured as a selected Dynamics 365 Commerce component rather than a typical per-user seat license. Quantity changes, reductions, cancellations, and substitutions follow Microsoft CSP rules for the selected SKU, term, and billing plan, so confirm change rights before ordering.

Annual and three-year CSP commitments are generally not freely cancellable after Microsoft’s allowed cancellation or reduction window, because the customer has committed to the selected term. Before purchase, confirm the current CSP cancellation rules, renewal date, and any reduction limits for the exact SKU in the live selector.

Renewal follows the selected CSP term and subscription settings, because Basic, Standard, and Premium scale-unit SKUs can be purchased under monthly, annual, or three-year structures. IT Partner should confirm auto-renewal status, renewal date, and any planned tier or billing changes before the renewal window closes.

Security and compliance are governed by the underlying Microsoft Dynamics 365 and Microsoft cloud service configuration, because this SKU is a Commerce component rather than a standalone security package. Your organization is still responsible for tenant configuration, identity controls, access governance, integrations, and compliance validation for its eCommerce deployment.

Do not assume it supports GCC or GCC High, because this page is for the Commercial segment and the source catalog lists Commercial, Charity, and Education segments rather than a government cloud offer. Government, GCC, GCC High, DoD, residency, and sovereign-cloud requirements should be confirmed separately before purchase.

A nonprofit or education organization should not assume Commercial is the best segment, because the source catalog shows separate Charity and Education segment availability for this product family. Eligibility, grant context, faculty or student licensing rules, and segment-specific pricing should be reviewed before selecting a Commercial SKU.

Start with a Commerce deployment review, because this purchase should match the required scale-unit tier, prerequisites, environment design, integrations, and rollout plan. IT Partner can help verify whether Basic, Standard, Premium, or Ratings and Reviews is the correct CSP component before the order is placed.

Possibly, but migration is not included in the SKU, because the catalog item only provides the selected Microsoft component. Existing storefronts, data, integrations, environments, and scale-unit architecture should be assessed separately to confirm whether the selected CSP component fits the current deployment.

A properly planned CSP partner transfer should not require moving the Dynamics 365 tenant data or taking the service offline, because the Microsoft cloud service remains in the customer tenant. The exact transfer path, billing effective date, and live CSP price must still be verified, because partner-of-record changes and subscription eligibility depend on Microsoft CSP rules and the current offer.