Reorder points, safety stock, and maximum stock: setting levels that hold up

Inventory & replenishment · 10 min read

Three fields decide most replenishment behaviour, and they are routinely set as if they were one field with three names. They are not. The reorder point answers when, safety stock answers how much uncertainty to absorb, and maximum stock answers how much is too much. Set each from its own job, then check which system is enforcing it — because Business Central and LS Central use the same words for noticeably different mechanics.

Three levels, three different jobs

In Business Central's own definition, a reorder point represents demand during lead time. When inventory is projected to pass below it, it is time to order more: stock keeps falling while the replenishment travels, and it might reach zero or settle at the safety stock level by the time the delivery arrives. Microsoft's best-practice guidance says to base the reorder point on the item's demand profile — if average demand is 100 units across a seven-day lead time, the reorder point can be set to 100 as a minimum.

Safety stock is the fluctuation buffer that sits underneath that calculation. The planning system monitors it through projected available inventory, and safety stock must always be available for unexpected demand. Guidance reserves it for items with large demand fluctuations, critical items, and items under service agreements — not as a blanket padding on every line. One interaction surprises people: if the Reorder Point field is left blank, the safety stock quantity also acts as the reorder point.

Maximum inventory is the ceiling. It only has meaning inside a policy or calculation that respects it, and it is the level that stops a trigger from becoming an overbuy. Alongside it sits safety lead time — a time buffer rather than a quantity buffer. Best practice puts it between 1D and 6D, at least one day so that supply planned to prevent a stock-out is available the day before it is needed, and longer for a new supplier until delivery performance is known. Note that it runs on the base calendar, so 14D is not necessarily two weeks.

The arithmetic underneath

The working formula is short: reorder point = expected demand during lead time + safety stock. Take an illustrative store item selling an average of 6 units a day with a 7-day vendor lead time. Lead-time demand is 6 × 7 = 42. If demand regularly swings by about two days' worth of sales, a safety stock of 12 covers the swing. The reorder point is then 42 + 12 = 54: order when the projected position falls to 54, expect to sell about 42 while waiting, and land near the 12-unit buffer rather than at zero. The order size is a separate decision — a fixed reorder quantity, or enough to refill to the maximum. With a maximum of 90, a refill at the trigger orders roughly 90 minus the projected position, before order modifiers such as minimum quantity, maximum quantity, and order multiple round it into something the vendor will actually ship. Treat the example numbers as arithmetic, not as settings: the inputs that matter are the item's own daily demand, its real lead time, and how much its demand actually swings.

How Business Central enforces the levels

Nothing is planned until a reordering policy exists on the Item Card: Fixed Reorder Qty., Maximum Qty., Order, or Lot-for-Lot. The first two are the inventory-planning policies, and they watch two different stock views — projected inventory (the gross level, carried forward by future supply and demand) monitors the reorder point and drives the Maximum Qty. quantity, while projected available inventory monitors the safety stock level. Planning also works in time buckets: demand events are collected over a period of at least one day, and if the reorder point is crossed inside the bucket, the new supply order is forward-scheduled from the end of the bucket. A weekly bucket mirrors how a buyer actually gathers one vendor's needs into one weekly order instead of reacting to every transaction.

Two safety valves deserve attention. The overflow level guards the ceiling: for Maximum Qty. it equals the maximum inventory (plus a minimum order quantity if one is set); for Fixed Reorder Qty. it equals reorder quantity + reorder point; an order multiple adjusts it for both. A planning line that would push projected inventory above the overflow level arrives as a warning with a Change Qty. (Decrease) or Cancel action rather than as a quiet overbuy. The emergency rule cuts the other way: if projected inventory goes negative — a future demand cannot be served at all — the suggested order covers the exact deficiency and deliberately ignores the maximum inventory, the reorder quantity, and the order modifiers, flagged with an Emergency warning. Maximum stock, in other words, is a ceiling for normal planning, not a promise the system will never break when the alternative is an unserved demand. Finally, per-location reality lives on the stockkeeping unit: the reordering policy and its parameters can be overridden per item and location on the SKU card, which is where a chain sets a busy store's levels differently from a quiet one's.

How LS Central enforces the same-named fields differently

In LS replenishment the fields sit on the item's Replenishment Control Data and feed the LS calculation types, and their jobs shift. The LS Reorder Point is a floor for a suggestion that already exists: if the calculation has found a demand and the suggested quantity is less than the reorder point, the system increases the quantity up to the reorder point — suggest 8 against a reorder point of 10, and the journal line becomes 10. The LS Maximum Inventory is a hard cap on the outcome: under the Stock Levels calculation type, stock is ordered up to the maximum once on-hand falls below the reorder point — maximum 20, reorder point 10, on hand 8, order 12 — and under Average Usage or Manual Estimate a calculated demand of 30 with a maximum of 20 still produces an order of only 12, because post-receipt stock cannot exceed the maximum. A maximum of 0 removes the cap. Stock Levels itself is the static method: fixed reorder point and maximum values identify the demand, which suits slow movers and defined display stock; under the history-based types the same fields act as guardrails on a forecast instead.

The practical warning writes itself: a level tuned in one system and copied into the other keeps the number and loses the meaning. A reorder point of 10 in Business Central fires an order process; the same 10 in LS quietly inflates small suggestions — useful for display stock, wrong for a slow line that should order 3.

Setting levels that hold up: a procedure

1. Start from clean demand and lead-time data. Use the item's actual average daily sales and the vendor's real lead time, including any lead-time calculation the LS side applies. Levels computed from guessed inputs fail politely and repeatedly — clean data is the precondition, and anything unknown should be cleaned up before it is entered, not after the journal exposes it.
2. Set the reorder point as lead-time demand first. Daily demand times lead time, before any buffer. In Business Central, check the demand-profile example: 100 units of demand across the lead time means a reorder point of at least 100.
3. Add safety stock only where fluctuation justifies it. Volatile sellers, critical lines, and service-agreement items earn a buffer; steady lines get a small one or none. Remember the blank-reorder-point trap: in Business Central, safety stock alone becomes the trigger.
4. Set the maximum from physical and commercial reality. Shelf or bin capacity, case and multiple sizes, and how much stock the store can sell before the next cycle — then confirm the maximum sits above reorder point plus a sensible order quantity, or every suggestion will fight the cap.
5. Align the modifiers. Minimum order quantity, maximum order quantity, and order multiple (purchase and transfer multiples on the LS side) round the suggestion; make sure the rounded result still respects the maximum.
6. Assign per location where locations differ. SKU overrides in Business Central, item store records in LS. One chain-wide level for a flagship and a kiosk is two wrong levels.
7. Run, review, and sanity-check the first suggestions. In Business Central, Calculate Plan in the requisition or planning worksheet; in LS, the replenishment journal. Every line should be explainable from the three levels. What success looks like: no emergency lines on ordinary items, no overflow warnings on the first run, and no suggestion that exceeds the maximum without a stated reason.

When the levels stop working

Levels are perishable. A supplier change quietly lengthens lead time and the reorder point that covered seven days now covers five days of a ten-day wait. A promotion lifts daily demand and nobody lifts the maximum, so the cap trims every peak suggestion back to ordinary. A seasonal swing arrives and a level set for a normal month is simply the wrong level — that case has its own playbook in the seasonality guide. And the silent failure beats them all: an item with a blank reordering policy is considered not planned, so Calculate Plan produces nothing for it at all — no error, no line, just an item quietly drifting to an empty shelf. Review levels on a cadence — monthly for fast lines, quarterly for the tail — and on every trigger event: new vendor, lead-time change, range change, or a stock-out on an item whose levels claimed it was protected.

FAQ

Is the reorder point the quantity to order? No. It is the trigger level in Business Central and a suggestion floor in LS. The order quantity comes from the policy — a fixed reorder quantity, a refill to maximum, or the calculated demand.

Can safety stock replace a reorder point? In Business Central, partially: with the Reorder Point field blank, the safety stock quantity acts as the reorder point. That is a fallback behaviour, not a design — a deliberate reorder point set from lead-time demand is easier to reason about and to review.

Why did an order exceed the maximum? In Business Central, check for an emergency line: projected negative inventory produces an exact-deficiency order that ignores the maximum by design. In LS, check whether the maximum was 0 — that disables the cap — and whether a reorder point or a multiple rounding lifted the line.