Common warehousing mistakes: WMS implementation pitfalls and best practices

Updated:

The hard part of picking your new WMS is over, and you’re ready to get started on integration and implementation. Congratulations, and welcome to the harder part.

That’s the unfortunate truth of a WMS implementation. It takes planning, patience, and diligence to turn its capabilities into a positive ROI. Here, we’ll look at three of the most common warehousing mistakes that threaten that return.

What are the most common WMS implementation mistakes?

  1. Choosing a system under sales pressure instead of doing your research
  2. Not having a solid implementation plan, or going live in your busy season
  3. Failing to achieve buy-in from leaders at every tier
  4. Migrating data into the new WMS without cleaning it first
  5. Not being flexible when the system needs adjusting to fit your warehouse
  6. Skipping the testing phase
  7. Skimping on user training
  8. Not knowing your best point of contact when problems occur
  9. Allowing employees to slip back into old legacy processes

Every one of them is avoidable. Here's how.

1. Succumbing to sales pressure

Every vendor wants you to choose their WMS instead of anyone else's. It's the nature of sales, but that doesn't mean you have to buy into the first product that comes your way.

Don't succumb to the pressure. Do your research before choosing the system that you will eventually use in your warehouse, and ask to see it run your own processes rather than a scripted demo. Not all warehouse management systems are created equal, and spending some more time being picky can save you a lot of time and trouble in the long run.

2. Not having a solid implementation plan

Imagine your accounting team buys a brand-new piece of software and moves all of your books over to it in one day. There are no backups and just the hope that all your accounts and partners can sync with it.

Feel your blood pressure rising yet?

Warehouse management tools are the same. Without an implementation plan in place, you’re taking a leap of faith that it’ll all work out, and you won’t grind your supply chain to a halt. And, if software has taught us anything in the past, it’s that there’s always some hiccup.

Check out our full WMS implementation checklist for a step-by-step method for implementing your system successfully

Implementation can be a long process. It involves multiple stakeholders, tests, checks, and other plans to stay on track, on time, and on budget. The more you plan, the higher your chance of success for the implementation and generating a positive return when people use the WMS correctly.

3. Failing to achieve buy-in

There's more than just financial investment at stake here. You need decision-makers personally invested in the proposed changes, too. Without buy-in from leaders at every tier of your organization, you risk rolling out a new system with which some of your most important team members are not familiar and cannot "promote" to the people who report to them in turn.

Enthusiasm for moving to a new warehouse management system has to come from the top, and you have to convincingly portray to the rest of the company the improvements it will bring and why everybody should become familiar with it quickly.

4. Migrating data without cleaning it first

Your new WMS is only as good as the data you put into it. Move messy records across, and you'll simply automate the errors you were hoping to leave behind, from wrong pick locations to stock that only exists on screen.

So, what data should you clean before migrating to a new warehouse management system? At a minimum:

  • Item master data: SKUs, descriptions, units of measure, and pack sizes. Remove duplicates and discontinued items.
  • Dimensions and weights: these drive slotting, putaway, and packing, so missing or wrong values cause problems quickly.
  • Location data: bin and location IDs, zones and capacities, matched to your actual physical layout.
  • Inventory balances: count your stock before cutover so opening balances match what's on your shelves, including lot, serial and expiry details where you track them.
  • Barcodes: make sure every item and location barcode is unique and scannable.
  • Supplier, customer and carrier records: addresses, contacts and shipping details, with duplicates merged.
  • Open orders: decide which open purchase and sales orders move across, and close or reconcile the rest.

Agree who owns each data set, archive what you no longer need rather than migrating it, and run a trial migration before go-live. Which brings us to testing.

5. Not being flexible

Even a WMS that looks like it fits your warehouse correctly might need to be changed here and there. Be flexible. If you have a system in place that doesn't quite work for you, then make the necessary changes.

Most systems let you configure workflows, rules, and screens without custom code, which also keeps future upgrades simpler. Adapt the system to work for you instead of having to work for the system.

6. Skipping the testing phase

You wouldn't implement a new production process without testing it, so why would you bring a new warehouse management system into your facility without a shakedown run first? No matter how long it takes, don't skip the testing phase.

Test with your real, cleaned data and everyday scenarios, from receiving and putaway to picking, packing, shipping, and returns, as well as the integrations with your other systems. This will also give you time to figure out what works and what doesn't for everybody who comes in contact with the system on an average day, so you can change workflows as needed to suit your company and staff.

7. Skimping on user training

If your team doesn’t know how to use your new system, how could you expect to have a positive WMS ROI?

It might seem obvious now, but there are plenty of times and reasons why companies try to skimp on training. The software may look similar; you might have hired someone who claimed to know the WMS, or you only trained one person and didn’t think about them getting sick or leaving.

They’re all terrible reasons. Don’t skimp on training.

Every piece of warehouse management software is different. Functionality may be the same, but the location and processes to find and use your inventory will vary. Reporting tools change, as do their capabilities.

You likely do inventory counts a little differently for several types of products. Often our metrics for raw materials and finished goods vary, for example. Without training, your team could make significant mistakes in these counts and significantly hurt your business.

A WMS implementation operates in the same way. Train your team and provide ongoing support so that they can understand and correctly use the system. It’s the only way to cash in on those promises of big WMS returns.

8. Not knowing your best point of contact

The ideal outcome in partnering with a vendor for a new warehouse management system is twofold. First, you have a reliable point of contact who can put a "face" on the software and other services involved, answer your questions, and provide ongoing advice as needed. Second, you come away with the peace of mind that bugs and issues don't have to be solved by in-house IT personnel.

But some of the biggest mistakes leaders make tend to occur in this "last mile". There should be a clear and easy process for employees and managers to raise support tickets when things don't work as expected. You should know how to react when problems occur, because they will from time to time. A good vendor won't leave you with a stalled warehouse, and they won't leave you guessing how to bring any issues to their attention.

9. Allowing employees to use old legacy processes

Building on the idea of a strong WMS return requiring training, leadership needs to enforce the things people learn during that training. The final WMS mistake is when you skimp on this review process.

Your change management plan and practice aren’t complete after the implementation finishes. Keep reviewing teams and what they do to ensure that they’ve actually adopted your new WMS, not just figured out new ways to go back to old habits.

Legacy processes were replaced because they harmed your business. If the training doesn’t stick or people start using past practices, your WMS ROI is going to shrink down to zero. Enforce your new rules to keep all of the gains you could make with a new WMS.

WMS best practices/TL;DR: Take a deliberate approach

A WMS implementation might not be as straightforward as you'd like, simply because of all the moving parts and all of the stakeholders involved who deserve consideration, including the employees whose daily workflows might look a little different after the changeover. Avoiding these warehousing mistakes comes down to a handful of best practices:

  • Do your research and choose a system with the features you need and enough flexibility to fit your warehouse
  • Plan the implementation, and go live in your slow season
  • Get buy-in from leaders at every tier
  • Clean your data before you migrate it
  • Test thoroughly before go-live
  • Train your team and keep supporting them
  • Know how to reach your vendor when issues arise
  • Keep reviewing adoption so legacy processes don't creep back in

Planning, training, and accountability are the three biggest keys to successful WMS implementation. They ensure that you know where you’re going, have the right map, and know what to do when you arrive at your destination. Anything less leaves your business open to significant risk and loss.

author image
Geoff Whiting

About the author…

Geoff is an experienced journalist, writer, and business development consultant with a focus on enterprise technology, e-commerce, and supply chain development. Outside of the office he can be found toying with the latest in IoT, searching for classic radio broadcast recordings, and playing the perpetual tourist in his home of Washington D.C.

author image
Geoff Whiting

Featured white papers

Related articles