Par level inventory explained (with a worked example and template)

Par level inventory is a fixed floor for each SKU: when stock on hand drops to the par level, you order enough to restore a set top-up quantity. It comes from bars and restaurant kitchens — every well has a par of bottles, and every shift restocks to it — and it's the simplest replenishment rule in retail. Order quantity is usually a fixed amount per SKU (a case, a week of sales), decided once, not recalculated.

The short version for a Shopify merchant: par levels work when supply is fast and demand is steady; they break when lead times are long. This article gives the par level meaning in operational terms, a worked example, a par level template you can copy into a spreadsheet, and the honest comparison with a full reorder point.

The par level meaning, precisely

A par level is the minimum quantity of a SKU you refuse to fall below. When on-hand stock touches par, you replenish — usually by a fixed quantity, back to a comfortable working level.

Two numbers define it:

• Par (the floor). Enough stock to cover demand during the replenishment wait, plus a small buffer.
• Top-up (the fixed order). The amount you order each time. Often one case pack, one week of sales, or whatever your supplier's minimum order quantity makes sensible.

The floor is the load-bearing number. The top-up is a convenience — a fixed amount keeps ordering decisions trivial, which is the entire appeal of the method.

If this structure sounds familiar, it should: par level is min/max's cousin. The par is a min, the par-plus-top-up is a max. The differences are in scale and rhythm — par levels suit short cycles and local supply; full min max inventory systems are built for longer, formal buying cycles.

A worked par level example

Your store sells cold-brew concentrate, SKU CB-CONC-1L, at 3.5 bottles per day. Your supplier is a local roastery delivering in 4 days. You restock twice a week and want 2 days of buffer for delivery hiccups.

Step 1 — Demand during the wait.

3.5 × 4 = 14 bottles

Step 2 — Buffer.

3.5 × 2 = 7 bottles

Step 3 — Par level.

14 + 7 = 21 bottles

Step 4 — Top-up. You restock Mondays and Thursdays. Sales between checks run about 3.5 × 3.5 ≈ 12 bottles, so a top-up of 12 bottles (one case) restores your working stock comfortably.

Running it: on Monday morning you count 19 bottles. That's below par of 21, so you order 12. By Thursday you're at roughly 19 − 12 + 0 delivered... count again: sales Mon–Wed ≈ 10, so you're at 9. Below par, order another 12. The delivery cycle keeps you oscillating between about 9 and 21 bottles — never deep, never dark. Total investment on this SKU: roughly a case and a half on the shelf at any time. For a $14.99 bottle, that's about $315 of working inventory. A method you can run on a fridge whiteboard.

Par level template

Copy this table into your spreadsheet, one row per SKU:

Two rules for the template:

1. Velocity from in-stock days only. If the concentrate was unavailable for 5 of the last 30 days, dividing sales by 30 understates demand and quietly sinks your par below safety. The correction is covered in why velocity numbers lie during out-of-stock days.
2. The wait is real time, not quoted time. Even local suppliers slip. Measure order-to-received, not what the rep says — the method is in the supplier lead time guide.

Par level vs reorder point

They overlap heavily, and most "par level vs reorder point" discussions overstate the difference. Both are floors that trigger a replenishment. The real differences:

The practical rule: par levels are the short-lead-time version of the reorder point formula. When your supplier is four days away, a fixed top-up and a twice-weekly count are all the precision you need — a statistically derived reorder point would be precision theater. When your supplier is 40 days and a container away, the fixed top-up stops working: demand over 40 days is too large and too variable to cover with a habitual order size, and one missed count puts you months behind.

When par levels beat reorder points — and when they fail

Par levels fit:

• Local or domestic suppliers with lead times under roughly a week
• Steady, non-seasonal demand — consumables, staples, core range
• Products bought in natural units: cases, sleeves, trays
• Stores where the person counting is the person ordering

They fail when:

• Lead times are long. The buffer math gets fragile, and a fixed top-up can't absorb a 6-week supply gap. This is where most spreadsheet par systems quietly break — the par still gets counted, but the order behind it arrives weeks late.
• Demand spikes. A viral week or a promo blows through par and the fixed top-up in one cycle.
• Velocity is seasonal. A par set in summer starves you in December. Rework pars seasonally or move those SKUs to calculated reorder points.
• Counts don't happen. Par levels assume you actually check stock on the cadence the top-up assumes. Skip two counts on a fast mover and the floor is fiction.

Converting a par level into a proper reorder point

If a SKU outgrows its par — longer lead times, faster or more variable sales — the conversion is mechanical, and you already have half the inputs:

1. Replace the check cadence with the real lead time. Par used your wait of 4 days; a reorder point uses your true average, measured from PO records.
2. Recompute the trigger: daily velocity × real lead time + safety stock. For our concentrate, if the roastery slips to a real 6-day average with 3 days of buffer: 3.5 × (6 + 3) = 32 units instead of 21.
3. Decide quantity per order instead of defaulting to the fixed top-up — usually velocity × a target cover period, rounded to case packs. The quantity math is the same order-up-to logic used in min max inventory.

A quick diagnostic for which SKUs need converting: compare each SKU's current days of cover against its replenishment wait. Anything with cover below the wait is already living on borrowed time, par level or not.

Common questions

What does par level mean in inventory? The minimum quantity of a SKU you refuse to fall below. When stock on hand reaches par, you replenish — usually a fixed top-up amount. The method comes from bar and kitchen practice, where each item has a par that gets counted and restored every shift.

How do you calculate a par level? Par = daily units sold × (replenishment wait in days + buffer days). A SKU selling 3.5 bottles a day with a 4-day supplier wait and 2 days of buffer carries a par of 3.5 × 6 = 21 units. Compute the velocity from in-stock days only, or the par will sit too low.

What's the difference between par level and reorder point? Both are floors that trigger replenishment. Par levels pair with a fixed top-up quantity and suit short lead times and steady demand; reorder points pair with a calculated order quantity and suit longer lead times. The par math is simpler because the replenishment wait it must cover is short.

What is a good par level for a new product? One you'll adjust weekly for the first month: start with two weeks of expected demand as the floor and a one-week top-up, then reset from observed sales. New products have no velocity history, so treat the first par as a guess with a review date, not a calculation.

Can you use par levels in Shopify? Not as a native trigger — as of October 2026, the Shopify admin lets you track quantities and set up inventory counts, but there's no built-in setting that fires a replenishment order at a par level. Merchants run par systems in spreadsheets against Shopify quantities, or use inventory apps to watch the thresholds.

Next step

Build the template above for ten fast-moving staples with short lead times — those are the SKUs where par levels genuinely outperform heavier machinery. For anything with a supplier wait over two weeks, don't stretch the par; compute a proper reorder point instead using the reorder point formula, and keep the par spreadsheet for the shelf-stable core.