True Cost Per Batch: Production Tracking for Makers
Ingredient cost is the easy part. What a batch really costs once labour, wastage and overhead are in, and how production tracking shows where it drifted.
You baked 100 loaves today. You know what the flour cost. But do you know what those 100 loaves actually cost to make — once the hours on the floor, the burnt tray, and a slice of the rent are counted in? For most makers that number lives in their head, roughly, and it is usually wrong.
It is not wrong because the maker is careless. It is wrong because the real cost of making something is built from several moving parts, most of them easy to forget, and it changes from one batch to the next. If you only ever track the obvious part — the ingredients — you are pricing and planning off a number that is missing half its weight. This guide is about finding the whole number: the true cost of a batch, every time you make one.
Product costing tells you the price tag. Production tracking tells you the story.
These two ideas sound the same and they are not, so it is worth separating them cleanly.
Product costing answers a single question: what does one finished unit cost me to make? It is the price tag on a cake, a bottle, a jar of sauce. It is a useful number and you should know it for everything you sell.
Production tracking is the thing that produces that number honestly, batch after batch — and shows you where it drifted. It follows the actual act of making: what you planned to use, what you really used, how long it took, what got wasted, and what it all came to once the doors-open costs are spread across the run. Product costing is the snapshot. Production tracking is the film.
You need the film, because the snapshot lies the moment anything changes. And in a real kitchen or workshop, something always changes.
What actually goes into a batch
When you make a run of something, four real costs go in. Sort everything into these four buckets and you will never again mistake the ingredient bill for the cost.
Materials, at what they really cost. Not the price on the shelf today, not the price you paid two years ago — the cost of the stock you actually pulled into this batch. If you bought flour at three different prices over three months, the bag you reached for this morning is worth a blended, weighted-average price, not a guess. Materials are the obvious bucket, but even here the number is slipperier than it looks.
Labour. The hands-on time it took to make and finish the batch, valued at what that time is worth. If two people spent ninety minutes on a run, that is three person-hours, and three person-hours has a cost even when one of the people is you. Your time is not free just because you never invoice yourself for it.
Wastage. The tray that burned, the spoiled portion, the off-spec units you could not sell. Wastage is pure loss baked into the batch — the materials and time are spent, but the saleable output is smaller. Ignore it and your cost-per-unit looks better than it is, which is exactly the lie that hurts most.
A share of overhead. Rent, power, gas, water, equipment — the costs that run whether you make one batch or ten. No single loaf "owns" the rent, but every loaf should carry a fair slice of it. A simple way to start: take your monthly overhead, work out roughly how much of it a batch consumes, and add that share in.
Add the four buckets, divide by how many good units came out, and you finally have an honest cost per unit. It will almost always be higher than the ingredient-only figure you carried in your head — and that difference is the money that was leaking out unseen, batch after batch.
It starts with a recipe
Before you can track a batch, you need a plan for it. That plan is a recipe — sometimes called a bill of materials, or BOM, which is just a fancy term for "the list of what goes into one finished thing, and how much." Ten units of flour, six of sugar, two of butter, forty minutes of labour. Nothing more mysterious than the card a good cook already keeps in their head.
The recipe gives you your standard cost — what a batch should cost if everything goes to plan and prices hold. That is your baseline, your line in the sand. It is also where most small makers stop: they cost the recipe once, write a price, and never look again. The recipe is the beginning of costing, not the end of it.
Then the batch happens — and reality has opinions
You raise a work order — "make 100 loaves" — and the recipe scales up: this is what we plan to consume. Then the real run happens, and reality rarely matches the plan exactly.
You meant to use 100 units of flour and actually used 108 because a batch stuck. A staff member was off sick so the run took longer. Two trays didn't rise. The sugar you bought last week cost more than the sugar in the recipe. None of these feel like much in the moment. Each one quietly moves your real cost away from the standard cost you priced against.
The gap between what a batch should have cost and what it actually cost has a name: variance. Variance is the single most useful number in production, because it is an early-warning light. A batch that came in 4% over once is noise. The same product running 15% over, week after week, is a problem with a cause — a supplier who crept their price up, a recipe that no longer reflects real yield, a step that wastes more than it should. Variance is how you catch the drift while it is still this week's problem and not next quarter's mystery.
Why two identical batches cost different amounts
This is the part that surprises people. You can make the exact same product twice and have it cost you two different amounts — and not by a little.
Yield wobbles: a batch that should make twelve sometimes makes ten because two stuck to the tin, so the same costs are spread across fewer units. Input prices move: flour in June costs more than flour in January. Wastage spikes on a bad day. Labour stretches when you are short-staffed. Each batch is its own small economy, and a cost you worked out six months ago and never revisited is not your cost anymore — it is a guess wearing an old price tag.
And here is the cruel twist, the same one that haunts every part of running a busy operation: the harder you push, the more this hurts. A slow week hides a costing problem. A flat-out week — more batches, more pressure, more corners — amplifies it. The days you most need your numbers to be right are the days you have the least time to work them out by hand.
Knowing which batch, and which is about to spoil
There is one more thing the make-process should give you, and it is worth real money: traceability. When a batch of finished goods can be traced back to the exact lots of raw material that went into it — and forwards, from a raw lot to every batch it touched — two expensive problems get smaller.
The first is recalls and quality issues. If something is wrong with a delivery of an ingredient, you want to know precisely which finished batches used it, not pull everything off the shelf in a panic. The second is spoilage. Perishable stock that quietly passes its date is money you are about to bin — and a maker who gets nudged before that happens can mark it down, use it first, or plan around it, instead of writing it off. Knowing what is in a batch and when it expires turns two of the most stressful, costly surprises in production into routine, manageable events.
How Eleo does this
This is where Eleo comes in, and it is built to give you exactly the film, not just the snapshot.
In Eleo, you build a recipe (your bill of materials) for a product, then raise a work order to make a batch of it. From there Eleo tracks the run for you: the materials actually issued and consumed — valued at their real weighted-average cost, not a stale guess — the labour time at your rate, the wastage, and a fair share of overhead. It adds those up into the true cost per unit for that specific batch, and it puts that next to the standard cost so you can see the variance — how far this batch drifted from what it should have cost, and in which direction.
It keeps the trace, too: which input lots went into which output batches, both ways, so a quality scare or a recall is a lookup, not a teardown. And it watches expiry, so perishable stock gets flagged before it becomes waste rather than after.
The point of all of it is the same simple thing: you stop guessing what it costs to make what you sell. You price with a real number, you spot the batch that ran hot before it becomes a habit, and you find out which products genuinely carry your business and which ones quietly bleed it. The example figures here are in naira, but a cost is a cost whether you count it in ₦, $, £ or € — the maths of a batch is identical everywhere, and so is the relief of finally knowing it.
You already do the hard part: you make the thing, every day, well. Production tracking just makes sure that every batch you pour your time into tells you the truth about what it cost — so the harder you work, the clearer your numbers get, instead of the other way around.