digiCARTCOMMERCE

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 7d window

Run-rate basis
7d15d30d60d90d
Total warehouse inventory
0
sellable units in our own warehouses, from the ledger
Total marketplace inventory
0
our units inside marketplace FCs — our books, not their claim
Total network inventory
0
warehouse + marketplace · nothing in transit
Average stock days
—
nothing sold in the 7d window, so cover is undefined — not zero, and not infinite
Out of stock
92
no sellable units on hand
SKUs below target
0
has stock, but under its reorder point
SKUs above target
0
cover above the maximum policy days
Overstocked
0
overstock plus slow-moving — capital sitting still
Purchase required
0
below the reorder point, after counting in-transit and open POs
Transfer required
0
a channel is short while an own warehouse holds a surplus it can spare

Counts are of the 92 SKUs in scope and are computed on the 7d run rate. An out-of-stock SKU is counted there only, never again under below target.

No stock and no sales on 2026-08-07

Stock days needs two things, and shows nothing until it has both. Demand comes from the daily sales rollup — one marketplace export is enough to start: a Zepto or Blinkit sales CSV, an Amazon all-orders report. Supply comes from the inventory ledger — an opening balance, then approved IMRs — and the locations it lands in have to be typed as own warehouse, marketplace FC or in transit in the location master, or their units cannot be classified.

Import a fileCheck the inventory positionCheck data health