Why your WMS doesn't show you what you need

The thing nobody tells you about WMS

I spent twenty years buying, configuring, and replacing warehouse management systems. WMSes I bought and configured as an operator. Manhattan. SAP EWM. HighJump (now Körber). Tecsys. Made4net. Camelot. Datex. Every one of them was sold to me on visibility. Every one of them did what it said on the tin: it tracked inventory, generated wave plans, printed pick tickets, and posted ASNs.

And every single one of them left me unable to answer the questions that actually mattered at 4am on a peak Saturday morning.

I'd spend six figures and eighteen months on the implementation, and at the end I still didn't know which dock door was bleeding labour. I still didn't know which client was actually profitable. I still didn't know whether the photo of the damaged carton existed, and if it did, which inbox or shared drive it was rotting in.

That isn't a defect in any one WMS. It's a category problem. WMS systems were never built to give you operational visibility. They were built to do inventory and order management. Those are different jobs.

What a WMS actually does

A WMS does five things well. Receive. Put-away. Slot. Pick. Ship. Add a sixth if you have it — cycle count. Everything inside a WMS is in service of those six verbs, and the underlying data model is built around two nouns: the inventory record and the order.

So when you ask your WMS, "how many units of SKU 4471 do I have, and where are they?", it answers in milliseconds. That's the job.

When you ask it, "which dock door took the longest to clear yesterday, and was that because of the inbound product mix or the team on shift?", it stares at you blankly. Because dock-door labour cost is not a thing a WMS knows about. Your WMS knows the receiving transaction happened. It knows the timestamp. It does not know who was standing there, whether the lift truck was waiting for a battery change, whether the inbound paperwork was missing for thirty minutes, or whether the trailer was loaded by an idiot.

The data exists somewhere — in your timekeeping system, in your TMS, in the head of your dock supervisor, in the photos on someone's phone — but it isn't joined together, and the WMS is not the place to join it. The WMS was built when "visibility" meant "I know where my inventory is." That is necessary. It is not sufficient.

Four questions your WMS can't answer

I keep a list. When operators tell me their WMS gives them everything they need, I run the list:

1. Which dock door is bleeding labour? Not which one is busiest. Which one is costing you the most labour-hour per inbound pallet, week over week. Your WMS knows the pallets came in. It does not know what they cost you.
2. Which slots are working and which are dead weight? Your WMS reports pick frequency in a table. Useful, but useless. You need to look at a layout of your floor with hot zones red and dead zones grey and see, in one glance, that the SKU your top client added last quarter is being walked past by every picker because it landed in the wrong aisle. The WMS report won't get you there. Months of trying haven't.
3. Where is the proof of delivery for that carton your client says never arrived? You know it was shipped. The WMS says it was shipped. The carrier scan says it was delivered. The client says it wasn't. Somewhere in your operation a driver took a photo with their phone. Where is that photo right now? The WMS doesn't know. It isn't the WMS's job.
4. What does the QBR for your biggest client look like, and is it good enough to win the renewal? Your WMS has thousands of data points about that client's volume. None of them are arranged into the story their procurement team is going to ask you for. The night before the QBR, somebody on your team is opening Excel.

If you can't answer those four questions in sixty seconds with the system you already paid for, you don't have a WMS problem. You have a visibility problem. And the visibility problem won't be fixed by buying more WMS.

Why operators buy more WMS anyway

They buy more WMS because every vendor who calls them in February has a slide that says "Complete operational visibility." The slide has a screenshot of a dashboard. The dashboard has bars on it. The bars suggest answers.

Then you buy the system, run the implementation, train the team, and one of two things happens. Either the dashboards are technically there but nobody in your operation opens them, because the data joining is so brittle that the numbers don't match what people see on the floor — or the dashboards aren't actually there and the slide was talking about a future module that is on the roadmap but isn't shipping until Q3 of next year.

I have lived both versions. I have also been the person across the table being sold the slide, and I have signed the cheque. So I am not throwing stones. I am telling you what I learned: the visibility you need is not a feature of your WMS. It's a separate category of tool. And until you start thinking of it that way, you will keep buying WMS upgrades and keep being disappointed.

Buying more WMS to fix a visibility problem is like buying a bigger engine to fix a windscreen wiper. The engine was never the problem. You couldn't see out of the windscreen.

What sits on top of the WMS

Visibility is a separate layer. It feeds off your WMS — pick history, order data, inventory positions — but it is built to answer different questions, and it has a different unit of measurement. The WMS measures the transaction. The visibility layer measures the operation.

At Warehouse Bridge we've organised this into five steps. I won't run through all of them here — the full method lives at the 3PL Operating System — but here's the shape of it:

• See It. Capture every dock photo, every BOL, every POD, every quality hold, in one searchable place that joins back to your WMS by carton or shipment ID. That's DockSnap. It is not a WMS feature. It is a tool that fixes the "where is that proof of delivery" failure mode.
• Map It. Lay your operation out spatially and see, in one image, which slots earn and which slots sleep. That's Warehouse Heatmap. It reads your WMS pick history and produces something the WMS will never produce on its own: a picture of your floor.
• Score It. Per-client operational scorecards that consume WMS data, DockSnap evidence, and Heatmap insights, and produce the QBR your client is asking for, automatically. That's Client Scorecard. The night-before-QBR Excel marathon stops.
• Light It. Put the answer at the point of action, with industrial-grade pick-to-light and put walls. Visibility becomes muscle memory in the aisle.
• Oversubscribe. Once you can see what's happening, you can price what it costs you, and you can stop discounting to win clients you can't afford to keep.

None of those steps require you to replace your WMS. They sit on top of it. They fix the questions the WMS was never built to answer.

What I'd do if I were running your operation tomorrow

If I were sitting in your seat tomorrow morning, the first thing I would do is take the 3PL Operating Scorecard. It's eight questions, sixty seconds, and it tells you which of the five dimensions — visibility, space, labour, client confidence, capacity discipline — is bleeding the worst right now.

That's the dimension where the WMS isn't showing you what you need. Start there. Don't start by upgrading the WMS. Start by adding the one named tool that closes the gap the WMS was never built to close.

If you remember nothing else from this note, remember this: your WMS is doing its job. Stop asking it to do a job it was never designed for. Buy the visibility tool that fits the question the WMS can't answer. You'll save eighteen months of implementation and six figures of fees, and at the end of the quarter you'll be able to answer the four questions that actually matter at 4am on a peak Saturday morning.

That's the deal we made with ourselves when we built Warehouse Bridge. It's the deal we make with every operator who works with us.

— Chuck