Don’ts – avoid common mistakes
1. Overcomplicated
In the first iteration, the template should be as simple and user-friendly as possible. Complexity leads to longer implementation times and makes acceptance more difficult.
2. Underestimating change management
A lack of communication and training can lead to rejection on the part of key users. Even a technically perfect template will fail if it is not accepted by the users.
3. Introduction without phase
An SAP EWM template should always be tested in a pilot warehouse first. This is the only way to identify errors at an early stage, check user-friendliness and ensure integration with other systems such as ERP. If this step is skipped, it could have a significant impact on the operational business.
4. Neglecting governance
Without a clear governance model, the template can develop in an uncontrolled manner, leading to a proliferation of functions and increased complexity.
5. Excessive individualisation
Too many company-specific customisations significantly increase maintenance costs and can limit the update and scalability of the template in the long term. Customisations should be made selectively and with caution.
6. Estimate total costs incorrectly
In addition to the initial implementation costs, ongoing operating costs ("total cost of ownership") must also be taken into account. This includes maintenance, support, upgrades and further development.
7. Relying exclusively on external consultants
External consultants such as KPS provide targeted support with implementation, design and project management and can therefore help the company to successfully implement SAP EWM. Nevertheless, the company should build up internal expertise and establish its own team, which will later take over the maintenance and further development of the template.
8. One size fits all
Even with a standardised warehouse layout, there are always individual differences. A good balance between global standards and local flexibility is crucial for success.