Written by: JJ Tan, Founder, Jelly
Key Takeaways
- UK hospitality wastes nearly one-fifth of purchased food, costing venues with £1 million turnover tens of thousands annually in lost margin.
- Most waste stems from poor ordering intelligence, not kitchen discipline, and the reorder formula (expected usage + safety stock − current stock) fixes this when fed live data.
- Ten practical rules cover data-driven par levels, smaller case sizes, just-in-time ordering, flexible MOQs, packaging loops, supplier-specific waste tracking, weekly audits, live invoice reorders, seasonal adjustments, and consolidated deliveries.
- Operators using these rules typically cut food-cost percentage by two points, recover thousands in credit notes, and save 10–20 admin hours monthly within 90 days.
- Book a demo with Jelly to automate every rule with real-time invoice scanning and POS integration.
The Reorder Formula Every Operator Needs
Next order = expected usage + safety stock − current stock. Expected usage comes from POS sales data mapped to recipe portions. Safety stock is a measured buffer, not a guess. Current stock is a live count. Without live invoice data feeding ingredient costs and usage rates into this formula in real time, the calculation quickly becomes stale.
Jelly’s automated invoice scanning updates ingredient costs and usage rates the moment a new invoice arrives, so this formula produces an accurate reorder quantity every single day, not once a month when the accountant sends a report.
How to Set Par Levels for Perishables
The reorder formula requires three inputs: expected usage, safety stock, and current stock. The following ten rules show you how to establish each input with precision, starting with data-driven par levels that define your target stock for every perishable SKU.
Rule 1 — Build data-driven par levels from POS sales, not memory.
Objective: Replace intuitive ordering with a repeatable stock target for every perishable SKU.
Exact action: Use the formula Par Level = (average daily usage × days between orders) + safety stock. Set safety stock from average usage, then refine it using the standard deviation of recent daily sales per item.
Inputs required:
- At least 30 days of daily sales-per-item data from your POS system
- Supplier delivery frequency per SKU
- Shelf life per perishable category
- Recipe portion sizes from your cookbook
Success metric: Zero spoilage write-offs for items on a set par, and actual stock on hand within 10% of par target on count day.
| Item | Daily Usage | Order Cycle (days) | Safety Stock | Par Level |
|---|---|---|---|---|
| Chicken breast | 30 lb | 3 | 30 lb | 120 lb |
| Fresh salmon | 8 lb | 2 | 8 lb | 24 lb |
| Heavy cream | 4 qt | 3 | 4 qt | 16 qt |
| Avocados | 48 units | 2 | 12 units | 108 units |
Set separate weekday and weekend pars when volume varies significantly. Review every par quarterly so it reflects seasonal menu changes.
Negotiate Smaller Case Sizes with Suppliers
Rule 2 — Request split cases before accepting standard pack sizes.
Objective: Reduce the volume purchased per delivery to match actual consumption and cut end-of-week spoilage on slow-moving lines.
Exact action: Identify every SKU where your weekly usage is less than one full case, because these are your split-case candidates. Once you have that list, request a split or half-case option from each supplier. For example, ask your dairy supplier to deliver 3 kg blocks instead of 6 kg cheese blocks, and ask your oil supplier for 5-litre containers instead of 10-litre drums.
Sample script: “We’re currently ordering [item] in [standard case size]. Our weekly usage is [X units]. Can we move to [smaller unit] to reduce spoilage? We’re happy to maintain the same order frequency to keep your logistics simple.”
Inputs required: Weekly usage data per SKU from Jelly’s spending insights dashboard, and current case size from scanned invoices.
Success metric: Spoilage on affected SKUs falls to zero within four weeks, and any unit cost increase is offset by waste reduction.
Switch to Just-in-Time Ordering for Perishables
Rule 3 — Shorten the order cycle on your highest-waste perishables.
Objective: Hold less stock at any one time by ordering more frequently in smaller quantities.
Exact action: For items with a shelf life under five days, move from weekly to three-times-weekly ordering where your supplier allows. Use Jelly’s Price Alert feature to monitor whether increased delivery frequency triggers surcharges, and renegotiate if it does.
Inputs required: Shelf-life data per SKU, supplier delivery schedule, and Jelly price alerts to flag any per-unit cost changes triggered by frequency adjustments.
Success metric: On-hand stock of targeted perishables falls by 30% or more, and spoilage write-offs on those lines reach zero.
Build Flexible MOQ Agreements with Suppliers
Rule 4 — Negotiate minimum order quantities down to match your actual weekly need.
Objective: Remove the structural over-ordering caused by supplier MOQs that exceed your consumption rate.
Exact action: Pull 90 days of invoice data from Jelly to calculate your true average weekly spend per supplier. Present this data in your next supplier review. Propose a lower MOQ in exchange for a committed order frequency, for example three orders per week instead of one large weekly order.
Sample script: “Our data shows we use [X units] per week on average. Your current MOQ of [Y units] means we’re carrying [Z units] of excess stock. We’d like to propose a revised MOQ of [X units] with a guaranteed three-order-per-week commitment.”
Inputs required: A 90-day supplier spend report from Jelly and average weekly usage per SKU.
Success metric: MOQ reduced to within 10% of average weekly usage, with no stockouts on affected lines.
Create Packaging-Loop Agreements with Key Partners
Rule 5 — Formalise return-and-reuse arrangements with key suppliers.
Objective: Reduce packaging waste and create a commercial incentive for suppliers to maintain delivery consistency.
Exact action: Identify suppliers who already collect crates, pallets, or containers. Formalise the arrangement in writing, and specify return timelines plus any credit or cost reduction tied to compliance. Track compliance weekly.
Inputs required: Current supplier delivery notes captured via Jelly invoice scanning, and an agreed return schedule.
KPI checklist:
- Number of packaging units returned on schedule each week
- Credit value received per month from packaging returns
- Percentage of deliveries arriving in reusable packaging vs. single-use
- Supplier compliance rate (returns on time ÷ total returns due)
Success metric: All agreed packaging returned within the agreed window, and measurable credit note value appearing on monthly supplier statements.
Track Waste by Supplier Item
Rule 6 — Assign waste to the specific SKU and supplier that generated it.
Objective: Move from total waste figures to supplier-level accountability so you can negotiate with evidence.
Exact action: Log every spoilage or trim event against the specific invoice line item it came from. Use Jelly’s invoice data to cross-reference the supplier, delivery date, and unit cost of every wasted item.
Inputs required: A daily spoilage log linked to Jelly SKU records, plus invoice line-item data from Jelly.
Success metric: Every waste event attributed to a supplier and SKU within 24 hours, and the top three waste-generating SKUs identified within the first two weeks.
Financial KPIs for food waste that support ordering decisions include waste-cost-per-ingredient and waste-cost-per-category, both of which Jelly’s invoice data makes calculable without a spreadsheet.
Run Weekly Supplier-by-Supplier Waste Audits
Rule 7 — Review waste data by supplier every Monday before placing orders.
Objective: Create a weekly rhythm that catches ordering errors before they repeat.
Exact action: Every Monday, review the previous week’s waste log sorted by supplier. Identify any supplier where waste-cost-per-SKU exceeded your threshold, with a suggested starting point of 2% of that SKU’s weekly invoice value. Adjust that SKU’s par level or order quantity before placing the week’s orders.
Weekly waste-by-supplier audit scorecard:
| Supplier | SKU | Weekly Invoice Value (£) | Waste Cost (£) | Waste % of Spend | Action |
|---|---|---|---|---|---|
| [Supplier A] | [Item] | [£] | [£] | [%] | Reduce par / split case |
| [Supplier B] | [Item] | [£] | [£] | [%] | Increase order frequency |
| [Supplier C] | [Item] | [£] | [£] | [%] | No action required |
Weekly property-level reviews of waste data allow kitchen teams to adjust operations within the same service period, rather than waiting for a monthly report that arrives too late to act on.
Use Live Invoice Data for Daily Reorders
Rule 8 — Replace gut-feel daily ordering with invoice-driven reorder calculations.
Objective: Make every reorder decision traceable to a data point, not a chef’s estimate.
Exact action: Connect your suppliers to Jelly so that every invoice, whether emailed or photographed, is scanned automatically. Use the resulting live ingredient costs and usage rates to run the reorder formula (expected usage + safety stock − current stock) daily. Jelly’s Flash Report gives you a daily gross profit view so you can see immediately if a reorder decision has moved your food cost percentage.
Inputs required: All supplier invoices flowing into Jelly via email or photo, POS integration for live sales data, and a daily stock count.
Success metric: Food cost percentage remains stable week-on-week, reorder quantities sit within 5% of actual consumption, and admin time on ordering falls by at least two hours per week.
Adjust Pars for Seasonality and Events
Rule 9 — Update par levels before every seasonal menu change and confirmed event.
Objective: Prevent event-week stockouts and post-event spoilage surges.
Exact action: Four weeks before a seasonal menu launch or confirmed large event, pull the previous year’s sales mix from Jelly’s POS integration. Recalculate pars for every affected SKU using the updated expected usage figure. Apply the weekday and weekend split approach described in Rule 1, and revert to standard pars within one week of the event ending.
Inputs required: Historical sales mix data from Jelly’s POS integration, confirmed event booking data, and updated recipe portions from Jelly’s Cookbook.
Success metric: No stockouts during event periods, and post-event spoilage write-offs no higher than a standard week.
Consolidate Deliveries Without Increasing Waste
Rule 10 — Reduce delivery days per supplier without increasing order volume per delivery.
Objective: Cut delivery administration and handling time while keeping order quantities matched to consumption.
Exact action: Identify suppliers where you currently receive more than three deliveries per week. Propose consolidating to two deliveries, and at the same time reduce the per-delivery order quantity so total weekly volume stays the same. Use Jelly’s supplier spend dashboard to confirm that consolidation has not caused a creep in total weekly spend.
Inputs required: Delivery frequency per supplier from Jelly invoice history, weekly spend per supplier, and current par levels.
Success metric: Delivery handling time reduces, total weekly spend per supplier stays unchanged, and spoilage does not increase on consolidated lines.
Common Ordering Mistakes and How to Fix Them
- Using one fixed par year-round for seasonal items. Fix: schedule a quarterly par review in your calendar and update pars four weeks before each seasonal menu change using Jelly’s historical sales data.
- Setting safety stock as a fixed number rather than a percentage of usage. Fix: start safety stock as a percentage of average usage and refine it using the standard deviation of recent daily sales.
- Ordering from memory after a busy service. Fix: run the reorder formula from Jelly’s live invoice and POS data before every order is placed, not after service when recall is unreliable.
- Accepting supplier price increases without a credit note process. Fix: use Jelly’s Price Alert feature to flag every price movement and raise a credit note request within 48 hours of any unannounced increase.
- Tracking total waste rather than waste by supplier SKU. Fix: implement the weekly waste-by-supplier audit scorecard from Rule 7 and link every write-off to an invoice line item in Jelly.
Measure Success: Food-Cost Percentage, Credit-Note Value, Admin Hours Saved
Food cost percentage is calculated as (Cost of Goods Sold ÷ Food Sales) × 100, and even a one- or two-point increase often signals portion creep, vendor price rises, over-prepping waste, or underpriced menu items. Review this metric weekly, not monthly.
The three primary metrics to track after implementing these rules are:
- Food cost percentage: target a reduction of two percentage points within 90 days, which matches the average improvement Jelly customers achieve in their first three months.
- Credit-note value recovered: track the cumulative value of credit notes raised via Jelly’s Price Alert feature each month. Amber restaurant saves £3,000–£4,000 per month through credits, better buying, and tighter menu controls.
- Admin hours saved: Jelly automates 10–20 hours of monthly admin, freeing operators and chefs to focus on margin improvement rather than data entry.
Hospitality businesses that implement food waste measurement typically achieve waste reductions of 20–50% within the first year, because measurement creates the visibility that motivates operational change. Jelly provides that measurement automatically from the moment the first invoice is scanned.
Frequently Asked Questions
How do I roll out these ordering rules across multiple sites without creating inconsistency?
The most reliable approach is to establish a single source of truth for invoice data, par levels, and supplier spend before rolling out to additional sites. Jelly operates on a per-location model at a flat rate of £129 per month per site, so each location has its own live data while the owner or operations director retains a portfolio-level view. Start by standardising the par-level formula and the weekly waste audit scorecard at your best-performing site, then document the process. Replicate it at each new location using that site’s own POS sales data to set location-specific pars. Avoid copying par levels directly from one site to another, because usage rates vary by location and a par set for a 120-cover restaurant will generate waste at a 60-cover site.
What should I do when a supplier raises prices mid-week without notice?
The first step is to have a system that catches the increase immediately rather than at month-end. Jelly’s Price Alert feature flags every price movement on every invoice line item the moment a new invoice is scanned, and gives you the specific SKU, the old price, the new price, and the supplier name. With that data in hand, contact the supplier within 48 hours, reference the specific invoice and line item, and request a credit note for the difference. If the increase is sustained, use Jelly’s 90-day supplier spend history to quantify the cumulative impact and use that figure in your next supplier negotiation. Operators who respond to price alerts within the same week consistently recover more in credit notes than those who raise the issue at a monthly review.
How long does it take to see a measurable reduction in food waste after implementing par levels?
Most operators see a meaningful reduction in spoilage write-offs within two to four weeks of setting data-driven pars, because the primary cause of perishable waste, ordering more than the consumption rate, is corrected immediately. The first week typically surfaces the SKUs where pars were most inflated. The second and third weeks allow you to refine safety stock based on actual variance. By week four, food cost percentage should begin to reflect the reduction, aligning with the two-point improvement target discussed earlier.
Can I use these rules if I only have one or two suppliers?
You can apply the reorder formula, par-level methodology, and waste audit scorecard regardless of how many suppliers you use. With fewer suppliers, the weekly audit is faster and the negotiation conversations are more focused. The advantage of having live invoice data in Jelly is that even a single supplier relationship becomes fully transparent, because you can see every price movement, every delivery, and every SKU’s contribution to your food cost percentage without manual reconciliation. Operators with a small supplier base often find that the Price Alert feature delivers the fastest return, because a single unnoticed price increase on a high-volume ingredient can move food cost percentage by a full point within a month.
What is the difference between a par level and a reorder point?
A par level is a scheduled stock target that staff count to on a fixed day and order up to, for example every Monday morning the team counts stock and orders the difference between what is on the shelf and the par. A reorder point is a trigger, where the moment stock falls to a set level an order is placed, regardless of the day. For most independent restaurants, pubs, and boutique hotels, par levels are more practical because they align with fixed supplier delivery schedules and require a single weekly count rather than continuous monitoring. Reorder points suit high-volume, fast-moving dry goods where stockouts are costly and deliveries can be requested at any time. Jelly’s live invoice and POS data supports both approaches, because the reorder formula (expected usage + safety stock − current stock) can run on a fixed schedule or trigger from a stock-count alert, depending on the item.
Conclusion: Turn Every Invoice into Ordering Intelligence
Guesswork ordering is a structural margin problem, not a discipline problem. The ten rules above give every UK restaurant, pub, and boutique hotel operator a repeatable framework: data-driven par levels, negotiated case sizes and MOQs, just-in-time delivery schedules, supplier-specific waste tracking, and live invoice data feeding every reorder decision. Each rule produces a measurable outcome. Together, they target the one-fifth waste rate documented across UK hospitality.
Jelly is the automation layer that makes every rule scalable. It scans every invoice, flags every price movement, updates every dish cost in real time, and connects directly to your POS system, so the reorder formula runs on live data, not last month’s spreadsheet. Stuart Noble at Cairn Lodge Hotel cut food costs by 5% in a month. Murat Kilic at Amber saves £3,000–£4,000 every month. The Howard Arms reached 80% gross profit. The common thread is live invoice intelligence replacing manual guesswork.
Turn your invoices into a real-time ordering system this week, and see Jelly in action.
