Technology in Supply Chain

Most warehouses I've talked to are running a WMS that was installed somewhere between 2004 and 2015, patched a hundred times, and is now held together by two people who know where all the bodies are buried. One of them is probably thinking about retiring. That's the real risk nobody puts in the budget meeting. The question of whether to migrate, modernize, or leave it alone doesn't have a universal answer, but it does have a right way to think about it. Start with what the sy

Customs delays rarely come out of nowhere. They come from the same handful of mistakes, made by different teams, on different shipments, over and over. Here's what's actually causing your freight to sit. Incorrect or incomplete commercial invoices are probably the single biggest culprit. A missing country of origin, a unit of measure that doesn't match the packing list, a description that says "parts" when the HS code says something more specific — any one of those can stop

Most compliance failures don't start with fraud or negligence. They start with drift — small process gaps that nobody fixed because the counts were close enough and shipments kept going out. Then an auditor walks in and starts asking questions you thought you'd answered years ago. Here's what tends to surface. Location records that don't match physical stock. This is the big one. If your WMS says 144 units of SKU 7823-B are in rack C-14 and the auditor counts 97, the conversa

Two picking philosophies run almost every warehouse on the planet, and the conversation about which one to use is usually muddier than it needs to be. Let me cut through it. Person-to-goods is what most of us grew up with. Picker walks the aisles, pulls from static rack locations, brings product to a pack station or drops it in a tote. Simple to set up, easy to train on, and the capital cost to start is basically shelving and a WMS license. If your SKU count is under a few th

External auditors walking your floor for the first time will find things your team stopped seeing years ago. A slot that's been miscounted since the racking was reconfigured. A handful of SKUs that live in two locations but only one of them made it into the WMS. A pallet of returns sitting in a grey zone between receiving and putaway that nobody claims. That's not a reflection of a bad team. That's just what accumulates in a working warehouse. Your job before the audit is to

Filing an insurance claim on lost or damaged stock is one of those things that feels straightforward until you're actually doing it at 11pm after a flood, a break-in, or a receiving error that somehow turned a full pallet of product into a line item nobody can trace. That's when you find out whether your records hold up. Most claims don't fail because the loss didn't happen. They fail because the documentation can't prove what was there before the loss occurred. An adjuster i

Three letters get thrown around in every automation conversation right now — AS/RS, AMR, AGV — and half the time the people saying them are using them interchangeably. They're not the same thing. Not even close. And if you're evaluating any kind of automation for your DC, mixing them up can point you toward a solution that doesn't fit your operation at all. An AS/RS (Automated Storage and Retrieval System) is a fixed infrastructure play. Think tall vertical carousels, shuttle

The agency called at 7pm. You've got three temps showing up at 6am and a cycle count starting at 7. There's no time for a three-day orientation. There never is. So here's what actually works when you need someone scanning and counting by mid-morning. Before they arrive, do the one thing most sites skip: pre-build their access. If your WMS or counting app requires a login, create it the night before. Sounds obvious. You'd be surprised how many floors lose 40 minutes per person

A lot of the nearshoring conversation happens in boardrooms and earnings calls, not in DCs. Cost of goods, freight rates, geopolitical risk — all real, all worth talking about. But I want to talk about what actually changes when your sourcing geography shifts, because it changes a lot more than your PO lead times. When you're running offshore supply, you get used to operating with deep safety stock. You order in big batches because ocean freight rewards volume. Your counts ma

A container goes overboard in the South China Sea. Or clears customs with a $40,000 duty bill nobody budgeted for. Or arrives at your dock damaged and nobody can agree whose insurance pays. In every one of those situations, the first question is the same: which Incoterm was on the purchase order? FOB — Free On Board — means the supplier's job ends when the goods are loaded onto the vessel at the origin port. From that moment, the risk is yours. You're paying freight, you're a

Your ERP says 144 units. Your WMS says 137. Your Shopify store sold 6 yesterday and the order hasn't hit your system yet. Which number do you pick when a customer calls asking if something is in stock? Most teams just... pick one and hope. That's not a process, that's a prayer. The fantasy of a "unified inventory view" sounds simple. One number, everywhere, always current. The reality is that your ERP was built to manage financial transactions, your WMS was built to move prod

Most warehouses think they're audit-ready until the auditor walks in and asks for a cycle count reconciliation report from Q2. Then the scrambling starts. The honest truth is that audit readiness isn't a thing you do in the two weeks before the date on the calendar. It's what happens every Tuesday at 6am when the second-shift count didn't get posted, or when someone adjusted a location without logging the reason, or when that one rack in the back corner hasn't been physically

Voice-picking gets oversold. Vendors love to lead with accuracy percentages and ROI calculators, and somewhere in the middle of the pitch you lose track of what the thing actually does on a Tuesday afternoon in a 40,000 sq ft ambient DC. So here's the short version, from someone who's watched pickers adapt to it in real time. The single biggest win is hands-free confirmation. When a picker is pulling from a rack at chest height and doesn't have to look down at a scanner or a

A lot of SMB warehouse managers hear "automation" and immediately picture a six-figure software rollout, a three-month implementation, and a consultant in a blazer explaining their own operation back to them. So they wait. They keep doing cycle counts on clipboards, reconciling spreadsheets at 9pm, and eating shrinkage they can't explain. The big investment never comes, and the small problems compound. Here's what I've seen work before anyone spends real money. Fix your count

Nobody tells you that the inventory you had perfectly dialed for one channel becomes a liability the moment you open a second. You go from shipping full pallets to one DC to picking singles for three different fulfillment paths, and suddenly the count accuracy you thought was fine — 98.2%, respectable — is no longer fine. A 1.8% error rate on bulk outbound is a rounding error. That same rate on ecom singles means real customers getting apology emails. The problem isn't the om

Warehouse labor shortage across the country are running counts, picks, and ships with crews that are 20-30% smaller than they were three years ago. That's not a projection. That's Tuesday. The Bureau of Labor Statistics has been tracking warehouse and storage turnover north of 40% annually for years now, and anyone who's tried to backfill a lead counter or an inventory analyst in the last eighteen months knows that number feels conservative. The causes stack up fast. An agi

Here is a scenario that plays out constantly: the ERP says you have 240 units of a SKU on hand. The WMS says 218. Someone just did a quick count in the aisle and came back with 203. Now three systems disagree, a customer order is on hold, and everyone is pointing at a different screen. This is not a technology failure. It's a clarity failure. These three systems are not interchangeable, and they were never meant to be. Your ERP — SAP, Oracle, NetSuite, whatever you're running

Inventory shrink is the polite word for it. A pallet comes in short, a bin count doesn't reconcile, a high-velocity SKU keeps showing phantom demand. The instinct is to blame the count process — bad scan, wrong location, somebody keyed it wrong. Sometimes that's true. But when the same dock door, the same shift window, or the same product family keeps showing up in your variance report, you're probably not looking at a process problem. Warehouse fraud tends to cluster. That's

Most warehouses track their returns rate. Fewer of them know if that number is actually bad. 8% sounds fine until you find out your product category benchmarks at 3%. 22% sounds alarming until you realize you're in apparel e-commerce, where that's Tuesday. So here's a rough cheat sheet. These are not magic targets — they're ballpark norms based on what the industry broadly reports, and your specific mix, channel, and customer base will move them. Use these as a starting poi

Automation in a warehouse doesn't have to mean robots and conveyor overhauls and a capital request that dies in committee. There's a quieter layer of it — the repetitive, brain-draining admin work that eats an hour here and two hours there — and most of it can be handled with software you could have running this quarter. Here's what I'd go after first. Cycle count scheduling. Most teams are still deciding manually which zones to count and when. A decent system will look a