Stock Days
Position on 2026-08-07 · run rate = net units ÷ calendar days, so a SKU that sold seven units on one day of a week runs at 1/day, not 7 · cover = network units ÷ run rate, on the 30d window
Counts are of the 92 SKUs in scope and are computed on the 30d run rate. An out-of-stock SKU is counted there only, never again under below target.
Inventory distribution
0 network units across 0 places on 2026-08-07 · own + marketplace = network
Nothing is in stock anywhere on 2026-08-07. Import an opening balance or an approved IMR to put units on the shelf.
Stock days by SKU
0 of 92 SKUs — the overstocked tile · position on 2026-08-07 · status and replenishment computed on the 30d run rate
No SKUs in this scope are overstocked on the 30d run rate. Clear the view to see every SKU in scope.
— in a cover column means nothing sold in that window, so cover is undefined. It is never shown as 0, ∞ or 999.
On a truck: counted toward the reorder gap, never toward cover.
Replenishment
0 SKUs need a decision on the 30d run rate · counting only the overstocked rows above · 0 units to buy · 0 to move · 0 above the maximum
Nothing to buy or move on the 30d run rate. Every SKU in scope is inside its policy band — widen the filters or change the basis window to review more of the catalogue.
A transfer fixes an imbalance; a purchase fixes a shortage. A warehouse only ships what it holds above its own safety stock, so a network that is genuinely short still shows a purchase.