Stock systems die because nobody has time to keep them updated.
There is almost nothing to keep updated. Catalogue once; a purchase is four numbers; usage is marking a sack done. Everything else is derived, not typed.
Know what runs out, before it runs out.
Stock software usually fails for one reason: it asks somebody to keep it updated. This one is built around how a kitchen actually buys — the same twenty-odd things, over and over. You enter the catalogue once. After that a purchase is picking the item and typing four numbers, and consumption is “that sack is finished”. From only that, it works out the date each item runs out, warns you before it bites, and tells you what this month actually cost.
4
numbers to record a purchase
12
items in the starter catalogue
10
categories, grain to gas
0
stock-take evenings
Who it is for
Mess and canteen kitchens buying in sacks, crates, tins and cylinders
Hostel and college kitchens with a monthly budget to answer for
Owners who find out the rice is finished when the cook tells them
Anyone whose stock system is a photo of a diary page
What it removes
Stock systems die because nobody has time to keep them updated.
There is almost nothing to keep updated. Catalogue once; a purchase is four numbers; usage is marking a sack done. Everything else is derived, not typed.
You find out an item is finished when the kitchen has already stopped.
Each item carries a projected run-out date based on how fast the last lots actually went. Low stock warns you while you can still do something about it.
Nobody can say what the kitchen cost this month, or why it went up.
Cost per pack, cost per kilo, and month spend by category — from the purchases you were already recording.
A sack of rice lasts “about a week”, which is not a number you can plan on.
It becomes a real number. Each lot records when it was opened and when it was finished, so how long a sack lasts stops being folklore.
Inside
Tur dal, sold in 30 kg sacks. Milk, in 20 litre cans. Set it up once and stop describing it.
Pick the item, enter packs, cost, date and when you expect it to finish. That is the whole entry.
A projected finish date for every item, from how the previous lots actually behaved.
Spend by category and by item, without a spreadsheet in the middle.
“Two sacks done” is the whole interaction, recorded against the lot it came from.
It ships inside MessMate, so the kitchen that feeds 300 students and the stock that feeds the kitchen are one system.
Getting started
Start from the twelve items every kitchen buys, then add your own. Five minutes, once.
Item, packs, cost, date. The lot is now tracked and costed.
That is the only ongoing habit. From it, everything else — run-out dates, real shelf life, monthly cost — falls out.
Questions
It ships as a module inside MessMate today, under the same login and the same roles. If you want it on its own for a kitchen that does not run a mess, that is a conversation worth having — talk to us.
No. It is built around packs — sacks, crates, tins, cylinders — because that is how kitchens actually buy. Per-unit cost is worked out from the pack size you set once.
The projection quietly gets less accurate; nothing breaks. Mark it when you remember and the history corrects itself.
Yes. Exports are part of the product, not a paid add-on.
Something not covered here?
Tell us what you run and what the worst part of your month is. We set it up with you — your structure, your formats, your logins.