A defect caught on the production line costs what it costs. The same defect caught by a customer costs 10 to 100 times more.1 Every quality professional knows this ratio. It shows up in textbooks, in training decks, in the mental math that justifies every inspection station on the floor. And yet the number of defects reaching customers is climbing.
Sedgwick’s 2026 State of the Nation index recorded 3,295 product recalls across five U.S. industries in 2025, with 858 million defective units, a 26% increase in volume over the prior year. European automotive recalls hit an all-time high of 900 events, up 34.5%. The direction is clear. More defects are escaping. And they’re escaping faster.
Quality discipline hasn’t gotten worse. If anything, inspection technology has never been more capable. The problem is that the fastest-growing category of defect is one that most quality systems were never configured to catch.
A defect category the QMS can’t handle independently
More than 13 million vehicles were recalled for software-related issues in 2024. This is a 35% year-over-year increase. Ford had a record recall year in 2025, with warranty costs consistently above $4 billion annually. A single fuel-injector recall covering 694,000 Bronco Sport and Escape vehicles carried an estimated cost of $570 million. CEO Jim Farley called quality the company’s largest near-term cost opportunity and described the situation publicly as “self-inflicted wounds.”
The pattern extends well beyond automotive. As products become software-defined, the defect profile shifts with them. Firmware interactions, integration errors between embedded systems, over-the-air update failures, etc. These aren’t dimensional or mechanical issues that a coordinate measuring machine or a torque verification station will catch. They’re failures that live in code. In the interface between components. In the behavior of systems under conditions that testing didn’t fully anticipate.
The quality management systems running in most plants were largely designed for a physical-defect world. Statistical process control, incoming material inspection and end-of-line functional testing are more necessary now than ever.
The seam where escapes happen
Software-defined defects are the most visible example. But the underlying problem is structural. Even for traditional defects, the escape almost always happens at a seam between systems.
Inspection results live in the QMS. Production parameters live in the MES. Equipment maintenance history lives in the CMMS. Material lot data lives in the ERP. A quality engineer investigating a suspect trend has to manually pull data from two, three, sometimes four platforms and reconcile it before the root cause even comes into focus. That takes hours. Sometimes days. And during those hours, production continues, defective units move downstream and the cost multiplier climbs.
LNS Research found that more than four in ten manufacturers don’t know their total cost of quality. That can't be chalked up to a discipline failure. It’s a visibility failure. The data exists in each system individually. What doesn’t exist is the connection between them that would make cost-of-quality measurement automatic. As opposed to a quarterly archaeology project.
What upstream detection actually requires
Catching defects at the source means more than adding inspection points. It's about building the data connections that let a quality signal travel backward from the symptom to the cause. In real time. Across systems that were never designed to talk to each other. Four capabilities separate plants that catch defects upstream from those that find out when the customer calls.
Quality data connects to production context in real time. An inspection result alone is a data point. The same result links to the process parameters that produced it: the maintenance state of the equipment, the material lot and the operator shift become a root-cause signal. Most quality systems capture the result. Few connect it to the full production context at the moment it’s generated. Closing that gap is what turns reactive quality investigation into real-time detection.
Detection coverage extends to software and integration failures. AI-powered machine vision continues to raise the bar for physical inspection. Intel’s wafer vision inspection system saves roughly $2 million per year in scrap. Automotive case studies show escape rates dropping from 2.3% to 0.1%. But vision systems don’t catch firmware bugs. Software-defined products need a parallel detection layer: automated integration testing, firmware validation protocols and post-update behavioral monitoring. The plants adding these capabilities alongside traditional inspection are the ones keeping pace with their own product complexity.
Close the loop between field and factory
Some of the most valuable quality signals arrive after a product ships. Warranty data. Service records. Field-failure reports. Customer complaints. These signals often contain patterns that production quality models never encountered during testing. A recurring field failure in a specific temperature range might expose a process parameter that passes every in-plant inspection. Feeding that signal back into the production quality model helps the system learn which escape patterns to watch for in the loop that most plants still haven’t closed. The ones that have closed it catch the second-occurrence defects before they ship.
A single quality record that travels with the product. The reason four in ten manufacturers can’t quantify their cost of quality is that quality data fragments across QMS, MES, CMMS and ERP. Each system holds a piece. Nobody holds the whole picture. A unified quality record, one that follows the product from material receipt through production through field performance, eliminates the reconciliation lag that lets defects accumulate undetected. It also makes regulatory response faster when recalls do occur, because the traceability chain already exists.
The compounding math
A quality escape is the purest compounding event in manufacturing. One escaped defect can trigger a line stoppage for containment. Or a CAPA investigation that pulls engineers off other work. Or a warranty claim, a regulatory filing and, at volume, a recall. Each of these events generates its own costs and each one takes longer and costs more when the systems involved aren’t connected.
NHTSA levied a $165 million civil penalty against Ford in 2025. Europe’s record 900 automotive recalls in a single year represent hundreds of millions in aggregate remediation costs across the industry. These are the visible numbers. The invisible ones, the production hours spent investigating, the throughput lost to containment holds, the customer trust that erodes with each incident, compound in ways that no single quality metric captures.
The disconnect between systems is what allows the compounding to accelerate. A connected quality infrastructure doesn’t prevent every defect. But it compresses the time between occurrence and detection, which is where most of the cost multiplier lives.
The coverage question
The quality systems most manufacturers run were designed for a world where defects were physical. Inspection was the last line of defense and the product didn’t change after it shipped. That world is receding. Products are more software-defined, supply chains are distributed and the cost of a single escaped defect has never been higher.
The question for every quality leader isn’t whether their current system works. It probably does. For the defect categories it was built to find. The question is whether it covers the risks that matter most today. And whether the blind spots become visible before the next shipment leaves the line.
The cost of manufacturing complexity can add up quickly. Read our whitepaper to learn more about how to change the math.