Inventory replenishment: a practical operating guide

Inventory replenishment is the process of restoring stock so that a business can keep meeting demand. The arithmetic matters, but a useful replenishment process also needs reliable source records, a named decision maker, and a way to handle missing information.

A threshold in a spreadsheet cannot tell you that an inbound shipment is delayed or that another teammate has already ordered the same SKU. This guide builds a review around the calculation, with an example and a record you can copy.

Decide what the review is responsible for

Choose one SKU and location first. Define the stock unit: individual items, cartons, or another unit your team actually purchases and sells. Mixing cases with individual items can make an otherwise correct formula unusable.

Then name the output. A small team might need a daily list of SKUs requiring attention, a proposed purchase order for approval, or an exception report for late inbound supply. These are separate deliverables. A completed review is not evidence that a supplier has accepted an order.

These are suggested responsibilities, not a substitute for your company's approval policy.

Pick a review method that fits the operation

Continuous review checks stock against a threshold as records change. Periodic review examines stock on a schedule. A top-off routine aims to restore a selected level during a planned replenishment window. ShipBob's inventory replenishment overview describes these common approaches and the operational factors behind them.

Whichever method you choose, record its assumptions. A weekly review needs to consider the wait until the next review as well as supplier lead time. The simple reorder point calculation below models demand during lead time; it is not a complete periodic-review policy.

Establish a usable inventory snapshot

Keep the source timestamp and the meaning of each quantity with your records. At minimum, establish:

• On-hand stock at the chosen location and any units unavailable for sale.
• Customer commitments, reservations, or backorders, with definitions that avoid subtracting the same demand twice.
• Open inbound supply, expected arrival, and the uncertainty attached to it.
• Recent demand and the period used to estimate a daily rate.
• Supplier lead time measured through to usable stock, plus the team's chosen safety buffer.
• Existing purchase orders and outstanding proposals for the same SKU.

Do not add every inbound unit to an available-stock total without checking when it can serve demand. An order arriving after the projected stockout does not resolve the earlier gap.

Calculate a threshold, then review the decision

The basic formula is average daily demand × replenishment lead time + safety stock. The reorder point calculator applies this formula to your inputs and rounds the final threshold up for whole units. Safety stock is an input you choose; the tool does not optimize it.

Consider a fictional retailer selling a travel organizer:

The threshold signals that this SKU deserves a replenishment review. It does not establish an order quantity. The planner should first confirm the existing inbound order, assess when stock is needed, and send a proposal to the purchasing owner. Ordering another 100 units immediately could duplicate work already in progress.

If the 12-unit daily rate came from a promotion that has ended, the next action may be to revise the assumptions rather than place another order. Preserve the old value and the reason for the change so the next reviewer can understand the decision.

Copy a replenishment review packet

Use this record for one SKU and location. Keep unknowns visible instead of filling them with guesses.

REPLENISHMENT REVIEW — DRAFT
SKU / location / stock unit:
Source snapshot and timestamp:
Reviewer / review date:

Demand period and daily rate:
Lead time and its source:
Safety stock and policy owner:
Calculated reorder point:

Usable on-hand stock and definition:
Commitments already included in that figure:
Open inbound orders / arrival evidence:
Existing proposals for the same SKU:

Decision needed:
Proposed action and rationale:
Unknowns / exception owner:
Authorized purchasing decision and receipt:
Follow-up date / evidence of completion:

For a recurring process, place this packet inside an SOP template. Document who refreshes the sources, who handles exceptions, and what allows a paused review to resume.

Handle exceptions before calling the review complete

A stale export, conflicting stock definitions, or an unconfirmed shipment should create a specific follow-up. “Investigate inventory” is too broad. “Purchasing owner to confirm the arrival date for open order DEMO-17 before today's decision” gives the next person an action and an acceptance condition. DEMO-17 is a fictional reference, not a real order.

Keep a proposal separate from its approval, and an approval separate from receipt of stock. This makes the record useful even when several people or systems participate.

Offloop's E-Commerce team includes inventory, fulfillment, analysis, and team-operations roles. With appropriate access and supplied source material, these roles can help prepare a review packet and document the process. Team installation and source access are separate steps; the template does not connect a store or place an order. The purchasing decision remains with the authorized owner.

Review the process using observed results

After several review cycles, compare assumptions with what happened: source freshness, supplier lead time, proposed orders that were duplicated or changed, and stockout or excess-stock exceptions. Use consistent definitions and a comparable period. A process that produces more proposals is not necessarily a better process.

Update the source assumptions and the SOP when evidence warrants it. Retain the version and reason so future reviewers can see which policy was used for each decision.