How sales velocity and days of supply work
Every reorder decision in SKU.io starts from two numbers: how fast a product sells (its velocity) and how long the stock you have will last at that pace (its days of supply). This page explains where those numbers come from, so you can read them correctly in the Inventory Planning report and in a demand forecast.
Velocity: how fast a product sells
Velocity is units sold per day or per month, counted from your sales orders. The Inventory Planning report shows it several ways:
| Column | What it shows |
|---|---|
| Sold 30d, Sold 60d, Sold 90d, Sold 180d | Total units sold over the last 30, 60, 90, or 180 days. |
| Daily Avg | Average units sold per day. |
| Monthly Avg | Average units sold per month: the 180-day total divided by six. |
| Demand Trend | Whether the product is speeding up or slowing down: the last 30 days' daily average compared with the last 90 days'. An up arrow means growing and a down arrow means declining. |
| Sell-Through % | The share of your supply that sold: units sold in 180 days divided by those units plus what's still available. A high percentage is a fast mover. |
| Inv. Turnover | How many times a year you sell through your stock: twice the 180-day sales, divided by total inventory. |
Daily Avg is the product's daily average consumption (DAC). How many days of sales it averages over is a setting; see Choose how much sales history drives daily average consumption.
These figures are refreshed every night at 2 AM. The line at the top of the report shows when the Velocity Cache was last refreshed and when it runs next. Click Refresh next to it to recalculate now, for example after importing a batch of historical orders.
Demand Trend needs enough sales to mean something. With fewer than 6 units sold in 90 days it shows a dash. With 6 to 19 units it shows faded, as a low-confidence reading. From 20 units it shows normally.
Velocity for one channel
The report's velocity counts sales from every channel together. To size an order on a single channel's demand, use Inventory → Demand Planning. Its sales order filters let you count only orders from a chosen Channel or Sub Channel, and leave out cancelled orders or returns. The forecast's Avg/d column is then that channel's velocity.
Days of supply: how long your stock lasts
Days of supply divides the stock you have by how fast you sell it.
| Column | Formula | What it tells you |
|---|---|---|
| Days of Stock | Available ÷ Daily Avg | How many days your current stock lasts at the current pace. ∞ means no recent sales. |
| Days Until Stockout | (Available + Inbound) ÷ Daily Avg | The same, counting units already on open purchase orders. It's higher than Days of Stock when you have stock on the way. |
| Stockout Risk | Days of Stock compared with the supplier's lead time | HIGH: you run out before a new order could arrive. MEDIUM: stock lasts less than one and a half lead times. LOW: comfortably more. NONE: no sales. |
The sales side is company-wide. When you filter the report by Warehouse, the stock columns change to that warehouse, but velocity still counts sales from every warehouse.
A demand forecast also reports days of supply. Its summary tiles show the days of coverage the recommended order would give you, and the target you set with Target Stock Days drives how much it recommends.
Velocity drives the reorder numbers
The report's reorder columns are built on the same velocity:
- Reorder Point = (Daily Avg × lead time) + Min Stock Level. When available stock falls below it, it's time to order. The report uses the longer of the supplier's quoted lead time and the actual lead time from your recent purchase orders.
- Suggested Qty = (Daily Avg × (lead time + Target Stock Days)) − Available − Inbound, rounded up to the supplier's minimum order quantity. 0 means current and inbound stock already cover the target.
Stockouts: what an out-of-stock day does to velocity
On a day a product is out of stock, it sells nothing. Counted as a zero, that day pulls the velocity below the product's real demand, and the reorder numbers built on it come out too small. This matters most for your best sellers, which are the products most likely to run out. SKU.io never estimates the sales you lost; it only decides whether those days count.
In a demand forecast, the Adjust for out-of-stock days option in Sales Order Filters leaves those days out. Velocity is measured over the days the product could sell: the days it was in stock, plus any days it sold on backorder. A product that sold 165 units in a 31-day window but was in stock for only 16 of those days plans at 10.31 a day instead of 5.32. The option is on for new forecasts. Guardrails cap the adjustment at three times the calendar velocity and skip it when the product had fewer than 7 days it could sell. See Adjust velocity for out-of-stock days for the steps and the badges.
With the option off, a forecast counts every calendar day. You can still remove the out-of-stock days by hand: click Detect Anomalies, Exclude the Drop days from the stockout, and turn on Exclude detected anomalies from baseline. See Review demand anomalies.
The Inventory Planning report always counts every day. Its velocity columns use neither the adjustment nor your anomaly exclusions.
Stock-out adjusted velocity in the Send Planner
The Send Planner and the WFS replenishment screen measure velocity per fulfillment network, and they do adjust it for stock-outs. When a network was out of stock on some days, the velocity divides the units sold by the days the product was in stock there, not by every day of the window. A product that sold 60 units in 30 days, but was out of stock at the network for 10 of them, plans at 3 a day (60 ÷ 20) instead of 2.
Demand forecasts use the same idea with the same 3× cap and 7-day floor. Three limits keep the Send Planner's adjustment honest:
| What you see on the line | When | Velocity used |
|---|---|---|
| In stock all window | The network had stock every day. | The plain velocity; nothing to adjust. |
| Stock-out adjusted, with the days out, such as (10 of 30 d out) | The network was out of stock for some days. | Units sold ÷ days in stock. |
| Stock-out adjusted, capped 3× | The adjustment would more than triple the plain velocity. | Three times the plain velocity. |
| Too little history, with its days in stock | The product was in stock for fewer than 7 days of the window. | The plain velocity, so the send may come out low. |
| No stock history | SKU.io has no daily stock history for the network yet. It builds up every night. | The plain velocity. |
When too few of a channel's orders can be traced to the network's warehouse, the line shows Channel fallback and counts that channel's orders directly. To see which basis a line used, open it in the Send Planner; see How a network's send is calculated.
Related
- Use the Inventory Planning report to act on these numbers across all suppliers.
- How a network's send is calculated to see how the Send Planner uses velocity for each fulfillment network.
- Check how far to trust a forecast to see how sparse or erratic sales affect a recommendation.