In order to bring their client base the ability to deliver more modern headless and composable commerce experiences, SAP announced the end-of-lifecycle, for several legacy front-end components. Specifically, SAP has announced the deletion of accelerator UIs and related add-ons are being deprecated, currently as of H2 2025. In addition, Omni Commerce Connect (OCC v1 and v2) template extensions and add-ons are also being sunset. Here is a detailed list of the SAP Commerce extension deprecation status.
The second half of 2025 may seem distant in the scheme of things, but when it comes to the inherent complexities underlying modern B2B commerce experiences, the time to decide on the path forward is now. It’s not like affected merchants can do “nothing” and still operate their commerce storefronts. Or can they? The good news is that merchants running affected versions of SAP Commerce have multiple options in determining how to move forward. The bad news is that merchants have these multiple options, and subsequent decisions will have downstream impacts for years to come. It comes down to finding the right approach to match a business’ operating model and overall strategy. So, let’s look at what paths are available to merchants and how they can narrow their options to make informed decisions.
It’s worth repeating: there is no ‘one-size-fits-all’ solution that will work for all businesses. Depending on the business, goals, and current level of digital maturity, each business must weigh the trade-offs between flexibility, agility, complexity, and cost. As we’ve noted in our Composable Commerce Continuum (C3), the start and end points will be different for every business and there are many points on the journey from so-called monolith to headless to fully composable.
Stay the Course (Temporarily)
Merchants on affected versions of SAP Commerce will not lose access to their storefronts when the accelerator UIs are deprecated. They will, however, lose access to enhancements, security patches, and the ability to innovate and iterate. Maintaining these storefronts can be achieved with the help of an experienced partner. That said, this is by no means a forever solution, but it does buy some time to determine the best long-term path forward. For those operating simple B2B ordering portals and other straightforward use cases this provides an ideal opportunity to assess options and create a roadmap for incremental change.
SAP Commerce Cloud Composable Storefront
Third-Party Front-End Storefront
This approach to headless relies on a third-party ISV to supply the front-end framework and UX to deliver the storefront front-end. As purpose-built solutions these options can offer synergies in storefront hosting, speed to deploy, and API orchestration. Numerous acquisitions in this space have narrowed the number of available options for businesses. As standalone vendors, all their revenue relies on licensing their platform offering. This can lead to significant costs that need to be weighed as part of the calculus for ROI as part of the full commerce solution.
Custom or Pre-Built Solutions
Going fully custom can be scary, but it also provides a business with the complete flexibility to build a commerce ecosystem perfectly suited to its needs. This in effect unlocks the full possibilities of composable commerce. Knowing where to start, what to prioritize, and how to incrementally transition can be the major challenges. The alternative? Find a partner that has committed to building part, or all, of the components necessary to jumpstart and/or sustain the process.
At Smith, we’ve created two potential solutions for merchants. The Ascend SAP Composable Cloud Extension is a pre-built, headless commerce solution that brings together Coveo and Contenful with SAP Commerce Cloud to enable powerful commerce capabilities, while condensing typical launch cycles. Going further, the Smith team has also created a Composable Storefront Platform (CSP). The CSP can be deployed as a headless front-end integrated with SAP Commerce Cloud and is designed for unlimited extensibility and customization and with a focus on B2B. Unlike an accelerator, the CSP is a fully realized product, complete with product roadmap and release schedule, which delivers value across the commerce solution lifecycle. As with any solution option the viability of Ascend or the Composable Storefront Platform is dependent on a business’ goals and needs.
Which approach is best for your business? Making the right decision starts with a conversation. Get in touch with the SAP Commerce Cloud experts at Smith and let’s determine the best path forward together.