PLANNING Replenishment

The replenishment task is ready before the shelf empties

When the reorder threshold is crossed, HaROS creates the replenishment task in WMS by itself. It calculates which product moves from which location to which picking point and when. You manage only the exceptions.

automatic task creation per-warehouse threshold management One system with WMS Approved or fully automatic mode

Stockouts are prevented: replenishment starts before the shelf empties Excess stock goes down: min/max thresholds are adjusted continuously No extra integration needed: replenishment runs inside WMS

Replenishment Flow

A single loop from demand to replenishment task

The process starts with the demand forecast, turns into a decision through threshold calculation and ends as a task in WMS. All steps take place inside HaROS.

Forecast-based threshold calculation

Kahin's demand forecast and the supplier's lead time are evaluated together. The reorder point (ROP) and order quantity (ROQ) are calculated for each SKU. The threshold does not stay fixed; it is updated with the forecast.

dynamic ROP

Automatic task creation

When the threshold is crossed, a replenishment task is created in WMS. Source and target location, quantity and priority are written to the task. The task can wait for approval or drop straight into the warehouse worker's list.

automatic task

In-warehouse transfer optimization

A replenishment task is not just a transfer order. HaROS picks the most efficient route, combines tasks that can be combined and takes staff workload into account.

route optimization

Barcode-verified completion

The warehouse worker verifies each step by scanning a barcode or RF. A wrong product or location warning comes instantly. Stock records are updated instantly.

verification · RF/barcode

Exception management

If there is not enough stock at the source location, HaROS suggests an alternative location or creates a purchase (PO) suggestion. The point that needs a decision is clearly shown to you.

exception · alternative source

Actual data flowing back into the loop

Every completed replenishment task returns to Kahin as data. The history of which threshold triggered when feeds the model, and the next period's threshold is calculated more accurately.

learning loop

Replenishment Parameters

Which values determine the replenishment decision

The replenishment decision is not a fixed rule. The values below are calculated together and continuously.

Reorder pointAverage daily demandLead time (days)Safety stock

Order quantity (ROQ)Economic order quantityMinimum order quantity (MOQ)Warehouse capacity

Priority orderStock level urgencySales velocityABC class

Trigger modeFully automaticApproved (one click)Suggestion (manual approval)

ScopePicking → Bulk locationIn-warehouse transferWarehouse → storeSupplier → warehouse (PO)

Link with WMS

Planning and WMS work in one system

Replenishment is the automatic link between the demand forecast and WMS.

Demand Forecasting

Feeds the threshold

Kahin's daily forecast at SKU × location level updates the reorder point. When a season or campaign arrives, the threshold rises or falls on its own.

Explore →

WMS

Executes the task

The replenishment task lands on the warehouse worker with location, quantity and priority. When the task is completed, the stock record is updated instantly and the data returns to Kahin.

Explore →

Planning Family

Demand Forecasting (Kahin) Demand forecasting with sales, stock and traffic data Open page →

Replenishment Automatic stock replenishment — creates tasks before the shelf empties ● YOU ARE HERE

Allocation Stock distribution by channel — the right product, at the right place Open page →

Frequently asked questions

Is replenishment fully automatic, or is there an approval step?

Both are possible. In fully automatic mode the task is created when the threshold is crossed and goes into processing in WMS. In approved mode the task is created as a draft and approved with one click. You decide during setup which mode runs for which product class.

Is the reorder point fixed or dynamic?

Dynamic. When the daily demand forecast or the lead time changes, the reorder point is updated. A fixed threshold that is updated by hand catches season changes late; a dynamic threshold rises in the peak season and falls in quiet periods so excess stock does not build up.

Are in-warehouse replenishment and supplier replenishment in the same system?

Yes. In-warehouse transfer (from bulk area to picking location) and the supplier purchase (PO) suggestion are tracked on the same screen. Stock status and scope settings determine which one comes into play.

Can we use replenishment with our existing WMS?

Yes. The replenishment output can be sent to your existing WMS through the open API. When WMS and planning run together in HaROS, verification, stock updates and feedback work faster.

How does replenishment work by store and channel?

HaROS monitors sales velocity and stock level separately by store, warehouse and channel. The task is created the moment the threshold is crossed. Each location is evaluated according to its own demand pattern.

Replenishment before the shelf empties, balance before excess stock builds up

Leave replenishment decisions not to intuition, but to the forecast, lead time and live stock status.

Request a demo

Related pages: Supply Chain Planning → · HaROS WMS →