How to Recalculate Reorder Points
in Your ERP

The Problem With Most Reorder Points

Ask an operations manager when their reorder points were last recalculated. In most cases the answer is some variation of "when we set up the ERP" — which could mean three years ago, five years ago, or longer.

That's a problem. Your business hasn't stood still since then. Demand patterns shifted. Suppliers changed. Product mix evolved. Lead times moved. But the reorder point in your system is still triggering orders based on a version of your operation that no longer exists.

The result shows up as stockouts on the items that matter most and excess inventory on the items that don't. Planners stop trusting the system and start rebuilding orders manually. Expediting becomes routine. And nobody connects the symptoms back to a planning parameter nobody has opened in years.

What a Reorder Point Actually Is

A reorder point (ROP) is the inventory level that triggers a new purchase order or production order for an item. When on-hand stock drops to the ROP, the system signals: order more.

The formula is straightforward:

Each variable in that formula can drift independently:

• Average daily demand changes as customer mix, seasonality, and product preferences shift
• Lead time changes when suppliers change, freight lanes shift, or order quantities move
• Safety stock should reflect current demand variability — which changes constantly

When any of these inputs become stale, the ROP becomes wrong. And a wrong ROP either triggers orders too early (overstock) or too late (stockout).

How to Know When Your Reorder Points Need Updating

You don't need to wait for a crisis. These signals tell you your ROPs need attention:

• You're regularly running out of items the system said were covered
• You're consistently holding more inventory than you need on slow-moving items
• Your planners are regularly overriding system suggestions
• A significant customer was added, lost, or changed their order patterns
• A key supplier changed lead times, minimums, or reliability
• Your product mix changed by more than 20% in the last 12 months
• You haven't formally reviewed ROPs in more than 12 months

If more than two of those apply, your reorder points are likely costing you money right now.

How to Recalculate Reorder Points

Step 1 — Pull 12-24 months of demand history

Export consumption or sales transaction data from your ERP for all active items. Filter to actual demand transactions only — exclude returns, adjustments, and interplant transfers. Calculate average monthly demand and standard deviation of monthly demand for each item.

Step 2 — Confirm current lead times

Check your item master or vendor master for lead times. Then verify: are those lead times accurate? Call your top 10 suppliers and confirm actual lead times, not the ones someone entered at ERP go-live. Include transit time if your system stores it separately.

Step 3 — Classify your inventory (ABC/XYZ)

Not all items deserve the same ROP methodology. A-items (high dollar value) should use statistical safety stock with a 97-99% service level target. C-items can use a simpler min/max approach. Items with erratic demand (Z-class) should not use statistical safety stock at all — they need a buffer quantity based on judgment, not a formula.

Step 4 — Calculate safety stock by class

For statistically-driven items, use the standard safety stock formula:

Step 5 — Calculate and compare

Apply the ROP formula. Before updating your ERP, compare current vs. proposed. Items where the proposed ROP differs by more than 30% are your highest-priority updates. Items with no ROP set at all are your most urgent.

Step 6 — Update and document

Update your ERP item master with the new values. Document the methodology, the review date, and the key assumptions. Set a calendar reminder to review again in 6-12 months.

Building a Review Cycle That Sticks

The most important step isn't the recalculation — it's building the habit of repeating it. A practical review cadence: A-items every 6 months, B and C-items annually. Document this in a Standard Operating Procedure with a named owner. Without an SOP, the review only happens when someone remembers — which is to say, not often enough.