> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to measure the cost of poor quality
- URL: https://blog.jestor.com/measure-the-cost-of-poor-quality/
- Published: 2026-09-16T18:56:06.000Z
- Updated: 2026-09-16T18:56:06.000Z
- Author: Bruno Bannach

Measuring the **cost of poor quality** means counting everything a defect causes, not the value of the defective item. In **Jestor**, returns, rework, support contacts and warranty claims can all connect to the product and batch, which makes the full cost calculable.

## Why quality costs are underestimated

The visible cost of a defect is the item itself. That is usually the smallest component.

The larger costs are the inspection performed on everything because defects occur, the rework, the return, the support contact, the replacement shipment and the customer who does not return. None of these appear in a scrap figure.

Components usually excluded:

- Inspection of good units, performed because defects exist
- Rework labour
- Return shipping and processing
- Support contacts generated
- Replacement fulfilment
- Lost future purchases

## Categories of quality cost

| Category         | Examples                       | Visibility        |
| ---------------- | ------------------------------ | ----------------- |
| Prevention       | Training, better specification | Budgeted          |
| Appraisal        | Inspection and testing         | Visible           |
| Internal failure | Scrap and rework               | Partially visible |
| External failure | Returns, warranty, support     | Usually hidden    |
| Lost business    | Customers who do not return    | Invisible         |

## Step by step to measure it

1. **Connect returns and claims** to the product and batch.
2. **Link support contacts** to the order they concern.
3. **Record rework time**, not only rework occurrence.
4. **Include inspection cost**, which exists because of expected defects.
5. **Calculate cost per defect**, including everything downstream.
6. **Compare against prevention cost**, which is usually far lower.
7. **Prioritize by total cost**, not by defect count.

## Why prioritizing by count misleads

The most frequent defect is often cheap to absorb, while a rare one generates returns, support and lost customers. Ranking by total cost rather than by occurrence changes which problem gets fixed first, and it is usually not the one people complain about most.

## Why choose Jestor

In **Jestor**, returns, warranty claims, support tickets and inspections can all connect to the product and batch as related records, which is what makes a cost formula across them possible. Dashboards group by product, batch or supplier from the same data, with drill down to the underlying records.

## Frequently Asked Questions

### What is most often left out of quality cost?

External failure costs such as support contacts and return processing. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Should defects be prioritized by frequency?

No. Prioritize by total cost, which frequently ranks them differently.

### Why include inspection cost?

Because inspecting good units is a cost incurred only because defects are expected.

## Video Tutorial: Step by Step

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by **AI**. Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.