Inventory Action Planning Branch-level replenish, clearance candidate and hold decisions
Login required. Inventory actions are not loaded.
Decision boundary Replenishment uses live stock and demand. Clearance remains a candidate until real inventory age, unit cost/value and future sales plan are connected.
Priority replenish 0 0 pcs suggested
Clearance candidates 0 0 excess pcs flagged
Hold and monitor 0 No immediate action signal
Selected branch stock 0 PG + KL branch rows

Decision Model

Explicit calculations used for every branch-SKU row

Branch-first / live data
DemandW/day = 70% x 90d/day + 30% x 6M/day
TargetW/day x branch T-days + buffer
ReplenishW/day > 0 AND stock < target
CoverageStock / W/day
Clear candidateHigh cover AND slow/inactive AND excess > 0
Decision orderReplenish first, then clear candidate, else hold

Priority Queues

Top branch-SKU actions after current filters

0 rows

Replenish

0

    Clearance candidates

    0

      Hold

      0

        Branch-SKU Action List

        PG and KL stay separate so one branch cannot hide the other branch's shortage or excess

        Action SKU Brand Branch Stock 90d/day 6M/day W/day Cover Target Need Excess Last sale Reason Confidence
        Login to load live inventory actions.

        Source Readiness

        Only connected fields participate in the decision

        Waiting for login
        Sales velocityConnected
        PG / KL stockConnected
        Last sale dateConnected
        Inventory ageNot connected
        Unit cost / stock valueNot connected
        Future sales planNot connected