Scheduled Supplier Price Changes: How Multi-Site Restaurants Keep Recipe Costs Up To Date Automatically

Curran Dye

July 27, 2026

Scheduled supplier price changes costed across every site - Supy

Enter a Supplier Price Change Before It Lands, and Recipe Costs Update Themselves

You can enter a known supplier price change ahead of time, set the date it takes effect, and let every recipe that uses the ingredient re-cost itself automatically the day the new price applies. No spreadsheet re-keying, no quarterly costing project. The price you were told about in an email becomes a scheduled change, and your food-cost numbers move with it on the right date.

That matters because a price rise almost never arrives on a convenient day. A supplier confirms a 14.7% increase on mozzarella, from $8.50 to $9.75 per kg, effective the first of next month. In most operations that email gets filed, and the recipes keep costing at the old price until someone finds time to update them. Scheduling the change closes that gap: the new cost is already in the system, dated, waiting to apply itself.

For a group running the same recipes across several sites, the scheduled change applies everywhere the ingredient is used, so a single entry keeps every location's costing accurate instead of leaving four branches on four different versions of the truth.

Workflow diagram: enter a scheduled supplier price with an effective date, it activates automatically, every linked recipe re-costs, and food cost updates on dashboards

Why Re-Costing Recipes by Hand Leaves 90 Days of Margin on the Table

The real cost of manual re-costing is not the labour, it is the lag. Operators who re-cost recipes by hand tend to do it quarterly at best, which means a price rise can sit unreflected in the numbers for up to 90 days. For all of that time the food-cost reports read low, the menu looks healthier than it is, and nobody makes the pricing or purchasing decision the change should have triggered.

The damage compounds because it is invisible. A 28-cent rise on a Margherita Pizza that sells hundreds of times a week does not announce itself; it just quietly pulls the gross margin down from 78% to about 76% while the report still shows 78%. Multiply that across every recipe touched by every ingredient that moved this quarter, and the group is steering on numbers that describe last season, not this one.

Scheduling the change removes the lag entirely. The cost updates on the effective date, so the first food-cost report after that date already tells the truth.

Stat callout showing a 90-day typical lag before a supplier price rise reaches recipe costs when recipes are re-costed by hand

What Changes on Every Affected Recipe the Day the New Price Applies

When a scheduled price takes effect, the recalculation is not limited to one recipe. Every recipe and prep recipe that contains the ingredient is re-costed, and the change carries through to semi-finished items that feed other dishes, so a base sauce and every plate built on it all move together.

The table below shows what a single mozzarella increase does across a handful of recipes: the Margherita Pizza plate cost moves from $2.90 to $3.18, the Four Cheese Pasta from $3.40 to $3.86, and smaller users like the Garlic Flatbread shift by only 14 cents. In this sample the one ingredient touched 37 recipes. Doing that by hand is where errors and omissions creep in; letting the system cascade it is both faster and complete.

Because costs are recalculated from each location's actual ingredient prices rather than a group-wide average, the recipe cost you see is the real one for that site, which is what makes the next decision, where to act, a per-location question rather than a group guess.

Table of recipe plate-cost changes after a 14.7% mozzarella increase across four recipes

Reading the Margin Hit Per Location, Not as a Group Average

A group average hides the sites that need attention. The same mozzarella rise lands differently depending on how much of each branch's menu leans on it: in this sample the Airport Outlet and North Branch food-cost percentages climb by 2.2 and 2.3 points, while Harbour View moves only 1.5. Averaged together they look like a mild groupwide drift; read per location they point straight at the two sites where the margin is actually leaking.

That per-site view is what turns a price change from a report line into a decision. For the branches taking the biggest hit, the options are concrete: reprice the affected menu items, re-spec the recipe, or take the increase back to the supplier with the volume those sites represent. Live food-cost and COGS dashboards at group, site, and menu-category level let you see the impact the day it lands and choose the response per site.

Bar chart of food-cost percentage increase by branch after the price change, highlighting the two sites above a two-point move

The first move is small: the next time a supplier confirms an increase, do not file the email, enter it as a scheduled change with the effective date instead. From there, three checks keep the group ahead of its costs. First, confirm every ingredient is mapped to the recipes and prep recipes that use it, because the cascade only reaches recipes the ingredient is actually linked to. Second, after the change applies, read the food-cost impact per location, not as a group average, and flag any site whose food-cost percentage moves more than about two points. Third, decide the response for those sites specifically: reprice, re-spec, or renegotiate.

You can also link this back to your wider costing work: it sits alongside supplier price management and per-location recipe costing, and it is worth confirming in a demo by scheduling a future price on one item and watching it cascade to every recipe that uses it.

Book a Demo with Supy - scheduled supplier price changes and per-location recipe costing

Get weekly insights and tips delivered straight to your inbox.

Ready to optimize your restaurant operations?

Book a demo



Blog

Our operational insights





No items found.

Your questions  answered

Everything you need to know about Supy — from setup to integrations, pricing, and daily use. If it’s not covered here, just ask.

How do scheduled supplier price changes keep recipe costs accurate?

Scheduling a change means entering the new supplier price along with the date it takes effect, rather than editing costs by hand after the fact. On that date the price applies automatically and every recipe using the ingredient is re-costed, so the food-cost figures on your reports reflect the new price from the moment it lands. For a multi-site group the same scheduled change applies across every location that uses the ingredient, keeping all branches on one accurate version of costs instead of several manually maintained ones.

What happens to recipes that share an ingredient when its price changes?

When an ingredient's price changes, every recipe and prep recipe that contains it is recalculated together, not one at a time. The change also carries through semi-finished items, so a base sauce and each plated dish built on it all update in the same pass. In a sample where one mozzarella increase applied, 37 recipes were affected at once. Handling that manually is where omissions creep in, because it is easy to miss a recipe that uses the ingredient indirectly; letting the system cascade the change reaches all of them.

Why does re-costing recipes by hand leave margin on the table?

The problem with manual re-costing is the delay, not the effort. Operators who update costs by hand often do so quarterly at best, so a price rise can go unreflected for up to 90 days. During that window food-cost reports read lower than reality, the menu looks more profitable than it is, and the pricing or purchasing response the change should trigger never happens. A 28-cent rise on a high-volume dish quietly pulls gross margin down while the report still shows the old, healthier number.

When should a multi-site group read food cost per location instead of as a group average?

Almost always, because a group average hides the branches that actually need attention. The same ingredient increase lands differently at each site depending on how much of its menu relies on that ingredient. In a sample, two branches saw food cost climb more than two points while another moved barely one, yet the group average looked like a mild, uniform drift. Reading the impact per location points directly at the sites where margin is leaking, so you can act on those specific branches rather than applying one blunt response everywhere.

Can a single supplier price change be applied across every location at once?

Yes. Entering the price change once applies it everywhere the ingredient is used, so a group does not have to repeat the update site by site. That single entry keeps every branch's recipe costing consistent and removes the risk of four locations ending up on four different versions of the same cost. Supplier pricing can also be managed in bulk, with catalog export, editing, and re-import for larger changes, so even a wide round of price updates after a negotiation is handled as one operation rather than item by item.

Which recipes are affected when a supplier raises the price of one ingredient?

Every recipe linked to that ingredient is affected, which is often far more than operators expect. Beyond the obvious dishes, the increase flows into prep recipes and semi-finished components, so anything built on an affected base moves too. This is why mapping matters: the recalculation only reaches recipes where the ingredient is actually linked, so keeping ingredient-to-recipe links complete is what makes the cascade accurate. Once that mapping is in place, a single price change updates the full set of affected recipes without anyone tracking down each one.

How can an operator prepare for a supplier price increase they already know is coming?

Instead of filing the supplier's email and dealing with it later, enter the increase as a scheduled change with its effective date so it applies itself on the right day. Before that date, confirm the ingredient is mapped to every recipe and prep recipe that uses it, so the cascade is complete. After it applies, read the food-cost impact per location and flag any site that moves more than about two points. Then decide the response for those sites specifically: reprice the menu item, re-spec the recipe, or renegotiate with the supplier.