Now that you know you need a WMS, you need to decide on which WMS and implementation provider best suits your business needs. This is no small task as there are literally dozens of WMS package vendors, custom development houses, implementation providers and system integrators that could potentially be right for your requirement.
Before you proceed, please be aware that choosing your WMS implementation provider is of equal and - more often than not - more importance than the software you choose, because purchasing great software but not implementing it successfully will obviously result in high levels of dissatisfaction.
There are four main variants when it comes to selecting your WMS Provider:
A packaged software company typically develops software that is sold to a large customer base. These companies have spent many years and significant amounts of money building out software that focuses on meeting core requirements of warehouse management and can be broken into two core categories:
There are many companies out there that can “build” you a WMS, whether from the ground up, or using a base shell of WMS features and then adding to those based on your requirements.
These companies typically step in once a best of breed or ERP module has been sold and support the vendor via technical and domain expertise in implementing the software.
System integrators will work with you to ensure the core software, hardware and even the physical design and layout of your facility are managed under a single banner during the implementation process.
In many instances, it might be obvious as to which type of WMS provider suits your business, but there are always aspects that are not known. It's important to call out some of the important differences between what each partner type typically offers (packaged vs. customised) and explain the detail behind the core offerings they provide:
Packaged software vendors such as Manhattan Associates develop warehouse management software as their core business. This software is designed to be used across their entire customer base. This has several benefits and considerations:
Custom development software companies develop applications that are purpose built for their customers there are benefits and considerations:
Read the Kolok Success Story to see how they improved their efficiency through exceptional application of Manhattan's packaged solution:
Functionality is key when choosing any software as the reason you are investing in a WMS is that the functionality will help you execute actions in your warehouse that you either can't do today or do in a manual and labour intensive manner.
When considering the various features and functions provided by WMS providers, the most important thing is to understand, define and document what is important for your organisation not only today, but also for the future. Remember, once you’ve chosen a WMS you’ll typically have it in place for 10-15 years.
Where possible, adopt best practices, thus avoiding lengthy development timelines and costs.
Domain expertise can be defined as a person with special knowledge or skills in a particular area of endeavor. There is a common perception that it takes 10,000 hours to become an expert at anything, but this differs vastly according to what you are trying to master.
When is comes to your WMS, we would suggest that once a company has achieved the following they will have built a high level of domain expertise:
It is more common that packaged software vendors have a greater level of domain expertise as their software is sold into specific industries based on its capability, whereas custom development houses are built to specific customer requirements and will be experts in your business and the software language they use, but not necessarily in your specific industry vertical.
The request for proposal process (RFP) has been in place for many years as the standard method that most companies use when choosing a WMS provider.
"Over the years I have filled in dozens of RFP’s and then subsequently have been involved in the implementation that follows. One of the outcomes that most frequently occurs during the implementation following an RFP (and I would suggest that this phenomenon is not limited to WMS) is that the actual requirement of the implementation is vastly if not totally different from the requirement prescribed in the RFP. This often leads to misalignment of expectations, over inflated implementation costs and implementation timelines being missed."
- Michael Badwi, CEO Supply Chain Junction
If you are considering embarking on a warehouse management software RFP, there are 5 key steps, which, if followed, will ensure that you avoid the vast majority of typical mistakes made during the RFP process and that you set a solid foundation for the subsequent implementation.
In our guide to a successful WMS RFP, we outline the core steps that should be considered as part of the process:
Once you have gone live with a WMS, the support you receive from your WMS provider is critical to your ongoing success. Support is typically delivered in the following forms:
There are plenty of software reference visit checklists to help you ensure you cover off the core governance questions, but perhaps the most important aspects of the reference visits are the learnings that existing customers will share. These will typically include:
Once you've worked through the core decision elements to determine the right WMS you need to ensure you confirm the most important reasons to partner with your WMS provider.
Find out more about Supply Chain Junction and Manhattan's success by exploring our case studies, or view our WMS implementation tools:
See how Tarsus Distribution, in collaboration with SCJ boost overall efficiency by 60%