How to Use Shopify Days of Inventory Remaining

Shopify defines days of inventory remaining as ending tracked inventory divided by average quantity sold per day. Its inventory report uses recent variant sales to estimate how long stock may last. Read the value as a planning signal, not a promised stockout date. The estimate does not know a future promotion, vendor delay, marketplace allocation, wholesale order, or demand shock unless those effects already appear in the records. Note the report period, ending date, location scope, active days, ending quantity, and units sold per day before copying the result into a purchasing decision.

Classify special values before assigning urgency. Shopify sets days remaining to N/A when the selected variant has no sales rate to support the estimate and can show zero when ending inventory is negative. Neither state means the same thing as a well-measured imminent stockout. Investigate tracking configuration, negative inventory, product launch status, stock availability, report processing delay, and sales history. Preserve the raw value and the reason for any override so a corrected inventory record is not mistaken for a changed demand forecast.

Compare ending quantity with Shopify inventory states and the operational ledger. Available, committed, incoming, unavailable, and on-hand quantities answer different questions. A high on-hand count may include units that cannot serve new orders, while incoming stock may miss the required date. Reconcile purchase orders, transfer receipts, returns, damaged stock, quality holds, fulfillment-service requests, and manual adjustments. Shopify's quantity sold measure does not represent every inventory adjustment, so review adjustment history when the ending quantity differs from the warehouse or 3PL count.

Check location-level coverage when fulfillment is distributed. A network can show adequate total inventory while one location reaches zero early and routing shifts orders farther away. Compare days remaining, observed demand, inbound dates, capacity, and routing priority by location. Use a transfer only when transport time, receiving capacity, service effect, and opportunity cost are better than the approved alternative. Keep purchase, transfer, expedite, and promotion decisions in one ledger so two teams do not respond to the same signal with conflicting inventory movements.

Define action bands from observed supplier lead time, receiving variance, service goals, and the existing reorder-point policy. Do not publish one universal days-remaining threshold. Fast domestic replenishment and a slow variable import require different review and order bands. Include minimum order quantity, case pack, cash constraint, shelf life, storage capacity, planned promotions, and safety stock. Assign each flagged variant one action: reorder, expedite, transfer, pause promotion, adjust routing, investigate data, or hold, with an owner and next review date.

Use sell-through as context rather than a substitute. Shopify calculates product sell-through from units sold relative to units sold plus ending inventory for the period. A high sell-through rate can accompany low absolute volume, while a low rate can be intentional during seasonal buildup. Compare sell-through and days remaining with revenue, contribution, stockout cost, forecast, and inbound commitments. Document the date window and quantity scope in every decision so later reviewers can distinguish a measured change from a different report period.

After the expected stockout or replenishment date passes, compare predicted coverage with actual inventory and orders. Explain variance through demand, availability, adjustments, receipts, returns, cancellations, or data latency. Do not label the report inaccurate until inputs and period are reconciled. Track decision outcomes separately from forecast accuracy: an expedite can prevent a stockout while adding cost, and a promotion pause can preserve service while reducing sales. The metric supports the decision, but supplier execution and operator action affect the result.

Review definitions whenever Shopify changes reports or the business changes fulfillment topology. Validate new locations, bundles, subscriptions, preorder logic, marketplace reservations, and 3PL integrations against the same inventory contract. Keep a fallback export for periods when analytics are delayed. Revisit thresholds using observed forecast error, lead-time variance, and service outcomes. A governed process survives interface changes because quantities, assumptions, decisions, and owners remain traceable instead of living only in a current dashboard tile.

Create a weekly exception table with variant, location, ending quantity, units sold per day, reported days remaining, open inbound quantity and date, supplier lead time, safety buffer, assigned action, and owner. Add a reason code for N/A, zero, negative inventory, promotion, launch, or data mismatch. Review the table with purchasing, warehouse, marketing, and finance owners so one team does not optimize service while another optimizes cash using different quantities. Close each row only when the source record and operational action agree, then retain the outcome for threshold calibration.

Sample variants outside the alert bands as a control. Confirm that adequate-looking coverage is not hiding unavailable stock, an overdue inbound, a broken sales rate, or a location imbalance. Compare the prior forecast with the current report and explain large changes. When an action is deferred, record the reason and the condition that will reopen it. This gives operators evidence for both intervention and restraint, reducing duplicate orders and unnecessary expedites.