Patrick Mouwen Patrick Mouwen PMN Consulting
Release Analysis & Technical Resources · 20 March 2025

Commerce CSU V9.53/10.0.43 - March 2025

For anyone new in this field: Commerce CSU is shipped as part of D365 ERP and can seamlessly integrate any Professional App, Social commerce, e-commerce or POS solution with D365 ERP.

I have been using Commerce CSU for integration scenarios since its early days around 2015. My mission is to empower anyone to use Commerce CSU effectively for their integration scenarios. Therefore, I will publish these unofficial CSU Release Notes with any upcoming new Dynamics 365 ERP and Commerce platform Release.

A-Release Note Details

These These release notes apply to the following CSU and D365 ERP version:

B-Downloads for your convenience

  • Latest V9.53 CSU full interface specification in OpenAPI/Swagger format: Link

  • Lestest V9.53 Overview of required Commerce Roles for all nearly 800 APIs: Link

C-For the Techies: API and Model Changes compared to the previous version 9.52/V10.0.42

C.1 New APIs

There’s one in the works, but not fully implemented yet:

This API seems to control a stored procedure to ensure post-processing for specific tables after the CDX synch between HQ and CSU DB has run.

For example, if tables like ECORESPRODUCTCATEGORY or RETAILPRODUCTATTRIBUTESLOOKUP are affected by the data synch between HQ and CSU database, then return policies are updated.

C.2 Removed APIs

None

C.3 Data Model Changes

  • Property AllowedMinimumDaysForRequestDelivery is added to Microsoft.Dynamics.Commerce.Runtime.DataModel.CartConfiguration
  • Property AllowedMaximumDaysForRequestDelivery is added to Microsoft.Dynamics.Commerce.Runtime.DataModel.CartConfiguration.

These properties are maintained in the Online store functionality profile in D365 ERP:

C.4 New flight keys

Microsoft implements new CSU flight keys with every new CSU version. These undocumented flight keys steer specific CSU behavior. Here is a list of the latest keys:

D-Sources

With my Team, I have developed a couple of tools to collect the information above for you:

  • Automation to extract the OpenAPI specification from the latest Commerce CSU package

  • Automation to compare the OpenAPI specification with a previous OpenAPI specification and identify any changes

  • Automation to parse the latest DLL with D365 Commerce OData end points and extract role identification from the DLL:

E-About the Author

I’ve been integrating non-Microsoft e-commerce solutions with D365 ERP and CRM since the early days of AX for Retail in 2009. Already back in 2015, I connected an E-commerce platform to D365 ERP by a predecessor of the current D365 Commerce CSU for the first time.

Get in touch via patrickmouwen.com/contact if you need help in implementing:

  • D365 Commerce on top of ERP including D365 Store Commerce App and D365 e-commerce
  • Customizing/Extending D365 Commerce, CSU, Store Commerce App and e-commerce
  • B2C and B2B Headless Commerce/D365 ERP integrations via Commerce CSU
  • B2C and B2B Commerce Platform/D365 ERP integrations via Commerce CSU
  • Customer Service operation based on D365 ERP and D365 CE data utilizing Commerce CSU
  • Social Commerce/D365 ERP integrations via Commerce CSU
  • Professional App (React.JS)/D365 ERP integrations utilizing Commerce CSU
  • POS/ERP integration

Disclaimer

The content of this article represents my independent technical analysis and personal interpretation of publicly available software artefacts. It is not endorsed by, affiliated with, or authorised by Microsoft Corporation. Nothing in this article constitutes official Microsoft documentation, guidance, or product commitments.

All findings are derived from analysis of the software and public documentation. Feature descriptions, presumable use cases, and “likely intent” assessments reflect my professional opinion based on observable code and API changes — they may not reflect Microsoft’s actual design intent, planned behaviour, or final implementation.

Information regarding features described as preview, private preview, or roadmap items is subject to change at Microsoft’s sole discretion and should not be relied upon for planning, purchasing, or architectural decisions. This article describes the product as at the date of publication above.

This article is provided for informational and educational purposes only, on an “as-is” basis without warranties of any kind, express or implied. The author assumes no liability for any direct, indirect, incidental, or consequential damages arising from the use of or reliance on the information contained herein.

For authoritative product information, consult Microsoft’s official documentation at learn.microsoft.com.

← All writing