INDEPENDENT QUALITY SYSTEMS PUBLICATIONPROCESS / CONTROL / EVIDENCE

Supplier quality / PRACTICAL EXPLANATION

Nonconforming Supplier Products

Nonconforming supplier products are external outputs that do not meet applicable acceptance requirements.

Nonconforming supplier products are external outputs that do not meet applicable acceptance requirements. The organisation needs to identify affected items, control unintended use and decide authorised disposition. The immediate handling decision and the later supplier improvement response are related but separate activities.

The Supplier Quality Management Guide: Selection, Evaluation and Monitoring places this topic in its wider QMS context. Technical concessions, rework and release decisions require appropriate authority and applicable customer or other requirements. This guide does not supply product-specific acceptance limits.

Define the decision and its boundary

Define the acceptance boundary for nonconforming supplier products before work begins. Explain which information must be available and what happens if it is incomplete. A colleague should be able to recognise a case that needs clarification without inventing a local rule. Review the boundary whenever customers, delivery arrangements or the nature of the work change, because old assumptions can remain hidden in familiar routines.

Maintain clear status when a delivery is split between accepted, rejected and awaiting-decision quantities. Repacking or moving items can destroy the practical separation established at receipt. Ensure systems and physical identification agree, and identify who may change the status. Preserve relevant supplier information so that later investigation can connect the items to orders, revisions and delivery records without relying on a staff member’s memory.

Put the method into practice

The following working sequence connects nonconforming supplier products with routine delivery. Test it on a small number of representative cases before making it the default. Check who handles a rejected input, a changed requirement or an absent decision maker. Exceptions reveal practical weaknesses that a successful normal case can hide, especially where responsibility crosses organisational boundaries.

  1. Identify the requirement, affected population and immediate control needed.

  2. Assess traceability and decide authorised disposition with relevant functions.

  3. Communicate the issue and evaluate whether supplier corrective action is warranted.

Worked example

A fictional warehouse finds a delivery with labels that do not match the agreed item identification. It segregates the affected stock and checks whether any units were already issued.

An authorised review determines disposition and customer impact. Purchasing communicates the facts to the supplier while operations retains control of stock status.

The fictional case illustrates nonconforming supplier products; it is not a published benchmark or a promised improvement. Compare the explanation with evidence from the affected work before copying the response. A convincing story can suggest a mechanism, but only observations from the real process can establish whether that mechanism applies and whether the proposed response addresses it.

Useful evidence and records

Design the record for nonconforming supplier products around continuity. Another competent person should be able to understand what was decided, what evidence supported it and what remains to be done. Avoid long copied passages when a controlled reference would be clearer. Equally, a bare link without context may become meaningless after a system change, so retain a useful description of the evidence.

Record elementWhat it should establish
IdentificationAffected items and traceability
RequirementAcceptance condition not met
DispositionAuthorised decision and conditions
CommunicationParties informed and response needed

Check the result and avoid a common mistake

Returning stock without checking earlier issues can leave affected items in use. Avoid assuming that the visible delivery is the entire population without examining relevant evidence.

Trace the disposition to authority and inspect status identification. Check whether immediate controls remained effective until the final decision was implemented.

Review nonconforming supplier products after sufficient relevant work has occurred to make the comparison meaningful. Define the evidence before examining the result, which reduces the temptation to select only favourable observations. Consider changes in volume, complexity or reporting practice. If a conclusion depends heavily on one assumption, test that assumption directly or explain why the decision remains provisional.

Connect the next decision

When nonconforming supplier products exposes a disagreement, separate missing facts from competing priorities. Further data may resolve the first, while the second needs an accountable management choice. Record the chosen approach and the conditions that would prompt reconsideration. This allows later reviewers to assess the reasoning fairly instead of judging an earlier decision using information available only afterwards.

Use Supplier Re-Evaluation Process when the work moves to the adjacent decision. The related guide to record control explains the wider process dependency. The handover should identify what has been accepted, what remains open and who will review the next evidence. Keep the original decision traceable when later information changes the conclusion.

Practical question

Can a nonconforming item ever be accepted? An authorised concession may be possible under applicable requirements, but it is a decision with defined conditions, not a reason to relabel the item as originally conforming. Confirm necessary approvals and preserve the record of the departure and disposition.

RESEARCH RECORD

Primary sources

  1. ISO 9001: current public overview ↗ Accessed 15 October 2026
  2. ASQ: supplier quality professional body of knowledge overview ↗ Accessed 15 October 2026

Sources support the factual context. Examples and implementation suggestions are original explanations, not quotations from ISO requirements.