Let me start with something embarrassing: the first time our little warehouse got burned by expiry dates, nothing had actually expired yet. The short-dated stock was buried at the back of the rack, and by the time we dug it out, it had less than a month of shelf life left. The customer refused it outright. It was only a few hundred cases of imported biscuits, but after we cleared them at a discount, the loss covered several months of rent. That day I learned something: first-in-first-out manages the order goods arrived in, but expiry management manages the life of the goods. This is how a small warehouse like ours got a warehouse FEFO expiry management system working in real life, without spending big money, using nothing but homegrown workarounds.
FIFO Manages Sequence. FEFO Manages Shelf Life
FIFO is simple: whatever came in first goes out first. But in a food or pharma warehouse, the batch that arrived first is not always the one that expires first. One batch arrived last month with a year of shelf life left; another arrived this week with only three months left. Under FIFO, the long-dated batch ships first while the short-dated one sleeps in its slot. By the time it wakes up, it has days left and nobody dares pick it. That is not lazy staff. The rule itself never cared about expiry dates.
FEFO flips the picking order: first expired, first out. It sounds like one sentence, but making it real means changing three things: the system has to know every batch's expiry date, the slots have to be arranged by expiry, and picking has to follow expiry. If any one of those breaks, FEFO is just a slogan on the wall. Our first attempt only changed the picking rule and never fixed receiving, so the system had no expiry field at all and pickers had to rely on memory. They picked wrong more often than right. The lesson is blunt: FEFO is not the picker's job. It is the system's job. That is the whole point of a warehouse FEFO expiry management system: the rule lives in the data, not in anyone's memory.
Three System Changes That Make FEFO Real
The first change is how expiry dates get recorded. At receiving, every batch needs a production date and an expiry date, and the receipt does not post if either is missing. Our method is crude: the receiver scans the production-date barcode with a handheld scanner, the system calculates the expiry date, and a person checks it once. Suppliers write dates in every format imaginable, some with day-month-year, some with month-year only. We standardize month-year dates to the last day of that month, deliberately conservative, never generous by a single day. Get one expiry date wrong and everything downstream is wrong, so we would rather be slow here than fast.
The second change is slot allocation and picking strategy. Short-dated stock goes in the easy-to-reach slots; long-dated stock goes deeper in. We added an expiry band to our location codes: near-expiry stock sits on the low, golden levels, long-dated stock goes up high. When the system assigns picking tasks, it sorts by expiry date first and then by nearest location. The veterans grumbled at first about walking a few extra steps, but those extra steps bought us something priceless: we have never again dug out stock with one month left. Picking has one hard rule too. When the same product has several expiry batches, the system only releases the earliest-expiring batch. Pickers do not get to choose. Take away the choice and most of the mistakes disappear with it.
The third change is the near-expiry warning threshold. Expiry is not something you alarm on when it arrives; you alarm on it while there is still time. We set two levels: for food, a yellow warning when a third of shelf life remains and a red alert at roughly one month left; for pharma, the thresholds are tighter. Once a warning fires, the response is fixed: first ask the customer if the stock can ship early, then talk about promotion or transfer, and only then write it off. There is no universal answer for thresholds. Every warehouse sets them by its own turnover speed, and once set, they go into the system, not into someone's head. Food and pharma warehouses have compliance floors to respect, and for the exact regulatory wording, check the official source for the latest policy rather than trusting anyone's memory of a clause number. A misremembered number is worse than no number at all.
The Hard Part: Getting Anyone to Act on the Warning
The hardest part of warnings is not setting the threshold. It is that nobody acts when the alarm goes off. Our warehouse has only a handful of people, and when warnings pile up, everyone goes numb. Red and yellow lights blazing together mean nothing at all. So we changed the routine: every morning meeting looks at one single sheet listing everything expiring within the next month, sorted by value, biggest first, and the top few items get an owner on the spot. A thin sheet makes the job clear. We also use another homegrown trick: near-expiry stock gets its own virtual location, visible on the books and impossible to miss during stock counts. It sounds small, but once short-dated stock blends into a big location, nobody on earth can find it.
A friend who runs a pharma warehouse told me a second story. His warehouse received a batch of medicine with barely half a year of shelf life left. Nobody noticed at receiving, the expiry field in the system stayed blank, and months later when a customer ordered, everything picked was nearly expired. The whole batch had to go back to the supplier and be re-shipped. The freight and labor for the round trip cost more than the margin on the goods themselves. His lesson is the same as ours: expiry problems never start on the day of shipment. They start on the day of receiving, when nobody treated the date as important.
Doing the Math: Is This Homegrown Setup Worth It?
Here is a hypothetical example. Take a small food warehouse of a few thousand square feet moving a few thousand cases a month. In our experience, before FEFO, write-offs and discount clearances caused by expiry problems ran to a few percent of goods value each year. After FEFO, most of that write-off money is saved. The cost is a few extra minutes recording dates at receiving and a few extra steps while picking. Run the numbers and the savings outweigh the effort by a wide margin. More important, no customer has refused a delivery over shelf life since. That trust does not show up on a calculator. I will not give you a precise payback figure, because every warehouse has different goods value and turnover. Plug in your own numbers with this same method and you will have the answer in half an hour.
Of course FEFO has a cost. The most direct one is that expiry-first picking breaks up the picking path. One order might send a picker to two zones, and efficiency dips a little. A small warehouse with modest picking volume can absorb that. A big warehouse copying this blindly should first calculate whether the extra walking is worth it. There is also a counterintuitive judgment worth stating plainly: the stricter your expiry management, the more willing you must be to admit some stock simply will not sell. Discount it early or transfer it early, which beats writing it off after it expires. Plenty of small warehouse owners refuse to discount, and in the end the write-off costs more than the discount would have. I have run that math, and it is real.
Small warehouses have their own way of surviving. We could not afford the big-brand expiry management software, so we ran FEFO with a barcode scanner, two spreadsheets, and a morning meeting. That is what a warehouse FEFO expiry management system looks like at our size, and it works because the discipline is in the routine, not in the price tag. Expiry management is not a contest of how expensive your system is. It comes down to whether someone carefully records the date on the day the goods arrive. Is there a batch sitting in the back of your warehouse right now with a month of shelf life left? If so, go dig it out today, before it becomes a number on a write-off form.
By Xiao Ma, Small Warehouse Owner







