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

Dynamics 365 Commerce for Nonprofits is a Microsoft Dynamics 365 Commerce catalog offering for Charity nonprofit buyers, because the supplied CSP catalog lists nonprofit-priced Dynamics 365 e-Commerce tier, band, and overage SKUs under the Charity segment. It is organized by e-Commerce Tier 1, Tier 2, and Tier 3 with multiple bands, not as a simple per-user seat license.

Dynamics 365 Commerce for Nonprofits is licensed in this catalog by e-Commerce tier and band, because the Charity SKUs are listed as Dynamics 365 e-Commerce Tier 1, Tier 2, and Tier 3 band items with separate overage SKUs. Buyers should not treat this page as a complete capacity entitlement statement; confirm Microsoft’s current tier and band definitions before purchase.

The supplied Charity listing includes nonprofit-priced Dynamics 365 e-Commerce Tier 1, Tier 2, and Tier 3 band SKUs, because those are the catalog entries shown for Dynamics 365 Commerce in the Charity segment. It also includes matching overage SKUs by tier and band, but those overage items are listed separately from the base tier/band SKUs.

This catalog page does not confirm exact transaction, order, page-view, storefront, or other usage thresholds, because the source only lists tier, band, billing, term, and SKU information. It also does not confirm whether implementation services, payment providers, tax engines, fraud tools, customer service capabilities, or third-party integrations are included, so those items should be validated with IT Partner before ordering.

No, overage should not be assumed to be included in the base tier/band entitlement, because the Charity catalog lists separate overage SKUs for the tiers and bands. A nonprofit should confirm what usage event triggers overage, how it is measured, and which overage SKU applies before it commits.

A nonprofit should choose the tier only after validating Microsoft’s current e-Commerce definitions, because the source catalog identifies Tier 1, Tier 2, and Tier 3 but does not define the capacity thresholds or usage measurements. IT Partner should help map expected digital commerce volume, storefront needs, and overage exposure to the correct tier and band.

The band numbers are catalog variants within each e-Commerce tier, because the Charity catalog lists multiple bands across Tier 1, Tier 2, and Tier 3. The source does not define what each band represents, so the meaning of each band and its threshold should be confirmed against current Microsoft licensing terms before quoting.

No free trial is listed in the supplied source pack, because every Charity entry for Dynamics 365 Commerce is marked as a paid, non-trial SKU. If a trial, pilot, or sandbox is needed, the nonprofit should ask IT Partner to confirm current Microsoft availability and deployment options.

The Charity catalog shows month-to-month commitment paid monthly, annual commitment paid upfront, and annual commitment paid monthly, because the source lists P1M and P1Y terms with monthly and annual billing options. Annual upfront is the lowest-cost posture in the supplied catalog, annual paid monthly runs higher, and month-to-month gives the shortest commitment.

No three-year term is listed in the supplied Charity catalog, because the source shows only P1M and P1Y terms for Dynamics 365 Commerce e-Commerce tier, band, and overage SKUs. If a longer commitment is required for procurement, IT Partner should confirm whether Microsoft has any current program option outside this catalog snapshot.

Cancellation and reductions depend on the Microsoft CSP term and the rules in effect at the time of order, because annual commitments generally carry stronger term obligations than month-to-month commitments. Since this product is tier/band based rather than per-user seat based in the supplied catalog, reductions usually mean changing or removing SKU quantities or tier/band choices under Microsoft’s applicable cancellation and renewal rules.

An upgrade may be possible, but it should be validated before purchase, because the source catalog lists multiple tiers, bands, and overage SKUs but does not state mid-term change rules. IT Partner should confirm whether the intended move is treated as a new subscription, a SKU change, an upgrade, or a renewal-time adjustment under current Microsoft CSP rules.

Possibly, but this catalog page does not confirm prerequisites, because it only lists Dynamics 365 e-Commerce tier, band, and overage SKUs. Before ordering, a nonprofit should confirm whether it also needs other Dynamics 365 Commerce, Finance, Supply Chain, Dataverse, Power Platform, or related licenses for the planned deployment.

No Teams or Microsoft 365 user licenses are shown as included, because the supplied Charity catalog entries are Dynamics 365 e-Commerce tier, band, and overage SKUs. If staff need Teams collaboration, Microsoft 365 productivity apps, or identity/security add-ons, those should be scoped and licensed separately.

Copilot is not confirmed as included by this catalog page, because the source does not list Copilot entitlements, AI add-ons, or user licenses. A nonprofit should verify any Dynamics 365, Microsoft 365 Copilot, or role-specific AI requirements separately before assuming AI functionality is available.

Those capabilities are not confirmed as included in this Charity listing, because the source only identifies e-Commerce tier, band, and overage SKUs. Payment providers, tax engines, point-of-sale rights, call center capabilities, fraud protection, and customer service integrations may require separate licensing, services, or configuration and should be validated with IT Partner.

A nonprofit should review identity, data protection, payment, privacy, and industry compliance requirements before purchase, because e-Commerce deployments often process customer, donor, order, and payment-related data. The supplied catalog does not state compliance certifications, data residency, payment-card responsibilities, or security add-ons for this SKU, so IT Partner should confirm the Microsoft service terms and any required third-party controls.

GCC or GCC High availability is not shown in the supplied source pack, because the product is listed for Charity, Commercial, and Education segments but not Government. A nonprofit with government residency, sovereign cloud, or GCC High requirements should not rely on this Charity catalog entry and should confirm the correct Microsoft cloud and licensing path before ordering.

Yes, nonprofit eligibility should be confirmed before ordering, because the listed SKUs are explicitly nonprofit-priced Charity catalog items. Eligibility, program approval, and any Microsoft nonprofit requirements are separate from technical deployment, and IT Partner should verify status before quoting or placing the order.

Yes, a CSP partner change can typically be handled without moving the tenant or reinstalling the service, because the Microsoft cloud tenant and subscriptions remain associated with the customer tenant while partner-of-record and subscription management are updated. The Microsoft catalog pricing for the same eligible Charity SKU and term is not changed merely by the transfer, but the final invoice, taxes, and partner commercial terms should be confirmed with IT Partner.