How to Set Your First Inventory Reorder Points

Confirm the SKU, unit, storage locations, and purchasing owner. Establish that recent movement records are reliable enough to estimate use. If quantities are inconsistent, investigate the difference before turning it into a replenishment rule.

Avoid assigning the same point to every item. Usage, delivery time, storage limits, and substitution options differ. Begin with a manageable group, inspect the first replenishment cycle, then expand the method when the team can explain its inputs.

For a new item with little history, document the planning assumption and the source of it. An estimate from a known job requirement is useful, provided the team can distinguish it from observed consumption.

Put usage and lead time on the same basis

Choose a time basis that fits the item and supplier. If you measure use per operating day, express lead time in comparable operating days and check how weekends or closures affect actual delivery. Alternatively, use calendar days consistently throughout the calculation.

Estimate usage from issues for work over a stated period. Separate exceptional jobs, returns, transfers, and recording corrections before treating the total as ordinary consumption. Moving ten units to another storeroom does not mean the business consumed ten units.

Measure lead time from the point your calculation assumes an order can be released until the stock is received and usable. Include routine internal approval or preparation delays when they fall inside that interval. A supplier's shipping estimate alone may omit time your own team needs.

If approval takes two days before a five-day delivery period begins, a calculation based on only five days leaves the first two uncovered. Record which stages your lead-time assumption includes.

Work through an initial reorder point

Consider a hypothetical service team using cable connectors recorded as individual pieces. Over 20 operating days, ordinary jobs used 160 pieces. The assumed average demand is therefore eight pieces per operating day.

The team assumes five operating days from order release to usable receipt. It chooses an initial buffer of 24 pieces, equal to three days of average use. That buffer is a planning choice for this example; it is not a universal service level or an optimized safety-stock calculation.

The starting rule is reorder point equals average demand during lead time plus buffer. Under the example's assumptions, reaching 64 pieces signals that the purchasing owner should review replenishment.

If an order is released immediately and demand follows the assumed average, 40 pieces would be used before receipt, leaving the 24-piece buffer. Higher demand or a later usable receipt consumes some of that buffer. The arithmetic explains the assumption; it does not guarantee that stock will always be available.

Distinguish the trigger from the quantity to order

A point of 64 pieces does not mean “buy 64.” The order quantity depends on the target you are replenishing toward, existing usable stock, commitments, incoming orders, package sizes, storage, and the purchasing decision.

Before acting on a low-stock signal, ask what quantity it represents. Stock on hand, stock available after reservations, and stock already on order answer different questions. A physical shelf count is useful, but it may include pieces committed to existing work.

For example, suppose the hypothetical team has 70 pieces on hand, 12 reserved, and 40 on a confirmed incoming order. Its available quantity after reservations is 58 pieces. That may justify reviewing the 64-piece threshold, but the incoming 40 pieces must be considered before placing another order.

Check the expected arrival and intended use of those incoming pieces. An open order arriving after the next job may not solve the immediate shortage. A recorded incoming quantity is not usable stock until the receiving process confirms it.

When projecting future needs, avoid counting the same committed job twice: once as reserved stock deducted from availability and again as an additional demand requirement. State how commitments enter the planning calculation.

Use the Purchase Request Checklist to carry the reviewed need through authorization and receiving. A reorder signal provides context for that process; it does not authorize a supplier commitment.

Choose a buffer you can explain and revise

Base the first buffer on the uncertainty the team is trying to cover. Review late deliveries, changing job demand, unreliable data, and the practical effect of running out. Consider storage and handling constraints alongside the need for continuity.

For stable items, a modest, explicit starting assumption can be reviewed after a few cycles. For volatile demand or costly consequences, use a more suitable planning method with the responsible specialist. A single average can hide the variation that matters most.

Record the reason for a change and the evidence behind it. A higher point can conceal a delayed ordering process without fixing that delay. Check the sequence before adding more stock.

Put one owner in charge of the first cycle

Name the person who reviews the signal, the person authorized to place an order, and the receiving owner. One person may fill several roles, but the team should know which action has happened.

Set a review cadence appropriate to the item's demand. A continuously calculated threshold can still be missed if nobody looks at it. Include review time in the planning assumptions when the team checks stock periodically rather than continuously.

Track the first cycle from the signal to usable receipt. Record the quantity and time at the trigger, the order decision, release date, confirmed arrival, actual receipt, and stock remaining at receipt. Note any urgent workaround or missed job requirement.

Use that observed sequence to revise the inputs. Preserve the original assumption so the next owner can understand why the point changed.

Keep the replenishment assumptions with the item

Use a short record for each starting rule:

• Item: SKU, unit, location scope, and responsible owner.
• Demand: Observation period, ordinary use, exceptional use, and time basis.
• Lead time: Start event, usable receipt event, and included internal delays.
• Buffer: Quantity and the uncertainty it is intended to cover.
• Point: Calculation, approved value, and effective date.
• Review: Cadence, incoming orders, committed stock, and decision owner.
• Learning: First-cycle result, revised inputs, and next review date.

Figena's Inventory workspace provides item reorder points and a low-stock view alongside structured units, locations, and movement history. Configure the point from a reasoned operating assumption, then review the displayed quantities in context. Setting the field makes the signal available to the team; it does not place a supplier order or guarantee delivery.

Turning Meeting Decisions Into Actions the Team Can Complete

Separate decisions, actions, and open questions in meeting notes. Use a practical handoff template to confirm owners, define completion, manage dependencies, and review the result.