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

Dynamics 365 Commerce under Charity pricing is the nonprofit-priced catalog path for eligible organizations that need the Dynamics 365 Commerce SKU. The provided catalog shows both a full Dynamics 365 Commerce nonprofit-pricing offer and an attach offer, because some buyers need Commerce as the primary license path while others qualify for a lower attach path tied to an existing qualifying Dynamics 365 base offer.

The provided Charity catalog includes Dynamics 365 Commerce availability under nonprofit pricing, with full-license and attach-license purchase paths. It also includes monthly commitment, annual commitment billed annually, and annual commitment billed monthly options, because those rows are present in the supplied CSP catalog data.

A trial license is not included, because the provided Charity catalog does not list a trial SKU for Dynamics 365 Commerce. The source pack also does not define detailed workload limits, implementation services, payment processing, tax services, shipping services, hardware, third-party connectors, or data migration, so those items should be validated and scoped separately before purchase.

The full Dynamics 365 Commerce Charity SKU is the standalone nonprofit-pricing purchase path for the Commerce license shown in the catalog. The attach SKU is different because it is only for customers that already have a qualifying Dynamics 365 base offer; it should not be treated as a standalone Commerce license path.

No, the Dynamics 365 Commerce attach SKU should not be purchased without a qualifying Dynamics 365 base offer, because the catalog explicitly describes it as an attach offer. IT Partner should verify the existing base license before quoting or provisioning the attach path.

No trial is listed for the full or attach Dynamics 365 Commerce paths in the provided Charity catalog, because those Charity rows are paid nonprofit-pricing SKUs. The September catalog does show trial-tagged entries for the new Headless Import and Headless Orchestration SKUs, and any broader trial or evaluation path should be confirmed in the live CSP catalog at quote time.

The September Charity catalog adds Dynamics 365 Commerce Headless Import and Headless Orchestration SKUs at nonprofit pricing, 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. Headless commerce generally refers to using the Commerce engine through APIs without the Microsoft-built storefront, but the provided catalog does not define included capacity amounts, metering rules, or the unit of measure, so confirm current Microsoft licensing guidance and nonprofit eligibility with IT Partner before ordering.

The provided Charity catalog shows monthly commitment, annual commitment billed annually, and annual commitment billed monthly options for Dynamics 365 Commerce. These are different purchasing structures, because billing frequency and subscription commitment are not the same thing under CSP terms.

Among the provided Charity rows, the annual commitment billed annually has the lowest listed unit price, because the catalog data shows that option priced lower than the other commitment and billing combinations. A nonprofit should still confirm current CSP pricing, taxes, term rules, and cancellation terms with IT Partner before committing.

No, annual commitment billed monthly is still an annual commitment, because monthly billing only changes the payment schedule, not the subscription term. Cancellation, reduction, and renewal rules should be confirmed at quote time because CSP change windows and Microsoft commerce policies can affect what changes are allowed during the term.

You can usually add quantities during a subscription term, but reductions and cancellations are more restricted because they depend on the selected commitment term, renewal timing, and current CSP commerce rules. IT Partner should confirm the exact change window, renewal date, and subscription quantity rules before you buy.

Charity pricing should be used only after nonprofit eligibility is confirmed, because the catalog identifies these rows as nonprofit-pricing offers. The source pack does not describe Microsoft nonprofit approval, grant eligibility, or validation steps, so your organization should confirm eligibility status through the appropriate Microsoft nonprofit process or with IT Partner before purchase.

The provided catalog shows nonprofit pricing for Dynamics 365 Commerce, not a donated grant entitlement, because the rows are paid CSP subscription offers. Some Microsoft nonprofit programs include grants for certain products, but this source pack does not state that Dynamics 365 Commerce is granted at no cost, so grant applicability should be confirmed separately.

A nonprofit school should not assume Charity and Education pricing are interchangeable, because each segment can have separate eligibility rules and role-based licensing requirements. The source pack confirms that Charity, Commercial, and Education segments exist for this product, but it does not define student versus faculty terms, so IT Partner should validate the correct segment before ordering.

You should not buy the Charity offer if nonprofit eligibility is not confirmed, because Charity pricing is intended for eligible nonprofit organizations. The source pack also shows a Commercial segment for Dynamics 365 Commerce, so IT Partner can help evaluate the standard business purchase path if Charity eligibility is unavailable or changes later.

No, the Dynamics 365 Commerce Charity catalog offer should not be treated as a Microsoft Teams license, because the source pack only lists Dynamics 365 Commerce SKUs and does not include Microsoft 365 or Teams entitlements. If Teams is needed for collaboration, meetings, or calling, the appropriate Microsoft 365 or Teams licensing should be confirmed separately.

No Copilot entitlement is listed in the provided Dynamics 365 Commerce Charity catalog, because the source pack only identifies Commerce full and attach SKUs. Any Microsoft 365 Copilot, Dynamics 365 Copilot capability, AI feature, capacity requirement, or preview availability should be validated separately before assuming it is included.

Do not assume those items are included, because the provided source pack does not define payment processing, tax calculation, shipping services, store hardware, devices, or third-party connectors as part of the Charity SKU. Commerce projects often require separate services, integrations, or devices, so those dependencies should be identified during solution design and quoting.

Dynamics 365 Commerce should be planned with Microsoft cloud identity, role-based access, environment governance, data protection, and compliance requirements in mind, because licensing the SKU does not by itself configure security. A nonprofit should confirm administrative roles, data handling, audit needs, integration security, and any sector-specific compliance obligations before deployment.

Government availability is not confirmed by the provided source pack, because it lists Charity, Commercial, and Education segments but does not list Government, GCC, or GCC High availability for Dynamics 365 Commerce. If your nonprofit has public-sector, sovereign cloud, or data residency requirements, confirm the correct Microsoft cloud availability and compliance boundary with IT Partner before purchase.

Start with licensing validation and project scoping, because the Charity SKU confirms a purchase path but does not define implementation, migration, integrations, or feature readiness. IT Partner should confirm nonprofit eligibility, full versus attach licensing, current CSP terms, required Commerce capabilities, data migration scope, payment and tax dependencies, and rollout requirements before provisioning.

A CSP transfer is normally an administrative licensing and partner-management change, not a data migration, because the Microsoft tenant and service data do not need to move when the same tenant is retained. IT Partner can validate the matching Microsoft CSP offer, term, renewal date, and subscription mapping before transfer; final invoicing can still depend on partner terms, taxes, and any services added.