The final SAP Commerce on-premise release is here, along with the end of mainstream maintenance. With that comes an an opportunity to look beyond the technical migration itself. This blog explains what the support change does (and does not) mean, how to evaluate the future role of SAP’s embedded PCM, and why a dedicated, best-of-breed PIM may be worth considering as part of a wider strategy for composable commerce, omnichannel growth, and AI readiness.
Table of Contents
Keywords
For organizations running SAP Commerce on-premise (formerly SAP Hybris Commerce), July 31, 2026 was an important planning date.
On that day, version 2205, the final on-premise release, reached End of Mainstream Maintenance and moved into Customer-Specific Maintenance.
It’s important to note that SAP has stated that there is currently no defined sunset or end-of-life date for SAP Commerce on-premise, and this change does not affect SAP Commerce Cloud.
The other good news is that this is not an overnight shutdown, nor does it automatically require every organization to replace its product information management capabilities. It is, however, a valuable moment to review the role SAP Commerce plays in your technology landscape and decide what should come next.
When SAP Commerce 2205 enters Customer-Specific Maintenance, customers can continue to access support under their existing arrangements, but the scope changes. SAP will no longer adapt the release to certain new or changing requirements, including legal changes, technological updates, new support packages, updates to third-party libraries, or support for new interfaces.
For some organizations, the logical next step will be a move to SAP Commerce Cloud. Others may use the milestone to compare commerce platforms, adopt a more composable architecture, or modernize several parts of their digital stack at once.
There is another important point to clarify: Product Content Management, or PCM, is not a standalone SAP product that is independently reaching end of life. It is an embedded capability within SAP Commerce, and SAP Commerce Cloud continues to include product, content, and catalog management capabilities. An organization moving to SAP Commerce Cloud can therefore continue using SAP’s embedded PCM without adopting a separate PIM.
The right conversation is not, “What must we replace?” It is, “What architecture will best support the business we are becoming?”
Moving from customer-managed infrastructure to a cloud service can be a major undertaking, but infrastructure is only one part of modernization.
Product information now supports far more than a single eCommerce storefront. The same data may need to power regional sites, mobile experiences, marketplaces, distributor portals, print catalogs, customer service tools, retail partners, and emerging AI-powered discovery channels. It must also serve teams across marketing, eCommerce, product, compliance, sales, and operations.
At the same time, organizations are investing in AI and composable commerce. Both increase the importance of trusted, structured, well-governed product information. An AI agent cannot reliably compare, describe, or recommend products when attributes are incomplete, terminology is inconsistent, or critical context is scattered across systems. A composable architecture also delivers limited flexibility when product data remains tightly coupled to one commerce platform.
That makes this milestone an opportunity to ask a broader strategic question: Should product information remain embedded within commerce, or should it be managed through a dedicated, best-of-breed PIM?
Embedded PCM can remain a practical choice for organizations whose product content processes are closely aligned with their SAP Commerce environment. A dedicated PIM becomes worth considering when product information has a wider role across the enterprise.
Questions to consider include:
These are stronger indicators of a PIM opportunity than the maintenance date alone. The goal is not to introduce another platform for its own sake. It is to create an operating model in which product information can be collected, enriched, governed, and activated efficiently wherever the business needs it.
Akeneo provides a centralized source of trusted product information that can sit alongside SAP Commerce Cloud or support a broader commerce transformation. Product data can be brought together from ERP systems, suppliers, and internal teams; enriched and governed in one place; and then delivered to commerce platforms, marketplaces, distributors, and other customer-facing destinations.
For organizations continuing with SAP, Akeneo offers an accelerator for SAP Commerce Cloud built on SAP Integration Suite. It provides prebuilt integration artifacts to help synchronize complete, localized product information from Akeneo PIM into SAP Commerce Cloud while reducing the need for custom integration work.
This approach allows commerce and product information to evolve on their own timelines. Your commerce platform can focus on transactions, storefront experiences, promotions, and orders, while a dedicated PIM supports product data quality, enrichment workflows, governance, and omnichannel activation.
It also creates room for a phased modernization strategy. An organization may first migrate its commerce infrastructure, then strengthen product data governance, expand to new channels, improve supplier collaboration, or prepare its catalog for AI-powered experiences. Modernization does not have to be a single, disruptive replacement project.
Every SAP Commerce environment is different. Some organizations have relatively standard implementations; others have years of customizations, integrations, and business processes built around the platform. The right modernization plan must reflect that reality.
Akeneo is committed to being a partner for life, not simply a technology selected for a single migration project. We help organizations assess the current role of product information, define the capabilities their future architecture requires, and build a practical path forward, whether that means complementing SAP Commerce Cloud with a best-of-breed PIM or supporting a wider transformation.
The July 2026 SAP maintenance milestone deserves attention, but it does not need to create panic. Approached thoughtfully, it can become a catalyst for better governance, greater architectural flexibility, and more reliable product experiences. The result is a product information foundation that can support today’s migration decisions and continue adapting as channels, customer expectations, and AI capabilities evolve.
Considering your next step after SAP Commerce on-premise? Connect with an Akeneo expert for a conversation about your modernization strategy, or request a personalized demo to see how a best-of-breed PIM can support your business, whether you’re migrating to SAP Commerce Cloud or exploring a broader transformation.
Our Akeneo Experts are here to answer all the questions you might have about our products and help you to move forward on your PX journey.
Summer Release
