How do I analyse stockouts and out-of-stock events with iDBQuery?

Ask iDBQuery 'Which products went out of stock last month, and what sales did we likely lose?' It finds zero-inventory periods across your stock and sales tables, estimates missed demand, returns the impact as a chart, and cites each stockout to its source rows.

A stockout is when a product hits zero inventory and you cannot fulfil demand, costing sales and eroding trust. iDBQuery helps you find where and when stockouts happened and estimate what they cost.

  • You'd ask iDBQuery: 'List products that were out of stock at any point last month, how many days each was unavailable, and the estimated lost sales based on their normal daily rate.'
  • It scans your inventory history for zero-balance periods, compares them to typical sales velocity, and returns a ranked table plus a chart of estimated impact.
  • Each stockout is cited to its source rows, so 'SKU 3320 was out for 6 days' traces to the exact inventory records.

The estimate of lost sales is directional and iDBQuery shows the SQL behind it, so a planner can refine the assumption. Follow-ups flow naturally: 'Which supplier's products stock out most often?' or 'Were the stockouts on our highest-margin lines?' Because inventory, sales, and supplier data often sit in different systems, the one live model joins them so the answer is complete. Pair it with demand forecasting to prevent the next one. Save the stockout report as a recurring alert-style report, and let the Analyst agent surface the products most likely to run short before their next delivery, backed by the underlying rows.

Updated 2026-06-22