E-commerce today requires more than just a high-performing platform. Organizations must make strategic choices that determine how agile, scalable, and future-ready their digital landscape will be. Within the Intershop Commerce Management ecosystem, that choice is not about selecting different products. Instead, it’s about how Intershop Commerce Management (ICM) is implemented: in a classic setup, as a cloud-native platform, or through a phased transition toward a composable architecture.

Among organizations evaluating Intershop, we see a clear pattern emerging. Management teams mainly want to understand whether the platform can support their long‑term growth ambitions, how significant the vendor lock‑in really is, and to what extent Intershop’s product vision and roadmap align with their strategic goals. These evaluations are often triggered by international expansion, platform modernization, rising cost pressure, security expectations, and the balance between out‑of‑the‑box features and the need for custom development.

In this article, we outline in a clear, management-friendly way, the Intershop architecture options organizations are choosing today, and when each approach makes the most sense for your business.

Organizations with ambitious digital roadmaps are increasingly choosing Intershop Cloud, the cloud-native SaaS platform by Intershop. In this setup, Intershop Commerce Management (ICM) is deployed on modern, scalable container technology such as Kubernetes, with a strong focus on APIs and composable integrations.

We see this in recent projects with clients such as Huisman, Plato Group, midocean, and Daily Fresh Food, where scalability, performance, and international growth were key drivers.

This approach is ideal for organizations operating across multiple markets or channels and needing to adapt quickly. The focus shifts from release management to architecture, automation, and continuous optimization.

In real projects, we see these advantages clearly. Plato Group uses CaaS to expand into new countries with ease, while midocean benefits from significantly improved performance and much faster data imports. Which also supported their move to a headless front end. Thanks to the composable architecture, new versions achieve a much faster time‑to‑market, and organizations can respond to innovation needs far more quickly.

In a traditional enterprise setup, the platform runs on‑premises, in a private cloud, or via managed hosting, with clear release cycles and maximum operational control.

This approach is ideal for organizations that:

• operate within strict IT governance or compliance frameworks

• rely heavily on existing infrastructure and integrations

• prioritize stability, predictability, and risk mitigation

Intershop’s cloud offering provides a modern, API‑first foundation that enables targeted modernization without immediately overhauling the entire operating model. Intershop also actively supports organizations during this transition to reduce risks, lead time, and budget impact. For example, it’s possible to deploy the new version while keeping the existing frontend intact, a level of flexibility that underscores Intershop’s collaborative approach with its customers.

A recent examples is Daily Fresh Food, which opted for an upgrade without moving to cloud‑native right away. The proven stability of Intershop and the ability to preserve existing integrations were decisive factors, especially given the end‑of‑life of version 7.10. Heavy processes are being gradually transitioned toward microservices, ensuring evolution without disruption.

The decision to upgrade to the latest Intershop Cloud offering is rarely purely technological.

In practice, we see six recurring business drivers:

These drivers become very concrete in real projects. Customers like Plato Group and midocean approached us because their business expectations were rising: more users, more markets, and higher requirements for reliability and future‑readiness. For companies like these, risk reduction is a key factor, the need to avoid getting stuck with a slow, rigid architecture that holds back innovation.

After an upgrade or migration, we see typical pain points disappear: data import processes run significantly faster, and architectural limitations that once caused delays are removed. In that sense, an upgrade or migration is not a goal in itself, but a way to realign the platform with the organization’s ambitions.

For many organizations already using the Intershop platform, reality is far more nuanced than choosing strictly between a classical setup and a fully cloud‑native model. That’s why they consciously opt for a gradual, phased modernization strategy:

• First, upgrade to the latest Intershop version

• Then modernize frontends using headless or PWA technologies

• Finally, introduce cloud‑native components step by step

This approach creates space for innovation while safeguarding business continuity. Teams can evolve their architecture at a controlled pace, ensuring stability today while building the foundation for tomorrow.

At Fenego, we don’t approach Intershop as a technical exercise but as a strategic foundation. We guide organizations toward choices that fit their maturity, ambitions and operational context, today and in the future.

Our approach builds on proven strengths: deep experience with complex Intershop projects, a transparent and non‑offshored delivery model, and a co‑creative way of working supported by agile processes and monthly SteerCos. A thorough analysis phase ensures every project starts with a solid architectural blueprint, reducing risk and giving management the confidence that the project is in expert hands.

We focus on:

• clear architecture and deployment decisions

• phased modernization with measurable business impact

• future‑proof roadmaps within the Intershop ecosystem

This ensures Intershop grows with the organization, instead of slowing it down.

Want to know more about this technology or the projects we use it for? Don't hesitate to contact us for more info! Reach us by email or fill in the form below.