Written by: JJ Tan, Founder, Jelly
Key Takeaways for Running This Ordering System
- Use the ordering-quantity formula (par level − current stock) + (forecast covers × average portion) − expected deliveries on every perishable line each cycle to cut over-ordering while protecting service levels.
- Log daily waste by weight and reason, then feed that data into the next order calculation so decisions reflect real loss rather than guesswork.
- Replace gut-feel ordering with seven-day item-level POS data to build accurate day-of-week forecasts and dynamic par levels that follow actual demand.
- Standardise portions, enforce FIFO and FEFO rotation, and negotiate supplier prices using automated invoice scanning to cut waste, lower food cost, and protect margins.
- Jelly automates invoice extraction, price alerts, live GP reporting, and POS integration so the seven-step ordering process runs continuously without extra admin, and you can book a demo to see how Jelly turns this system into a low-admin, high-control routine for your kitchen.
The Ordering-Quantity Formula for Every Perishable Line
Calculate order quantity as: (par level − current stock) + (forecast covers × average portion) − expected deliveries. Because demand patterns shift across the week, adjust this calculation daily using the previous seven days of sales mix and your waste log. This rolling window keeps orders aligned with current trends instead of outdated averages. When you apply the formula consistently, it prevents over-ordering while protecting service levels. Use it on every perishable line, every ordering cycle, without exception.
Worked Example: Chicken Breast Ordering Over Three Days
| Day | Item | Par Level (kg) | Current Stock (kg) | Forecast Covers | Order Quantity (kg) | Waste Logged (kg) |
|---|---|---|---|---|---|---|
| Monday | Chicken Breast | 12 | 4 | 60 | 8 | 0.4 |
| Tuesday | Chicken Breast | 12 | 3.6 | 55 | 8.4 | 0.3 |
| Wednesday | Chicken Breast | 12 | 4.1 | 70 | 7.9 | 0.2 |
Par levels come from historical daily usage, so they reflect real patterns rather than guesswork. Systematic par management that follows day-of-week patterns helps reduce pre-plate waste. Waste logged each day then feeds directly into the next cycle’s order calculation.
See how Jelly automates this formula across every ingredient line in your kitchen.
Step 1: Daily Waste Logging in Your Kitchen
Objective: Build an accurate daily record of what is discarded and why so ordering decisions rely on real loss data, not assumptions.
Action: Assign one team member per shift to record every item discarded, including spoilage, trim, over-prep, and plate returns, by weight and reason. Log entries at the end of each service instead of trying to reconstruct them at the end of the week.
Inputs required: A standardised waste-log template with columns for date, item, quantity, unit, reason, and cost, plus a kitchen scale accessible at the pass or prep station.
Success looks like: A complete daily waste log with no blank rows, reviewed by the head chef each morning before ordering begins. Sushi Revolution’s monthly stocktake using Jelly’s feature takes 5–20 minutes, down from 2–3 hours previously, so daily logging at that speed is realistic from day one.
Step 2: Sales-Based Demand Forecasting from POS Data
Objective: Replace gut-feel ordering with item-level sales data so prep quantities and purchase volumes follow actual demand.
Action: Pull the previous seven days of item-level sales from your POS system. Identify day-of-week patterns and adjust forecast covers for each day accordingly. Most food waste in restaurants does not come from ordering too much, it comes from prepping too much relative to actual shift volume, and anchoring prep quantities to a reliable daypart-level covers forecast reduces both physical waste and emergency reorders.
Inputs required: Item-level POS data. Jelly integrates natively with Square, EPOS Now, Lightspeed, and Toast via real-time API, pulling item-level sales the moment each transaction completes. Connecting any supported POS takes approximately five minutes.
Success looks like: A weekly forecast that is reviewed against actuals every Monday, with variance noted and fed into the following week’s par-level adjustment. Once you have reliable demand forecasts, the next step is turning those forecasts into clear inventory boundaries through minimum and maximum levels.
Step 3: Setting Min, Max, and Par Levels for Each SKU
Objective: Create a floor and ceiling for every ingredient so ordering decisions follow data instead of habit.
Action: Set a minimum safety stock and a maximum par level for each SKU based on lead time, day-of-week demand, and shelf life. Review par levels weekly for the first month while patterns settle, then move to monthly reviews once the data stabilises.
Inputs required: Seven to fourteen days of waste logs, sales history by day of week, and supplier lead times.
Success looks like: Restaurants that move from static to dynamic par levels see measurable food-cost reductions. Industry reports estimate that restaurants waste 4–10% of purchased food before it reaches a customer, and dynamic par management helps reduce these pre-plate waste levels.
Step 4: Matching Order Frequency and Size to Shelf Life
Objective: Align order cadence with shelf life so perishables arrive fresh and in quantities that will be used before spoilage.
Action: Split your ordering into two tracks based on shelf life, because perishables and dry goods need different ordering rhythms. For perishables such as proteins, dairy, and fresh produce, order small quantities frequently, ideally daily or every two days, to limit spoilage risk. For ambient and dry goods, consolidate into weekly or fortnightly bulk orders where storage costs allow, since these items hold their quality and larger orders reduce per-unit delivery costs.
Inputs required: Shelf-life data per SKU, current holding costs, and supplier minimum order values.
Success looks like: A 2020 ECR Retail Loss report analysing data from 27 stores of three European retailers found that shipping stores smaller quantities can reduce food waste while increasing on-shelf availability. For perishable goods, holding-related costs dominate, so frequent smaller orders are often the better choice. Industry estimates show that carrying costs often equal roughly 20–30% of total inventory value, including capital cost, warehousing, shrinkage, and spoilage.
Step 5: Enforcing FIFO and FEFO Rotation
Objective: Use the oldest and soonest-to-expire stock first so preventable spoilage from poor rotation disappears.
Action: Label every delivery with the date received and best-before date, then store new deliveries behind existing stock. For items with varying expiry dates within the same batch, apply FEFO, or first expired first out, so the item closest to its use-by date is always pulled first.
Inputs required: Date labels, a clear labelling protocol posted in the walk-in, and a short team briefing at each delivery.
Success looks like: FIFO implementation in restaurants reduces food waste by 30–50% by ensuring older inventory is used before newer deliveries. Kitchens without rotation systems can lose a significant portion of their food budget to preventable spoilage.
Step 6: Standardising Portions and Recipe Costs
Objective: Remove portion variance so every dish costs what the recipe states, and ordering quantities match real consumption.
Action: Build every dish in Jelly’s Cookbook using ingredients already populated from scanned invoices. Jelly handles unit conversions and calculates live dish cost automatically. Work that previously took 28 minutes per menu item in a spreadsheet now takes about three minutes in Jelly.
Inputs required: Standardised recipes with gram-level portion weights, a kitchen scale at every prep station, and Jelly’s Sales Mix report to highlight which dishes drive the most volume.
Success looks like: Standard recipes can lower food cost by 5–15%, and restaurants without fixed recipes lose an average of €15,000–€50,000 per year in hidden costs due to varying portions and ingredient use. Reducing portion sizes by 15% can boost profit margins by 2–4% while cutting food waste in half. With portions locked in, your recipe costs become predictable, so any supplier price increase directly threatens those margins. The final step uses invoice data to catch and challenge those increases before they erode profitability.
Step 7: Using Invoice Data for Supplier Negotiation
Objective: Turn every price movement into a negotiating opportunity instead of silent margin erosion.
Action: Jelly scans every invoice submitted by photo or email and extracts line-item prices automatically. When a supplier increases the price of an ingredient, Jelly’s Price Alert flags the change in real time, giving the head chef or operations manager the data needed to call the supplier, request a credit note, or switch to an alternative source.
Inputs required: Supplier invoices routed to Jelly via a dedicated email address or photographed on delivery, with no manual data entry required.
Success looks like: Amber restaurant in East London saves £3,000–£4,000 per month through credits, better buying, and tighter menu controls enabled by Jelly’s price change alerts and real-time costing. Chef-Owner Murat Kilic states: “Jelly keeps my business alive.”
Request a walkthrough of Jelly’s Price Alert feature to see how it surfaces every supplier price movement before it damages your margins.
Common Mistakes That Undermine This Ordering System
- Inconsistent portion data: When recipes are not built to gram-level accuracy in a single system, ordering quantities drift. A variance of 30 ml of sauce per cover across 1,000 covers per month creates meaningful untracked cost.
- Missing supplier price changes: Last-minute supplier runs due to poor inventory rotation cost restaurants 20–30% more than planned purchases. Silent price creep compounds this further when invoices are not scanned and compared line by line.
- Over-ordering for events: Event-driven ordering without a specific forecast adjustment inflates par levels temporarily and leaves perishable surplus after the event. Build a separate event forecast using confirmed covers and revert par levels the following day.
Measuring Success of Your New Ordering Process
Track three metrics weekly from the moment the system goes live.
- Weekly waste percentage: Calculate value of wasted food divided by total food purchases, then multiply by 100. A downward trend over four to eight weeks confirms that the ordering system is working.
- Admin hours saved: Measure time previously spent on manual invoice entry, price checking, and stocktaking. Jelly users consistently report saving 10–20 hours of admin per month.
- Gross profit margin: Use Jelly’s Flash Report to see daily GP calculated from invoice costs and POS sales. A sustained upward movement in GP, even one to two percentage points, represents significant annual profit at £500k or more in revenue.
Scaling to 2–5 Sites with Live POS Integration
Single-site discipline creates the foundation for multi-site consistency. Once par levels, waste logs, and portion standards are embedded at one location, Jelly centralises forecasts and standardises ordering across additional sites from the same platform.
For multi-location restaurant groups, centralising forecasts and standardising ordering across all stores creates consistency and control, allowing regional managers to focus on coaching staff rather than spreadsheets. Each site retains the location-specific par levels established in Step 3, which account for different sales patterns at each restaurant, while the operations manager sees consolidated GP and spending data across all locations in one view.
Jelly’s POS integrations with Square, EPOS Now, Lightspeed, and Toast deliver item-level sales data the moment each transaction completes, so forecasts update in real time without manual exports or reconciliation. Sushi Revolution used Jelly to set separate target gross profits on dine-in and delivery menus, accounting for 30% delivery commissions, which resulted in actual gross profits 2–3% higher on average and a discipline that scaled directly to their second site.
How Jelly Automates Every Step of This System
Every step in this guide generates data, and without automation that data sits in separate spreadsheets, WhatsApp messages, and paper delivery notes. Jelly connects these inputs into a single, continuously updated system.
- Invoices are photographed on delivery or emailed directly to Jelly, and every line item, including quantity, SKU, price, and tax, is extracted automatically and updates ingredient costs across all linked recipes in real time.
- Price Alerts flag every supplier price movement in the same week it occurs, giving operators the evidence needed to negotiate credits or switch suppliers before the margin impact compounds.
- The Flash Report delivers a daily view of gross profit margin calculated from actual invoice costs and live POS sales, so you do not wait for a monthly accountant’s report to discover a problem.
- The Sales Mix report, powered by POS integration, shows which dishes are most popular and most profitable, giving you the two inputs needed to refine portion standards and par levels at the same time.
Jelly charges a flat rate of £129 per month per location, with no per-user fees and no variable charges. Onboarding delivers initial value within the first week.
Frequently Asked Questions
Who owns the data when using Jelly?
Your data remains yours. Jelly processes invoice and sales data on your behalf to generate insights, but operators retain full ownership of all information entered into or generated by the platform. You can export your data at any time, and Jelly does not sell or share your operational data with suppliers or third parties.
How quickly can a single site implement the full ordering system?
Most single-site operators see initial value within the first week. The POS connection mentioned in Step 2 is live within minutes of setup. Once suppliers begin sending invoices to a dedicated Jelly email address, or the team starts photographing invoices on delivery, Price Alerts and spending insights are live within 24 hours. Building out the full Cookbook with standardised recipes typically takes one to two weeks depending on menu size, after which live dish costing and GP tracking are fully operational.
How do multi-site teams keep ordering consistent?
Jelly centralises invoice processing, recipe costing, and GP reporting across all locations in a single platform. Operations managers and finance managers can view consolidated spending and margin data across every site without relying on individual chefs to compile reports. Each site maintains its own location-specific par levels and forecasts, but all data flows into the same system, which removes the spreadsheet drift that usually causes ordering inconsistency between sites.
What happens during seasonal events or sudden menu changes?
For planned events, build a separate event-specific forecast using confirmed covers and adjust par levels for that period only, then revert to standard levels the following day. For sudden menu changes such as a supplier outage, a dish removal, or a new special, Jelly’s Cookbook allows recipe updates in minutes. Because ingredient costs are pulled directly from scanned invoices, any new ingredient added to a recipe is costed automatically from the first delivery, and Price Alerts flag any price movement on new ingredients from the moment they enter the system.
Conclusion: Turning Seven Steps into a Repeatable System
Reducing restaurant food waste through smarter ordering comes from a system of seven interlocking steps, not a single action. Daily waste logging, sales-based forecasting, dynamic par levels, frequency-matched ordering, FIFO and FEFO rotation, standardised portions, and invoice-driven supplier negotiation all depend on accurate data from the previous step.
The main barrier for most operators is not understanding the system, it is sustaining it without adding administrative burden to an already stretched team. Jelly removes that barrier by automating invoices, costs, price alerts, and GP reporting so the system runs continuously without manual intervention.
Operators using Jelly cut food costs by an average of 3% in the first three months and save 10–20 hours of admin per month. Gross margins improve by an average of two percentage points, and the ordering system described in this guide becomes sustainable because the data it relies on is always current, accurate, and visible.
Book a demo to see this ordering system in action and discover how Jelly turns it into a low-admin, high-control routine for your kitchen.
