Most quality reports show a scrap percentage and a rework count, but neither of those numbers tells a plant manager what quality is actually costing the business in dollars, because the real cost of poor quality includes far more than the scrapped material itself — inspection labor, warranty claims, customer returns, and the engineering time spent chasing root cause all belong in the same figure. Cost of Poor Quality, or COPQ, is the standard framework for rolling all of that up into a single number, but calculating it accurately requires unit-level data that most plants simply don't have, since their quality systems record aggregate scrap rates rather than which specific unit failed and why. iFactory rolls COPQ up from unit-level events captured by vision inspection and sensor data feeding live statistical process control, so every scrap, rework, or customer return traces back to a specific unit, process step, and root cause instead of a monthly aggregate percentage. That level of detail is what turns a COPQ number from an accounting exercise into a prioritized action list, and iFactory support can help set up unit-level COPQ tracking on a priority line.
AI-Driven COPQ Analytics · Quality Management
Roll Up Cost of Poor Quality From Unit-Level Data, Not a Monthly Scrap Percentage
iFactory captures unit-level vision and sensor data feeding live statistical process control, so every dollar of COPQ traces back to the specific unit, process step, and root cause that generated it.
The Four COPQ Categories
Where Cost of Poor Quality Actually Comes From, Beyond Just Scrap
A COPQ figure that only counts scrapped material misses most of the real cost, since prevention activity, inspection labor, and downstream failure costs are all part of the same total. Breaking the figure into its standard four categories is what makes it possible to see which one is actually driving the number up.
Prevention Costs
Investment in process control, training, and quality system design meant to stop defects before they occur.
Appraisal Costs
Inspection, testing, and audit labor spent finding defects that prevention did not catch upstream.
Internal Failure Costs
Scrap, rework, and downgraded material identified before it ever leaves the plant.
External Failure Costs
Warranty claims, customer returns, and field failures discovered only after shipment.
From Unit Event to COPQ Dollar Figure
How a Single Defect Becomes a Traceable Line in the COPQ Rollup
1
Unit-Level Capture
Vision inspection and process sensors log a defect against a specific unit, batch, or heat number rather than an aggregate count.
2
Category Classification
Each event is classified as internal failure, external failure, appraisal, or prevention-related, based on where in the process it was caught.
3
Cost Attribution
Material, labor, and downstream cost figures are attached to the specific event, converting it into an actual dollar figure rather than a unit count.
4
Rolled-Up COPQ Dashboard
Individual events aggregate into a live COPQ figure broken out by category, process step, and root cause for prioritization.
A Scrap Percentage Tells You Something Is Wrong. It Doesn't Tell You What It's Costing or Why.
iFactory turns unit-level quality events into a real COPQ figure your team can actually prioritize against.
Aggregate Scrap Rate vs. Unit-Level COPQ
Monthly Scrap Percentage vs. iFactory Unit-Level COPQ Rollup
Function
Aggregate Scrap Percentage
iFactory Unit-Level COPQ
Root Cause Detail
Shows a rate but not which specific unit, process, or cause drove it
Every event traceable to a specific unit, process step, and cause
Cost Visibility
Counts scrapped material but rarely captures inspection or warranty cost
Rolls up prevention, appraisal, internal, and external failure costs together
Update Frequency
Typically compiled monthly from batch reports
Updates continuously as unit-level events are captured
Prioritization
Hard to know which improvement project would actually reduce cost most
Largest COPQ category and root cause surfaced automatically for action
External Failure Link
Field returns rarely connected back to the specific process that caused them
Customer returns traced back to the originating unit and process step
Measured Outcomes
What Quality Managers Report After Adopting Unit-Level COPQ Tracking
15-25%
Typical COPQ Reduction
Plants targeting their largest identified COPQ category report meaningful cost reduction within the first improvement cycle.
4
Cost Categories Tracked Together
Prevention, appraisal, internal failure, and external failure costs rolled up into one figure.
Unit-Level
Traceability on Every Dollar
Each cost line traces back to the specific unit and process step that generated it.
Live
Continuous COPQ Dashboard
Cost figures update as events happen rather than waiting for a monthly close.
10-14 Days
Typical Deployment Timeline
Time to establish unit-level tracking and a live COPQ dashboard for a priority line.
1
Prioritized Action List, Not a Report
Largest cost driver surfaced automatically instead of buried in a spreadsheet.
Field Case
Finding That Warranty Claims, Not Scrap, Were the Largest Share of COPQ
A quality team had spent two years focused on reducing an internal scrap rate that had already dropped substantially, yet overall quality costs had not fallen at anywhere near the same pace, and nobody could clearly explain why. After implementing unit-level COPQ tracking that connected warranty claims back to the specific process steps that produced the affected units, it became clear that external failure costs from a specific downstream assembly issue were actually the largest COPQ category, roughly double the size of the scrap costs that had absorbed most of the team's attention. Resources were redirected to the assembly process identified as the root cause, and total COPQ began declining meaningfully within the following quarter for the first time in two years.
2 YearsFocused on the wrong cost category
~2xLarger true cost driver identified
1 QuarterTo first meaningful COPQ decline
Frequently Asked Questions
Quality Managers and QA Engineers Ask These Questions First
What data do we need to start calculating COPQ at the unit level?
Unit-level COPQ requires linking defect or scrap events to a specific unit identifier, such as a serial number, batch, or heat, along with cost figures for material, labor, and any downstream cost like warranty claims. Most plants already have some version of this data spread across MES, quality, and finance systems, and the main work is connecting those sources so a single event carries its full cost picture.
Book a Demo to review what data your current systems already capture.
How are external failure costs like warranty claims connected back to the plant floor?
Where units carry a traceable identifier through to the field, a warranty claim or customer return can be matched back to its original production record, including which process step, shift, and equipment configuration produced it. This connection is what allows an external failure cost, which often shows up weeks or months after production, to still be attributed to a specific root cause on the floor rather than remaining a disconnected finance line item.
Does tracking COPQ this closely create extra work for quality engineers?
The unit-level capture itself is automated through vision inspection and sensor data rather than manual logging, so the ongoing data collection does not add work for quality engineers. What changes is that engineers spend their time acting on a prioritized cost breakdown instead of manually compiling and reconciling scrap reports from multiple systems each month, which is generally a net reduction in administrative work.
Can COPQ be broken down by product line, shift, or customer separately?
Yes, because the underlying data is captured at the unit level, COPQ can be sliced by product line, shift, customer, or any other dimension the unit record carries, rather than only being available as one plant-wide figure. This makes it possible to see, for example, whether a particular customer's returns are disproportionately tied to a specific shift or process configuration.
Contact support to discuss the breakdown views most useful for your reporting needs.
How long does it take to get a live COPQ dashboard running?
For a line with existing vision inspection or quality data capture, a unit-level COPQ dashboard typically takes 10 to 14 days to set up, connecting cost data and classification logic to the existing event stream. Lines without unit-level traceability in place yet generally require three to five weeks to establish that foundation first.
Book a Demo to get a scoped timeline for your quality data setup.
Know What Quality Is Actually Costing You, Down to the Unit and the Root Cause.
Unit-level COPQ tracking rolled up from live vision and sensor data, ready in as little as 10 days.
