Thresholds and recalculation plans
Minimum and maximum thresholds are the basis of the whole automation: without them there are no reorder suggestions, no replenishment suggestions and no level-based replenishment schedules.
They can be set by hand, in bulk from the stock list, or the module can recompute them from sales history.
Stockly → Purchasing → Stock Thresholds → Threshold plans.
A plan
Section titled “A plan”A plan is a job that recomputes thresholds on a cycle. The list shows Plan, Active, Saving, Runs, Last run, Next run, and the row menu has Run now.
How much the plan may save
Section titled “How much the plan may save”What the plan may save is the most important decision:
- Proposes only — nothing is written; every result waits for a person,
- Saves within limits — writes what stays inside the jump limits,
- Saves B and C classes — holds class A for a person, because a wrong threshold costs most there,
- Saves automatically — writes everything it computes.
On top of that, Dry run computes and records proposals but changes nothing, regardless of the save mode. It should be left on until the first results have been read.
Schedule
Section titled “Schedule”Every N days and At hour (UTC). Fast movers require a shorter cycle than the long tail.
Warehouses, Suppliers, ABC classes — empty covers everything. Skip new products leaves out goods younger than two weeks, which have no established sales rate yet, only noise.
Calculation parameters
Section titled “Calculation parameters”- Sales window (days) — how far back the demand rate is measured. Short windows react faster and fluctuate more.
- Default lead time (days) — used only for products whose supplier has no lead time recorded.
- Safety factor (%) — fallback cover for products with too little history to measure variability.
- Review cycle (days) — how long one replenishment should last; this is the distance from the minimum to the maximum.
- Split across warehouses — demand history is network-wide, and this decides how it is divided between buildings: Equal share per warehouse, Share of past demand per warehouse or Share by sales channel.
Seasonality
Section titled “Seasonality”Use seasonality removes the season from the history before measuring, then sizes the threshold for the weeks the delivery actually lands in. It needs two years of history; without them the plan falls back to a flat average on its own.
Seasonal history (days) sets how far back the season is measured. Two years is the minimum that can tell a season from the year it happened in.
Limits
Section titled “Limits”Max increase (%) and Max decrease (%) cap how far a threshold may jump. Empty means no limit; they apply only to the mode that saves within limits.
Decisions to make
Section titled “Decisions to make”Whatever the plan did not save waits on its own page. → Thresholds to decide
Every pass a plan made over the catalogue is kept, with what it looked at and what it wrote. → Threshold runs
Setting a plan up from scratch, in the order that keeps it from writing anything unread. → Letting a plan recalculate reorder thresholds