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

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

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

Demand tells you what customers want—and when they want it When the waiter promises something the kitchen can't deliver, the customer leaves angry and doesn't come back. That's not a hospitality metaphor. That's a warehouse Tuesday. Demand is fast, loud, and confident. It takes orders without checking with anyone. Supply is slower — it's physical, it lives on pallets and in slots, it has lead times and receiving windows and cycle count schedules. The problem is that most oper

More orders. More pressure. More room for fulfillment errors Fast growth in D2C is exciting right up until you realize your inventory numbers are fiction. Not malicious fiction — just slow drift. A unit miscounted here, a return not logged there, a bundle kit partially picked and shelved wrong. When you're shipping 50 orders a day out of a garage, you feel the discrepancy instantly. When you're shipping 800 orders a day out of a 3PL with two shifts, the drift is invisible unt

Not every SKU needs the same counting frequency A facility I heard about last year dropped six figures on new reach trucks and a conveyor upgrade. Pick rates went up 30%. Fulfillment errors went up too. Turns out they'd been running on cycle count data that hadn't been fully reconciled in months, and the faster they moved, the faster they shipped the wrong thing to the wrong place. Better equipment is worth every penny — when the stock it's moving is where the system says it

Cycle counting means checking stock continuously—not once a year Most warehouses pick a counting method early on and never revisit it. The operation grows, SKU count doubles, and they're still running the same full physical they ran when they had a single dock door and twelve employees. That mismatch is where shrink hides. A full physical count stops the building. Everything freezes — receiving, shipping, picks — while your team walks every slot and reconciles every discrepan

Moved physically. Never moved in the system Your system says you have 48 units of a SKU. Your picker walks to the slot and finds 11. Or a empty bay. Or someone else's product shoved in there from a messy put-away two weeks ago. The order is late, the customer is calling, and your inventory accuracy report from last Tuesday still says 98.6%. That number is the problem. Not because it's lying exactly, but because it's a snapshot of what your last count found, not a reflection o

Know what you have, where it is, and when it moves Bad stock numbers don't come from laziness. They come from clipboards, spreadsheets that are three days out of date, and count sheets that someone filled in from memory because the scanner died in aisle 9. The gap between what your system says you have and what's actually on the rack is where shrink hides, where stockouts happen, and where your team loses an hour every Tuesday morning reconciling numbers that should never hav

Your KPI isn’t wrong. It’s missing context 98.7% cycle count accuracy. Looks great in the Monday meeting. Nobody asks follow-up questions, the slide moves on, and everyone feels good about the operation. Then a 3PL customer calls because their pick list showed 200 units of a SKU you physically cannot find, and suddenly that number means nothing. The accuracy figure was real. The counts were done, the math checked out. What it didn't tell you was that the 1.3% variance was con

One portal. Clear billing. Measurable SLA performance Most 3PL portals are glorified spreadsheet dumps. You log in, you see a table of SKUs and quantities, and you leave knowing roughly what you knew before. That's not a portal. That's a file with a password. If you're building one or evaluating one, here's the standard that actually matters to the people on the other end of it — your clients. On the inventory side, real-time on-hand is table stakes. What clients actually nee

Inventory isn’t just stock. It’s cash sitting on your shelves A distribution center I heard about last year was sitting on 11 weeks of a particular SKU because their cycle counts kept coming back clean. Clean on paper. In reality, a slotting change six months earlier had split the product across two locations, and nobody had reconciled it. Eleven weeks of carrying cost, tied up in units they thought they needed to reorder. They didn't. This is the part that doesn't show up in

Peak demand can expose every weakness in fulfilment Most online retailers know exactly when peak season is coming. They've seen the calendar. They've read the forecasts. And they still get buried. Every year. The reason isn't that volume is unpredictable — it's that high volume exposes everything that was already quietly broken. Here's what that looks like in practice. You're running a 40,000 sq ft DC. Normal throughput is manageable, errors are tolerable, and you've got a rh