Innovations in Inventory Management

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

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

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

Turn inventory data into smarter buying decisions Most wholesale distributors I talk to are running a version of the same system: a buyer who knows the catalog cold, a spreadsheet that gets exported every Monday, and a gut call on what to reorder. That works until it doesn't. And when it stops working, it usually stops working on your highest-volume items at the worst possible time — like going stockout on a $40 HVAC part in July because the seasonal bump came three weeks ear

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

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

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

Before changing tools, get your inventory data in order The spreadsheet isn't what breaks you. What breaks you is switching off it before you understand what it was actually doing for you — the workarounds someone built into column G, the color-coding that only Karen in receiving understands, the tab that nobody touches but everyone is afraid to delete. Rip that out without a plan and you don't get cleaner data. You get chaos with a better UI. So if you're feeling the ceiling

The goal isn’t the lowest stock. It’s the right stock There's a metric that gets chased in every DC I've ever worked in: inventory reduction. Leadership wants it down, finance wants it down, and whoever hits the lowest number gets the slide in the QBR. I get it. Carrying costs are real. But I've watched operations cut so deep they were air-freighting product at 9x the cost because a single supplier had a two-week delay. The savings evaporated fast. The goal isn't lowest. It's

Air moves faster. Sea costs less. The real question is when the time saved is worth the premium Everyone knows air freight is faster. Not everyone knows when it's actually worth it. The default for a lot of operations teams is to book air the moment something looks like it might be late — stockout risk, customer escalation, product launch breathing down your neck. That reflex is understandable. It is also how you quietly bleed margin all year without anyone putting a number t

The price on the shelf is built layer by layer — from raw materials and labour to logistics, margins, and taxes. Most people who work in warehouses know roughly what a product costs. They see the PO, they know the unit price, they've got a general sense of margin. But that number on the PO is not the price of the product. It's the starting point. By the time a unit is received, putaway, counted, picked, replenished, maybe miscounted and recounted, and finally shipped — it has

A full warehouse doesn’t always mean available inventory Your warehouse looks full. Pallets stacked, racks loaded, floor lanes choked with product. And yet someone just told you they can't fill an order because the item is showing zero on hand. Both things are true at the same time. That's the part that makes operators crazy. What's usually happening is a location problem, not a quantity problem. The units exist. They're just sitting somewhere the system doesn't expect them —

Inventory on paper tells a story. Your inventory report said 144 units. The floor had 11. If that's never happened to you, you haven't been doing this long enough. The system number and the physical number are two different things, and pretending they're the same is how you end up promising a customer a shipment you can't build. The system records what was supposed to happen — what got received, what got picked, what got transferred. The floor records what actually happened.

Most procurement slowdowns aren't a software problem. They're a data problem that starts on the warehouse floor and works its way up until someone in purchasing is ordering 200 units of something you already have 340 of, sitting in a back lane, miscounted three cycles ago. The sequence usually goes like this: counts are done on paper or clunky handheld devices, the numbers get manually keyed somewhere, someone fat-fingers a quantity, and the system of record is now quietly wr

Data says one thing, shelves say another. Refund numbers don't match Finance emails the warehouse asking why the refund credit from that outdoor furniture vendor is showing $4,200 on their end and $3,800 on yours. Someone schedules a call. The call turns into two calls. Meanwhile the vendor is waiting, and somebody's month-end is already wrong. This happens constantly in operations that handle vendor returns manually or across disconnected systems, and the root cause is almos