Shelf Life Management ERP Rules That Stop Write Offs

Every business with perishable stock records expiry dates. Far fewer manage them. The gap between those two shows up in the write off line.

Recording a date is data capture. Managing shelf life is a set of rules that have to act when stock is allocated, picked and despatched. That is where most setups turn out to be thinner than anyone assumed.

Shelf life management in ERP starts at allocation

The first rule is that the system decides which lot goes out, not the picker.

Leave it to a person and the nearest pallet wins. That is not carelessness. It is efficiency under time pressure. The result is that short dated stock drifts to the back of the warehouse and shows up as a write off later.

First expiry first out flips that. The system picks the soonest expiring lot that can satisfy the order. It is worth being clear why this differs from first in first out. Received order and expiry order usually agree. They come apart exactly when it matters, such as when a delivery lands with less remaining life than stock you already hold. A first in first out rule sends the wrong pallet on precisely the day the difference counts.

Overrides need a reason and a record

A rigid rule with no override gets defeated within a week, because there are good reasons to break it. A customer needs a specific production date. A lot is reserved for a promotion. A pallet is physically stuck behind another.

The answer is not to drop the rule. It is to make breaking it visible. An override that needs a reason code and leaves a record turns a silent workaround into a reportable pattern. After a month the report tells you whether the rule is being broken for good reasons or whether the rule itself is wrong.

Minimum remaining shelf life sits on the customer

Retail customers commonly require product to arrive with a set share of shelf life still remaining. The share differs by customer and sometimes by category.

If your system does not hold that requirement, you learn about breaches through rejected deliveries. Those cost you the freight, the product and a bit of the relationship.

Put the requirement on the customer record and check it at allocation. Now the problem surfaces as an exception before the pallet is built. Either the order allocates compliant stock or it flags and somebody decides with time to act. It is a small piece of configuration with a big effect on how many arguments your commercial team has each month.

A hold has to actually stop movement

Quality holds are where setups are often weaker than they look. A status that shows a warning is not a hold. A hold stops allocation and picking in every location at once.

Three things matter. It works at lot level rather than item level, because holding a whole item when one lot is in question stops the business for no reason. It takes effect everywhere at the same time, because stock at a third party site is exactly the stock most likely to keep moving. And the person who first knows there is a problem can apply it, with no request queue in the way.

Short date visibility is a commercial tool

Most systems can report what has expired. Fewer report what is about to, early enough for anyone to do something.

The useful report looks forward and splits stock by how much runway is left. Long runway needs no action. Stock inside the window where a promotion could still move it is a commercial opportunity. Stock past the point where any customer would take it is a write off waiting to be recognised.

Set those thresholds by category. Put the report in front of the commercial team on a fixed rhythm. That is the difference between selling short dated stock at a reduced margin and skipping it at zero. The threshold has to allow for how long a decision and a delivery really take, which is longer than people guess.

Shelf life on the lot, not just the item

A default shelf life on the item record is a fine starting point and an unreliable single source of truth.

Real remaining life varies with the production site and with how the stock was stored since. Sometimes it varies by supplier specification. Where that variation matters, the expiry date belongs on the lot, set at receipt or production. Use the item default only to calculate one when nothing better is available.

This matters for goods received too. Capture the supplier expiry at receipt rather than calculating one from the receipt date. For product that spent three weeks in transit, that is the only way the number reflects reality.

How this connects to everything else

Shelf life rules touch almost every other part of the build. Demand planning has to respect them, because ordering a quantity you cannot sell within its life is a guaranteed write off. Warehouse layout has to support them, because a pick rule that the physical layout fights will lose. Costing has to allow for expected wastage or unit margin will read better than it is.

Those connections are why this belongs in design rather than in a later optimisation phase. Our food and beverage guide covers how it sits next to traceability. The warehouse management guide covers the physical execution.

A test you can run this week

Take the ten products with the highest write off value last year. For each one work out whether it was written off because it was ordered in the wrong quantity, because it sat behind newer stock, because it was rejected on delivery, or because nobody saw it in time.

How those four answers split tells you which of the rules above to fix first. It is rarely all four and it is rarely the one people assume.

TechCloudPro configures shelf life management in ERP for food and beverage businesses and for wholesale and distribution operations handling dated stock, as part of NetSuite work. If write offs are a recurring line nobody can fully explain, the explanation is usually in these rules.