Flour went up. What does that actually do to your prices?

A rise in costs never costs you what it looks like. Because profit is the thin slice, a 5% rise in costs takes 8% off the profit on a well-priced loaf — and 13% off a cinnamon bun. The multiplier is simple: your cost divided by your profit. Here is how to find it, and what to do about it.

The question most micro bakers ask when flour goes up is how much should I put my prices up. It is the wrong first question. The right one is how much the rise has already cost you, because the answer is reliably larger than it feels.

The amplifier

Costs and profit do not move together. A rise applies to your whole cost; it comes out of your profit, which is a much smaller number. So the percentage damage is magnified, and the multiplier is exactly:

cost ÷ profit = how many percent of profit each percent of cost takes

For the sourdough loaf costed across this blog — $5.85 to make, sold at $9.50, so $3.65 of profit — that multiplier is 1.6. Every 1% on costs takes 1.6% off the profit.

What a 5% rise in total costs does to two products at their current prices.
	Sourdough loaf	Cinnamon bun
Costs to make	$5.85	$1.20
Sells at	$9.50	$1.65
Profit	$3.65	$0.45
Amplifier (cost ÷ profit)	1.6×	2.7×
Profit lost to a 5% cost rise	8%	13%

The bun is the lesson. It looks like the safer product — small, cheap, quick — and it is the one a quiet cost rise damages most, because its profit is thin enough that anything moving underneath it shows up immediately.

Work out that ratio for each of your products and you have a ranked list of what to watch. Anything above about 2.5 is fragile.

Why the damage goes unnoticed for months

Nobody misses a 20% jump in butter. What gets missed is the drift: a sack up forty cents, a box up a penny, a label supplier adding a surcharge. None of them is worth acting on alone, and together they move your floor under a price list that has not changed since spring.

The structural reason is that most costing is done once, at the moment a product is launched, in a spreadsheet built for that purpose. Repricing then means finding which of fifty recipes use that flour and editing each one. It is not difficult, it is just a job nobody does twice — which is why so many price lists are quietly built on last year's invoices.

The fix is in how the pantry is stored

If a recipe stores flour costs $0.61, every price change is fifty edits. If it stores 500 g of the flour in my pantry, and the pantry stores $19.60 for 16 kg, then one edit moves everything that touches it. That is the whole difference, and it is a data-modelling decision rather than a discipline problem.

Which means the honest answer to how do I keep up with ingredient prices is: stop trying to. Record what you paid when you pay it, and let the recipes recost themselves. Costing a recipe properly is a one-time job; keeping it current should not be a job at all.

A recipe costing app like Baketly is built around exactly that model: the pantry stores what you paid for how much, recipes draw on it per gram, and a new sack price moves every loaf and bun that touches it before you have put the sack down.

Deciding when to move

Continuous tracking, deliberate repricing. Set a threshold in advance — when a product's margin has slipped by more than a few points from where you set it, it goes on the list — and review the list monthly rather than reacting to invoices.

When you do move, move once and far enough to matter. Two cautious rises three months apart are more visible to a regular customer than one clear rise with a reason attached, and they leave you behind the curve both times.

The short version

Find your cost-to-profit ratio per product; that is how hard any rise will land. Expect thin-margin products to take it worst. And make the pantry, not the recipe, the place a price is stored — because the reason prices go stale is never that bakers do not care, it is that the alternative was fifty edits.

Questions

How often should I recost my recipes?

Whenever a price you paid changes, which in practice means whenever you shop. If that sounds like too much, it is a sign the costing lives somewhere too slow — the point of pricing a pantry per unit is that recosting stops being a task at all.

Should I raise prices every time flour moves?

No. Track continuously, reprice deliberately. Watch the gap between what you assumed and what you are paying, and act when it crosses a threshold you set in advance — a few percent of margin, say — rather than on each invoice.

Which ingredients matter most?

The ones that are both expensive and volatile. For most bakeries that is butter and flour, with eggs close behind. A rise in the price of salt is not a business event.

Can I absorb a rise instead of passing it on?

For a while, and sometimes you should — if a rise looks seasonal, eating it is cheaper than two price changes. The danger is absorbing it by accident, for a year, because nobody recalculated.

What if my customers push back?

Flour and butter prices are public and your customers buy them too. One clear rise with a plain explanation lands better than a series of small quiet ones, and far better than shrinking the loaf.

Change the sack price, not fifty recipes

Baketly prices your pantry per gram, so when a sack changes price every recipe that uses it moves with it.

Download on the App Store