Let me be straight with you: in a food warehouse, the thing that scares us is not volume. It is expiry dates.

One Monday morning last summer, I walked into the warehouse and our quality inspector was waiting at the door. A batch of yogurt had 12 days of shelf life left, but the system said 20. We dug into it and found the problem at receiving: the batch had been logged wrong, the older stock got buried behind the newer stock, and the newer stock shipped first. By the time anyone noticed, that yogurt had under two weeks left and the customer refused it outright. The whole batch was written off. Tens of thousands of yuan, gone.

After that, our warehouse made a rule: in food warehousing, first-in-first-out is not enough. You have to ship by expiry date. That is FEFO — first expired, first out. Sounds simple. The details are where it lives or dies.

How first-in-first-out goes wrong

First-in-first-out manages receiving order. Expiry management manages shelf life. Those two orders are often different.

Take one example. Same brand of biscuits. Batch A arrived March 1, expires September 1. Batch B arrived March 10, expires August 15. First-in-first-out says ship batch A first. Wrong. Batch B expires first, so batch B should ship first. Ship by receiving order and batch B can expire on the shelf.

That is exactly how we used to work. The system queued by receiving time, pickers followed the list, and nobody looked at expiry dates. Stock with the nearest expiry sat at the back, and by the time we dug it out, it was too late.

After switching to FEFO, the system sorts by expiry date, and the pick list prints the batch and expiry right on it. Pickers do not have to think. They follow the list. Simple — except the whole thing jams up at receiving if you get that step wrong.

Receiving is where you cannot afford a mistake

Folks, half of expiry management in a food warehouse happens at receiving.

Here is our receiving process now. The moment freight arrives, we check the expiry date, then log the batch. Stock with under 30 days left gets a red tag, goes into a separate zone, and ships first. Stock with 30 to 90 days gets a yellow tag — normal flow, but the system watches it. Over 90 days, green tag, normal flow.

It looks tedious. It saves real money. We used to deal with one or two near-expiry batches every month — discounting, promotions, returns to the supplier, and we still lost money on the round trip. Now near-expiry stock gets flagged 60 days ahead, sales finds a channel to move it early, and almost nothing gets squeezed into the last two weeks.

One more detail: one batch, one location. We used to put the same batch wherever there was space, which meant one batch in three locations at count time. Now one batch gets one location, and a cycle count takes half an hour.

How far ahead should the expiry warning go?

We tested the warning window several times. Thirty days ahead was too late — sales could not move the stock in time. Ninety days was too early — the screen was full of warnings and nobody took any of them seriously.

We settled on two levels. Under 60 days to expiry: red alert, counted weekly, and sales reports a clearance plan every week. Sixty to 120 days: yellow notice, reviewed monthly. We have run this rhythm for almost a year now, and near-expiry write-offs have basically dropped to zero.

There is one more move, agreed with customers in advance: for stock with under 45 days left, we call the customer before shipping and only send it if they confirm they can sell through it. Otherwise the customer refuses it on arrival, and we pay freight both ways.

When stock is already near expiry, how do you move it?

A warning is one thing. Moving the stock is another. Near-expiry freight does not walk out on its own — somebody has to find a way.

We clear near-expiry stock with three moves, in order. First, internal transfer: one store cannot sell it, another store may be short of it. Check the stock distribution in the system, raise a transfer order, and it is gone. Cleanest move, no money lost — but it has to be fast, because the closer to expiry, the harder the transfer.

Second, promotion. For stock with 30 to 60 days left, tell sales early and run a buy-one-get-one or a price cut, and stores will take it. The key is not to wait until the last week — a discount in the final week will not sell through either.

Third, return to the supplier. Some contracts include a near-expiry return clause — stock under 60 days can go back. But it costs you: return freight, the supplier relationship, and bargaining room next time. We only use this one when the stock genuinely will not move.

Last winter we had a batch of imported biscuits with 50 days left, and the quantity was not small. Sales transferred half to another store, then ran a buy-one-get-one on the rest, and it cleared in two weeks. Not a cent written off. In the old days that batch would almost certainly have been discounted and still cost us freight.

What our warehouse does now, as a fixed routine — everything we kept after stepping on the rakes:

First, receiving always verifies expiry and logs the batch; stock under 30 days goes to a separate zone and ships first. Second, picking follows expiry order, not receiving order, and the pick list prints batch and expiry. Third, expiry warnings run on two levels — weekly counts under 60 days, monthly review at 60 to 120 days. Fourth, stock under 45 days gets customer confirmation before it ships. Fifth, one batch, one location, so counts never mean tearing the warehouse apart.

In food warehousing, expiry dates are money. Control the dates and stock stays sellable. Lose control and everything you earned goes to write-offs.

One reminder for fellow operators: do not wait for an incident to fix the process. That yogurt batch cost us tens of thousands. Take the lesson for free.

By Chen Feng, Warehouse Operations Manager