# Stockout Root Cause Report Template

> Source: https://netray.co/tools/stockout-root-cause-report-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A structured report to investigate a stockout, classify the cause and assign corrective actions with owners.

## Category

supply-chain

## Audience

- Materials planner
- Supply chain manager
- Plant manager

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company

**Key:** company

**Type:** text

**Default:** Acme Precision Ltd

#### Report number

**Key:** report_no

**Type:** text

**Default:** SO-2026-031

#### Report date

**Key:** date

**Type:** date

**Default:** 2026-10-20

#### Prepared by

**Key:** author

**Type:** text

**Default:** A. Planner

#### Part number

**Key:** part_no

**Type:** text

**Default:** PCB-7710

#### Date stock reached zero

**Key:** stockout_date

**Type:** date

**Default:** 2026-10-12

#### Duration of stockout

**Key:** duration

**Type:** text

**Default:** 5 working days

#### Impact

**Key:** impact

**Type:** textarea

**Default:** Assembly line 2 stopped for two shifts. Two customer orders shipped three days late.

#### Primary cause category

**Key:** cause_category

**Type:** select

**Options:**

- Forecast error
- Supplier late delivery
- Planning parameters wrong
- Inventory record inaccuracy
- Quality rejection
- Demand spike
- Process or transaction error

**Default:** Supplier late delivery

#### Five whys summary

**Key:** why

**Type:** textarea

**Default:** Supplier shipped 18 days after the confirmed date. The lead time in the item master was 42 days while the last three receipts averaged 49 days. The reorder point was therefore too low.

#### Corrective actions

**Key:** actions

**Type:** textarea

**Default:** Update planned lead time to 50 days. Raise safety stock after recalculation. Add supplier delivery review to monthly meeting.

**Blocks:**

#### Stockout Root Cause Report

**Body:** Company: {{company}}
Report no: {{report_no}}
Date: {{date}}
Prepared by: {{author}}

#### Summary

**Table:**

**Columns:**

- Part
- Stock reached zero
- Duration
- Primary cause

**Rows:**

**0:** {{part_no}}

**1:** {{stockout_date}}

**2:** {{duration}}

**3:** {{cause_category}}

#### Impact

**Body:** {{impact}}

#### Root cause analysis

**Body:** {{why}}

#### Corrective and preventive actions

**Table:**

**Columns:**

- Action
- Owner
- Due date
- Status

**Rows:**

**0:** {{actions}}

**3:** Open

#### Review and approval

**Signatures:**

- Planner
- Purchasing manager
- Operations manager

**Notes:** Keep the analysis factual and blame-free. This is a starting template; adapt the cause categories to your own planning policy.

## Content

**Intro:** A stockout is rarely one failure. It is usually a chain: a parameter that was off, a supplier that slipped, a record that was wrong. This template guides a short, honest investigation that ends with actions and owners.

**Sections:**

#### How to fill it in

**Body:** Complete it within a week of the stockout while the facts are fresh. Record when stock reached zero and for how long, then describe the real impact in terms the plant manager cares about: lines stopped, orders late, expedite cost. Choose the primary cause category and use the five whys field to walk back from the symptom to the parameter, process or behaviour that allowed it.

#### Cause categories explained

**Body:** Each category points to a different fix. Forecast error leads to review of demand planning inputs. Supplier lateness leads to lead time and supplier management. Planning parameters wrong means reorder point, safety stock, lot size or lead time in the item master. Record inaccuracy means cycle counting and transaction discipline. Quality rejection means incoming inspection and supplier quality.

**Bullets:**

- Pick one primary cause, list others in the narrative
- Check item master parameters before blaming the supplier
- Verify on-hand accuracy for the part and its bin

#### Closing the loop

**Body:** The report is only useful if actions are tracked. Add each action with an owner and a due date, review them in the monthly inventory meeting, and close the report when the changes are in the ERP. Over a quarter, count reports by cause category. If most are planning parameters, a parameter review will prevent more stockouts than expediting ever will.

#### Common mistakes

**Body:** Stopping at the supplier as the root cause, writing actions with no owner, and skipping the on-hand check are the common ones. Another is writing the report only for big events; a handful of small ones often reveal the same parameter problem.

**Cta:** We can help surface likely stockout causes from your ERP history automatically, so the report starts with evidence. Ask for a short review.

**Faq:**

#### When should I write a stockout report?

**Answer:** Whenever stock reaches zero and it affects production or a customer order, or when a part you classed as critical runs out. Many plants set a threshold on days of impact or value at risk.

#### Is five whys enough?

**Answer:** For most planning stockouts, yes. For repeated or complex events use a fuller method such as a fishbone diagram or 8D. The template can be attached to either.

#### How is this different from a shortage log?

**Answer:** A shortage log tracks what is short today. This report analyses why a past stockout happened and what will prevent it, so the two work together.

#### Who should review it?

**Answer:** The planner, the buyer, and a plant or operations manager. Include quality if the cause was a rejection, and finance if expedite or write-off costs were significant.

## Search terms

stockout root cause analysis template, stock out report format, material shortage investigation form, stockout report word, why did we run out of stock, inventory stockout analysis

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json