Replenishment Control
Replenishment control is the process that automatically refills stock before it drops below a critical threshold – it decides when and in what quantity to reorder or reproduce.
Replenishment control refers to the planned regulation with which a company refills its stock levels in time – that is, it defines when, where and in what quantity items are reordered, transferred or reproduced so that goods stay available without tying up unnecessary capital in the warehouse. It answers the core question of any inventory management: how much must flow in and at what point, so that neither a shortage nor an excess stock arises?
In an ERP and inventory management system, replenishment control runs mostly rule-based and automated: the system continuously monitors stock, requirements and lead times, and triggers a purchase proposal, production or transfer order once defined thresholds are reached. It is thus the operational link between procurement, production and warehouse logistics and a central lever for delivery capability and working capital.
At a glance
- Governs when and how much to reorder, transfer or produce
- Balances delivery capability against capital tied up in stock
- Works with reorder point, safety stock and lead time
- In the ERP usually automated via purchase proposals and planning runs
- Uses consumption data (retrospective) or requirements planning (program-driven)
How does replenishment control work?
Replenishment control starts from a simple control loop: a target stock level is defined, the actual stock is continuously measured and, in case of deviation, a replenishment action is triggered. To do this, the control needs reliable master data – lead time, minimum and lot sizes, packaging units – as well as up-to-date transaction data on stock, open orders and reserved quantities.
In principle, two triggering logics are distinguished. With consumption-based planning, the system reacts to actual stock issues and relies on historical values; it is suited to easily plannable C-items and consumables. With requirements-based planning, replenishment is derived from concrete orders, bills of materials and sales forecasts – typical for high-value or sporadically needed items.
Reorder point and reorder point method
The classic method is the reorder point method: as soon as the available stock reaches the reorder point, a reorder is placed. The reorder point is calculated from the expected consumption during the lead time plus a safety stock that cushions fluctuations in demand and delivery time. The more reliable the supplier and forecast, the lower this buffer can be.
Order quantity and lot size
Besides timing, replenishment control governs the quantity. Fixed order quantities, refilling up to a maximum stock level or economic lot sizes are common strategies. Framework contracts, tiered prices, minimum purchase quantities and storage costs feed into the decision, so that replenishment is not only available but also cost-efficient.
Why replenishment control matters
Good replenishment control directly determines delivery capability: if an item is missing, aborted sales, overselling in online retail, contractual penalties or production standstill loom. At the same time, excessively high stock causes tied-up capital, storage costs, scrapping risk and, for perishable goods, write-downs. The control seeks the economic point between these two errors.
The economic benefit shows in metrics such as inventory turnover, service level and average capital commitment. Those who set reorder points and safety stocks data-based rather than by gut feeling often reduce stock and shortages at the same time. That is why replenishment control is frequently combined with an ABC/XYZ analysis: high-value A-items are managed tightly, low-value C-items may be stocked more generously.
Replenishment control in the ERP system
In the ERP system, replenishment control is typically part of planning or, respectively, of material requirements planning (MRP). In a periodic planning run, the system reconciles stock, open orders, reservations and requirements and generates purchase proposals, production orders or transfer proposals from them. The planner reviews and approves – or, given high data quality, the system posts through automatically.
For retail and e-commerce operations with multiple warehouses and sales channels, the location dimension is added: replenishment can be an external procurement or an internal transfer between central and regional warehouse or into the fulfillment center. The prerequisite is clean, cross-channel inventory management in real time, so that reserved and available quantities feed correctly into the control. Systems such as those linked in the profiles cover this logic to varying depths.
How far automation reaches differs considerably between the system classes. Lean cloud ERP for retail often rely on consumption-based purchase proposals with a reorder point, while comprehensive ERP suites bring multi-level, requirements-based planning with capacity reconciliation. For the selection it is therefore decisive whether one’s own assortment is rather fast-moving and consumption-stable or heavily order- and bill-of-materials-driven.
Distinction: replenishment control vs. planning and MRP
The terms overlap but do not mean the same thing. Planning (Disposition) is the umbrella term for the quantity- and date-based planning of material supply; replenishment control is the operational, often rule-based part of it that continuously triggers the refilling of existing warehouses. It is more stock-oriented and reactive.
MRP (Material Requirements Planning) goes beyond this: it derives secondary requirements from primary requirements and bills of materials and plans multi-level across production stages. Replenishment control in the narrower sense is thus more the stock-driven, consumption-near branch, while MRP maps the requirements-driven, planning-intensive branch. Related but not identical are also just-in-time and Kanban: they are replenishment principles in which consumption itself pulls the replenishment instead of planning it centrally.
Levers and typical mistakes
The quality of replenishment control stands and falls with data quality and parameterization. Wrong lead times, outdated consumption values or blanket safety stocks across the entire assortment lead to shortages for some items and excess stock for others. Seasonality, promotions and trends must feed into the forecast, otherwise the system stubbornly projects the past forward.
It has proven effective to maintain parameters differentiated by item class, to review safety stocks regularly against the actual service level and to manage exceptions deliberately instead of processing every purchase proposal manually. This keeps the planner able to act and focused on the few critical positions rather than on routine.
Another frequent mistake is isolated consideration: if replenishment control is not interlinked with purchasing conditions, supplier reliability and sales planning, it optimizes locally and generates costs elsewhere. Only the interplay of reliable lead time, realistic forecast and suitable order strategies turns individual rules into a viable control that keeps service level and stock in lasting balance.
Example
Example: replenishment in e-commerce retail
A mid-sized online retailer sells around 4,000 items via its own shop and two marketplaces from a central warehouse, with part additionally handled through a fulfillment center. For a bestseller with a daily sales of 60 units and a lead time of ten days, the ERP sets a reorder point of 600 units plus 200 units of safety stock – that is, 800 units.
If the available stock falls below 800 units in the nightly planning run, the system automatically generates a purchase proposal with the main supplier in economic lot size and additionally a transfer proposal into the fulfillment center. Ahead of the big seasonal business, the planner deliberately raises safety stock and forecast, so that despite the demand peak neither overselling arises nor residual stock has to be written off after the season.
Frequently asked questions
Matching ERP systems
Related services
Questions about Replenishment Control in your ERP project?
We advise vendor-neutrally – and implement it ourselves on request.