If you’ve spent enough time in manufacturing, you’ve probably experienced it. The customer sends a claim, the photographs arrive, the complaint is entered into the portal, and the deadline starts counting.

Somewhere inside your organisation, someone looks at the evidence and says:

“But this isn’t our fault.”

Sometimes they’re right. Not every customer claim is technically justified. Not every defect found at the customer was necessarily created by your process, and not every conclusion in the first customer email will survive a proper investigation.

But this is exactly where many suppliers make a dangerous mistake.

They start defending themselves before they start controlling the situation.

“Not Our Fault” Is a Conclusion — Not a First Response

When a claim arrives, the temptation to defend the company can be immediate. “We checked our process.” “We’ve never seen this defect.” “Our inspection records are OK.” “This could have happened after delivery.”

Perhaps. But at the beginning of a claim, those are possibilities.

They are not yet evidence.

A strong supplier does not accept blame without facts, but it also does not reject responsibility before the facts are known. At the beginning of a claim, the goal is not to win the argument. The goal is to understand the risk, protect the customer where necessary, and establish what actually happened.

You can challenge a claim and still protect the customer.

Those two things are not contradictory.

Customer Protection Is Not an Admission of Guilt

This distinction is critical. When the customer reports a possible defect, their first concern is usually not who will eventually be blamed. Their first concern is whether they are protected.

Can production continue? Can existing stock be used? Is more suspect material on the way? Is the next shipment safe? Does anything need to be isolated while the investigation continues?

Those questions exist regardless of who ultimately caused the problem. That means you may need to temporarily identify suspect stock, verify shipments, review traceability, inspect material, or introduce additional controls while technical responsibility is still being established.

That is not admitting fault.

It is managing risk.

Protect first. Investigate fairly. Decide responsibility from evidence.

Because the Customer Has a Problem Right Now

From the supplier’s side, the debate may be: “Who caused the defect?” Inside the customer, the questions may be very different.

The customer may already be managing operational disruption before technical responsibility has been established. If your first reaction is only “This isn’t ours,” you may be answering a question the customer isn’t ready to ask yet.

First, they need control. Responsibility can be established through the investigation.

Evidence Changes the Conversation

If you genuinely believe the claim was not caused by your organisation, arguing harder is rarely the solution.

Bring evidence.

The stronger the evidence, the less emotional the discussion needs to become. Start with the basics.

The objective is not to build a legal defence. The objective is to reconstruct what actually happened.

The part, the batch, the production history, the inspection evidence, the shipment, and the customer finding all need to connect.

If those pieces do not connect, you have an investigation to continue—not a conclusion to defend.

Traceability Can Be Your Strongest Argument

There is a huge difference between saying:

“We don’t think this came from us.”

and being able to demonstrate:

“The claimed component has been traced against the identified delivery, production batch and available inspection records. The evidence currently does not support the reported failure originating within the reviewed production scope.”

One is an opinion. The other is an evidence-based position.

Strong traceability allows you to narrow the suspect population. It allows you to show what was produced, when it was produced, what was checked, what was shipped, and where the material went.

It can support your customer and protect your company.

Most importantly, it can turn a disagreement into a factual investigation.

Don’t Confuse Confidence With Defensiveness

There is nothing wrong with defending your organisation when the evidence supports you. The problem is how you do it.

Defensive responses often sound like: “Impossible.” “Our process cannot create this defect.” “Everything was checked before shipment.” “This must have happened at your site.”

Those sentences may feel strong internally. To the customer, they can sound like the supplier has already decided the result before completing the investigation.

A more controlled position is:

“Our current evidence has not identified the reported failure within the reviewed production records. Customer protection remains active while both sides complete the evidence review.”

Calm, factual, professional—and importantly, it leaves room for the facts to lead the investigation.

Sometimes the Claim Really Isn’t Yours

A proper investigation may eventually show that the original assumption was wrong. If that happens, you should be able to explain why with evidence—not emotion, frustration, or twenty years of experience telling you that your process “couldn’t possibly” have done it.

Evidence.

If the evidence proves the claim was not caused by your organisation, that should be communicated professionally and clearly.

But here’s the interesting part: the customer will remember how you behaved while responsibility was still uncertain.

Did you help protect them? Did you respond quickly? Did you share evidence? Did you stay factual? Did you work with them to understand what happened?

Or did the relationship turn into a courtroom within fifteen minutes of receiving the complaint?

There Are Two Responsibilities

This is the distinction I believe matters most.

There is technical responsibility for causing the failure, and there is professional responsibility for managing the situation.

You may eventually prove that you did not cause the defect. But while the facts are being established, you still have a responsibility to manage your side of the investigation properly.

Receive the claim. Understand the risk. Protect the customer where necessary. Secure the evidence. Check traceability. Communicate what is known. Explain what remains unknown. Define when the next update will come.

You don’t have to accept blame to demonstrate control.

The Best Claim Response Is Not Defensive or Submissive

It is evidence-based. That’s the balance.

Don’t accept responsibility simply because the customer raised the claim. But don’t reject responsibility simply because the claim is inconvenient.

Protect the customer. Investigate properly. Follow the traceability. Let the evidence decide. And communicate professionally throughout the process.

Because being right and handling the claim well are two different things.

The strongest suppliers do both.

So here’s the question I’d like to put to the manufacturing community:

Have you ever received a customer claim that was eventually proven not to be your fault?

And perhaps the more interesting question:

How did your organisation behave before the evidence proved it?

Protect first. Prove with evidence. Let the facts decide.