Spotting a supplier price rise before it eats your margin

Most food cost work happens once: you cost the dish, set the price, move on. The ingredient doesn't stay still. A supplier absorbs a cost increase for a while, then passes it on — sometimes on the invoice line, sometimes folded into a "restructured" price list nobody reads line by line. Either way, the dish that was, say, 28% food cost in January can be 33% by June, still selling at the January price, and the only place that shows up is a gross profit report someone has to go looking for.

Why this is different from just reading invoices.

Reading an invoice tells you what you paid today. It doesn't tell you that today's price is different from the price your recipe costing was built on — that comparison is a second step most systems don't do automatically, so it falls to someone remembering to check, which in practice means it doesn't happen until the numbers are bad enough to notice on their own.

What actually catches it:

1. A fixed reference price per ingredient, not just "what we paid last time" — otherwise a slow creep across several invoices never registers as a change, because each one looks normal next to the one before it.
2. A recipe that's linked to that reference price, so a change to the ingredient recalculates every dish that uses it, rather than sitting static until someone manually re-costs the menu.
3. Something that flags the difference, not just stores it — a system that quietly updates the "current cost" field without telling anyone is barely better than not tracking it at all.

What to actually do about it, this week, with nothing automated:

• Pick your three highest-spend ingredients — the ones where a 10% move actually matters in cash terms, not percentage terms.
• Pull the last three invoices for each and check the unit price line by line, not the total.
• If any of them moved, check whether the dishes using that ingredient have been re-priced since, or are still running on the old cost.

That's the whole method. It doesn't need software — it needs someone to actually do it, on a schedule, rather than waiting to notice.

Where FoxEra fits, honestly:

Photograph a supplier invoice, and FoxEra reads each line against what that ingredient last cost — so a price move shows up the same day rather than the same quarter, and every recipe using that ingredient re-costs itself automatically. That's the whole feature; it doesn't replace deciding what to do about a price rise once you've spotted one, and it won't catch a price change buried in a restructured price list rather than a per-line invoice increase — that one still needs a human reading the list.

If a price rise on one ingredient is quietly moving the cost of three different dishes without anyone re-pricing them, that's the same failure covered in