Batch and Expiry Tracking: Managing Perishable Stock Without Losses

Every stock item has a lifespan. Some expire on a printed date: food, medicine, cosmetics, chemicals, reagents. Others expire commercially when a model is superseded or a manufacturer recalls a specific production run. Businesses that manage these items by unit count alone find out too late that stock exists in the system, exists on the shelf, and cannot be sold.

The fix is not an extra stock count. It is that every receipt carries its own identity: a batch number and an expiry date, and that the system uses both to drive issuing, alerting and recall. This guide covers how to start without stalling warehouse operations.

First: separate the batch number from the expiry date

Confusing the two is a common reason these projects fail. A batch number identifies a group of units produced or received together. An expiry date is the last day the item is fit for use. The batch answers: where did this come from, who received it, and where did it go? The expiry answers: what do I issue first, and when do I raise a flag?

Some items need both. Some need only a batch, because they never expire but may be recalled. Some need neither.

Second: do not track everything

The implementation most likely to collapse is the one that forces a batch and a date on every item in the warehouse. A storekeeper receiving a hundred lines will not key a hundred dates by hand; they will copy the same value down the list or leave it blank. Sort your items into three tiers:

• Full tracking: batch and expiry mandatory at both receipt and issue. For food, pharmaceuticals and anything subject to regulatory control or recall.
• Batch only: a batch or production-run number with no date. For spare parts and devices that could be pulled for a manufacturing defect.
• No tracking: low-value, fast-moving consumables.

Start with the first tier only. If it holds for two months, widen the scope.

Third: issue the nearest expiry first

The familiar warehouse rule is first in, first out, and for perishable stock it is not always correct. A delivery arriving today may carry less remaining shelf life than one received last month, simply because it sat longer at the supplier.

Rule	Issue criterion	Suits
First in, first out	Receipt date	Non-expiring items and general warehouse rotation
First expired, first out	Expiry date	Food, pharmaceuticals, cosmetics, chemicals

The rule alone is not enough; the system has to enforce it. When an item is issued, the system should propose the nearest-expiry batch and refuse an override unless the user has the permission and records a reason. Without that enforcement the rule stays a poster on the warehouse wall.

Fourth: alert before expiry, not after

A report telling you what expired yesterday is not a report, it is a loss statement. A useful alert reaches you while you still have options: a promotion, a transfer to a faster-moving branch, a return to the supplier if the contract allows it, or internal use. Set the alert window by the options actually available to you, not by an arbitrary number.

Remaining life	Suggested action	Owner
Early	Pause reordering the item and review the order quantity	Purchasing
Middle	Discount, bundle or transfer between branches	Sales
Short	Quarantine the batch off the shelf, decide write-off or return	Warehouse

The table above is a frame you fill in. A fast-turning grocery is not a slow-moving chemical store.

Fifth: backward traceability when a recall lands

If a supplier announces a recall, the first questions are: how many units of that batch did we receive, how many are still here, and who did we sell the rest to? A business that records the batch at receipt and at issue answers in minutes. A business that does not pulls the whole item from the shelf, writes off good stock, or cannot notify the buyers at all.

Link the batch number to the outgoing invoice, not only to the stock movement. That link is what turns tracking from an internal log into an actual ability to act.

Sixth: write-offs have an accounting and documentary side

Destroying expired stock is not merely a quantity reduction in the system. It affects cost of goods and the income statement, and it needs a signed disposal record showing item, batch, quantity, reason and authorising manager. For the tax treatment of damaged or lost goods, review the official guidance published by the Zakat, Tax and Customs Authority at zatca.gov.sa, since the treatment varies by case and should not be decided by internal interpretation.

Common mistakes during implementation

• Recording the expiry date in a free-text notes field, so the system can neither sort by it nor alert on it.
• Capturing the batch at receipt only and never at issue, so you know what came in but not what went out.
• Allowing the batch date to be edited after receipt with no audit trail.
• Mixing two different batches in one storage location, which leaves the record correct and the shelf wrong.
• Sending too many alerts to too many people, until the team learns to ignore them.