Written by: JJ Tan, Founder, Jelly
Key Takeaways
- Par levels are the target stock quantity needed at the start of each trading period. They use average daily usage, lead time and safety stock to reduce both stockouts and excess inventory.
- Accurate par setting depends on correct data entry for Par/Max, Reorder Point/Min, inventory unit, pack size, supplier, lead time and order frequency in your inventory software.
- UK operators should review lead times quarterly and adjust pars immediately after menu changes, supplier switches or confirmed delivery schedule changes because supply chain risks remain high.
- Multi-site groups need site-specific pars driven by each location’s own sales mix and usage data, with weekly reviews for high-value ingredients and monthly reviews for the rest.
- See how Jelly automates invoice scanning and multi-site par management at a flat rate of £129 per location.
Before You Begin
Gather these items before opening your inventory software so the setup runs quickly and accurately.
- Current supplier invoices, or digital access to them, including pack sizes and unit-of-measure data per ingredient
- Supplier lead times and confirmed delivery days for each supplier
- POS sales data or sales mix reports covering the last four to six weeks
- Recipe cards with gram weights per ingredient per dish
- A recent stocktake count
Ownership matters because par setting spans two roles. The head chef or kitchen manager usually owns the day-to-day par values. The owner, operations manager or finance manager owns the review cadence and cross-site consistency. Both roles depend on the same unit and pack-size data, so they must agree those fields for every ingredient before setup begins. Bad unit data at this stage corrupts stocktakes for months.
Initial setup takes a few hours per site. After that, expect a recurring weekly review of 15–30 minutes for high-value ingredients. The process runs faster when invoices are already digitised, because ingredient costs and pack sizes populate automatically instead of being typed in manually.
Watch Jelly digitise your invoice line items so pack sizes and costs stay current without manual entry.
Why This Process Matters
Pars that are too low cause mid-service stockouts and emergency supplier runs. Food waste accounts for 4–10% of purchases industry-wide, and well-set par levels can cut inventory carrying costs by 20–30%. Pars that are too high tie up working capital. A kitchen carrying 20% excess inventory on a $50,000 monthly food spend has $10,000 tied up in stock that sits in storage longer than needed.
Correct par levels give you margin visibility and consistent control across locations. They also reduce manual order errors and strengthen supplier oversight, because every order uses the same usage data. That accuracy makes stocktakes more meaningful. When suggested orders are accurate, the gap between theoretical and actual usage narrows, and variance becomes a genuine signal rather than noise.
UK supply chain conditions make conservative par settings and regular reviews essential. The UK National Audit Office’s September 2026 report on food supply chain resilience found that disruption to food supply can lead to food price inflation, reduced consumer choice, increased operating costs and disrupted operations for businesses. The Food Standards Agency recorded 2,073 food and feed safety incidents in 2025/26, a 14% increase on the previous year, with further disruption expected from geopolitical instability and climate change. Defra’s Agriculture in the United Kingdom 2025 estimates the UK food production to supply ratio at 60% for all food, with extreme import dependence for some produce categories, such as tomatoes at 17% and fresh fruit at 14% of domestic supply. These conditions mean lead times behave as moving values that need at least quarterly review.
Step-By-Step: Setting Par Levels In Your Inventory Software
Follow these steps in order. Each step maps directly to a field or set of fields in your inventory software.
- Work Out Usage Per Ingredient Per Delivery Cycle. Pull POS sales mix or usage data for the last four to six weeks. Convert recipe usage into the inventory unit, such as kg, litre or each, for every ingredient. Average daily usage can be measured three ways, in decreasing order of accuracy: recipe data multiplied by POS menu mix (theoretical usage); stock count history (opening stock plus deliveries minus closing stock); and order history (total quantity ordered over eight weeks divided by 56 days). The output of this step is a usage figure per ingredient per delivery cycle based on data rather than guesswork.
- Apply The Par Level Formula. The formula is:
Par Level = (Average Daily Usage × Lead Time in Days) + Safety Stock
Average Daily Usage is how much you use per day. Lead Time is the number of days between placing an order and receiving usable stock. Safety Stock is the buffer for demand spikes, late deliveries and rejected products.
Worked UK example: a dish uses 2.4 kg of chicken per day. The supplier delivers twice a week, giving a delivery cycle of 3.5 days. Lead time is 2 days. Safety stock is one day’s usage (2.4 kg), which suits a standard fresh protein. The calculation is:
Par Level = (2.4 kg × 2 days) + 2.4 kg = 4.8 kg + 2.4 kg = 7.2 kg
The supplier sells chicken in 10 kg cases. Divide the par level by the case size: 7.2 ÷ 10 = 0.72 cases. Round up to 1 case (10 kg). That value becomes the Par/Max expressed in cases. Calculated order quantities must be rounded to supplier pack sizes, and the rounded quantity must still be checked against practical storage and expiry limits.
- Set The Par/Max Field. Enter the par level in the inventory unit. In the chicken example, that means 10 kg, which equals one case. Because Par/Max is the ceiling the system orders up to rather than the amount you order each time, you also need to confirm the pack-size field will order whole cases instead of fractions. Ordering the Par/Max value instead of ordering up to it causes excess stock to build up every cycle.
- Set The Reorder Point/Min Field. The Reorder Point/Min is the trigger that tells the software when to flag a reorder. Set it below Par/Max, based on lead-time usage plus safety stock. The logic is simple: count stock, compare with Min, and if stock sits at or below Min, order up to Max. The minimum level acts as the reorder trigger, so when on-hand stock touches or falls below it, the item is flagged for replenishment. Setting Par/Max and Min to the same number breaks ordering because the system only triggers when stock hits the trigger point and then has no gap to refill.
- Set Unit And Pack Size Correctly. This step prevents most bad suggested orders. Enter the inventory unit, such as kg, litre or each, separately from the purchase unit, such as 10 kg case, 12 × 750 ml case or 20 L drum. If a system treats a 5 kg case as a single stock unit, 40 kg of real usage reads as 8 units, understating consumption by about 80%, and theoretical stock stays high while the shelf tells a different story. The table below shows how the same ingredient can have a different inventory unit and purchase unit, which is the mismatch that causes most bad suggested orders. Use it to check your own setup:
| Ingredient | Inventory Unit | Purchase Unit | Pack Size |
|---|---|---|---|
| Chicken breast | kg | Case | 10 kg |
| Chips (frozen) | kg | Case | 12.5 kg |
| Cooking oil | litre | Drum | 20 L |
| Plain flour | kg | Sack | 16 kg |
- Add Supplier, Lead Time And Order Frequency. Assign each ingredient to a supplier. Enter the lead time in days as the actual measured time from order to shelf, not the distributor’s quoted transit time. Set the order frequency to match your confirmed delivery days. Given the NAO’s September 2026 finding that UK food supply chain disruption risks are rising, lead time fields should be reviewed quarterly rather than set once. The UK Department for Business and Trade’s 2025 payment statistics note that payment terms and physical replenishment lead times are distinct and should be configured as separate fields in supplier records.
- Review The First Suggested Order Before Sending It. Compare the software’s suggested order against your own rough calculation from step 2. The suggested order should cover usage until the next delivery without over-ordering whole cases. If the numbers diverge significantly, the most likely cause is a unit or pack-size mismatch in step 5. Correct the field rather than overriding the order.
Walk through Jelly’s par level fields with our team and see these steps inside the software.
Par Level Vs Reorder Point
Now that you have entered both fields, it helps to clarify exactly what each one means, because these values are often confused. These two terms describe different things and must be entered as different values in your software.
The par level (Par/Max) is the target stock level, meaning the quantity you want on hand after a reorder is received. The reorder point (Reorder Point/Min) is the trigger that tells the software to act. Safety stock is the floor you protect, the reorder point is the trigger that makes you act, and the par level is the ceiling you refill to.
The operational rule is simple: count stock, compare with Min, and if stock sits at or below Min, order up to Max. The order quantity equals Max minus current on-hand stock rather than the Max value itself.
Setting Par/Max and Min to the same number is a common configuration error. If both sit at 10 kg, the system triggers an order the moment stock hits 10 kg and then orders up to 10 kg, which means it either orders nothing or triggers constantly depending on how the software interprets the condition. Max par is usually reorder point plus your standard order quantity. Keep a meaningful gap between the two.
The 80/20 Rule And Minimum Inventory Level
The 80/20 rule in inventory, also called the Pareto principle, states that roughly 80% of your stock value and usage comes from 20% of your ingredients. In ABC analysis, A items are roughly the top 20% of items driving about 80% of value and require tight control, frequent review and accurate forecasting; B items are around 30% of items and 15% of value; C items are about 50% of items but only 5% of value.
In practice, identify your top 20% of ingredients by spend, typically proteins, seafood and premium produce. Set and review their pars tightly every week. Use looser, simpler pars for the long tail of dry goods, condiments and packaging, reviewed monthly.
The minimum inventory level uses the same formula you applied in step 2, which multiplies average daily usage by lead time and then adds safety stock. This value feeds the Reorder Point/Min field in step 4. Under an order-up-to-Max replenishment policy, the order quantity when the Min level is reached equals Max minus current on-hand stock.
The 80/20 rule also shows when a spreadsheet stops being enough. Excel can handle a single site with a small menu. It cannot provide live invoice updates, automatic unit conversion, POS-linked sales mix or multi-site roll-up. Software becomes the more practical choice when an operator runs more than one location, spends more than two hours per week on inventory administration, or needs real-time rather than end-of-month food cost data.
How To Set Par Levels Across Multiple Sites
Each site has a different sales mix, so the same ingredient needs a different par at each location. A site with a strong weekend brunch trade needs a higher egg and bread par than a site focused on evening covers. A location near offices needs higher lunch inventory on weekdays. A residential-area site needs more product for dinner and weekends. A location with limited cooler space may need smaller, more frequent deliveries rather than a higher par.
In software, use the same ingredient and supplier records across all sites, and enter separate Par/Max and Reorder Point/Min values per location driven by that site’s own usage data. Multi-unit operators often wrongly copy the same pars to every store, even though each location has different sales patterns, storage constraints and product movement.
Apply the same weekly and monthly cadence described in the 80/20 section for multi-site groups, and review pars immediately after any menu change, supplier switch or confirmed lead-time change.
Running site-specific pars manually across multiple locations is where most groups struggle. Jelly is built to run site-specific pars across a group. It starts with the invoice, where every line item is scanned automatically so ingredient costs and pack sizes populate from real data instead of manual entry. That data feeds the POS integrations with Square, Lightspeed, EPOS Now and Toast, which push real-time sales mix into dish costing so usage figures reflect what each site actually sells. Setup takes about five minutes across all four systems. Jelly’s POS-to-dish linking only surfaces items sold since the integration was connected. This keeps mapping clean and free of legacy menu clutter. From there, Price Alert flags every supplier price change, giving chefs evidence for negotiations before margins slip. All of this runs at a flat £129/month per location, with onboarding in the first week.
Jelly users cut food costs by 3% on average in the first three months, and gross margins increase on average by 2 percentage points in the same period. One operator improved gross profit from 65% to 72% within 12 weeks on approximately £500,000 in revenue.
See how Jelly manages site-specific par levels across a multi-site group and keeps every location aligned.
Common Mistakes And How To Fix Them
- Mixing Inventory Units And Purchase Units. This happens when you record usage in kg but enter the pack size as a single case without a conversion factor. Fix: enter both the inventory unit, such as kg, and the purchase unit, such as 10 kg case, as separate fields and confirm the software converts between them.
- Setting Par/Max And Min To The Same Number. This configuration causes either constant ordering or no ordering. Fix: set Min at lead-time usage plus safety stock, and set Par/Max above that by at least one order quantity.
- Ignoring Lead-Time Changes. A supplier that moves from two-day to four-day delivery doubles the lead-time component of the par formula. Fix: review lead-time fields quarterly and after any supplier communication about delivery schedule changes.
- Using Last Year’s Usage Data After A Menu Change. Pars built on a previous menu will be wrong for the current one. Fix: recalculate usage from POS data after every menu update.
- Forgetting Wastage And Yield In Recipe Costing. Ten kg of beef going into a slow-braised dish might yield 6.8 kg after a 68% yield, understating the true portion cost by roughly a third if yield is ignored. Fix: enter yield percentages in recipe cards and confirm the software applies them to usage calculations.
- Over-Ordering Because Pack Size Rounds Up. A calculated requirement of 7.2 kg rounds to one 10 kg case, leaving 2.8 kg of buffer beyond the par. Fix: check that storage capacity and shelf life can absorb the rounded quantity before confirming the par.
- Skipping Par Reviews After A Supplier Switch. A new supplier may use different pack sizes or have a different lead time. Fix: update Pack Size, Supplier and Lead Time fields immediately when a supplier changes.
How To Measure Success
Correctly configured par levels produce measurable operational improvements. Suggested orders begin to match real usage. Stockouts fall. Dead stock and waste fall. Stocktakes reconcile more closely to theoretical usage.
Track these directional indicators to see whether your par setup works.
- Emergency supplier runs per week, measured as a simple count before and after par setup. A falling number shows that pars cover demand.
- Time spent manually building orders, measured in weekly minutes. This should drop as suggested orders become reliable.
- Invoice discrepancies at delivery, counted as mismatches between delivered and invoiced quantities. Fewer discrepancies indicate cleaner supplier and unit data.
- GP visibility per dish, checked by whether you can see gross profit per dish without waiting for month-end. This visibility should become immediate.
Jelly’s Flash Report provides a daily, weekly or monthly view of gross profit margin calculated from invoice costs and POS sales, so the impact of correct par levels on GP appears without waiting for a monthly accountant’s report. See the Flash Report and Price Alert in action and connect them to your own data.
Advanced Tips And Next Steps
Once par levels are stable, connect them to live dish costing. When a supplier price rise is flagged by Price Alert, Jelly immediately shows which dishes have dropped below their target GP margin. That visibility lets you make repricing decisions from data rather than instinct.
Use sales mix and menu engineering data to decide which dishes justify tighter pars. High-volume, high-margin dishes warrant the tightest par control because a stockout on those items has the greatest revenue impact.
Connect POS and accounting so invoice data flows into Xero, with Sage integration coming soon. This link reduces bookkeeping time by about 90% and keeps food cost data current instead of end-of-month.
Several adjacent tasks become easier once pars are correctly configured. These include supplier price negotiation using Price Alert data, delivery menu costing with commission factored in, and multi-site GP reporting via the Flash Report.
Frequently Asked Questions
What Is The Difference Between Par Level And Reorder Point?
The par level (Par/Max) is the target stock quantity you want on hand after a reorder is received, which acts as the ceiling you order up to. The reorder point (Reorder Point/Min) is the stock quantity that triggers a new order, which acts as the floor where the software flags that replenishment is needed. The order quantity is the difference between the par level and current on-hand stock. Setting both to the same number breaks the ordering logic.
How Often Should I Review Par Levels?
Review high-value ingredients such as proteins, seafood and premium produce weekly. Review dry goods, condiments and packaging monthly. Review all pars immediately after a menu change, a supplier switch or a confirmed change in delivery lead time. As noted earlier, UK supply chain disruption makes quarterly lead-time reviews a minimum requirement.
Should Par Levels Be The Same Across All Sites?
Par levels should differ by site. Each site has a different sales mix, storage capacity and delivery schedule. A site with strong weekend brunch trade needs a higher egg and bread par than a site focused on evening covers. Use the same ingredient and supplier records across all sites, and enter separate Par/Max and Reorder Point/Min values per location driven by that site’s own POS usage data.
What Happens If My Pack Size Changes?
Update the Pack Size field in your inventory software immediately. A pack size change affects the rounding step in the par formula. A supplier moving from 10 kg to 12.5 kg cases changes how many cases the software suggests ordering. Failure to update the field produces suggested orders that are wrong by the difference between the old and new pack size, and that error compounds across every order cycle until corrected.
Can I Set Par Levels Without A POS Integration?
You can set par levels without a POS integration, but the usage figures behind the par formula become less accurate. Without a POS integration, average daily usage must be calculated from stock count history or order history, both of which are less precise than recipe-level theoretical usage derived from actual sales mix. A POS integration automates the usage calculation and keeps it current as the menu mix changes, which matters especially for multi-site groups where manual data collection across locations does not scale.
How Do I Handle Seasonal Menu Changes?
Recalculate usage figures from POS data for the new menu before the seasonal change takes effect. Update Par/Max and Reorder Point/Min fields for any ingredient whose usage changes materially. For ingredients that drop off the menu entirely, set their par to zero or archive them to prevent the software from generating unnecessary suggested orders. For new ingredients, begin with a conservative par based on estimated usage and adjust after two to four weeks of actual sales data.
What If My Supplier Lead Time Changes?
Update the Lead Time field in your inventory software immediately and recalculate the Reorder Point/Min for every ingredient supplied by that supplier. A lead time extending from two days to four days doubles the lead-time component of the minimum inventory level formula, so the trigger point must be set higher to avoid stockouts during the longer resupply window. Review lead-time fields quarterly as standard practice and after any supplier communication about delivery schedule changes.
Conclusion
Setting par levels correctly follows a repeatable, software-driven process. Calculate usage from real POS data, apply the par level formula, enter Par/Max and Reorder Point/Min with accurate units and pack sizes, assign supplier lead times, and review weekly for high-value ingredients.
Operators who maintain control as they scale treat pars as a living number, adjusting them after every menu change, supplier switch and lead-time update. Done correctly, the result is a kitchen where suggested orders match real usage, stockouts fall, dead stock falls and GP is visible in real time rather than at month end. Jelly automates the invoice scanning, dish costing and POS integration that make this possible across multiple sites, at the same flat per-location rate mentioned earlier, with onboarding in the first week.
See how Jelly sets, maintains and reviews par levels across every site in your group and keep control as you grow.
