Sourcing decision log

With several warehouses the question arises sooner or later: why did that order ship from there. This log contains the answer.

Stockly → Settings → Diagnostics → Sourcing decisions.

The list

Columns: Decided, Node, Rule, Trigger, Candidates, Degraded.

Rule says what decided:

Reason	Meaning
Pickup rule named this warehouse	a pickup rule named that building
Kept with the rest of the order	keeping the order in one building
First warehouse with unpromised stock	the first building with stock promised to nobody
First warehouse with any stock	the first building with any stock
Backorder node (nothing in stock anywhere)	the goods are nowhere
Default warehouse, First active warehouse	fallback resolutions
Moved to where the goods lie	the cover followed the goods
A transfer brought the goods here	a transfer delivered them here
No warehouse at all	no building was found

Candidates shows the alternatives considered, and Degraded marks a decision made in a degraded mode: one in which the module had to settle for less than its preferred answer.

When an entry appears

A row appears when a demand line is first booked, when it changes node, and when it degrades. Repeated identical decisions only increment a counter instead of adding further rows to the list.

Switching it on and pruning

Both settings live in Stockly → Settings → Stock → the Order Allocation tab. Record sourcing decisions decides whether anything is written here at all and is on after installation; Sourcing decision log retention (days) decides how long a row survives, a year by default, pruned by a daily task. → Stock settings · Scheduled tasks

Deleting

The log can be cleared, by selection or entirely.