Handling Rejected Parts and Customer Complaints

Published by
Throne of Profit Editorial

Reviewed by
William Hassell
Founder & Chief Editor, Throne of Profit

Every shop gets returns. A dimension runs out of tolerance, a batch ships with the wrong finish, a customer's inspector flags a burr your operator waved through. The return itself isn't what loses the account. What loses the account is the second return — the same defect, on the same part, three months later, after you swore it was handled. A rejected part is a warning, not just a credit note; if you only issue the credit and skip the fix, you've paid for the lesson and thrown it away.

Most small manufacturers treat complaints as isolated fires: replace the part, eat the cost, move on. But a defect that reached the customer got past everything you had — setup, operator, inspection, packing. Closing the loop means finding where it slipped through and changing something so it can't slip through again. That's corrective action, and it's the difference between a customer who trusts you more after a problem and one who quietly moves the work to your competitor.

   A REJECTED PART: TWO PATHS

   return arrives
        │
        ├─ replace + credit only ──────► defect returns → account at risk
        │
        └─ contain → find root cause →
             fix the process → verify ─► defect gone → trust rebuilt

Owner symptoms

• The same defect keeps coming back on repeat parts, even after you "handled" it.

• Complaints get resolved by replacing product, but nobody knows why it happened.

• A customer's quality team is asking for a corrective-action report and you're improvising.

Why this happens

A return triggers an urgent, emotional response: the customer is unhappy, product is down, and everyone wants it made right fast. So the shop does the one thing it knows how to do quickly — remake the part and ship a replacement. That satisfies the symptom and feels like resolution. But remaking the part answers "how do we make the customer whole today," not "why did a bad part leave the building." Those are different questions, and the second one rarely gets asked because it's slower, less satisfying, and nobody owns it. So the root cause stays in the process, waiting to reoccur.

Common mistakes

• Fixing the part, not the process — replacing product while leaving the cause untouched.

• Guessing at the cause instead of tracing the actual part back through the job.

• No containment step — not checking whether other shipped or in-process lots have it too.

• Skipping verification — assuming the fix worked without proving it on the next run.

• No paper trail, so the customer can't see you took it seriously and neither can you.

Business consequences

A single return is cheap; a pattern of returns is how you lose an account. When the same defect reappears, the customer stops seeing bad luck and starts seeing a supplier who can't control their process — and that judgment moves work elsewhere, quietly and permanently. It also invites tighter incoming inspection, source inspection visits, and the reputation that follows a shop from one buyer to the next. The owner who runs a real corrective-action process spends more on the first occurrence and far less over the relationship: the defect gets designed out, the customer watches you handle it like a professional, and a problem becomes proof you're worth keeping.

How experienced operators think about it

They separate two jobs that panic tends to fuse: contain the damage and find the cause. Containment is fast and defensive — quarantine suspect stock, check other lots, protect the customer from a second bad shipment. Root cause is slower and honest — walk the actual rejected part backward through the traveler, the setup, the tooling, the inspection point it passed, and keep asking why until you reach something you can change in the process, not just something you can blame on a person. Then they change it, and they verify on the next run rather than hoping. The mindset is that a defect that escaped is free information about where your controls are thin — and it's cheaper to fix the hole than to keep patching parts.

Practical actions

1. Contain first. Quarantine the returned lot and check whether other shipped or in-process work shares the same setup, material lot, or operation.

2. Trace the real part backward. Follow the specific rejected piece through its job history to the operation where the defect was introduced — don't theorize from the desk.

3. Find the process cause, not the person. Keep asking why until you hit something you can change: a fixture, a check, a setup step, a tolerance nobody flagged.

4. Change one thing and verify it. Adjust the process, then prove the defect is gone on the next run before you call it closed.

5. Write it down and send it. A short corrective-action record — problem, containment, cause, fix, verification — protects the account and builds your own history.

Questions every owner should ask

• When a part comes back, do we find the root cause, or just remake the part?

• Could this same defect be sitting in other lots we've already shipped?

• If a customer asked for a corrective-action report tomorrow, could we produce one?

Frequently asked questions

What's the difference between containment and corrective action?
Containment is the fast, defensive move: stop the bleeding by quarantining the bad lot and checking whether other shipped or in-process parts have the same problem, so the customer doesn't get a second bad shipment. Corrective action is the slower fix: trace the defect to its root cause in your process and change something so it can't happen again. You need both. Containment protects the customer this week; corrective action protects the account long-term. Skipping containment risks a repeat shipment; skipping corrective action guarantees a repeat defect.

How much of a corrective-action process do I really need for a small shop?
Less formal paperwork than a big supplier, but the same thinking. You don't need a software system — you need a repeatable habit: contain, trace the actual part to a root cause, change the process, verify it worked, and write down what you did. A single-page record per significant return is enough to satisfy most customers and to build your own history of what fails and why. The discipline matters more than the format; the goal is that the same defect never surprises you twice.

Related articles

• Running a Profitable Small or Midsize Manufacturing Business — the pillar.

• Getting Through a Customer or Certification Audit — how corrective-action records hold up under scrutiny.

• Tracking Material and Lots So You Can Prove What You Shipped — the traceability that makes root-cause tracing possible.

• Why Jobs Take Longer Than You Quoted — rework and returns as hidden time drains.

• Where Time Leaks on a Typical Job — where defects and rework eat the schedule.

Every business has more decisions than time

Whether you need help solving one problem, evaluating a major opportunity, or making a company-changing decision, Throne of Profit gives you consulting capacity on demand.

Purchase only the consulting capacity you need and use it across Weekly Focus, Strategic Focus, Financial Focus, and ThinkTank engagements.

Explore Throne of Profit