All Posts

When departments stop sharing information, financial blind spots appear Most fraud doesn’t beat your controls. It walks through the gap between teams who each assumed someone else had checked. A supplier’s accounts team emails yours on a Thursday afternoon. They’ve changed banks, the new details are attached on headed paper, and could the next payment go to the new account, please. It’s polite, it’s plausible, and it’s sitting in an inbox purchasing can’t see. Accounts payabl

Every supply chain tool needs one thing: reliable data Forecasting, planning, order promising and robots all read the same stock number. If it’s wrong, every one of them gets it wrong faster. The dashboard says 40 on hand. The control tower is green. A picker’s standing at the location looking at an empty slot, and those 40 have already been promised to customers. Nobody bought a bad tool. Every system involved did what it was told. They all read the same number, and the numb

Everyone needs the stock number. One person counts it The buyer needs the number to place the order. The planner needs the number to build the forecast. The warehouse manager needs the number to hit the fill rate. The 3PL customer needs the number by end of day. And somewhere in the back, one person is walking the rack with a scanner, trying not to lose count because someone started talking to them in aisle 7. This is the quiet dysfunction of inventory counting. It's a cross-

Pick faster by making the right item easier to find Speed and accuracy feel like opposites on the pick floor, but they're usually failing for the same root cause: the picker is making too many small decisions in real time. Which slot? Which UPC? Is this the right qty? Every micro-decision is a chance to get it wrong, and when you're running 400 lines before noon, those chances add up fast. The operations that close that gap tend to do a few things differently. They keep their

The right reorder point gives replenishment time to arrive Most warehouses I've seen reorder one of two ways: someone notices the shelf is getting thin and fires off a PO, or they run out completely and spend a Tuesday morning calling three suppliers to find out who can ship today. Neither of those is a system. Both of them are exhausting. Here's the thing about your fuel light. It doesn't come on when you're on empty. It comes on when you have roughly 50 miles left — enough

Inventory inherits every shortcut the warehouse takes I've never met a lazy inventory team. Not once. What I have met, over and over, is inventory teams running on bad tools and worse timing, expected to produce accurate numbers in conditions that almost guarantee they won't. Here's the thing people outside the warehouse don't get: the count never happens in isolation. The dock is receiving while the pickers are still pulling from the same locations you're trying to freeze. S

99% at every step. Why only 93% at the end? A warehouse running 99% accuracy at receiving, putaway, picking, and packing sounds pretty tight. Four steps, four nines. But if you actually multiply those out — 0.99 × 0.99 × 0.99 × 0.99 — you land at 96%. Add a fifth step like a transfer or a label scan and you're in the low 90s. That's not a disaster scenario. That's a normal operation with no single obvious failure point, bleeding out slowly across every shift. This is why 'our

Demand rises overnight. Fulfilment capacity doesn't Most companies have a plan for selling more. Almost none of them have a plan for counting more. And that gap is exactly where things fall apart. Here's what actually happens. Demand jumps — a big retail promo, a seasonal surge, a contract you weren't quite ready for. The warehouse goes from moving 800 lines a day to 1,400. Pickers are moving faster, receiving is stacking pallets in the wrong lanes because the right ones are

Robotic forks thrive where routes and tasks are predictable A robotic forklift will not save you if your receiving dock runs four lanes wide with irregular pallet drops, mixed load heights, and a dock crew that never quite parks the trailer the same way twice. That environment is chaos by design, and chaos is exactly what autonomous lift equipment struggles with. I've seen facilities drop six figures on AMRs that ended up parked in a corner within eight months because nobody

Five units miscounted. Two hundred units overbought Five units. That's the gap between what was physically on the shelf and what the system said was there. Not 500. Not a whole pallet gone sideways. Five. And somehow that five-unit discrepancy triggered a purchase order for 200 more. Here's how it usually goes. Somebody counts a fast-moving SKU — batteries, say, or a generic poly bag that goes on every kit — and they're off by five. Could be a double-scan, could be a box tuck

The bottleneck is where work starts waiting Most warehouse managers I've talked to think they already know where their bottleneck is. It's pick. It's pack. It's the dock doors at shift change. But when you actually map where orders are sitting — not moving, just sitting — the answer is almost never where the noise is loudest. Start with dwell time, not throughput. Pull your order timestamps and find where the gap between "arrived at this stage" and "left this stage" is widest

Find the source of the error before correcting the number Most inventory errors aren't counting problems. They're process problems that counting eventually exposes. Think about where discrepancies actually come from in a real operation. A pallet gets moved without a transfer being logged. A kit gets partially picked and the remainder gets shoved back on the shelf in the wrong slot. A barcode is damaged and the scanner misreads it, or the counter skips it entirely because they

10 calculations every supply chain planner should know Most planners learned these numbers the hard way — standing at a dock door explaining to a buyer why their replenishment didn't land in time. Nobody hands you a cheat sheet on day one. You pick it up in pieces, usually after a miss. So here's the list, written the way I wish someone had handed it to me. Days of Supply: on-hand inventory divided by average daily demand. Simple, but I've seen teams carry 90 days of a slow-m

The closest warehouse isn't always the best choice Most systems will give you an answer when an order drops. Nearest warehouse. Most stock. First available. Sounds simple. But anyone who has run fulfilment across more than one DC knows that the automatic answer and the right answer are not always the same thing. Take a scenario that comes up more than people admit: you have two locations that can both fulfil a customer order. One has full stock, one has to split across two pa

Faster fulfilment starts with finding the right product quickly Most fulfilment bottlenecks don't live at the dock or the pack station. They live earlier, in the gap between what the picklist says and what's actually sitting in the slot. A picker gets sent to lane C-14 for a qty of 6. There are 4. Now they're hunting, radioing, waiting — and the order behind them is already late. The frustrating part is that gap usually comes from count data that's days or weeks old. Cycle co

Everyone has the evidence. Nobody has the same answer Ask the warehouse team how many units of SKU 4471 are on hand and they'll tell you 144. Ask the replenishment planner and she'll say 112. Pull the ERP and it shows 158. Nobody is lying. Nobody keyed anything in wrong on purpose. They're just working from counts that happened at different times, in different ways, with different people running the scan guns. And now three groups are making real decisions off three different

A full warehouse doesn't guarantee a healthy bank balance A distributor I know was convinced they had a cash problem. Payables piling up, line of credit getting thin, the usual pressure. What they actually had was $340,000 in finished goods sitting in three different rack locations that their WMS thought was either sold or not yet received. Real product, real value, invisible to finance. This happens more than people want to admit. The balance sheet says you're inventory-rich

Trust the count, not the noise Your system says 144 units on hand. Your count says 117. Someone made a decision last quarter based on that 144, and now you're short on a Tuesday afternoon with a truck at the dock. This happens more than anyone wants to admit, and the usual response is to argue about the count rather than fix what's causing the noise. The noise is the problem. Cycle counts done on clipboards that get transcribed later. Scanner guns that drop connections mid-ai

Counted right. Stored wrong. Still lost You ran the count. Numbers matched. Everyone went home feeling good about it. Then someone spent forty minutes Tuesday morning tearing apart rack D-7 looking for 36 units of a SKU that the system said was there — because it was there, once, before someone putaway a replenishment pallet in D-9 and keyed it as D-7 without catching it. The count was right. The location was wrong. The inventory was, for every practical purpose, lost. This i