Which client decisions make implementation more difficult than technology 

Technology is rarely the main source of problems in implementations

In e-commerce projects, it is very easy to attribute difficulties to technology. The platform turns out to be too complex, integrations more complicated than assumed, and the schedule begins to slip. From a project practice perspective, however, it is clearly visible that the biggest challenges do not result from the technology itself, but from decisions made on the business side – often in good faith, but without full awareness of their consequences.

It is worth stating this clearly: this is not about looking for those to blame. An e-commerce implementation is a joint process in which both the client and the software house operate under conditions of uncertainty, time pressure and organizational constraints. However, certain decisions, even if rational from a business perspective, can significantly hinder project execution – more than any platform limitations.

Postponing key decisions “until later”

One of the most common and at the same time most understandable decisions is the desire to leave some arrangements for a later stage of the project. Clients often want to “see the system in action” before making final decisions regarding processes, integrations or offer structure. From a business perspective, this sounds reasonable.

The problem is that many decisions in e-commerce are fundamental in nature. They concern data architecture, pricing logic, user roles or the way integrations with other systems are handled. Postponing them means that the project is built on temporary assumptions that later need to be changed. Each such change affects the time, cost and stability of the implementation.

Projects that run more smoothly are those in which the client decides to have difficult conversations and make choices as early as possible, even if it means giving up some flexibility at the start.

The desire to retain all exceptions from the current system

A very natural reflex when implementing a new platform is the desire to transfer all existing mechanisms exactly in the form in which they worked before. Every exception has its history, business justification and users who have become accustomed to it.

From an implementation perspective, however, this means attempting to recreate years of technological compromise in a new environment. Instead of simplifying processes, the project begins to focus on faithfully copying them. As a result, the new platform very quickly takes over the complexity of the old system, losing some of its natural advantages.

The decision about which processes are truly critical and which can be simplified or abandoned is often difficult, but it frequently has a greater impact on project success than the choice of a specific technology.

Lack of a clear decision owner

Many organizations operate in a team-based model built on consensus and broad consultations. This is a great value at the level of organizational culture. In e-commerce implementation projects, however, the lack of a clearly indicated decision owner can significantly slow down progress.

When decisions are distributed among several departments or individuals and none of them has a final mandate, the project begins to stall at the alignment stage. The software house does not know which arrangements are binding, and the client increasingly returns to decisions that were already made.

Well-functioning projects do not eliminate consultations, but they clearly define who ultimately makes the decision and takes responsibility for it.

Treating scope as a wish list

At the planning stage of an implementation, it is very easy to create a list of functionalities that “will definitely be useful”. The client wants to use the opportunity of a new platform to implement all ideas postponed for years. From a business development perspective, this is understandable.

The problem arises when the scope ceases to be a planning tool and becomes a catalogue of expectations without priorities. In such a situation, every functionality seems equally important, and decisions about abandoning or postponing items become very difficult. The project begins to expand, and its execution becomes increasingly complex.

Implementations that run more smoothly are based on clearly defined priorities and readiness to phase development.

Changes during the project without full awareness of their consequences

Changes in projects are inevitable. The market changes, new requirements appear, and some assumptions lose their relevance. What is crucial, however, is the way in which changes are introduced.

Often, the client perceives a change as a minor clarification, while from a technical perspective it means rebuilding logic, integrations or data architecture. If the consequences of these changes are not discussed openly, tension arises and a sense of losing control over the project appears.

Conscious change management – taking into account its impact on budget, schedule and scope – significantly reduces the risk of conflicts and delays.

Expecting technology to “organize” processes

A new e-commerce platform is very often perceived as an impulse to organize the organization. Clients expect the system to enforce better processes, discipline data and simplify the daily work of teams. To some extent this is true – technology can support standardization.

However, it will not replace business decisions. If processes are not thought through and responsibilities are not clearly defined, the platform will only make these problems visible. Expecting the system to “fix” the organization on its own very often leads to disappointment.

Technology as part of a larger puzzle

Platforms such as Shopware today offer enormous possibilities in terms of flexibility, scalability and integration. However, their effectiveness depends on the quality of decisions made on the business side. Technology amplifies what already exists – it makes good decisions even better, and can intensify disorder.

A shared project requires shared responsibility

An e-commerce implementation is not a test of the client’s or the software house’s competencies. It is a process in which both sides learn from each other and jointly make decisions of great business importance. Awareness of the impact of these decisions on the course of the project is one of the key elements of success.

At CREHLER, we place great emphasis on a partnership approach in implementations. Working with clients on Shopware projects, we help not only select technology, but above all organize decisions that allow this technology to truly work. If you are wondering what in your project may be a greater challenge than the platform itself – a conversation with a team that can combine business and technological perspectives is often the best starting point.