In SAP Commerce Cloud, extension deprecation serves as an early warning system to help businesses plan their long-term architecture. When an extension is marked as deprecated, SAP continues to provide support and security fixes, but no new features are developed for it. This grace window allows customers to continue using the extension while they migrate to a recommended alternative, such as moving from legacy Accelerators to SAP Commerce Cloud Composable Storefront.
Maintenance support for a deprecated extension continues until it reaches its official "deleted" status or until its SAP Commerce Cloud version reaches End of Main Maintenance (EOMM). While maintenance is provided, using deprecated extensions in new projects is strongly discouraged, they are slated for removal in future releases.
Following is a sample list of deprecated extensions. For a complete list, please check SAP Help Portal - Deprecation Status.
| Extension | Module | Announced Deprecation With | Planned Deletion | Reason for Deprecation | Mitigation Plan |
|---|
| addonsupport | Core-accelerator | 2205 | Q2 2024 | The deprecation of the Accelerator UI and older OCC template extensions is aligned with the SAP Commerce Cloud vision to provide a modern and headless commerce experience. | For information on how to start the mitigation process, see Changes to Planned Removal Date for Deprecated Accelerator UI and Extensions |
| eventtrackingmodel | event-tracking | 2011 | Q4 2028 | The Event Tracking module is an old implementation using outdated libraries. Sending a large number of customer interactions through the SAP Commerce Cloud back end does not scale. | In SAP Commerce Cloud, Composable Storefront, the event service does what the Event Tracking module extensions did. |
| y2ysync | platform | 1905 | To be determined | Dependency on deprecated parts of the product. | |
Extension deprecation is component-specific, meaning it applies at the individual extension level. In contrast, End of Main Maintenance (EOMM) is version-specific and applies to the entire software release. Once a release reaches EOMM (such as SAP Commerce Cloud 2105), it is no longer covered by standard maintenance, regardless of whether its extensions are active or deprecated. To remain compliant with your support agreement, you must run a supported SAP Commerce Cloud version:
| | Bug Fixes (maintenance release) | Security Vulnerability (maintenance release) | Technical Support |
|---|
| Supported version with a valid subscription | Yes | Yes | Yes |
| EOMM versions | No | No | Partly supported |
Key Takeaways
- SAP Commerce Cloud provides three license types: Temporary (for testing), Development (up to two years for local environments), and Regular (auto-provisioned in cloud deployments).
- The platform follows a continuous innovation model on version 2211, with monthly cumulative updates using JDK 21-based naming (2211-jdk21.x), each supported for exactly six months.
- Third-party library versions are updated monthly and must be regularly verified on the SAP Help Portal, while deprecated extensions remain supported until deleted or until its SAP Commerce Cloud version reaches End of Main Maintenance (EOMM).