How to Set Reorder Points and Safety Stock for a Small Business

Running out of a popular item feels like a sales problem, but it is usually an inventory-system problem that began days or weeks earlier. The opposite problem is just as expensive: shelves full of products that are not moving, cash trapped in slow stock, emergency markdowns, and purchase orders placed because someone “felt” inventory was getting low. A practical reorder-point system replaces those guesses with a repeatable rule for when to buy again and a separate rule for how much uncertainty you want to absorb.

This guide shows small retailers, ecommerce sellers, wholesalers, makers, and service businesses with stocked parts how to build that system without pretending you have perfect forecasting software. You will start with clean item data, measure real demand and lead time, calculate a basic reorder point, add safety stock only where it is justified, account for minimum order quantities and seasonality, and then test whether the rule works in the real world. The aim is not mathematical elegance. The aim is to place replenishment orders early enough to protect sales while avoiding unnecessary inventory.

Quick definition: a reorder point is the inventory position at which you should trigger a replenishment order. In its simplest form, it equals expected demand during the replenishment lead time plus a safety-stock buffer. Oracle’s inventory documentation describes reorder-point planning in essentially the same way: projected available inventory is compared with safety stock plus forecast demand during replenishment lead time. Microsoft’s Business Central documentation likewise treats the reorder point as the demand expected during lead time. Those definitions matter because they prevent a common mistake: treating the reorder point as the quantity you should order. It is a trigger, not an order size.

Organized storage makes stock counts and replenishment decisions easier to verify. Photo by Shixart1985, CC BY 2.0, via Wikimedia Commons.

1. Separate the four inventory questions before you calculate anything

Inventory conversations become confusing when four different decisions are mixed together. Before opening a spreadsheet, give each question its own field or rule.

• How much do we normally use or sell? This is demand.
• How long does replenishment actually take? This is lead time.
• How much uncertainty do we want to protect against? This is safety stock.
• How many units should we buy once the trigger is reached? This is order quantity.

The reorder point answers only one of those: when to reorder. A business can have a perfectly reasonable reorder point and still overbuy because its order quantity is too large. It can also order a sensible quantity too late because the trigger is too low. Keeping the decisions separate lets you diagnose the real failure.

For example, imagine a shop that sells an average of 12 filters per day. The supplier normally takes 8 days to deliver. Expected demand during that lead time is 96 filters. If the shop wants 30 units of safety stock, its basic reorder point is 126 units. Reaching 126 does not mean “buy 126.” It means “start the purchasing process now.” The quantity ordered could be 100, 240, one supplier carton, or another amount based on economics and purchasing constraints.

How to verify this step: look at your inventory sheet or software and ask whether the reorder trigger and order quantity are stored as separate fields. If one number is being used for both purposes, fix that before continuing.

2. Build a clean SKU list instead of calculating from messy names

A reorder formula is only useful if every item refers to one real, countable stock-keeping unit. Small businesses often discover that their “inventory problem” is actually a product-master problem: the same item appears under multiple names, sizes are combined, bundles consume components without recording them, discontinued products still look active, or purchase units do not match selling units.

Create one row per SKU and include, at minimum:

• SKU or internal item code;
• plain-language item name;
• selling unit, such as each, pair, box, kilogram, or meter;
• purchase unit and conversion factor;
• primary supplier;
• supplier item number;
• normal case pack or order multiple;
• minimum order quantity if any;
• current on-hand quantity;
• open purchase-order quantity;
• backorders or committed quantity;
• current unit cost;
• whether the SKU is active, seasonal, new, clearance, or discontinued.

If you purchase a carton of 24 but sell individual units, convert everything to the selling unit before doing demand calculations. Otherwise, one person will think “10” means ten cartons while another thinks it means ten pieces. That kind of unit mismatch can create a 24-fold ordering error without any formula being technically wrong.

Bundles deserve special attention. Suppose a gift set consumes one mug, two tea sachets, and one box. If sales record only the gift-set SKU while component inventory is not relieved automatically, the system will overstate the components. Your reorder point then reacts to fiction. Either configure the bill of materials correctly or record component usage through a consistent manual process.

Common mistake: calculating reorder points for every item in a catalog before cleaning inactive and duplicate SKUs. Start with active inventory that actually consumes cash and shelf space.

3. Use inventory position, not just what you can see on the shelf

The number that triggers replenishment should usually reflect inventory position, not merely physical on-hand stock. A simple practical version is:

Inventory position = on hand + on order − committed/backordered demand

Why does this matter? If you have 40 units physically present and 100 more already confirmed on a purchase order, placing another order because “stock fell below 50” could create unnecessary overstock. Conversely, if you have 80 on hand but 60 are already committed to customer orders, the effective position is much lower than the shelf count suggests.

Different software systems define projected inventory and available-to-promise quantities in different ways, so use the terminology of your platform, but document exactly what your trigger watches. Microsoft’s Business Central documentation, for example, discusses projected inventory crossing the reorder point rather than looking at one isolated shelf count. The general operating principle is the same: replenishment should consider supply already coming and demand already committed.

Practical test: pick five recent purchase orders. Reconstruct what the buyer believed inventory was at the moment each order was placed. If incoming POs or committed orders were invisible, your replenishment process is making decisions with incomplete information.

4. Measure demand from transactions, not memory

The most useful demand number is not “what we usually sell” in someone’s head. It is a documented rate calculated from a defined period.

For a stable item, a simple starting point is:

Average daily demand = units sold or consumed during the measurement period ÷ number of operating days in that period

If you sold 900 units over 90 operating days, average daily demand is 10 units. If your business sells every calendar day, calendar days may be easier. If you are closed weekends and suppliers also operate on business days, using operating days can make the model clearer. What matters is consistency between the demand period and the lead-time period.

Do not blindly use revenue instead of units. Reorder points need physical demand. A price increase can raise revenue while unit demand falls. Similarly, do not mix returns, replacements, samples, internal consumption, and sales without deciding whether each event should reduce inventory. If a free sample physically leaves the shelf, it still contributes to consumption even though it may not count as a sale.

Choose a measurement window that matches the product

A 12-month average can hide a fast-growing item. A 14-day average can overreact to a temporary promotion. Choose a window deliberately.

• Stable everyday items: 8 to 13 weeks can be a practical starting window.
• Fast-changing products: compare recent 4-week and 12-week averages instead of relying on one.
• Seasonal items: use comparable seasonal periods rather than a full-year average.
• Slow movers: weekly or monthly demand may be more meaningful than daily demand.
• New products: start with a temporary planning assumption and review frequently because historical demand does not exist yet.

How to check for distortion: graph weekly unit demand. If one promotion, one wholesale order, or one stockout creates a dramatic spike or drop, annotate it. You do not always remove unusual demand, but you should know it is unusual before it influences the rule.

5. Correct demand history for stockout days

This is one of the most important improvements small businesses can make. Sales history records what customers were able to buy, not always what they wanted to buy.

Imagine an item normally sells 10 units per day but was out of stock for 12 days in a 60-day period. Recorded sales might be only 480 units. Dividing 480 by 60 gives 8 units per day, making the product look slower precisely because inventory management failed. A new reorder point based on that depressed average can repeat the stockout.

When possible, mark stockout periods and use one of these approaches:

• calculate average demand only across days when the item was actually available;
• estimate lost demand from comparable periods;
• use wait-list, backorder, or page-traffic information as supporting evidence;
• for stores with substitution, examine whether a related SKU spiked while the primary SKU was unavailable.

Do not invent lost sales with false precision. If you cannot estimate reliably, flag the SKU as “history constrained by stockouts” and give it more frequent review. The purpose is to avoid learning the wrong lesson from incomplete data.

6. Measure actual supplier lead time from order date to usable stock

Lead time is commonly underestimated because businesses count only transit time. For replenishment, lead time should cover the entire interval between triggering the purchase and having units available to satisfy demand.

Depending on your workflow, that can include:

• internal approval time;
• time before the purchase order is sent;
• supplier processing or manufacturing time;
• transport;
• customs or import handling;
• receiving delays;
• inspection, labeling, kitting, charging, sterilizing, or preparation before the item becomes usable.

Oracle’s inventory documentation explicitly treats item lead time as potentially including preprocessing, processing, and postprocessing components. That is a useful reminder for small businesses: “supplier says five days” does not necessarily mean “we can sell it five days after the trigger.”

Calculate lead time from real purchase orders

For each received PO, record:

Actual lead time = date stock became available − date order was placed

If ten recent deliveries took 6, 7, 8, 6, 11, 7, 9, 7, 6, and 8 days, the average tells you more than the supplier’s brochure. The spread matters too. An average of 7.5 days with deliveries tightly clustered between 7 and 8 days is very different from the same average created by some 3-day and some 14-day deliveries.

Common mistake: automatically using the longest delivery ever as normal lead time. That can create excessive inventory. Track both typical performance and variability, then decide how much risk buffer you actually need.

7. Calculate the basic lead-time demand

Once demand rate and lead time use compatible units, calculate:

Lead-time demand = average demand per period × average lead time in the same period

Example: a business consumes 18 units per day and average replenishment lead time is 9 days.

18 × 9 = 162 units

If demand and lead time were perfectly predictable, 162 would be the reorder point. When inventory position reaches 162, a new order would arrive just as those units are consumed.

Real operations are rarely perfectly predictable, which is why safety stock exists. But do not jump to safety stock before calculating this base. It is the part of inventory required for expected demand, not an emergency reserve.

8. Add safety stock for uncertainty, not for anxiety

Safety stock is extra inventory held to absorb variation in demand, lead time, or both. It is not a universal percentage that every SKU deserves.

North Carolina State University’s Supply Chain Resource Cooperative notes the core relationship: longer lead times and greater variability in demand or lead time generally require more safety stock. That logic is more useful than copying a blanket “keep 20 percent extra” rule from another company.

A simple small-business formula is:

Reorder point = average lead-time demand + safety stock

Suppose lead-time demand is 162 units and you choose 45 units of safety stock. The reorder point becomes:

162 + 45 = 207 units

When inventory position falls to about 207, you trigger replenishment.

A practical first safety-stock method when your data is limited

If you do not yet have enough clean history for statistical modeling, create a transparent operational buffer rather than pretending to have sophisticated certainty.

One approach is to ask: How many additional days of typical demand do we deliberately want to cover?

If daily demand is 18 units and you decide that two additional days is a reasonable temporary buffer:

Safety stock = 18 × 2 = 36 units

Then:

Reorder point = 162 + 36 = 198 units

This is not mathematically optimized, but it is auditable. You can explain why the buffer exists, observe whether it is enough, and replace it with a more data-driven method once demand and lead-time history improve.

When a simple days-of-demand buffer is not enough

Use a more rigorous model when the SKU is valuable, demand is volatile, service failures are costly, lead times vary materially, or you manage enough volume that excess stock itself is expensive. Statistical safety-stock formulas can incorporate the standard deviation of demand, lead-time variation, and a chosen service level. However, those formulas depend on assumptions. Recent supply-chain research continues to examine non-normal and intermittent demand because conventional normal-distribution methods can perform poorly for highly skewed patterns. The lesson for a small business is not “use the most complex formula.” It is “do not let a complex formula hide a bad fit.”

Inventory visibility helps connect physical stock with purchasing rules. Image by CyberStockroom.com, CC BY-SA 4.0, via Wikimedia Commons.

9. Decide which SKUs deserve high availability

One of the biggest causes of excess inventory is setting the same service expectation for every item. Not every SKU deserves the same safety stock.

Classify items using business impact rather than only sales volume. Consider:

• gross profit contribution;
• frequency of demand;
• customer importance;
• whether a substitute exists;
• supplier reliability;
• replacement lead time;
• expiration or obsolescence risk;
• storage footprint;
• minimum order quantities;
• consequence of a stockout.

An inexpensive spare part might need a high availability target because one missing piece prevents a technician from completing a high-value job. A decorative accessory with many substitutes might tolerate occasional stockouts even if unit sales are similar.

Create simple tiers such as:

• Tier A: critical or high-contribution items; review frequently and protect availability.
• Tier B: important normal items; standard buffer and review.
• Tier C: slow, substitutable, or low-impact items; lower buffer or buy-to-order where practical.

This is more intelligent than inflating every reorder point “to be safe.” Holding inventory is also a risk: cash becomes less flexible, products can expire or become obsolete, and crowded storage makes counting errors more likely.

10. Treat intermittent demand differently

Some SKUs do not sell a little every day. They sit still for weeks and then move in bursts. A daily average can be mathematically correct but operationally misleading.

Consider a spare part that sold 24 units in a year, but the pattern was four orders of six units each. The average is about 0.066 units per day. Multiplying that by a 10-day lead time suggests less than one unit of lead-time demand, even though a real customer order tends to consume six at once.

For intermittent items:

• look at order-event size as well as average rate;
• measure the time between demand events;
• consider whether customers can wait for replenishment;
• distinguish critical spare parts from optional slow movers;
• avoid forcing a normal-demand safety-stock formula onto lumpy history without testing it.

Sometimes the correct policy is not a conventional reorder point at all. A rare, expensive, noncritical item may be better purchased to order. A rare but mission-critical component may justify carrying one or two units even if the historical average is tiny.

11. Adjust reorder points for seasonality before the season starts

A reorder point based on annual average demand often fails during predictable peaks. If demand doubles every November, waiting until November to notice faster sales is already late when lead time is several weeks.

Build seasonal reorder points using demand expected during the lead time that begins when you place the order, not merely demand in the current month.

Example: a product normally sells 10 units per day, but expected demand during a holiday period is 22 units per day. Supplier lead time is 12 days. A normal-period base is 120 units, but peak lead-time demand is 264 units before safety stock. If the reorder point stays at 120, the business can run out even though the old calculation was accurate for the rest of the year.

Practical workflow:

1. Mark known peak and low seasons by SKU or product family.
2. Estimate demand rates separately for those periods.
3. Move the new reorder point into effect early enough that replenishment ordered before the peak reflects peak demand.
4. Schedule a date to reduce the point again after the season so temporary buffers do not become permanent overstock.

Promotions need similar treatment. If marketing plans a two-week campaign but purchasing uses normal demand, the campaign can create its own stockout.

12. Account for minimum order quantities and case packs without corrupting the trigger

Suppliers often require a minimum order quantity (MOQ) or fixed case pack. These constraints affect the order quantity, not necessarily the reorder point.

Suppose your reorder point is 80 units, but the supplier sells only cartons of 60 and requires at least two cartons. When inventory position reaches 80, the purchasing system should trigger an order; the order then must be rounded to at least 120 units.

Do not raise the reorder point to 120 just because 120 is the MOQ. Doing so changes when you order and can increase average inventory. Keep the trigger and purchasing constraint visible as separate fields.

However, MOQ should influence whether the item belongs in your current assortment. If a supplier forces you to buy nine months of demand at once, the real problem may not be reorder-point math. It may be supplier terms, item selection, or purchasing strategy.

13. Include open purchase orders carefully

Incoming stock should reduce the need for another order only if the incoming supply is credible.

Create statuses for open POs, such as:

• draft;
• sent to supplier;
• confirmed;
• in production;
• shipped;
• partially received;
• delayed;
• cancelled.

If your inventory system adds every draft PO to “on order,” a forgotten or cancelled purchase order can suppress a legitimate replenishment signal. The buyer thinks stock is coming when it is not.

Define which statuses count toward inventory position. For example, you might count confirmed and shipped POs, but not unapproved drafts. If supplier confirmations are unreliable, add an exception report for overdue POs rather than blindly trusting the on-order number.

14. Fix inventory accuracy before blaming the formula

A reorder point of 200 is useless if the system says 220 units exist while the shelf contains 140. Before tuning buffers, measure how accurate inventory records are.

Use regular cycle counts. Instead of closing the business for one massive annual count, count selected items on a rotating schedule. High-value or high-movement SKUs can be counted more often than slow items.

When a count differs from the system, do not simply adjust the quantity and move on. Record a reason when possible:

• receiving error;
• unrecorded damage;
• picking error;
• wrong unit conversion;
• bundle/component issue;
• customer return not processed;
• stock stored in the wrong bin;
• theft or unexplained loss;
• duplicate transaction;
• incorrect opening balance.

The pattern of discrepancies tells you what to fix. Increasing safety stock to compensate for poor transaction discipline is expensive and does not solve the root cause.

Physical availability must match inventory records for reorder rules to work. Photo by Alexander Zbitnev, CC BY 4.0, via Wikimedia Commons.

15. Build a simple spreadsheet that a buyer can audit

You do not need enterprise software to create a useful first model. A spreadsheet can work if the inputs are controlled and the business can keep it current.

Create columns for:

• SKU;
• item name;
• average daily or weekly demand;
• average lead time;
• safety stock;
• reorder point;
• on hand;
• confirmed on order;
• committed quantity;
• inventory position;
• reorder status;
• MOQ;
• case pack;
• supplier;
• last calculation date;
• next review date.

If daily demand is in column C, lead-time days in D, and safety stock in E, the conceptual formula for reorder point is:

= (C × D) + E

If on hand is G, confirmed on order is H, and committed quantity is I, inventory position is:

= G + H − I

Your reorder status can then test whether inventory position is less than or equal to the reorder point.

Do not hide every assumption inside one giant formula. Separate inputs so a buyer can inspect them. Add data-validation rules to prevent negative lead times, text inside numeric fields, or inconsistent units. Protect formula cells if multiple people edit the file.

16. Create a worked example from start to finish

Assume a small ecommerce company sells replacement water-filter cartridges.

During the last 12 weeks, after excluding days when the item was unavailable, it sold 1,008 cartridges over 84 calendar days:

1,008 ÷ 84 = 12 units per day

The latest eight supplier orders took 8, 9, 10, 8, 12, 9, 11, and 9 days from ordering to usable stock. For a simple initial system, the business chooses an average planning lead time of 9.5 days and rounds operationally to 10 days.

Base lead-time demand:

12 × 10 = 120 units

The supplier has occasional delays, and a stockout causes customers to buy a competitor’s compatible filter. The business initially chooses three extra days of average demand as a transparent safety buffer:

12 × 3 = 36 units safety stock

Reorder point:

120 + 36 = 156 units

Current records show:

• 130 units on hand;
• 60 units on a confirmed purchase order;
• 25 units committed to customer orders.

Inventory position:

130 + 60 − 25 = 165 units

Because 165 is above the 156 reorder point, another order is not yet required. Without counting the incoming 60 units, the business might have ordered prematurely. Without subtracting the 25 committed units, it would also overstate true availability. The value of the system is not only the formula; it is the complete view.

17. Do not confuse safety stock with “stock we never touch”

Safety stock is not a sacred pile that employees are forbidden to sell. It is a planning buffer. If demand is higher than expected or a supplier is late, inventory will naturally enter that buffer. That is exactly what it is there for.

The warning sign is not “we used safety stock once.” The warning sign is “we repeatedly consume the buffer before replenishment arrives.” If that keeps happening, investigate:

• demand rate may be understated;
• lead time may be understated;
• lead-time variability may have increased;
• purchase orders may be placed late after the trigger fires;
• inventory records may be inaccurate;
• supplier fill rates may have deteriorated;
• promotional demand may be missing from the forecast.

Each cause needs a different fix. Automatically increasing safety stock can hide an operational problem while increasing working capital.

18. Track the delay between trigger and actual purchase order

A reorder point assumes action happens when the threshold is reached. In many small businesses, the alert appears Monday, someone reviews it Friday, approval happens next Tuesday, and the PO is finally sent Wednesday. That internal delay is part of practical replenishment lead time.

Measure:

Trigger-to-order time = PO sent timestamp − first threshold-crossing timestamp

If this delay is routinely three days, either improve purchasing workflow or include those three days in the planning lead time. Improving the workflow is usually better because it reduces the buffer every SKU requires.

Create a daily or scheduled reorder report rather than depending on someone remembering to inspect stock. The report should show only actionable exceptions: SKUs at or below their trigger, overdue purchase orders, major demand changes, and inventory discrepancies.

19. Decide how often each reorder point should be recalculated

A reorder point is a policy based on assumptions. Assumptions expire.

Use a review cadence based on volatility and importance:

• fast, important SKUs: weekly or biweekly review;
• stable core items: monthly review;
• slow, low-impact items: quarterly review may be enough;
• seasonal items: review before and after each season;
• new products: review frequently until a stable demand pattern emerges;
• supplier changes: recalculate after enough deliveries establish the new lead-time pattern.

Do not recalculate from scratch every day unless your operation truly needs that sensitivity. Overreacting to short-term noise can make reorder points jump around and create unstable purchasing.

Keep the previous value and the reason for major changes. If a reorder point jumps from 140 to 260, the buyer should be able to see whether demand doubled, supplier lead time changed, or someone manually raised the buffer.

20. Use exception thresholds so every fluctuation does not create work

Not every tiny change needs a new setting. Establish review rules such as:

• average demand changed by more than a chosen percentage;
• supplier lead time increased materially;
• the item stocked out;
• inventory entered safety stock multiple times;
• excess inventory exceeded a defined number of weeks of demand;
• MOQ or case pack changed;
• the product moved between criticality tiers;
• a promotion or season is approaching.

This makes the system manageable with a small team. Buyers focus on exceptions instead of endlessly editing hundreds of stable rows.

21. Measure whether the reorder point is actually working

A formula should be judged by business outcomes. Track at least these measures by SKU or product group:

Stockout frequency

How often did an item become unavailable while there was demand? A low reorder point or insufficient safety stock can contribute, but verify supplier and inventory-record problems too.

Emergency orders

How often did you need expedited freight, emergency local purchases, or rush manufacturing? These are strong signals that planning or execution is failing.

Weeks or days of supply

How much demand does current inventory represent? Rising coverage can reveal overbuying even while stockout performance looks excellent.

Inventory age

How much inventory has remained unsold beyond your normal lifecycle? An availability target is not successful if it creates obsolete stock.

Supplier lead-time performance

Track actual delivery times and late-order frequency. A reorder model built on a 7-day promise cannot perform if the supplier regularly takes 13 days.

Fill performance or service outcome

Measure whether customer demand is actually fulfilled from stock. NCSU’s supply-chain tutorial distinguishes cycle service level from fill rate; they are related but not identical. That distinction is useful when a business starts using formal service targets rather than a vague goal of “never stock out.”

Review these metrics together. Zero stockouts could simply mean you are carrying far too much inventory.

22. Diagnose repeated stockouts systematically

When an item stocks out, do not immediately raise its safety stock. Run a short postmortem.

1. Was the inventory record accurate? If not, fix the transaction or count problem.
2. Did the trigger fire at the right level? If not, inspect the formula and data.
3. Was the PO placed when the trigger fired? If not, fix process delay.
4. Did demand exceed the planning assumption? Determine whether it was a trend, promotion, or one-off event.
5. Was the supplier late or short? Update lead-time and supplier-performance assumptions.
6. Was incoming inventory counted before it was truly confirmed? Tighten PO-status rules.
7. Did the supplier enforce an unexpected MOQ, allocation, or case-pack change? Update purchasing constraints.

Only after identifying the cause should you change the reorder point or safety stock. Otherwise, the business slowly accumulates excess inventory because every operational failure is “solved” with more buffer.

23. Diagnose chronic overstock with the same discipline

If a SKU is always full, do not assume the reorder point is too high. Overstock can come from:

• order quantities that are too large;
• supplier MOQs;
• duplicate POs;
• demand decline;
• seasonality ending;
• multiple buyers ordering the same item;
• returns flowing back into inventory;
• a reorder trigger that ignores incoming supply;
• safety stock never being reduced after a temporary disruption.

Compare reorder point, order quantity, inventory position at time of order, and demand since receipt. This separates a trigger problem from a purchasing-quantity problem.

24. Avoid five tempting shortcuts

Shortcut 1: “Order when one case is left”

This works only by accident unless one case happens to equal demand during lead time plus an appropriate buffer.

Shortcut 2: “Keep 30 percent extra on everything”

Percent-of-stock rules ignore lead time, demand rate, SKU criticality, and volatility. Thirty percent of a slow mover may be wasteful; thirty percent of a fast mover may be insufficient.

Shortcut 3: “Use the supplier’s stated lead time”

Measure your own order-to-usable-stock history. Supplier promises and your total replenishment cycle are not necessarily the same.

Shortcut 4: “Let the software calculate everything automatically”

Automation scales assumptions. If SKU units, demand history, PO statuses, or lead times are wrong, automation can create wrong orders faster.

Shortcut 5: “Never allow a stockout”

Absolute availability is not free. Some low-margin, perishable, obsolete-prone, or easily substituted items should not receive the same protection as critical items.

25. Upgrade from spreadsheet rules to software only when the process is clear

Inventory software can automate projected inventory, reorder policies, purchase suggestions, barcode transactions, supplier lead times, and alerts. Microsoft Business Central, for example, supports several reordering policies including fixed reorder quantity, maximum quantity, order, and lot-for-lot approaches. Oracle inventory systems likewise use reorder-point logic alongside forecast demand, safety stock, and lead time.

But software selection should follow process definition, not replace it. Before migrating, make sure you can answer:

• What exactly is our inventory position?
• Which PO statuses count as incoming supply?
• How do bundles consume components?
• What unit is each SKU stocked and purchased in?
• How is lead time measured?
• Who owns exceptions?
• How are cycle counts handled?
• How are demand spikes and seasonality represented?
• Who can override a reorder point, and is the reason recorded?

If those answers are unclear, software will inherit the ambiguity.

26. Build a 30-day implementation plan

Days 1–5: clean the foundation

Choose 20 to 50 economically important SKUs rather than the whole catalog. Clean units, supplier details, on-hand balances, open POs, and committed demand. Run physical counts on those items.

Days 6–10: measure demand

Export transaction history, correct obvious stockout distortions, identify promotions, and calculate a documented demand rate. Mark seasonal and intermittent items separately.

Days 11–15: measure lead time

Review recent POs from order date through usable receipt. Record average and spread. Identify internal approval delays and unreliable suppliers.

Days 16–20: set initial triggers

Calculate lead-time demand. Add a transparent safety-stock method appropriate to the data quality. Store reorder point and order quantity separately. Account for MOQ and case packs.

Days 21–25: create alerts and ownership

Build a daily or scheduled exception report. Assign one owner to review triggers and overdue purchase orders. Record when the trigger occurred and when the PO was sent.

Days 26–30: test and refine

Observe whether alerts make operational sense. Investigate anomalies instead of editing them away. Document the rules, then expand to the next group of SKUs.

27. A practical checklist for every new SKU

• Assign one unique SKU and unit of measure.
• Record purchase-unit conversion and case pack.
• Record supplier and MOQ.
• Choose an initial demand assumption and label it as provisional.
• Record expected replenishment lead time.
• Choose a temporary buffer based on item risk and uncertainty.
• Set a review date early enough to replace assumptions with actual data.
• Verify how bundles, samples, damages, and returns affect the quantity.
• Confirm the item appears on the replenishment exception report.

New products need more human review because there is little history to learn from. Avoid giving a new SKU a permanent reorder rule based on launch-week sales.

28. Questions small businesses commonly ask

What is the simplest reorder-point formula?

The common basic formula is expected demand during replenishment lead time plus safety stock. If you use daily demand and lead time in days, multiply those two values and add the chosen buffer.

Is reorder point the same as minimum stock?

They can be configured similarly in some systems, but the clearest operational definition is that the reorder point is the threshold that triggers replenishment. “Minimum stock” is used differently by different businesses and software, so document what your field means.

Is safety stock the same as reorder point?

No. Safety stock is the buffer for uncertainty. Reorder point includes expected lead-time demand plus that buffer.

Should I calculate reorder points from sales or forecasts?

Use the best estimate of future consumption available. Stable items may work well with recent historical demand. Seasonal, promotional, trending, or new items may need a forecast adjustment. Do not let a historical average override information you already know about the future.

How much safety stock should a small business keep?

There is no defensible universal percentage. The amount should reflect demand variability, lead-time variability, service importance, stockout consequences, storage cost, obsolescence risk, and data quality. Start transparently, measure outcomes, and refine.

What if my supplier has a very long lead time?

Longer lead time usually raises lead-time demand and exposes the business to more uncertainty. You can respond with more inventory, but also investigate supplier alternatives, earlier ordering, order frequency, local backup supply, better forecasts, or reducing internal processing time.

What if demand is growing quickly?

A trailing annual average will lag the trend. Compare shorter and longer windows, use an explicit forward adjustment, and review the SKU more often. Record the assumption so buyers understand why the reorder point changed.

Can I use reorder points for raw materials?

Yes, but demand should reflect material consumption, not finished-goods unit sales unless the conversion is fixed and correctly modeled. Bills of materials, scrap, yield loss, and production schedules can materially change requirements.

When should I stop using a reorder point?

Consider another policy for make-to-order items, rare expensive parts, highly intermittent demand, perishable products with severe expiry risk, or items controlled primarily by scheduled production plans. Reorder points are a tool, not a requirement for every SKU.

29. Sources and further reading

• Oracle Inventory Help: Reorder Point Planning — explanation of reorder point, lead-time demand, safety stock, and replenishment lead-time components.
• Microsoft Learn: Handling Reordering Policies in Business Central — documentation on reorder points, projected inventory, and available replenishment policies.
• NC State Supply Chain Resource Cooperative: Reorder Point Formula — educational discussion of safety stock, demand/lead-time variability, cycle service level, and fill rate.

Conclusion: make the trigger explainable before you make it sophisticated

A useful reorder-point system should be understandable by the person who has to act on it. Start with one clean SKU, measure actual demand, measure the full order-to-usable-stock lead time, calculate expected lead-time demand, add a deliberate buffer for uncertainty, and compare the result with inventory position rather than shelf count alone.

The most important mistake to avoid is increasing safety stock every time something goes wrong. A late PO, inaccurate count, slow approval, broken bundle setup, demand surge, and unreliable supplier can all create the same visible symptom—low stock—but they need different fixes.

Your first action should be small: choose the 20 items that matter most, physically verify them, and reconstruct their recent demand and supplier lead times. A simple rule built from trustworthy data is more valuable than a sophisticated formula built on quantities nobody trusts.