# Why ibakepro will not change your prices or your allergen labels for you

> ibakepro recosts your products when a supplier price moves and suggests a new price, but your sell price and allergen labels only change when you approve them.

Should bakery software update your prices automatically when ingredient costs
go up? We decided no. In ibakepro, a supplier price change updates the cost of
every product that uses that ingredient and flags the ones whose margin has
slipped, with a suggested new price, but the price your customers see only
changes when you apply it. Allergen labels work the same way: a change upstream
is worked out and shown to you, and the published label waits for a person.

## When a supplier price moves

You change the price of an ingredient. Straight away, every recipe that uses
it is found, including a layer down: flour in the sponge, the sponge in a tiered cake,
the tiered cake recosted. Each affected product gets its new raw material,
labour, overhead and total cost.

Your sell price stays exactly where you put it. Instead, products whose margin
has drifted from the target you set are flagged for review, each with the
price that would restore that target. A drift of a fraction of a cent does not
raise a flag. On each flagged product you can apply the suggested price, type
your own or keep the current one. Applying is what pushes the new price out to
your storefront and everywhere else it shows.

If a cost cannot be worked out at all, nothing is suggested, so a missing cost
never turns into a suggested price of zero.

## When an ingredient's allergens change

You change the allergens on a pantry item. Every recipe using it is
recalculated, and every product downstream gets a new suggested allergen set,
with the stricter level winning when the same allergen arrives from two places
("contains" beats "may contain").

The published label does not move. Instead the product is flagged with what the
label says now, what it would say and exactly which allergens would be added or
removed. Applying the change is what publishes it to your storefront and
orders. Dismissing it keeps the current label.

## Why the line sits there

An allergen declaration is a legal statement. A price is a promise to a
customer. When someone with a nut allergy reads the label on your website, the
business making that statement is yours, and when a price goes up between a
customer asking and ordering, you are the one explaining it.

Removals are the sharper half of the allergen case. An addition that published
itself would over-declare, which is annoying and safe. A removal that published
itself would turn "contains nuts" into nothing between breakfast and lunch
because a supplier's data changed. The review flag shows removals plainly
because that is the line a person most needs to read.

The price case is less dramatic and more common. Ingredient prices move on
almost every delivery. If software chased each move into your prices, your
storefront would reprice itself several times a month, quotes would go stale
mid-conversation and the price points you chose on purpose would be replaced by
whatever restores a margin percentage. Choosing what to charge is one of the
most strategic decisions a bakery makes, and a cost rise is rarely the same
size as the price change it justifies.
[Your flour just went up 20 percent, now what](/blog/repricing-when-ingredient-costs-move)
shows why with numbers.

## How to work the review list

Change one widely used ingredient and you may see a long list of flagged
products. Work it like this:

- Apply the suggested price on anything now below cost straight away.
- Batch the rest into one repricing session a month, with a changeover date
  you tell customers once.
- Read every allergen flag on the day it appears, removals first.

The list stays until each item is applied or dismissed, so nothing that changed
upstream goes unseen.

## What runs on its own

Plenty happens without you. Costs cascade from ingredients through recipes to
products. Recipe allergen sets recalculate when an ingredient changes.
Allergens roll up from pantry items through components to products and onto
order lines as you build. A price you apply is pushed everywhere it appears, so
nobody sees a number different from the one they will be charged.

The detail of both sits on the feature pages:
[allergen management](/features/allergen-management) and
[recipe costing](/features/recipe-costing). For what else to look for in a
system, see [how to choose bakery software](/blog/choosing-bakery-software).
