In retail, IT projects have long ceased to be merely supportive. Today, they are essential tools that directly determine operational performance: on-shelf availability, inventory turnover, display accuracy, and the manageability of the sales floor. It is at the shelf and shop floor level where it becomes clear most quickly whether digital solutions are delivering a real impact or if the project was executed as a mere formality.

In practice, many implementations end the same way: the system is launched, interfaces work, and reports are generated, yet the actual state of the shelf continues to follow its own rules. Planograms diverge from the physical display, data from shops arrives with delays, and the sales floor remains an under-managed resource. The cause is often not the solution’s functionality, but how the project was integrated into the retailer’s operational model.

When discussing IT projects in this article, we are not referring to abstract "digitalisation" or one-off tweaks to individual systems. We are talking about the implementation of applied solutions that directly influence floor space management and daily shelf operations: from assortment planning and planogram generation to execution control, analytics, and management decision-making. Such systems inevitably affect both the head office and the shop floor, requiring the alignment of data, processes, and people.

This is why projects related to display and space management are often among the most challenging. They rely on the quality of source data, require precise integrations with other IT systems, and are particularly sensitive to organisational imbalances. Below, we will examine the key systemic errors that most often prevent such IT initiatives from delivering sustainable and reproducible business results.

One of the most common issues when launching IT projects in retail is a superficial approach to selecting a solution. Often, an initiative starts with the phrase "we need a modern tool" or "this is how the market has been operating for a long time", without a clear understanding of exactly which business tasks the project should solve and what changes are expected at the shelf and shop floor level.

As a result, a solution is chosen based on a set of features, presentations, or market recommendations, but without being linked to specific operational processes. Already at the implementation stage, it becomes clear that some work scenarios have not been considered, data is not ready, and the requirements of different departments contradict one another. The project begins to accumulate customisations, deadlines shift, and the final result increasingly fails to meet initial expectations.

Projects related to display and space management are particularly sensitive to this. Here, it is not enough to formally "be able to build planograms" or generate reports. It is vital to understand exactly how assortment decisions are made, who is responsible for display accuracy in-store, how often planograms change, and how their execution is monitored. Without this, even a functionally strong solution remains detached from the actual work at the shelf.

Another typical risk is the lack of predefined success criteria. If the project’s start does not establish what changes should occur in turnover rates, product availability, or space manageability, evaluating the impact of the implementation becomes virtually impossible. In such conditions, the system is quickly perceived as a secondary tool rather than a part of the management model.

To avoid this error, the choice of an IT solution should begin not with market research, but with a description of one’s own processes and tasks. A clear understanding of what decisions should be data-driven, which roles are involved, and exactly how the system will be used in the shop and head office allows for the correct project requirements to be set from the outset, avoiding most problems in the subsequent stages.

Even a well-chosen IT solution rarely delivers results if the project lacks a clear owner from the business side. In retail, this role is often formally assigned to the IT department or an external integrator, particularly when the project involves implementing a new software product. In practice, such an approach almost always leads to a disconnect between the system and real-world processes.

Projects affecting display and stock distribution are, by their nature, cross-functional. They sit at the intersection of category management, operations, IT, and retail. If a project lacks a responsible owner who understands how shelf operations should change and who makes decisions at each stage, the system begins to exist in isolation from operational reality.

Another typical situation is leadership involvement only during the launch phase. The project receives approval, budgets are agreed upon, yet it progresses thereafter without regular attention from management. Consequently, key decisions are made on an ad hoc basis, priorities shift, and the implementation loses momentum. This is especially noticeable in projects requiring process adaptation and changes to established work scenarios in shops.

A lack of internal ownership also complicates managing user resistance. When employees do not understand why the traditional approach to display or execution control is changing, the new system is perceived as an additional burden. Without a clear decision-making centre, such issues remain unresolved, and the use of the tool declines over time.

Effective practice involves appointing a business representative as the project owner — someone responsible for performance metrics rather than technical implementation. Their task is to align requirements, build collaboration between departments, and ensure the system becomes part of daily operations. In this case, the IT project ceases to be a one-off initiative and begins to function as a sustainable management tool.

Projects concerning the control of product placement are particularly sensitive to the quality of integrations. Planograms, physical displays, sales data, and stock levels must rely on unified master records and be synchronised without delay. If it is not established at the outset which systems act as the data sources and exactly how information is exchanged, discrepancies begin to accumulate very quickly.

A typical scenario looks like this: the solution formally functions, yet data from different systems do not align, reports show conflicting figures, and users lose trust in the analytics. Consequently, display control shifts back into manual mode, and the shop, as an operational unit, loses transparency.

Another issue is the lack of a person responsible for the integrity of the IT architecture. When each integration is handled locally, without a holistic view of the system, the project gradually becomes cluttered with temporary links and exceptions. This complicates scaling, slows down changes, and increases support costs.

Early architectural design and a clear description of integration scenarios help to avoid this situation. Appointing someone responsible for data and architecture allows for a unified understanding of how the shop floor picture is formed and upon which data management decisions are based. In this case, the system ceases to be an isolated tool and becomes part of the retailer’s unified "digital circuit".

One typical situation is formal user training. Employees are shown the system’s functionality, but it is not explained exactly how it should assist them in their daily tasks. As a result, the tool is perceived as an additional form of monitoring or reporting rather than a workplace assistant. This is particularly critical for solutions related to display planning and control, where regularity and execution accuracy are vital.

Over time, the gap between planograms and the state of the shelf begins to grow. Data in the system ceases to reflect the real picture, and trust in the tool declines. At this point, users increasingly return to their accustomed ways of working, even if they are less accurate and more labour-intensive.

Post-launch support also requires dedicated attention. In many projects, it is assumed that once the system is commissioned, users will adapt to the new processes themselves. In practice, without regular feedback, updated instructions, and answers to queries, the system gradually falls out of the operational circuit.

A sustainable effect occurs when training and support are viewed as a continuous process. Users must understand the role the tool plays in managing the sales floor and what decisions are made based on the data they generate. In this case, the system ceases to be a formality and begins to function as part of a unified shelf management process.

The shelf relies on a multitude of interconnected data: assortment, product specifications, equipment dimensions, planograms, physical placement, sales, and stock levels. If this data is not properly organised from the start, the system begins to reproduce inaccuracies and amplify discrepancies between the plan and reality. Consequently, the manageability of the space declines, and analytics cease to inspire confidence.

The migration of data from existing systems requires particular attention. It is often viewed as a one-off stage before launch, without a deep analysis of the quality of master records and historical data. Errors at this stage do not manifest immediately, but over time, they lead to incorrect planograms, distorted calculations, and additional manual work in shops.

Another common risk is the lack of a unified understanding of which data serves as the "golden record". When different systems interpret the same metrics differently, the sales floor loses transparency as a managed object. Employees begin to rely on their own experience and intuition rather than data, which reduces the impact of automation to a minimum.

Avoiding this requires early work with data as part of a business process, rather than just an IT task. Auditing master records, aligning data sources, and establishing update rules allow for the creation of a foundation upon which shelf processes become manageable, reproducible, and scalable. In this case, the system begins to reflect the actual state of the retail space, rather than a mere formal model.

At the shop floor level, this manifests in non-obvious but systemic problems. A lack of clearly configured roles and access rights leads to situations where changes to planograms or data can be made without proper oversight. Over time, this blurs accountability and complicates the analysis of why discrepancies occur between the plan and the physical display.

An additional risk is associated with integrations. The more systems involved in forming a unified picture of the retail space, the more vital it is to ensure a secure and transparent exchange of data. Insufficient attention to these aspects can lead not only to operational failures but also to a loss of trust in the system from both users and management.

Another frequently underestimated aspect is compliance with internal regulations and security requirements. If these are not considered during the design phase, the project must be adapted after launch, which increases costs and reduces operational stability. In such conditions, the system is perceived as a source of additional risk rather than a management tool.

Practice shows that a sustainable result is achieved when security and control issues are embedded into the project from the outset. A clear role model, a transparent "audit trail" for changes, and controlled integrations allow for maintained shop management and sustained trust in data. This is especially important for solutions intended to operate at scale and reproducibly across a retail network.

Successful IT implementation in retail is not a matter of technology, but a question of a systemic approach. Even the most advanced solution will not work if it is viewed as a one-off technical task rather than an element of the management model.

The six critical errors described in this article — from unclear business objectives to ignoring data quality — form an "invisible barrier" behind which digital tools lose touch with the reality of the shop floor. Outwardly, the system functions, yet at the shelf level, nothing changes: displays remain chaotic, and decisions stay intuitive.

The true impact appears when IT becomes part of the operational routine: when data is updated as part of the process, not on demand; when responsibility for the result lies with the business, rather than IT; and when users in shops see the system as an assistant, not a monitor.

It is precisely this approach that transforms the shelf from a passive element of decor into a manageable, flexible, and measurable resource — the foundation of a sustainable retail network of the future. Those who build IT projects around this logic do not merely avoid failure — they gain a tangible advantage that grows with every updated planogram and every synchronised data point.