Written by: JJ Tan, Founder, Jelly | Last updated: 11 October 2026
Key Takeaways
- Supplier price change alerts flag when an invoice line-item price differs from the last recorded price. They surface movements between invoices rather than weeks later in reports.
- Invoice-triggered alerts give UK operators the most reliable signal, because they reflect what suppliers such as Brakes, Bidfood and JJ Foodservice actually charged.
- Verification matters. Operators need to separate genuine price rises from pack-size changes, unit-of-measure switches and temporary promotions before they act.
- A structured four-stage workflow of detect, verify, act and recover supports timely supplier challenges, SKU switches and menu re-pricing that protect margin.
- Jelly automates invoice scanning, price alerts and live dish costing so UK restaurants, pubs and boutique hotels can recover margin quickly and consistently.
See Jelly Catch Price Changes On Every Invoice
How Supplier Price Change Alerts Actually Arrive
Two detection mechanisms drive supplier price alerts. Invoice-triggered alerts fire when a new invoice is scanned and a line-item price differs from the stored price for that SKU. Price-list-triggered alerts fire when a supplier publishes a new price list. For UK operators, invoice-triggered alerts form the reliable backbone because they reflect what was actually charged on the invoice.
Alerts arrive in three formats: email, in-app notification or daily digest. Instant alerts catch changes fastest but create noise across a busy multi-supplier operation. Digests reduce noise but can delay reaction by almost a full day. Digest notifications queue each item until the next UTC midnight, and the actual delivery time also depends on the worker and any retries. The right cadence depends on spend category. High-spend proteins and fresh produce warrant daily review, while ambient lines can wait for a weekly digest. But receiving an alert is only the first step. Before acting on one, an operator needs to know whether it reflects a real price rise.
Jelly scans every line item of every invoice, including quantity, SKU, price and tax, via photo or a dedicated email address. It then fires its Price Alert feature automatically. No one needs to check prices manually. The moment a Brakes or Bidfood invoice lands with a different unit price for a SKU, the alert goes live. For more on how real-time price change alerts work in practice, Jelly’s existing guide covers the mechanics in detail.
Watch How Invoice Alerts Work In Jelly
The Verification Step: Confirming a Real Price Increase
This step sits at the heart of the workflow and most competitors skip it. Many alerts do not represent genuine price increases. An operator needs to separate four scenarios before taking action. These scenarios are a real price increase, a pack-size change, a unit-of-measure switch and a promotional or temporary price.
Four checks separate a genuine price rise from a false alarm, and each one targets a different way a supplier invoice can mislead you:
- Compare cost per base unit such as per kg, per litre or per each rather than pack price. A case price that looks identical may conceal an effective increase if the pack has shrunk from 40 units to 36.
- Check whether the pack size on the invoice changed. Dividing invoiced quantity by ordered quantity is the first test for unit-of-measure drift. A clean integer ratio such as 12 or 24 indicates a pack-size conversion, while an irregular ratio like 1.04 indicates a genuine delivery variance.
- Check whether the change is flagged as a promotion with an end date. A promotion usually signals a temporary movement rather than a list-price change.
- Check whether the SKU itself changed. A new SKU often indicates a supplier substitution at a different price point.
Manual spreadsheet tracking usually fails at this stage because the spreadsheet records pack price rather than unit cost. An analysis of 1.27 million invoices found that 22.7% contained at least one line billed at a price that did not match the agreed price. Of those lines billed above the agreed price, nearly half were 20% or more over. Yet manual checking quietly stops because three quarters of lines are correct and the effort finds nothing most of the time.
Jelly handles unit conversions automatically so the comparison stays like-for-like. That automation makes an alert trustworthy and actionable. It also allows an operator to take the alert straight into a supplier conversation instead of spending time verifying it first.
How to Set Up Supplier Price Change Alerts Across Multiple Suppliers and Sites
A UK multi-site operator running invoices from Brakes, Bidfood, JJ Foodservice and local suppliers can follow a clear setup sequence.
- Route every supplier invoice to a single capture point. Use a dedicated email address or photo upload into Jelly so nothing gets missed.
- Let the software digitise each line item so ingredient prices build a history automatically. This removes manual entry and keeps the data consistent.
- Map each supplier SKU to the ingredient used in your recipes so a price movement on a Bidfood chicken SKU flows directly into the dish cost for every recipe that uses it.
- Set the alert threshold or accept every movement. Once price history starts building, you can decide how much noise you want. Some operators flag only changes above 3%, while others want visibility on every line.
- Connect your POS so sales mix and margin context sit alongside the cost change. Jelly works alongside Square, EPOS Now, Toast and Lightspeed, and each connection takes approximately five minutes.
- Review alerts on a fixed cadence. Use daily reviews for high-spend proteins and produce, and weekly reviews for ambient and dry goods.
The multi-site case also needs a group-level view. When the same chicken SKU rises at three sites, head office should see one consolidated movement as a single issue to address. Sushi Revolution used Jelly to boost gross profits by 2-3% on average through tools such as daily menu price adjustments and supplier negotiations. Jelly’s POS integrations feed item-level sales data into the same margin picture, and digitised invoices push into Xero with one click. Sage integration is coming soon. For a deeper look at automated multi-supplier price alerts across sites, Jelly’s dedicated guide covers the group-level workflow.
What to Do When an Ingredient Price Alert Fires
The detect, verify, act and recover loop in practice runs as a repeatable cycle. Detection and verification are covered above. This section focuses on the act and recover stages. Once an alert has been verified as a genuine price increase, three main paths open up. You can challenge the supplier, switch or renegotiate, or accept and re-price.
For the supplier conversation, Jelly’s line-item invoice history shows the exact date and amount of every price movement. That data supports a direct question about whether this is a permanent list change or a temporary one. Well-drafted commercial contracts typically address price volatility through periodic price reviews, exceptional price increase clauses and hardship clauses. Where an increase was not notified in line with account terms, a credit note becomes a legitimate outcome. Most distributors will apply a credit for an undetected price increase if the operator catches it within 30 days and has documentation.
If the increase is permanent and the supplier will not move, the alternatives are clear. You can switch that SKU to a competing supplier, renegotiate on volume across sites or accept the increase and re-price the dish. Because Jelly updates ingredient costs with every invoice, dish costs and GP margins update in real time. A red percentage appears when a dish’s margin drops and green when it grows. The operator can re-price, re-engineer the dish or move it off the menu before the month closes.
Jelly users cut food costs by 3% on average in the first three months, and gross margins rise by around 2 percentage points. Murat Kilic of Amber restaurant in East London saves £3,000–£4,000 per month using price alerts and real-time costing: “Jelly keeps my business alive.” For more on how live dish costing connects to the alert workflow, Jelly’s automated price alerts and food costing guide covers the margin feedback loop in detail.
Explore The Full Detect → Recover Workflow In Jelly
Why Jelly Fits This Supplier Price Alert Workflow
Jelly serves growing UK restaurants, pubs and boutique hotels that turn over £500k or more and expand to 2–5 sites. These teams rarely have large back-office departments. Jelly focuses on fast setup and early value so operators see impact in the first week at a flat cost that does not scale with users or features.
- Automated invoice scanning captures every line item, including quantity, SKU, price and tax, so price history builds without manual entry.
- Price Alert flags every increase or decrease, shows by how much and from which supplier, the moment a new invoice is scanned.
- Live dish costing keeps GP visible so an alert becomes a menu decision in the same week instead of a month-end surprise.
- POS integrations with Square, EPOS Now, Toast and Lightspeed connect in approximately five minutes each and automate 2–5 hours of weekly admin work.
- Xero integration pushes digitised invoices with one click. Sage integration is on the roadmap.
- Onboarding that generates initial value in the first week so price alerts and spending insights go live as soon as invoices start arriving at the dedicated email address.
- Flat £129/month per location with no per-user or per-feature charges.
What Price Alerts Cannot Do
Price alerts still rely on clean inputs and human judgement. Alerts cannot catch a price change if the invoice never arrives or arrives late, because the system depends on invoices being routed to the capture point consistently. Alert quality also depends on the accuracy of supplier invoice data, including correct pack sizes and SKUs. If a supplier changes a SKU reference without notice, the system will treat it as a new ingredient until it is mapped. Alerts also stop short of prescribing the response. The decision to renegotiate, switch supplier or re-price a dish remains a human judgement, informed by the data Jelly surfaces.
Frequently Asked Questions
How Do Supplier Price Change Alerts Work Between Invoices?
Invoice-triggered alerts fire the moment a new invoice is scanned and a line-item price differs from the last recorded price for that SKU. Because Jelly scans every invoice as it arrives via photo or dedicated email, the alert goes live between delivery cycles rather than at month end. The operator sees which ingredient moved, by how much and from which supplier without waiting for a reconciliation report.
How Do I Challenge a Supplier Price Increase With Invoice Data?
Pull the line-item invoice history for the affected SKU, which shows the exact date and amount of every price movement. Present this to the supplier and ask whether the increase is a permanent list-price change or a temporary one, and whether the required notice period was met under your account terms. Where the increase was not properly notified, a credit note often becomes a reasonable outcome. Having the invoice history in a structured format rather than a spreadsheet keeps the conversation specific and documentable.
Can I Track Ingredient Price Changes Across Multiple Sites?
A group-level view rolls up price movements across all sites and all suppliers. Head office then sees that the same chicken SKU rose at three locations as a single consolidated alert rather than three separate one-site problems. This matters for operators running 2–5 sites with invoices from Brakes, Bidfood, JJ Foodservice and local suppliers simultaneously, because the same price movement affects every site’s dish costs and GP margins.
Which Restaurant Software Handles Ingredient Supplier Price Change Alerts in the UK?
Jelly is the platform built specifically for this workflow. It scans every invoice line item automatically, fires a Price Alert on every price movement and updates dish costs in real time. Jelly also works alongside Square, EPOS Now, Toast and Lightspeed POS systems in approximately five minutes each. Onboarding generates value in the first week, and the cost stays at a flat £129/month per location with no per-user or per-feature charges.
Conclusion
Margin lost between invoices across multiple suppliers and sites is a workflow problem, not a reporting one. The detect, verify, act and recover loop creates a repeatable process that turns every supplier price movement into a decision in the same week. That decision might be a credit note, a supplier switch or a menu re-price. Jelly runs that loop end to end, from the moment a Brakes or Bidfood invoice is scanned to the moment a dish margin updates in real time. At £129/month per location, with onboarding value in the first week and no per-user charges, Jelly gives UK multi-site operators a practical way to stop absorbing price creep and start recovering it.
Start Recovering Margin With Jelly



