Weeks of supply: check the demand calendar behind coverage

A constant weekly average can hide a near-term demand spike or a receipt that arrives after stock runs out.

Kartik Deshpande··6 min read

An item shows several weeks of supply, yet next week's promotion may consume the available stock before its replenishment arrives. Start with eligible inventory units divided by an explicitly chosen weekly demand rate. Then walk the dated demand and receipt calendar when the rate is uneven. A single average can summarize coverage without establishing uninterrupted availability.

For a constant-rate calculation, weeks of supply = eligible units / units demanded per week. State whether demand comes from recent observed sales or an approved forward plan. The same stock can produce different coverage under those two assumptions. Keep that distinction visible before a buyer changes an order.

Define stock that can serve the selected demand

Choose an item, location, base unit and cutoff. Separate stock on hand from stock available for the demand you are testing. Quality holds, customer allocations and ownership restrictions can reduce usable quantity. Retain the source statuses and the approved eligibility rule so a reviewer can explain every exclusion.

Do not subtract a reservation twice. If the exported available balance already removes reserved units, subtracting the allocation again understates coverage. Reconcile the source's on-hand, reserved and available fields before building a new calculation. The inventory allocation workflow explains why total stock and stock eligible for a particular order can differ.

Shopify’s inventory report documentation says reports switched to On hand quantities on October 1, 2026, including committed and unavailable stock. Confirm the exported quantity’s meaning before treating it as usable supply. An eligibility adjustment may be needed even when the source calls the number inventory.

Keep a purchase order outside current on-hand stock. A confirmed future receipt belongs on its expected usable date (including any required receiving and quality-release delay) in a separate scenario, with supplier status retained. Ordered quantity is not evidence of material already available. A scenario based on expected receipt timing needs to say so.

Normalize units before dividing. Demand recorded in cases and stock recorded in individual units need an approved pack conversion, including the effective size where it changes. Store the original quantities beside the normalized values. A ratio that cancels the wrong units can look plausible while describing no physical coverage.

Choose the rate and window before calculating

A trailing rate summarizes observed consumption or sales over a stated history. Record which complete weeks enter the average and whether returns reduce the units. Keep confirmed zero weeks and separate missing extracts. Removing low-volume weeks because they look unrepresentative changes the measure and needs a documented reason.

Observed sales can understate demand when an item was unavailable. Retain stockout or availability evidence beside the history instead of treating zero sales as proof of zero demand. A new launch also lacks the history of a mature replenished item. Use a labeled planning assumption when the available evidence cannot establish a representative rate.

For forward coverage, use the demand plan accepted by its owner, with its version, item-location scope and calendar. Oracle's average daily demand horizon documentation makes the averaging horizon a specified input to days-of-cover calculations. That is a documented planning-system example of why the horizon belongs beside the result.

The stock-to-sales ratio compares stock and sales values under declared valuation conventions. Here the decision concerns physical units against a weekly demand sequence. Keep a cost-valued inventory-to-revenue ratio separate from unit coverage; dividing dollars at cost by sales at selling prices does not directly identify the week stock runs out.

Calculate the constant-rate result first

Assume an illustrative SKU has 500 eligible units at the cutoff and an approved constant demand assumption of 200 units per week. There are no receipts, losses or other demands in this first scenario. Coverage is 500 / 200 = 2.5 weeks. This is a calculation under the stated assumptions, not an observed stockout date.

If the selected demand rate is zero, leave the ratio undefined and explain the zero-demand population. An infinite-looking result can conceal a discontinued item, missing history or an inappropriate window. Negative net demand after returns also needs investigation before it is used as a coverage denominator.

For multiple items, preserve item-level results rather than dividing total units by a mixed demand rate. A unit of one product cannot satisfy demand for another without a supported substitution rule. An aggregate can hide an imminent shortage inside excess stock elsewhere. Where substitutions are allowed, retain their eligibility and conversion rules.

Check the inventory and demand scope

Bring one approved stock snapshot and the historical or planned demand series used in its coverage report.

Walk the uneven demand calendar before accepting a runout

Now use the same 500 units with a forward demand sequence of 100, 200, 300 and 400 units over four successive weeks. Assume demand is distributed uniformly within each week for fractional interpolation, and that there are no receipts in the base case. These teaching inputs vary by week so the limits of a single average remain visible.

WeekDemand assumptionBalance after demand, no receiptSeparate receipt scenario
1100 units400 units400 units
2200 units200 units200 units
3300 unitsFirst shortage during the week200-unit receipt usable at week start; 100 units remain
4400 unitsAlready uncoveredFirst shortage during the week

The no-receipt case covers two full weeks, then 200 / 300 of week three: about 2.67 weeks under the uniform-within-week assumption. A mean across all four demand weeks is 250 units per week, which would give 2.0 weeks from the same initial stock. The constant 200-unit scenario gave 2.5 weeks. Each result follows a different demand assumption.

In the separate scenario, 200 additional units become usable at the start of week three. After week three, 100 remain, covering 100 / 400 of week four. Continuous coverage is therefore 3.25 weeks under the same interpolation assumption. Keep the receipt scenario separate from current-stock coverage, and retain the promised usable date that makes the calculation possible.

A receipt arriving after the first shortage does not establish continuous coverage through that gap. Show the first uncovered demand and the later recovery as separate events. If demand is concentrated on particular days, replace weekly interpolation with the actual dated requirement pattern. A fractional week alone cannot promise which customer order will be served.

Keep current stock and receipt scenarios distinct
Current stock

Eligible units at cutoff

Demand calendar

Accepted version and dates

Receipt scenario

Usable quantity and arrival

A later receipt can improve a projected balance without removing an earlier gap in availability.

Explain the change before changing a purchase

Compare the new result with the prior snapshot using the same definition. Separate movements caused by changed stock, a revised demand plan and a changed receipt promise. A class or color can direct attention, but keep the quantities and calendar behind it. The forecast accuracy review addresses the separate job of evaluating a demand forecast against actual outcomes.

Review coverage alongside lead time and minimum order constraints. The fact that a product has less than a target number of weeks does not establish an order quantity without those inputs and the service policy. Ask the planner to approve any changed parameter. Do not convert an analytical exception into an automatic purchase approval.

How Permute preserves the coverage assumptions

Permute sells connected business data and custom applications. We can combine approved Shopify or NetSuite inventory records with planning extracts in Excel or Google Sheets, reconcile product and location identities, and retain the source snapshots. An unresolved status or missing demand bucket remains an exception for the owner.

We can apply your declared stock-eligibility rules, demand calendar and scenario boundaries in a repeatable analytical output. An inventory planner can ask which items lose coverage before their next expected receipt and inspect the approved inputs and extraction times within their permissions. The report can distinguish a revised assumption from a new stock movement.

Keep forecasts and buying authority separate

We are not a forecasting engine and do not choose a service target or certify a supplier's arrival promise. This workflow analyzes approved records; it does not release a purchase order or change an ERP planning parameter. Any supported external action needs its own explicit permission and approval path. Missing availability history limits what the past sales rate can establish.

Use coverage as a dated scenario

Weeks of supply is useful when its eligible stock, demand basis and cutoff are visible together. Calculate the constant-rate ratio, then test the dated calendar when demand or receipts change within the horizon. Preserve the first uncovered requirement instead of allowing a later receipt to hide it. The planner can then decide whether the proposed buying response addresses the actual gap.

Review the inputs behind a stock-coverage warning

Bring one disputed coverage result, its stock snapshot and the demand and receipt versions behind it.

Questions about inventory coverage in weeks

Should safety stock be subtracted from eligible units?

State the service-policy convention before calculating. One view can measure coverage of all usable stock, while another measures coverage above a protected buffer. Label those views separately and avoid subtracting a buffer already removed by the source balance.

Can expected customer returns count as future supply?

Only a labeled scenario should include them, with quantity, usable date and release assumptions. A return authorization does not establish that stock has arrived or can be sold again. Keep current-stock coverage separate until those conditions are evidenced.

Why can two systems report different weeks of supply?

Compare their stock statuses, demand horizons, calendar buckets and receipt treatment. A trailing-average report and a dated forward scenario answer different questions. Reconcile those inputs before treating the difference as an arithmetic failure.