Two costs pulling in opposite directions
Batch production has one cost that falls as the batch grows and one that rises. The falling one is setup: gathering ingredients, heating the pot, and the twenty minutes of cleaning that happen whether you made twenty portions or four hundred. Spread across more portions, that fixed block shrinks per portion without limit. The rising one is waste, which is zero right up until the batch is bigger than what gets used inside its usable life, and then grows one for one with every extra portion.
Because the waste cost is exactly zero below a threshold and the labour saving is always positive, the two curves do not cross gently. They meet at a corner, and the corner sits at daily usage multiplied by usable life. Below it, bigger is always cheaper. Above it, every additional portion is thrown away and the cost per portion sold climbs immediately.
Worked through: 38 portions a day with a four-day life gives a crossover at 152. Making 200 means the last 48 never get sold, so 200 portions worth of ingredients get divided across 152 sales. At 42 cents of ingredients, that is $20.16 discarded on every run, and the cost per portion sold goes up rather than down despite the batch being bigger. The intuition that bigger batches are always more efficient is correct only on one side of a line that most kitchens never work out.
The two kinds of prep minutes
Not all prep time is fixed. Some of it genuinely scales: more onions to dice, more containers to fill, a longer stir. The calculator splits these, because treating all prep as fixed overstates the case for a large batch. If a batch takes 75 minutes of setup plus six minutes per hundred portions, then doubling from 150 to 300 takes the time from 84 to 93 minutes rather than leaving it flat, and the labour saving per portion is real but smaller than the fixed-only version suggests.
Measure both by timing two different-sized runs of the same item. Subtract, divide by the difference in portions, and you have the scaling rate. The remainder is the fixed block. It is worth doing once for your three or four biggest prep items, because those are where a change to the production schedule actually shows up on the payroll.
The labour rate to use is the loaded one, wage plus everything the employer pays on top of it, which the employee cost calculator works out. Using the bare wage understates every labour figure on this page by whatever your burden rate is.
Demand is not a constant, and neither is the crossover
The crossover moves with usage, so it moves every week. A slow week does not just reduce sales, it also shrinks the batch you can safely make, and a batch sized for a good week produces waste in a bad one. The downside check on this page runs your current batch against a reduced usage rate to show what that costs.
The practical response is not to size batches for the worst case, which throws away all the labour saving. It is to size them for typical demand and change the size when you can see the week coming: a known slow period, a holiday, weather that empties the dining room. Kitchens that produce to a fixed recipe card regardless of the forecast are the ones with a bin problem, and the fix is a production sheet that carries a number rather than a recipe.
| Situation | What moves | Effect on the crossover |
|---|---|---|
| Quiet week | Usage falls | Crossover falls proportionally — same life, fewer portions |
| Shorter life on a new recipe | Life falls | Crossover falls proportionally — more runs, more setup |
| Item added to a second dish | Usage rises | Crossover rises — bigger batches become viable |
| Portioning and freezing part of the run | Life rises for that part | Two different crossovers, run them separately |
When the answer is to change something other than the batch
If the crossover comes out small enough that you are running the item daily and paying the setup every time, the batch size is not the problem. The options are to raise the usage by putting the item on more dishes, to change the process so the fixed block shrinks, or to split production so that a portion of the run gets a longer life through a different handling method and the rest is made fresh. Each of these changes an input to this calculation rather than the calculation itself.
The reverse case is an item with a long life and low usage, where the crossover is enormous and the real constraint is storage space or the size of your largest pot. When the physical constraint binds before the shelf life does, put the constraint in the batch field and ignore the crossover.
What the shelf life field is and is not
The number you put in the life field is one you established for your own product, in your own containers, with your own cooling and storage, under your own written food safety plan. This calculator does not supply it, does not check it, and has no way of knowing whether it is right.
Nothing this page outputs is a holding time. The crossover is a production and cost figure that happens to be bounded by a number you entered, and if the number you entered is wrong the output is wrong in a way that no amount of arithmetic will catch. How long a prepared item may be kept, at what temperature, how it must be cooled after cooking, and how it must be dated and labelled are determined by your local health authority and by your own hazard analysis, and they are a separate discipline from costing. The food safety guide covers the general vocabulary and is not a substitute for either your regulator or your plan. If you are scaling the recipe itself rather than deciding how much to make, the recipe scaler handles the ingredient arithmetic, and the recipe cost calculator gives you the per-portion ingredient figure this page asks for.
Questions people ask
How do I work out how long a prep item lasts?
Not from this page, and not from a table on the internet. Establishing how long a prepared item can be kept is part of your food safety plan, and it depends on the product, the process, how it was cooled, what it is stored in, the storage temperature and your local regulations. In most places this is your responsibility as the operator, usually documented, and often subject to inspection. The number is set by that process and then used here as an input. If you do not have one established, the honest position is that you cannot size a batch by this method yet, and the thing to sort out first is the plan rather than the batch.
Why does the calculator say bigger is always better below the crossover?
Because in this model the only cost that rises with batch size is waste, and below the crossover there is none. Ingredient cost per portion is flat by definition, the scaling minutes are flat per portion, and the fixed setup block gets divided by a larger number. So cost per portion falls all the way to the crossover and then turns sharply upward. In a real kitchen there are other limits the model does not carry: the size of your largest vessel, cooler space, how much a single person can handle safely, and whether quality holds up on day four the way it does on day one. Those cap the batch below the crossover often enough that the crossover should be read as a ceiling rather than a target.
Should freezing be treated as extending the shelf life?
Only if the frozen portion is genuinely a different product with its own established handling, and then it is cleaner to run it as a separate calculation. A batch where half is used fresh over four days and half is portioned and frozen is two production streams with two different lives and two different quality outcomes, and averaging them into one life figure gives a crossover that describes neither. Run the fresh portion at its own usage and life to get its batch size, then treat the frozen stream as a separate item. Whether freezing is appropriate at all for a given product, and how it must be done, is a food safety and quality question rather than a costing one.
My waste is already zero. Does that mean my batch size is right?
It means it is not too big, which is only half the question. Zero waste with a batch that clears in a day and a half against a four-day life means you are running the fixed setup nearly three times as often as you need to, and that labour is as real a cost as the waste would be. The table on this page shows both effects across a range of sizes so you can see which side you are on. The one case where a small batch with zero waste is genuinely right is where quality falls off noticeably over the life, and that is a judgement about the dish rather than an arithmetic result.
How does this interact with ordering the raw ingredients?
It sets the rhythm that ordering has to serve. Once you know the batch size and how often you run it, you know how much raw product a week consumes and in what lumps, which is the input an ordering calculation needs. The one thing to watch is that raw ingredients and the prepared item have entirely separate lives, and a raw item bought to cover three batches has to survive until the third one gets made. Where the raw ingredient has a shorter life than the prep schedule assumes, the ordering pattern has to change rather than the batch. Ordinary reorder point and safety stock arithmetic is on the inventory order calculator.