FEFO expiry management in food warehouses starts with a scene that stings. A batch of yoghurt arrived last Tuesday and expires next week. An identical batch arrived yesterday and expires the day after tomorrow. Under first in, first out, the older arrival ships first, and the batch that arrived yesterday sits in the rack waiting to expire. On paper, FIFO did nothing wrong. On the shelf, a whole batch walks toward the write-off bin. That is the first problem FEFO exists to solve: arrival order and expiry order are two different things, and they diverge all the time.

FEFO stands for first expired, first out. Picking follows the expiry date, not the receiving date. FIFO follows the receiving date. When the two orders agree, the methods produce the same result and either one will do. When they diverge, only one of them protects the customer. Think of it like the milk in your fridge at home: you reach for the carton that expires tomorrow, whichever carton got into the fridge first. A child understands the logic. Getting a warehouse to live by it means changing the system, the process and the performance review, and the difficulty is all in the execution.

Why FEFO Expiry Management in Food Warehouses Has to Be FEFO

Run the numbers first. The following is a hypothetical calculation: a food warehouse ships 10,000 cases a month with an expiry write-off rate of 3 percent, at 200 yuan per case, so the monthly write-off is 60,000 yuan and the annual write-off is 720,000 yuan. Three hundred cases a month are not stolen and not crushed. They sit in storage until the expiry date arrives. Is that money wasted? Yes, and what wastes it is not the expiry date itself, it is a pick rule that ignores expiry dates. Cut the write-off rate from 3 percent to 1 percent and the annual saving is 480,000 yuan. Once that number is on the table, the question of whether the FEFO system work is worth paying for answers itself.

Last summer, a night shift at a chilled food warehouse in East China ran straight into this trap. Two lots of the same chilled ready meal: one with 40 days of shelf life left, one with 6. The lot that arrived first had the longer life, and the lot that arrived later had the shorter one. The pickers followed the old habit, first in first out, and the 6-day lot sat behind the other one until it landed on the short-dated list, the customer refused it, and the whole lot was written off. The pickers were not at fault. They followed the rule. The rule was the problem, because it recognised receiving dates and ignored expiry dates. FEFO changes the rule, not the people.

There is a sneakier trap: if the expiry data is captured wrong, FEFO fails faster than FIFO. FIFO gets the order wrong, so the older stock ships late. FEFO gets the direction wrong, so the system confidently ships nearly expired stock to exactly the customer who should not receive it. A lot whose expiry was never captured at receiving, or a production date keyed in as an expiry date, poisons picking, alerting and recall in one move. So the first checkpoint of expiry management is not the pick face, it is the receiving dock: lot, expiry date, production date and location, four fields, none optional, and anything that cannot be scanned gets keyed in with a second-person check.

The System Setup: Four Fields First

Getting FEFO live comes down to four things in the system, and missing any one of them stalls the whole machine. Capture expiry at receiving, so lot and expiry travel with the goods from the moment they enter the building, on the pallet label and in the system. Manage stock by lot, so the same product in different lots is two records in the system, never merged into one total. Pick by expiry, so the task the system issues already names the earliest-expiring lot, and the picker does not decide and does not get to choose. Alert before expiry, in tiers, instead of sounding the alarm on the day the stock dies. That is what FEFO expiry management in food warehouses actually runs on: four fields, no exceptions.

For the alert tiers, a sample configuration is 90, 60 and 30 days. Ninety days is a heads-up, when purchasing and sales start working on a plan. Sixty days is action, when promotion, transfer to a faster-moving site, or return to supplier all run at once. Thirty days is the red line, when the stock is unlikely to move and the loss has to be accepted and cleared fast. The exact day counts are not a standard answer, and different categories and shelf lives need their own tuning, but the tiering itself is not optional. An alert with no tiers is someone remembering three days before expiry, when every option is already too late.

| Rule | Sorted by | Suits | Biggest trap | | First in, first out | Receiving date | Stock where expiry order always matches receiving order | Ships the wrong lot the moment expiry diverges | | First expired, first out | Expiry date | Chilled, frozen and dated ambient food | Wrong expiry data corrupts everything downstream |

To be blunt about it: not every product deserves FEFO. A shelf-stable seasoning with a 24-month life has receiving order and expiry order that practically overlap, so forcing FEFO onto it is a pseudo-requirement, money burned for peace of mind. Look at expiry spread first. If the expiry dates of different lots of the same product sit within a week of each other, FIFO is perfectly adequate. If they can spread a month or more, FEFO is worth the investment. It is like fitting a turbocharger to a bicycle: the spec sheet looks impressive, the ride feels exactly the same, and the money is gone.

Short-Dated Alerts and Recall: The Two Places FEFO Fails

Short-dated stock needs an exit plan 60 days before expiry, not a meeting three days before. Promotion, transfer to a site that moves faster, return to supplier, donation: each route has a cost, and deciding early is what keeps the bargaining power. With three days left, nobody takes the promotion, the transfer cannot make it in time, the return needs a process, and the only road left is the write-off. Short-dated management is won by the plan made two months early, not by the action taken on the last day.

Recall is the second test, and it is the one that shows whether expiry management is real or wallpaper. When a lot has a problem, can the system answer three questions at once: which location holds it, which customers received it, and how much is still in the building. Set the drill target at a full destination list within 2 hours. If the drill cannot hit that number, the lot fields were never really wired through, and FEFO is a policy on the wall. Run the drill at least once a year and review what jammed: a missing field, or a location that was never properly managed.

On compliance, one point needs stating plainly: no regulation names FEFO specifically. The food safety schemes that do set the bar, SQF Edition 9, BRCGS Issue 9 and FSSC 22000 Version 6, all require demonstrable stock rotation and traceability, and FEFO is the method most facilities use to meet those requirements. At the United States federal level, infant formula is the only product category where a date is regulated as a safety limit, and for other foods the dates are generally not a safety indicator and are not required by federal law, according to the relevant federal guidance on food product dating. Check the official source for the latest policy before acting, and read the expiry clauses in customer contracts before signing, because contract terms often bite harder than the regulation itself.

The system work, the scanners and the alert development all cost visible money. What they save is invisible: write-offs avoided, refusals avoided, customers kept. So is the money worth it? Look at one number: the expiry write-off rate. Divide one year of implementation cost by one year of avoided write-offs. A ratio below 1 means the money was well spent. A write-off rate that has not moved after three months means the fields were captured wrong or the rule never really ran, and the money was wasted. That is the whole test of FEFO expiry management in food warehouses: one ratio, one rate, no slogans. Numbers do not lie, and neither does FEFO.

By Da Liu, Automation Engineer