People ask me what they are actually paying for when they bring in a warehouse consultant. Fair question. A lot of consulting looks like a slide deck and a list of software to buy.

The useful part happens on your floor, in the first two days, before anyone opens a laptop to write recommendations. If a consultant shows up with the answer already in hand, you are about to get a sales pitch.

Here is how I spend those two days, and what you should expect to get back.

Day one, morning: walk the flow before talking to anyone

I start at the receiving door and walk the building in the order product moves. Dock, staging, putaway, storage, pick, pack, ship. Then returns, because returns are usually where the bodies are buried.

I am not asking questions yet. I am looking for things like:

  • Pallets sitting in staging with no paperwork on them
  • Aisles that people walk around instead of through
  • Handwritten labels taped over printed ones
  • A desk in the corner covered in sticky notes (there is always one)
  • Product stored on the floor because the racks are full of something nobody has touched in a year

Every one of those is a symptom with a cause behind it. The walk tells me where to dig.

Day one, afternoon: follow real orders

Next I pick three to five orders from that day's queue and follow each one from the moment it drops to the moment it leaves the dock. Not a demo order. Real ones, picked by the people who normally pick them.

I want to see how the picker finds out the order exists. Is it a printed sheet, a screen, someone yelling across the building? How do they know where to go? What happens when the bin is empty?

That last question matters most. The happy path in most warehouses works fine. The exceptions are where the time goes, and where the inventory numbers start drifting.

What I write down while following an order

  • Every handoff between people
  • Every time someone walks back to a desk or a printer
  • Every time they check a second location because the first was wrong
  • Every piece of paper that gets created and where it ends up

A single order with four handoffs and two trips to the printer tells me more than any process document you could send me.

Day two, morning: time things

Opinions about where time goes are almost always wrong. So I time it.

I use a stopwatch and a clipboard. Nothing fancy. I time a sample of receipts, a sample of picks, and the pack and ship step. I break each one into pieces: travel, search, handling, paperwork, waiting.

In most small warehouses I visit, travel and search eat 50 to 60 percent of picking time. Owners usually guess it is closer to 20. That gap is the whole conversation.

Why timing beats interviews

Interviews tell you what people think happens. Timing tells you what does happen. When a supervisor says receiving takes "maybe 20 minutes a truck" and I watch it take 75, that is not a lie. It is just the version they remember.

You can do this part yourself, by the way. Pick a slow Tuesday, grab a stopwatch, and time ten picks. You will learn something.

Day two, afternoon: talk to the floor

I talk to the people who do the work last, after I have seen it. That way I can ask about specific things I watched instead of asking open-ended questions that get open-ended answers.

I ask pickers, receivers, and the person who handles returns. I ask the same few questions:

  1. What is the most annoying part of your day?
  2. Where do you go when the system is wrong?
  3. What do you do that nobody told you to do?
  4. If you ran this place for a week, what would you change first?

The third question is the gold. Every warehouse runs on workarounds that live in one person's head. The receiver who knows that a certain vendor always ships short. The picker who keeps a private list of where things really are. If that person quits, the warehouse gets noticeably worse the next week.

I also talk to whoever owns the inventory numbers in the office, usually someone in accounting. Their version of the warehouse and the floor's version rarely match.

What you should get back

Two days on site should produce a written report you could hand to a new operations manager and have them understand the building. If it is mostly opinions about software, ask for your money back.

At minimum, you should get:

  • A current state process map, drawn from what was observed, not from the procedures binder
  • Timing data with the method explained, so you can repeat it in six months
  • A ranked list of problems, with a rough cost or time impact on each one
  • The workarounds that live in people's heads, written down
  • A short list of fixes you can make this month without buying anything

That last item matters. In my experience, more than half of the problems I find in the first two days are fixable with layout changes, labeling, a cycle count program, or a rule about who touches what. None of those need a purchase order.

What should make you suspicious

A few red flags I would watch for if I were hiring someone like me:

  • They recommend a specific software product before day two is over
  • The report has no numbers in it
  • They never talked to anyone on the floor
  • The findings would apply to any warehouse in the country

If the report could have been written without visiting, it probably was.

It depends on the building

Two days is right for a single building with one or two shifts and under 50 people. A multi-site operation or a 24/7 facility needs more, and the night shift deserves its own walk because it almost never runs the same way days do.

But the shape stays the same. Walk it, follow real work, time it, and then listen. The recommendations come after that, and they should be specific enough that you can argue with them.