Skip to main content

Retail replenishment and the Replenishment Director agent

Replenishment keeps continuing products in stock by reordering them as they sell. This guide covers the reorder point, safety stock and order-up-to calculations with a worked example, how replenishment teams work today, and how the OODARIS Replenishment Director agent drafts the daily order.

By Fatih Nayebi, Founder and CEO of OODARIS. Updated .

What replenishment is

Replenishment is the process of reordering products a retailer sells continuously, so that stock is there when customers want it without holding more than the business needs. It applies to basics and continuity lines, such as the core sizes of a classic loafer or everyday accessories, rather than to seasonal fashion, which is usually bought once and then allocated.

There are two flows. Store replenishment moves stock from a distribution center to stores. Distribution center replenishment buys stock from vendors through purchase orders. Both answer the same two questions for every item and location: when to order, and how much.

Replenishment runs on a few parameters per item and location: the forecast rate of sale, the lead time from order to arrival, how often the item is reviewed, the safety stock held against uncertainty, and the ordering rules (pack size, minimum order quantity and vendor schedules). Get the parameters right and most orders can be generated by a calculation. Get them wrong and the team spends its week correcting suggested orders by hand.

How replenishment teams work today

Replenishment analysts set parameters for each item and location, such as min and max levels, reorder points, safety stock and review cycles. A replenishment system or the ERP generates suggested orders from those parameters each day or week. Analysts review the exceptions, adjust for promotions and events, and release the orders to vendors or to the warehouse.

The same problems come up again and again:

  • Parameters are set once and rarely revisited, so they drift away from current demand.
  • Safety stock is a flat number of weeks for a whole category, not a figure based on how variable each item’s demand is.
  • Vendor lead times are taken from the vendor’s promise rather than from how the vendor actually delivers.
  • Promotions and events cause spikes that the standard calculation does not expect.
  • Pack sizes and minimum orders push order quantities up, and nobody tracks the stock that rounding adds.

The result is a team that spends most of its time writing and checking orders instead of improving the parameters that produce them.

Reorder point, safety stock and order quantity

A periodic-review system, the most common setup in retail, uses three calculations:

Reorder point = forecast demand during the lead time + safety stockOrder-up-to level = forecast demand over (lead time + review period) + safety stockOrder quantity = order-up-to level − (on hand + on order), rounded to the pack size and at least the minimum order

At each review, if the inventory position (on hand plus on order) is at or below the reorder point, an order is placed to bring it back up to the order-up-to level. Min/max systems work the same way, with the reorder point as the min and the order-up-to level as the max.

Safety stock covers the uncertainty in demand during the lead time. A common way to set it uses the standard deviation of demand:

Safety stock = z × σ × √(lead time)

Here σ is the standard deviation of demand per period, the lead time is in the same periods, and z is the service-level factor: about 1.28 for a 90% cycle service level, 1.65 for 95% and 2.33 for 99%. The formula assumes a steady lead time. When lead times vary too, safety stock has to cover that variation as well, which is why unreliable vendors cost inventory.

A worked replenishment example

A core sneaker at one distribution center (illustrative numbers)
Input or resultValue
Forecast demand120 pairs a week
Standard deviation of weekly demand30 pairs
Lead time2 weeks
Review period1 week
Service level95% (z = 1.65)
Pack size and minimum orderPacks of 24, at least 96 pairs
Safety stock1.65 × 30 × √2 = 70 pairs
Reorder point120 × 2 + 70 = 310 pairs
Order-up-to level120 × 3 + 70 = 430 pairs
Inventory position220 on hand + 60 on order = 280 pairs
Order430 − 280 = 150 pairs, rounded up to 7 packs = 168 pairs

The inventory position of 280 is below the reorder point of 310, so an order goes out. The raw quantity of 150 pairs becomes 168 once it is rounded up to whole packs, which also clears the 96-pair minimum.

The core sneaker over five weeks, reviewed weekly: the first order from the table, then the same rules each week (pairs, illustrative numbers)

Now suppose the vendor’s lead time slips from two weeks to three. Safety stock becomes 1.65 × 30 × √3 = 86 pairs, the reorder point becomes 120 × 3 + 86 = 446 and the order-up-to level 120 × 4 + 86 = 566. The same inventory position of 280 now calls for 286 pairs, or 12 packs (288 pairs). One extra week of lead time raised the order by more than two-thirds. Lead time matters as much as the sales forecast, which is why replenishment teams track how vendors actually deliver.

Choosing service levels and review cycles

Not every item deserves the same service level. Each step up costs more safety stock than the last: in the formula above, moving from 95% to 99% raises z from 1.65 to 2.33, or about 41% more safety stock for four points of service. Teams usually set higher service levels for items whose stockouts hurt most, such as core sizes of best-selling continuity styles and items customers expect to find every time, and lower ones for slow movers and items with close substitutes.

The review cycle is a trade-off too. Reviewing daily lets orders follow demand closely and keeps the order-up-to level low, but it means more, smaller orders, which pack sizes, minimum orders and delivery schedules may not allow. Weekly review is common for vendor orders, daily review for store orders from a nearby distribution center.

Finally, parameters need upkeep. Forecasts, demand variability and vendor lead times change through the year, and a reorder point set in spring can be wrong by autumn. Reviewing the parameters on a schedule, and whenever a vendor’s delivery record changes, keeps the calculation honest.

Measures replenishment teams watch

  • In-stock rate: the share of item-location combinations with stock on hand.
  • Fill rate: the share of demand, or of ordered units, met from stock.
  • Weeks of supply: stock divided by the forecast weekly sales.
  • Forecast error: how far actual sales landed from the forecast, which drives the safety stock needed.
  • Vendor lead time and fill rate: how long vendors actually take, and how much of each order they ship.

Short definitions are in the retail planning glossary. Replenishment orders also draw on the buying budget, so they show up in open to buy as stock on order.

How the OODARIS Replenishment Director agent works

In OODARIS, the Replenishment Director works in the allocation crew, alongside the Inventory Optimizer. It is part of how OODARIS applies agentic AI to retail planning. On the agents page, it is where OODARIS suggests starting when order writing eats the week.

  1. WatchesDaily sales and stock on hand and on order, against reorder points.
  2. ProposesThe daily replenishment order, within pack, minimum-order and vendor rules.
  3. Approved byReplenishment or allocation.
  4. Writes backApproved orders, to your ERP purchasing module.

It drafts daily orders that respect pack sizes and minimums, scores suppliers and feeds the scores back to the other agents, and leaves your system of record as the authority. It works with ERP purchasing, supplier portals and transportation management. In the open-to-buy crew, the Procurement Navigator also scores suppliers on delivery, quality and risk.

OODARIS reads from the systems you run today and writes changes back to the system that owns them. Each writeback uses the target system’s own APIs or event paths and is logged with the decision that caused it.

By default, the person who owns the decision approves each change before anything is written back. Teams can also keep OODARIS read-only, or let it act on its own inside limits the decision’s owner sets, with every action logged with its reason and reversible; how it works describes the four levels.

Frequently asked questions

How do you calculate a reorder point?

Reorder point = forecast demand during the lead time + safety stock. With 120 units a week of demand, a two-week lead time and 70 units of safety stock, the reorder point is 310 units.

How much safety stock should a retailer hold?

Enough to cover demand uncertainty during the lead time at the service level you want. A common formula is z × σ × √(lead time), where σ is the standard deviation of demand per period and z is about 1.65 for a 95% service level. More variable demand or longer, less reliable lead times need more safety stock.

What is the difference between min/max and order-up-to replenishment?

They are closely related. In a min/max system, an order is placed when stock falls to the min and brings it back up to the max. In an order-up-to system, the reorder point plays the role of the min and the order-up-to level the role of the max, both calculated from the forecast, lead time and safety stock.

What is the difference between replenishment and allocation?

Replenishment reorders continuing products as they sell. Allocation distributes a limited quantity of a product, often seasonal, across stores and sizes.

Does the Replenishment Director send orders to suppliers?

It drafts the daily replenishment order within pack, minimum-order and vendor rules. By default, replenishment or allocation approves it, and approved orders are written back to your ERP purchasing module. Your system of record stays the authority.

Start with one decision.

Pick the decision where margin leaks first. In a demo we walk through one like it in OODARIS; a pilot runs one live cycle on your data.

What happens next

  1. A reply within 24 hours

    A person on the OODARIS team reads your note and writes back to set up a first call.

  2. The first call

    We map the decision's data, handoffs and approvals, and show how OODARIS would work through it.

  3. A pilot, if it fits

    8–12 weeks to a first live cycle, run on your data with your approvals.