Expiry Date and FEFO Batch Tracker

Food, cosmetics, medicine-like items and chemicals go bad on a date. Stock is rotated by eye, short-dated deliveries are noticed late, and the first sign of a problem is a bin of expired product you already paid for.

Add each item, then each delivery as a batch with lot number, expiry date, quantity and cost. The Dashboard shows what is expired but still in stock, what to use within your red window, what expires soon, and what is on watch, with the money at risk in each group and a chart of the value expiring week by week for eight weeks. Issue (FEFO) takes a quantity and tells you which batches to take from, earliest expiry first, and records the issue. Batches on hold or already expired are skipped. Stock lists every live batch with filters and writes off expired batches in one click, and the Log keeps every receipt, issue and write-off.

An item with expiry date 20/11/2026 is usable on 20/11/2026 and expired from 21/11/2026. The red, amber and watch windows in days, and the as-of date, are settings.

What is inside:

• Dashboard, Stock, Receive, Issue (FEFO), Items, Log, Settings and Start here tabs
• A warning when a delivery arrives with less than a set share of its shelf life left
• CSV import of batches, CSV export, JSON backup, printable expiry report
• A worked example of eight items and 14 batches

Who it is for: cafes, restaurants, bakeries, groceries, cosmetics shops and anyone who stocks dated goods.

What it is not: it only knows the dates you enter. It is not a food safety system and does not replace temperature checks, supplier documents or the rules your local authority sets on shelf life, relabelling and disposal. Check those rules for your products.

How it differs: the document expiry trackers in the catalogue follow licences, visas and staff documents. This one follows stock batches and FEFO issue.

Tested: expiry state, days left, window grouping, FEFO allocation order and quantities, write-offs and values were compared with a separate Python implementation on randomised stock, 3,500 cases and 4,313 assertions, with no differences. 59 scripted browser checks cover receiving, issuing, write-off, CSV import, backup restore, print and the 375 and 1280 pixel layouts, with no console errors. Browser tests ran in Chromium and WebKit; Firefox, a real phone, a real printer and a real scanner were not available, so they were not tested.