You Made More Units Than Planned. That's Not Automatically Good News.
The QuickCosting Team
You hit a great production run. More units out the door than you budgeted for. Feels like a win.
But if you're allocating fixed costs across those units, making more than planned means each unit absorbs less cost than it should. Your cost-per-unit drops. Your margin looks better. And none of it may be real.
This is the over-allocation trap, and it catches small manufacturers, food brands, and makers all the time.
What Allocation Actually Means
When you cost a product, some costs are direct (ingredients, materials, packaging). Others are indirect or fixed: rent, equipment depreciation, insurance, your production labor if it's salaried.
Because those fixed costs don't change with volume, you spread them across your planned output. That's cost allocation.
Example: You pay
,000/month in kitchen rental. You plan to make 500 jars of hot sauce. You allocate .00 per jar for kitchen overhead..33 jar. It's a .00 jar that had a rough month.Simple enough. The problem starts when actual production doesn't match your plan.
When You Make More Than Planned
Say you actually produce 800 jars that month instead of 500.
If you're using your actual output to allocate costs, each jar now only absorbs
.25 in kitchen overhead (.33 in overhead this month is not a,000 divided by 800). Your cost-per-unit falls. Your margin looks wider..33 in kitchen overhead. Your cost-per-unit spikes. Margins shrink or disappear.But you didn't spend less. You spent exactly the same.
This is over-allocation in practice: your fixed costs are being spread too thin across too many units. The individual unit cost looks artificially low.
Here's what that looks like side by side:
Scenario Units Produced Kitchen Cost Per Jar Apparent Margin (at $8 retail) Planned 500 .00 Calculated on real cost Over-produced 800 Looks better, but isn't If you reprice, reorder, or make business decisions based on the lower number, you're working from a distorted picture.
What To Do When You Over-Produce
A great run feels like a reason to celebrate, and it is, for revenue. But before you touch your pricing, do three things:
- Hold your cost-per-unit at the standard. Keep allocating fixed costs against your planned volume (500 jars), not your actual 800. The extra 300 jars didn't make your rent cheaper.
- Treat the gap as a favorable variance, not a discount. That saved overhead is a one-time signal that this month ran hot, not a new permanent cost. Bank it as a buffer, don't bake it into your price.
- Ask if the high run is repeatable. If 800 jars is your new normal, then raise your standard volume on purpose and reprice once, deliberately. If it was a fluke, leave the standard where it is.
The rule: a good month should improve your cash position, not quietly rewrite your cost sheet.
When You Make Less Than Planned
The reverse is just as dangerous, and often more immediately painful.
You planned 500 jars but only made 300 (equipment issue, ingredient shortage, a bad batch). Now each jar absorbs
This is under-allocation: fixed costs are over-concentrated in fewer units. Your product looks unprofitable even if the underlying economics are sound.
Small production runs, seasonal slowdowns, and supply disruptions all cause this. If you're not tracking it, you might cut a product line that's actually viable, or panic-discount to move inventory.
What To Do When You Under-Produce
This one stings more, because the per-unit cost spikes exactly when you can least afford a panic decision.
- Don't reprice off the bad batch. A jar that absorbed
Separate the variance from the product. Log the unfavorable variance against the cause (equipment downtime, ingredient shortage, short run), not against the recipe. The product economics didn't change. The conditions did. Check viability at your realistic low, not the disaster. Before you cut a line, ask whether it holds up at your normal slow-season volume. If it does, the product is fine and the month was the problem. Look for a pattern across cycles. One bad month is noise. The same SKU under-producing every summer is a planning decision waiting to be made. The rule: investigate the variance, then decide. Never let a single short run trigger a price hike or a product cut.
Why This Hits Seasonal and Food Businesses Especially Hard
Your coffee costs more to make in July than January, because you might be running smaller batches in summer, or your overhead stays flat while volume dips.
For any business where:
- Production volume varies month to month
- You run multiple SKUs sharing the same overhead
- You have a mix of high-volume and low-volume products
...allocation shifts constantly. A cost that looks fine in Q4 can look broken in Q2, using the exact same price and recipe.
The fix is not to reprice every month. The fix is to cost against your planned or standard output, not your actual output, and then track the variance separately.
Use a standard cost (based on your realistic planned volume) as your pricing anchor. Track actual production against that standard. When variances are large or recurring, investigate them as a business signal, not a costing correction.
What Good Tracking Looks Like
You don't need a complex system. You need consistent answers to three questions each production cycle:
- What did I plan to make? (Your standard volume)
- What did I actually make? (Your actual output)
- What did I actually spend? (Total costs for the period)
With those three numbers, you can calculate your real cost-per-unit, compare it to your standard cost, and see whether the variance is a fluke or a pattern.
A few things worth tracking over time:
- Which months consistently under-produce (and why)
- Which products have the most volatile cost-per-unit
- Whether your pricing still holds at your lowest realistic production volume, not just your best month
Price for your normal, not your best day. If your margin only works when everything goes perfectly, it doesn't really work.
What QuickCosting Does About All This
That's the manual version. Here's where the tool earns its keep: it keeps your cost-per-unit honest while your volume swings around, so you don't have to redo the math every cycle.
- It alerts you when you're over-allocating. This is the big one. When your fixed costs get spread across more units than planned and your per-unit cost drops below where it should sit, QuickCosting flags it. You find out the number is distorted before you price off it, not three months later when the margin doesn't show up in the bank.
- Allocate fixed costs against a standard volume, automatically. Set your overhead and G&A pools once, point them at your planned output, and QuickCosting holds that per-unit number steady. A hot month or a short run doesn't silently move your cost sheet.
- Pools and allocation methods that match how you actually run. Route rent, depreciation, and salaried labor into overhead or G&A pools, then allocate across SKUs by the method that fits, instead of guessing a flat per-unit number in your head.
- A pricing anchor that survives bad months. Because your catalog costs are built on standard volume, the price you set in your best month still holds in your worst one. No monthly repricing scramble.
- Variance you can see instead of stumble into. Compare what you planned to make against what you actually made and spent, so a big swing shows up as a number to investigate, not a distortion you average away by accident.
You bring three answers each cycle (planned, actual, spent). QuickCosting watches the allocation for you and speaks up when it drifts, so your price reflects your normal, not your luckiest or unluckiest day.
The Takeaway
More units is good for revenue. It is not automatically good for your cost picture.
When fixed costs get spread across more units than planned, your per-unit cost drops on paper without your actual spend changing. When output falls short, costs concentrate and margins compress. Both distortions lead to bad pricing and business decisions if you're not watching.
Track planned versus actual production consistently. Cost your products against a realistic standard volume. And treat big variances as signals worth understanding, not just numbers to average away.