How to Track Supplier Defects and Incoming Quality Trends

A supplier defect found at incoming inspection is easy to record badly. “Parts rejected” in a spreadsheet may be enough to stop the lot today, but it gives Purchasing and Quality very little to work with next month.

Useful supplier-quality data starts at receiving. The inspection record should show what arrived, what was checked, what failed and what happened to the lot. It should also make repeat problems visible without somebody rebuilding the history in Excel.

Start with traceability at goods-in

An incoming inspection record needs to identify the material and the transaction that brought it into the business. Depending on the industry, that normally includes:

• supplier
• purchase order and goods receipt
• part number and revision
• supplier part number, where different
• lot, batch, date code or serial number
• quantity received
• inspection date and inspector

This is the chain needed later when a defect is found in production or a supplier asks which shipment is affected. A description and photo without lot and receipt details may prove that a fault existed, but it does not define the exposure.

Use an inspection plan, not a generic checklist

Different components carry different risks. A generic pass/fail form tends to produce inconsistent inspections because the inspector must decide what to check each time.

The inspection plan should be tied to the part or part family. It can include visual checks, dimensions, certificates, packaging, date codes, labelling, functional tests and any characteristics that have caused trouble before.

Where statistical sampling is suitable, an AQL-based plan can determine the sample size and acceptance criteria from the lot size, inspection level and defect class. Critical, major and minor defects should not share one acceptance rule. Neither should a proven supplier and a supplier whose quality has deteriorated.

Record defects in a form that supports action

A defect record must make sense to somebody who did not perform the inspection. Capture the measured or observed result beside the requirement. Add clear photos, mark the affected feature where useful and retain test output or certificates with the record.

Structured fields are needed for reporting:

• defect category
• defect severity or class
• quantity inspected and quantity defective
• inspection result
• part and supplier
• lot or batch
• repeat-defect indicator
• linked NCMR, SCAR or return record

The defect description remains important, but categories should come from a controlled list. Otherwise the same issue appears under several names and disappears into the reporting noise.

A rejected sample does not finish the job

Once an inspection fails, the business needs a controlled response. The received lot may be placed on hold, returned, sorted, subjected to tighter inspection or released under an approved concession.

The response depends on risk and operational need, but the record should answer four questions:

1. What material is affected?
2. How was it contained?
3. Who approved the disposition?
4. What supplier follow-up is required?

A failed incoming inspection will often create an NCMR. The inspection record contains the checks and results. The NCMR controls the non-conforming material through containment, disposition, approvals and closure. Linking the two avoids retyping evidence and keeps the audit trail intact.

Escalate suppliers using defined rules

Sending a corrective-action request for every isolated defect wastes time. Failing to escalate repeated faults teaches the supplier that each rejection will be treated as a separate event.

Set practical escalation triggers. These may include:

• a repeat defect within a defined period
• a critical characteristic or safety risk
• line disruption or customer exposure
• cost above an agreed threshold
• several failed lots or deteriorating incoming yield
• an ineffective previous corrective action

The trigger should open the appropriate supplier corrective-action process and retain the source inspection and NCMR links. Quality history should be available during supplier review, not assembled after the meeting has started.

Measure supplier performance without hiding the detail

A single supplier score can be convenient, but it can also hide the problem. Review the underlying measures:

• lots accepted and rejected
• incoming yield
• defects by category and severity
• repeat defects by part number
• response and closure time for corrective actions
• scrap, sorting, rework, freight and line-impact costs

Normalise the figures where necessary. A supplier delivering two small lots should not be compared with a supplier delivering hundreds of lots using defect count alone. At the same time, do not let a good percentage hide a critical failure.

Let inspection history change the next inspection

The useful loop runs back to receiving. If a supplier’s performance deteriorates, move to tightened inspection, add a check for the recurring feature or require additional evidence. When sustained performance improves, the plan may return to normal or reduced inspection under your defined rules.

This is where incoming quality control becomes more than record keeping. Past results affect the amount and type of verification applied to the next lot.

A quick test for your supplier-quality records

Choose one supplier and one part number. Can you retrieve every received lot, inspection result, defect photo, NCMR, disposition and supplier response from the past year? Can you see whether the same defect is becoming more or less common?

If the answer requires several spreadsheets, email searches and a manually prepared chart, the data exists but the process is not connected.

NS-eIQC incoming quality control software manages AQL sampling, part-specific checks, measurement records, defect evidence and supplier trends. When material is rejected, NS-NCMR carries the issue through containment, MRB disposition, supplier responsibility and closure.