Adobe Commerce Is Evolving: What Merchants Should Know Before Choosing Their Next Step

Adobe Commerce is evolving, not disappearing.

If you run on Adobe Commerce or Magento Open Source today, you may have seen more discussion around SaaS, composable commerce, Commerce Optimizer, faster storefront experiences, and Adobe’s broader commerce roadmap. Some of that conversation can make it sound like every merchant needs to make a platform decision immediately. That is not the case.

What has changed is that merchants now have more paths than before. Adobe continues to support Adobe Commerce on Cloud / PaaS while also investing in Adobe Commerce as a Cloud Service and Adobe Commerce Optimizer. Magento Open Source also remains available as a self-managed option.

Merchants don’t need to start with “Should we move?” The better question is whether the current platform still supports where the business is headed.

For some merchants, the answer will be to keep optimizing the current Adobe Commerce environment. For others, it may be time to modernize the storefront, evaluate SaaS, reduce technical debt, or compare broader platform options. The right path depends on the business model, technical complexity, team capacity, and customer experience goals.

Understanding the Platform Landscape

Adobe’s commerce ecosystem now includes several distinct models. These options are not interchangeable. Each one changes who owns the platform, how customizations are handled, and how much ongoing technical work the merchant needs to manage.

Adobe Commerce on Cloud

Adobe Commerce on Cloud is Adobe’s PaaS option. Adobe provides the hosted cloud environment, while the merchant and its implementation partner own much of the application layer.

In practical terms, the merchant needs to manage custom code, extensions, integrations, testing, performance work, release planning, and applying the necessary upgrades and patches.

This model can be a strong fit for merchants with complex catalogs, B2B requirements, custom checkout needs, unique pricing logic, multiple storefronts, or deep backend integrations. The control is valuable. The tradeoff is that the environment still requires active technical management.

Adobe Commerce on Cloud can be highly flexible, but it is not a “set it and forget it” platform.

Adobe Commerce as a Cloud Service

Adobe Commerce as a Cloud Service is Adobe’s SaaS option.

In this model, Adobe manages more of the core platform, including the application, infrastructure, updates, and platform operations. That can reduce the burden of traditional upgrade cycles, infrastructure management, and patch planning.

The biggest change is how customization works. Teams don’t modify the core application code in the same way they might in a PaaS or self-managed environment. Instead, customizations and integrations are handled through APIs, Adobe App Builder, API Mesh, UI SDKs, events, and other approved extension patterns.

For merchants with simpler environments, newer builds, or a strong desire to reduce maintenance, this can be appealing. It may let internal teams spend less time managing the platform and more time improving the customer experience.

For merchants with heavy customizations, the evaluation needs to be more careful. A SaaS move is not just an upgrade. It can require changes to architecture, integrations, development patterns, governance, and day-to-day operations.

Adobe Commerce Optimizer

Adobe Commerce Optimizer is not a full backend replatform. It is a SaaS-based way to modernize the storefront, catalog, and merchandising experience while keeping an existing commerce backend in place.

That distinction is important. Some merchants don’t need to replace everything at once. Their backend may still handle orders, pricing, inventory, fulfillment, customer accounts, or B2B workflows well. The bigger issue may be that the customer-facing experience is slow, difficult to update, or limiting the merchandising team.

Commerce Optimizer can be useful in that situation. It gives merchants a way to improve performance, merchandising agility, and storefront experience without immediately changing the transaction engine behind the scenes.

For some businesses, this can be a practical first step. It can create near-term value while giving leadership more time to decide what should happen with the backend over the longer term.

Magento Open Source

Magento Open Source remains a self-managed, open-source commerce platform. It can be a good fit for merchants that value independence, code control, and the ability to shape the platform around their own requirements.

The tradeoff is ownership. Merchants using Magento Open Source are responsible for hosting, development, security, upgrades, performance, monitoring, extensions, support, and long-term planning. Most businesses need either a strong internal technical team or a reliable partner to keep the platform secure, up to date, and stable.

Magento Open Source is not the same as Adobe’s commercial commerce offerings. It does not include the same Adobe support model, managed services, or SaaS innovation path as Adobe Commerce as a Cloud Service, Adobe Commerce on Cloud, or Adobe Commerce Optimizer.

That does not mean Magento Open Source is going away. It means merchants using it should be clear-eyed about the responsibility they are taking on. The platform can still work well, but the roadmap depends more heavily on the merchant and its partners.

The Real Shift: Choosing How Much Platform You Want to Own

Adobe’s newer investments point toward managed services, SaaS delivery, composable patterns, faster storefronts, and more flexible ways to build commerce experiences. Merchants don’t need to treat this shift as an emergency, but they should understand the direction of the market.

This is not only a technology decision. It is a decision about ownership: how much of the commerce platform the business wants to manage directly, and how much it wants Adobe or another provider to handle.

Every commerce platform asks the business to own something. The question is how much.

The decision usually comes down to three questions:

• How much control does the business truly need?
• How much platform maintenance can the team realistically support?
• Would the biggest improvement come from changing the backend, modernizing the storefront, or cleaning up the current environment?

There is no universally right path. A complex B2B manufacturer, a high-volume retailer, a fast-growing DTC brand, and a lean merchant with limited technical staff may all arrive at different answers.

What Merchants Should Evaluate

This is a good moment for merchants to step back and assess the current environment. Not because a move is required, but because platform decisions are easier when they are made before there is pressure.

Rather than starting with “Should we migrate?”, merchants should start with a more practical assessment:

• Business Fit: Is the current platform helping the business grow, improve customer experience, and move quickly enough?
• Technical Complexity: How much does the business depend on customizations, extensions, integrations, complex workflows, or backend control?
• Operational Burden: How much time, budget, and partner support are required to maintain, upgrade, secure, and optimize the platform?
• Future Direction: Does the business need more control, less maintenance, faster innovation, better frontend performance, or a phased path to modernization?

Those questions are more useful than abstract platform comparisons. A platform can be technically stable and still hold the business back. On the other hand, a newer model is not automatically better if it does not support real-world requirements.

For Magento Open Source merchants, the roadmap question deserves extra attention because more long-term planning falls to the merchant and its partners.

For Complex Commerce Environments

Merchants with heavy customizations, multiple integrations, complex pricing, B2B workflows, or unique fulfillment rules should be especially careful with the word “migration.”

Modernization is rarely one clean step. It may involve rethinking architecture, reviewing extensions, mapping integrations, cleaning data, changing release processes, and retraining teams.

For these merchants, a phased approach often makes sense. Stabilizing the current platform, reducing technical debt, improving performance, or modernizing the storefront first can protect the business while still moving it forward.

Common Paths Forward

Most merchants will fall into one of a few paths, depending on their complexity, resources, and growth strategy.

Optimize the Current Platform

For many merchants, the right next step is not a platform change. It is making the current environment healthier.

This path makes sense when Adobe Commerce on Cloud or Magento Open Source still fits the business, but the environment needs work. That could mean improving performance, cleaning up extensions, reviewing integrations, reducing technical debt, planning upgrades, strengthening security, or tightening release governance.

Modernize the Storefront First

In some cases, the biggest issue is not the backend. It is the customer-facing experience.

A storefront-first approach can make sense when the site is slow, merchandising is difficult, or frontend limitations are affecting conversion, but the current backend still supports core operations well. This can create near-term value while giving the business more time to evaluate the longer-term platform strategy.

Evaluate Adobe Commerce as a Cloud Service

Merchants who want to reduce operational overhead and move toward a more managed model may want to evaluate Adobe Commerce as a Cloud Service.

This evaluation should look closely at customization needs, integration patterns, data migration, business workflows, extensibility, and operational change. The goal is not just to decide whether SaaS is possible. It is to understand what would need to change for SaaS to work well.

Remain Self-Managed

Some merchants will decide that a self-managed model is still the right fit.

That may mean staying on Magento Open Source or another self-managed platform. This path can make sense for businesses that value independence, have strong technical ownership, and want full control over hosting, code, and release decisions.

The key is to be honest about the ongoing responsibility. Self-managed does not mean lower effort. It means more of the effort sits with the merchant and its partners.

Consider Broader Platform Options

Some merchants may determine that their long-term needs are better served by another commerce platform, a composable architecture, or a hybrid approach.

This does not need to be the first conclusion. But it is a valid part of the evaluation if the current environment is expensive to maintain, difficult to evolve, or no longer aligned with the way the business wants to operate.

How to Think About Timing

Merchants don’t need to rush. But waiting until a performance issue, an upgrade deadline, a security concern, or a business change forces the conversation is not ideal.

Now: Assess the current state. Review site speed, checkout experience, merchandising workflows, integrations, customizations, upgrade status, security posture, release process, and operating costs.

Near term: Compare realistic options. That may include optimizing the current environment, modernizing the storefront, evaluating Adobe Commerce as a Cloud Service, reviewing Commerce Optimizer, continuing with Magento Open Source, or comparing broader platform options.

Longer-term: Align the platform roadmap with the business strategy. If the company is expanding into new markets, growing B2B, launching new brands, reducing operational costs, or rebuilding the customer experience, the commerce roadmap should reflect those priorities.

Closing Thoughts

Adobe Commerce merchants have more options than they did before. That is useful, but it also makes planning more important.

The best next step is not necessarily a migration decision. It is a platform assessment.

Merchants should understand where the current environment is working, where it is creating friction, and what the business needs next. From there, they can decide whether to optimize, modernize incrementally, evaluate SaaS, remain self-managed, or plan a larger transition.

The goal is not to chase the newest platform model. It is to move deliberately, not reactively.