Shelf Life Management for Manufacturers

Most writing about shelf life management is written for shops. Watch the dates, discount what is about to turn, do not let it sit. Sound advice if the product arrives finished and leaves finished.

Manufacturing is a harder version of the problem, because the life is already partly spent when the ingredient arrives and you are about to spend more of it.

Four hands, one clock

A jar of cream with an eighteen month life does not get eighteen months anywhere. That period is divided, usually without anybody dividing it deliberately:

• The supplier holds the raw material for a while before it ships. You inherit whatever is left.
• The material sits in your store until a batch needs it.
• The finished goods wait for orders.
• The customer needs enough life left to sell it.

Each hand is optimising its own step. Nobody owns the total, which is why the shortage shows up at the end, as a delivery rejected for being too close to its date.

The number that actually matters

Expiry dates invite a yes or no question: is this expired. That is the wrong question almost every time you ask it, because the answer is nearly always no right up until it is catastrophically yes.

The useful number is remaining life at the moment of the decision, and the decision changes what counts as enough. A lot with six weeks left is fine to use in a batch shipping next week, marginal for a customer who stocks quarterly, and unusable for one whose supply terms require most of the life to be ahead of them on arrival.

Trade customers set those minimums in their terms, which is the part that surprises people the first time a pallet comes back. Being inside the expiry date is not the standard. It never was.

Where the life actually leaks

Three places, roughly in order of how much they cost.

Picking the wrong lot. Two pallets of the same product are not interchangeable when one expires in three weeks and the other in eleven months, and the one that arrived later is often the one at risk, because the supplier had held it longer. If rotation is a habit rather than a rule, the fresh pallet ships and the old one quietly becomes a write-off. FIFO and FEFO is the difference between the two.

Finding out too late. A warning that arrives after your options have closed is not a warning, it is a loss notification. Whatever you use to flag ageing stock, the lead time has to be long enough to run the slowest thing you might do about it. Lot and expiry tracking covers how the threshold is set.

Spending good life on the wrong order. The subtler one. Allocating your freshest stock to the customer with the loosest requirements, then having nothing left with enough life for the one who actually enforces a minimum.

What a system can and cannot decide

Rotation is mechanical and belongs to software. When a product has dated lots, allocation should pick the soonest-to-expire one without anybody remembering to, and stock past its date should be refused rather than flagged. That removes the largest and dullest source of waste.

What stays yours is every judgment about remaining life. Whether six weeks is enough for this customer, whether a short-dated lot should go into a batch or be discounted, whether to take the write-off now rather than ship something that will be rejected. IEMSuite does not make those calls and does not pretend to: a lot expiring tomorrow is not blocked, because one day of remaining life is a commercial question, not a system one.

It is also worth being clear that the shelf life of something you made is your determination, not an arithmetic result the software hands you. The system holds the dates you give it and rotates on them.

A short discipline

Record an expiry on every perishable receipt, because one blank line sends that lot behind every dated one. Set alert thresholds from your slowest response. Know the remaining-life minimum for each trade customer before you allocate rather than after they reject the pallet. And when a lot looks wrong, hold it instead of shipping it and hoping, which is the same discipline a recall runs on, with less time pressure. The records behind both are the same ones traceability software exists to keep.

Questions people ask