Nonconforming Product: FDA QMSR Control and the Former 820.90
Follow affected medical devices from detection through documented disposition, keeping current FDA QMSR obligations distinct from historical references and operational practice.

On this page · 12 sections
- 1What nonconforming product means—and what it does not
- 2Current FDA QMSR scope and the former 820.90 reference
- 3Identify affected product and contain it without losing traceability
- 4Evaluate impact and justify the investigation decision
- 5Make a disposition decision with explicit authority and conditions
- 6Rework to specified requirements and evaluate the verification approach
- 7Assess concessions and customer communications without assuming permission
- 8Connect product decisions with CAPA, complaints and FDA reporting
- 9Worked cases: incoming parts, labeling errors and distributed devices
- 10Link evidence, inventory and execution across connected systems
- 11Recognize control failures before they obscure the product decision
- 12Review the process using a complete product-to-evidence trace
How does Nonconforming Product (21 CFR §820.90) apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What nonconforming product means—and what it does not
Nonconforming product is product that does not meet a specified requirement. This is an operational definition, not a standalone FDA definition. The useful starting point is an identifiable item, lot or software version, the applicable specification revision, and the acceptance criterion it failed.
A suspected nonconformity is an unresolved concern; a confirmed failure has evidence establishing that the applicable requirement was not met. In practice, record that distinction explicitly rather than treating every inventory hold as proof of failure.
These operational meanings separate the product state from the observation or quality process:
| Term | What it describes | Relationship to product control |
|---|---|---|
| Nonconforming product | Product failing a specified requirement | Identifies what needs a product decision |
| Nonconformity | Nonfulfilment of a requirement | May concern product, process or system |
| Defect | Shortcoming affecting intended use | Focuses attention on use consequences |
| Deviation | Departure from an expected method or condition | Does not alone establish product failure |
| Out-of-specification result | Test result outside specified acceptance criteria | Needs evaluation against the product and test context |
| CAPA | Corrective and preventive action process | Addresses causes and recurrence, not merely product disposition |
For US medical devices under Part 820, 21 CFR 820.3(a) defines components to include software, firmware and labeling intended for inclusion in the finished, packaged and labeled device.
When mapping acceptance criteria to product specifications, distinguish nonconformance from deviation. For a separate product-sector example, see finished-product specifications for supplements; that framework is not the device rule.
02Current FDA QMSR scope and the former 820.90 reference
This page's URL uses the former 21 CFR 820.90 section number; this article addresses current Part 820 nonconforming-product obligations rather than restating superseded section text or its prior duties. Use the current FDA device quality-system framework when mapping procedures to regulatory obligations, and confirm any legacy section reference against that current framework rather than relying on a historical number.
For manufacturers of US finished human-use medical devices subject to Part 820, 21 CFR 820.10(a) requires documentation of a quality management system complying with applicable ISO 13485 requirements, incorporated by reference, and other applicable Part 820 requirements. Keep ISO 13485 readiness connected to that regulatory context rather than treating the standard as a standalone substitute for Part 820.
| Market and product | Current reference | Boundary |
|---|---|---|
| US finished human-use devices | 21 CFR 820.1(a)(1) | Part 820 applies to finished devices intended for human use manufactured in the listed US jurisdictions. |
| Finished human-use devices imported into the US | 21 CFR 820.1(a)(1) | Expressly includes devices imported or offered for import into the United States. |
| Component or part manufacturers within the US medical-device framework | 21 CFR 820.1(a)(2) | Part 820 provisions do not apply to manufacturers of components or parts of finished devices. |
| Other markets or product categories | Separate applicability assessment | Identify the relevant framework independently; for example, assess the UK device framework separately. |
For US medical-device manufacturers performing only some operations covered by Part 820, 21 CFR 820.1(a) limits compliance to requirements applicable to those operations. As an operational recommendation, map the site's actual activities before selecting procedure references; a business label alone is a poor basis for that mapping.
Keep the authority levels distinct throughout this article: cited regulatory obligations are binding within their stated scope; official guidance is identified separately; operational recommendations describe practical controls, not additional regulatory mandates. Software support belongs in implementation discussions, not as legal authority or proof of compliance. Approval and release decisions remain with authorized people.
03Identify affected product and contain it without losing traceability
For medical-device operations, the following is a practical containment approach, not a statement of additional regulatory requirements. Start an intake record with the observed condition, requirement reference and revision, detection point, reporter, product identifier and initial scope. Describe what was observed separately from suspected causes; mark uncertain identifiers or quantities as unresolved rather than guessing.
Build the potentially affected population from lot, serial number, configuration, supplier batch and shared process relationships. Use lot genealogy to follow splits, combinations and transfers. Record why related stock is included or excluded, with supporting record references. A shared supplier alone may justify checking adjacent stock, but does not establish that every receipt is affected.
Nonconforming-product control covers the decision lifecycle; physical segregation addresses containment within it. Moving stock into a designated area does not, by itself, document the affected population or resolve its disposition.
Coordinate identification across receiving, work in progress, finished stock, samples and returned devices. For each location, record the identifier, quantity, explicit unit, container or storage position, and responsible person. Distinguish pieces, assemblies, packages and mass; document conversions where relevant. Account for samples separately to avoid counting them both as stock and as laboratory holdings.
Where movement is impractical, operational options include visible status labels, marked boundaries, restricted access and blocked picking, consumption or shipment transactions. Connect these measures to inventory status control so the physical identifier and recorded status agree. Select controls that address how the product could actually be used or moved.
Keep the population record current as stock moves or additional units are identified. Log changes in quantity, location and scope with the reason and responsible person, preserving the link to the original concern.
04Evaluate impact and justify the investigation decision
As operational practice for medical-device nonconformance evaluation, separate what is known from what is inferred. A useful assessment keeps these elements distinct:
- Observed fact: the actual inspection finding, measurement or reported behavior, with its source and conditions.
- Applicable requirement: the specification, drawing, labeling instruction or acceptance criterion against which the observation is evaluated, including the relevant revision.
- Hypothesized cause: a possible explanation, identified as unconfirmed until evidence supports it. A plausible supplier or operator explanation is not an established cause.
Assess consequences through quality risk management within the quality assurance process. Consider device function, labeling accuracy, compatibility with accessories, package integrity and related product only where the failure could plausibly affect them. Record the connection between the observed defect and each potential effect; do not substitute a generic hazard list for that reasoning.
Investigation depth is commonly informed by uncertainty, potential harm, recurrence and whether affected devices have been distributed. These are operational decision factors, not universal legal triggers. Explain why a focused review is sufficient or why broader root cause analysis is warranted. Record the rationale for the chosen depth, including any decision not to investigate further, and the evidence that would prompt reconsideration.
To narrow scope, compare process records, supplier information, inspection findings, configuration history and relevant test results. Look for shared conditions and meaningful differences between affected and apparently unaffected product. A passing result supports exclusion only to the extent that the test addresses the suspected failure under relevant conditions.
Keep unresolved assumptions visible with an owner, an evidence request and their effect on the provisional scope. When new evidence arrives, document why the affected population expands or narrows, preserving the earlier assessment and the reason for the change.
05Make a disposition decision with explicit authority and conditions
In operational practice, disposition separates the authorized product decision from its execution and subsequent verification. A material review board commonly coordinates technical input; the responsible approver authorizes the selected route within assigned authority. The table below is a practical evidence model, not regulatory permission to use any route.
| Proposed route | Decision evidence | Execution evidence |
|---|---|---|
| Rework | Approved instructions, intended result and verification criteria | Completed work record, verification results and review |
| Return to supplier | Return authorization, affected scope and handling conditions | Shipment identity, quantities and supplier receipt confirmation |
| Rejection or scrap | Rejection rationale and authorized handling or destruction method | Rejected-stock transfer or destruction record, matched to affected identifiers |
| Separately assessed acceptance request | Documented assessment of acceptability, limits and authorized decision | Evidence that approved conditions were met and the responsible person authorized release |
Keep further evaluation as a pending state, not a completed disposition. Record the unanswered question, its owner and the evidence needed before a decision. Moving the record into an evaluation queue does not resolve the product's status.
A practical disposition decision record identifies the affected scope, selected route, rationale, conditions, responsible approver and execution owner. Distinguish authorization to perform work from confirmation that work succeeded. Keep human review, authorization and any release decision explicit: a workflow transition or inventory transaction does not substitute for the responsible person's decision.
For split dispositions, link every resulting subset to the original affected population. Assign each subset its identifiers, quantity, route and execution evidence; reconcile the subsets against the original scope. Keep unresolved units visibly pending rather than allowing completion of one subset to close the entire event.
- DetectRecord the unmet requirement, observation and product identity.
- Bound ScopeIdentify affected units and related inventory.
- ContainPlace affected stock under controlled status.
- EvaluateAssess evidence, potential consequences and investigation needs.
- Authorize DispositionRecord the decision, rationale and responsible approver.
- ExecuteComplete the authorized action and associated checks.
- Reconcile and closeConfirm inventory, evidence and linked actions agree.
06Rework to specified requirements and evaluate the verification approach
For US medical devices under Part 820, 21 CFR 820.3(b) defines rework as action on nonconforming product that brings it into fulfillment of the specified requirements in the medical device file before release for distribution.
As operational practice, connect the rework instruction and routing to the original failure, applicable product configuration, affected units and planned acceptance evidence. Identify which operations will change the product and which characteristics could be affected. This makes the instruction specific enough to execute and the resulting evidence meaningful to a reviewer.
For example, assume an assembly has a misplaced bonded component and the proposed rework uses heat to remove it. Correct positioning afterward may resolve the original defect, while heat could affect adjacent adhesive or material properties. Repeating only the position inspection would not address those potential effects. A practical verification plan identifies the additional characteristics at risk, selects suitable checks and records why those checks cover the proposed action.
When rework changes an established process, route the proposal through change control and a process-validation assessment. Evaluate whether existing process evidence remains applicable to the proposed conditions, equipment, materials and sequence; do not treat every event as an automatic revalidation trigger. Document the rationale for retaining existing evidence or obtaining additional evidence, including any unresolved uncertainty. The review should explain verification coverage—not merely record that the original inspection passed after rework.
07Assess concessions and customer communications without assuming permission
As an operational practice, treat a concession or acceptance request as a proposed exception—not evidence that the failed requirement has been met. Assess whether an exception is available before seeking approval; neither routine acceptance nor blanket rejection is a sound default.
Examine who owns the requirement, the device’s intended use, the technical rationale, affected product scope, and relevant contractual or market constraints. Distinguish a customer preference from a requirement whose purpose is device safety or performance. A focused quality audit can examine whether supplier quality agreements and customer specifications clearly identify decision authority and communication responsibilities.
Customer agreement records the customer’s position; it does not, by itself, establish technical suitability or resolve regulatory acceptability. Keep that agreement separate from the manufacturer’s assessment and authorized product decision. A supplier’s willingness to replace parts likewise does not settle the acceptability of devices already made with them.
For customer and supplier communications, record the recipient, reason, affected product identifiers, agreed action, and acknowledgment where relevant. Link return arrangements to the RMA process, rather than treating correspondence as completed execution. Keep these operational records distinct from the FDA reporting interfaces addressed in the next section.
08Connect product decisions with CAPA, complaints and FDA reporting
As an operational practice, assess recurring failures, shared causes and cross-product patterns for potential corrective and preventive action within the FDA QMSR. A product event can inform a separate CAPA assessment without automatically becoming a CAPA. Preserve the individual product-disposition record so that a systemic investigation does not obscure what happened to the affected product.
For complaint handling, keep the reported facts, product evaluation and systemic-action decision linked but separately identifiable. Common practice is to distinguish what the complainant reported from what examination established, then record the rationale for opening—or not opening—a CAPA. Shared identifiers help reviewers follow these relationships without treating separate decisions as interchangeable.
For manufacturers of US medical devices subject to Part 820, 21 CFR 820.10(b)(3) requires FDA notification of complaints meeting Part 803 reporting criteria. Assess those criteria separately rather than treating every complaint as an FDA report.
For US medical devices subject to Part 820, 21 CFR 820.10(b)(4) requires advisory notices to be handled in accordance with Part 806. Keep the detailed applicability assessment separate from the product-event classification.
A practical reporting-assessment record names the responsible owner, links the supporting facts and records the resulting decision against the product event. This makes responsibility visible and helps prevent teams from assuming that a product disposition or CAPA decision also resolves reporting questions.
09Worked cases: incoming parts, labeling errors and distributed devices
These hypothetical cases illustrate practical decision-making, not prescribed regulatory outcomes. Each proposed path depends on evaluation and authorization by the responsible personnel.
Incoming molded housings
- Assumptions and units: A documented material-grade mismatch is discovered before assembly. Quantities are individual housings.
- Observed failure: The supplied grade differs from the approved material specification; this is not merely a purchasing-description discrepancy.
- Scope reasoning: Trace the received population through receipt, storage and issue records. Reconcile housings remaining in stores with material issued to production, including unused line-side stock. Compare affected part references with the approved bill of materials.
- Proposed path: Assess return or rejection after confirming identity and extent. Investigate whether mixed stock or supplier substitution could affect other receipts.
- Evidence needed for closure: Retain the specification comparison, population reconciliation, authorized disposition and evidence of completed return or rejection controls. A supplier’s replacement promise does not establish what happened to the mismatched housings.
Outer-carton labeling mismatch
- Assumptions and units: An outer-carton label differs from the approved device configuration; the device package remains unopened. Quantities are individual finished devices.
- Observed failure: Identify the substantive difference, such as the stated configuration, rather than recording only that the label is wrong.
- Scope reasoning: Compare actual device configuration, approved labeling and packaging records. Bound the population by label version and packaging activity, not carton appearance alone.
- Proposed path: Assess whether controlled label replacement can restore the intended configuration without compromising identification or package integrity. An unopened package alone does not establish correction feasibility.
- Evidence needed for closure: Retain authorized correction instructions, label reconciliation and verification of corrected labeling against device identity. Document assessment and verification of additional consequences, including obscured information or packaging damage.
Intermittent shutdown after shipment
- Assumptions and units: Intermittent shutdown is reported for a shipped device. Quantities are individual serialized devices.
- Observed failure: Record shutdown as the reported observation; keep a suspected power-system fault separate from confirmed findings.
- Scope reasoning: Examine related hardware, software, accessories and operating conditions. Use the failure-mode assessment to inform scope without treating a suspected mechanism as established.
- Proposed path: Consider return for examination and interim action while connecting the event to the complaint and reporting interfaces covered above.
- Evidence needed for closure: Preserve evaluation results, scope rationale, authorized product action and linked complaint/reporting decisions. Failure to reproduce the shutdown does not itself explain the report.
10Link evidence, inventory and execution across connected systems
The following are practical integration controls, not a statement of legal obligations. Use the accompanying data-model diagram to follow relationships rather than treating the nonconformance as an isolated form: affected product defines scope; evaluation supports disposition; execution evidence shows whether the approved action was completed. Record closure and inventory availability are separate states.
Assign an authoritative owner for each information domain. A workable allocation places product identity with inventory master-data stewardship, stock status with inventory operations, approved specifications and evaluation records with quality, and execution results with manufacturing. Quality owns disposition approval; receiving systems enforce the authorized inventory or production action. Document these boundaries in the integration design.
Join records using stable product, lot, serial and nonconformance identifiers—not displayed descriptions that can change. Preserve the requirement revision used in the evaluation and decision, even when a newer specification becomes current. Link changes and approvals for contextual audit trail review.
- Duplicate messages: retain event identifiers and processing outcomes so replay does not repeat a stock movement or execution instruction.
- Delayed events: track acknowledgments that distinguish receipt from successful application; investigate pending transfers instead of assuming completion.
- Out-of-order changes: validate event sequence and expected prior state before applying an update, preventing an older release instruction from overriding a newer hold.
For failed transfers, route the exception to a named owner, preserve unresolved holds and compare authoritative records with receiving-system states. Use inventory reconciliation across MES and WMS to resolve quantity, location and status differences. Record the reconciliation decision, approver and replay or correction outcome; retain the original failure. A successful retry confirms data transfer, not human approval to release product.
Nonconformance
What failed, where and against which requirement.
- nc_id
- detected_at
- requirement_id
- requirement_revision
- observation
- reporter_id
Affected Product
Scope, identity and controlled inventory.
- scope_id
- nc_id
- item_id
- lot_id
- serial_id
- quantity
- uom
- location_id
- inventory_status
Evaluation
Impact, uncertainty and investigation reasoning.
- evaluation_id
- nc_id
- risk_summary
- investigation_decision
- evidence_ref
- evaluator_id
Disposition
Authorized decision, rationale and conditions.
- disposition_id
- scope_id
- decision_code
- rationale
- conditions
- approver_id
- approved_at
Execution Evidence
Completed actions, verification and reconciliation.
- execution_id
- disposition_id
- work_instruction_revision
- result_ref
- verifier_id
- verified_at
- event_id
11Recognize control failures before they obscure the product decision
A completed nonconformance record can still conceal unreliable decision inputs. These practical diagnostics target record integrity and follow-through; they are industry-practice controls, not a separate statement of FDA requirements.
| Failure mode | Why it matters | Practical control |
|---|---|---|
| Copied requirement reference points to the wrong revision. | Evaluation may use acceptance criteria that do not apply to the affected product. | Retain the applicable requirement snapshot or a revision-controlled reference through document control. |
| Photographs or test files attach to the wrong product event. | Authentic evidence can support an incorrect conclusion when its identity is wrong. | Check product, lot or serial identity and event identifier; preserve explicit evidence-to-record associations. |
| Cause codes are selected only to complete a form. | An unsupported classification becomes apparent fact in later trending. | Preserve uncertainty; record the evidence and reasoning supporting any later cause conclusion. |
| Split populations lose clear membership. | Subsets can omit units, overlap or conceal an unexplained quantity difference. | Reconcile subset membership, quantities and units of measure against the original scope. |
| Overdue actions disappear from operational attention. | Unresolved exceptions remain open without a visible next step. | Assign named owners and review unresolved exceptions; escalate persistent barriers into management review where appropriate. |
Test these controls against actual records, including corrected attachments, changed classifications and unresolved actions—not just blank templates.
12Review the process using a complete product-to-evidence trace
Use this practical checklist during quality-system audits, with findings feeding management review. Select an event and trace forward from the failed requirement to every affected product subset, then backward from each final inventory state to its supporting decision.
- Requirement identification: locate the applicable specification revision and evidence of failure.
- Affected scope: account for included and excluded lots, serial numbers, locations and quantities.
- Containment: compare recorded restrictions with physical stock and system permissions.
- Evaluation: locate the impact assessment, investigation rationale and unresolved uncertainties.
- Decision authority: identify the human approver, authorized disposition and conditions.
- Execution evidence: connect completed actions and verification results to each product subset.
- Reconciliation: explain quantity differences and confirm that final inventory states match authorized, completed actions.
Check that linked complaint, supplier and CAPA actions remain identifiable when their completion dates differ from product disposition. Exercise delayed-interface and unavailable-system scenarios: test the exception controls described above, including recovery reconciliation.
Review legacy procedure references against the current US-device framework rather than relying on former section identifiers, applying the 820.10(a) quality-management-system obligation described earlier in this article. Route reference corrections through document control and change control.
Can another qualified reviewer reconstruct what failed, what was affected, why the decision was made and what evidence shows the authorized action was completed?
Frequently asked questions
Q.Can a documentation discrepancy make otherwise acceptable product nonconforming?+
A documentation discrepancy establishes nonconformity only when it demonstrates that an applicable requirement—including a required documentation condition—was not met. Where it instead leaves conformity unresolved, such as a missing inspection result or an unclear record, treat the product as held under precautionary control pending further evaluation rather than as a confirmed nonconformity. Identify the affected requirement, assess whether reliable contemporaneous evidence resolves the gap, and document the disposition rationale. Use requirements traceability to establish what acceptance depends on and document control to distinguish an obsolete instruction from the applicable revision.
Q.How should containment boundaries be handled when the affected serial numbers are not yet known?+
A practical approach is to establish a provisional suspect population using shared exposure: component lots, equipment, processing periods, tooling, or handling conditions. Record why each boundary was chosen and what evidence would justify narrowing or expanding it. Use forward genealogy tracing to locate potentially affected downstream product. As distinguished earlier, containment decides scope while physical segregation is a separate containment measure. Keep unresolved units within the provisional boundary rather than treating missing serial-number information as evidence of acceptability.
Q.What should happen when a manufacturer and its customer disagree about the applicable acceptance requirement?+
Keep the technical question separate from the commercial dispute. A practical review compares the approved specification revision, order terms, drawings, intended configuration, and any authorized changes, then records precisely where interpretations diverge. Route the issue to accountable quality and technical decision-makers, using a material review board where appropriate. Document the agreed basis for evaluation before reassessing the product. A customer concession is not, by itself, evidence that the product meets the manufacturer's applicable acceptance criteria.
Q.Does receiving replacement stock from a supplier close the original nonconformance?+
Not by itself. Replacement stock resolves a supply need, while the original record still needs an accountable outcome for the affected material. Common practice is to retain links between the original receipt, supplier response, replacement receipt, and return or destruction evidence. Evaluate replacements through the applicable receiving process rather than assuming they are acceptable because they are replacements. Connect the return authorization to the original record and use the event in supplier risk management when its significance warrants further follow-up.
Q.How can recurring failures be grouped without losing the disposition history of individual units?+
Use a shared investigation or trend identifier while retaining unit-level or lot-level disposition records. Common practice is to group events by a defined failure mode and relevant production context, not merely by similar free-text descriptions. Each linked record retains its affected identities, evidence, decision, approver, and final handling outcome. Record why events were grouped and reassess that grouping when causal evidence changes. A shared investigation conclusion does not establish an identical disposition for every linked unit.
Q.How can a reviewer assess whether existing tests adequately cover a proposed rework action?+
As defined earlier in this article, rework must bring nonconforming product into fulfillment of the specified medical device file requirements before release for distribution. In practice, map each proposed operation to the characteristics it could alter, including adjacent features and cumulative processing effects. Compare those effects with existing test coverage, method sensitivity, and inspection access. The rework route should identify additional evaluation where coverage is incomplete; passing an unchanged final test alone may leave rework-specific effects unexamined.
Q.What should a reopened record show when an earlier disposition decision proves mistaken?+
Preserve the original decision and add a traceable reopening event rather than overwriting the history. A useful record explains the new evidence, why the earlier rationale no longer holds, who authorized reopening, and which product movements occurred after the original decision. Record the revised status, additional containment, reassessment, and subsequent approval separately. An audit trail helps reviewers distinguish what was known at the original decision from what emerged later, including whether previously distributed units need further assessment.
Q.How should destructive evaluation or retained samples be accounted for when reconciling affected product?+
Treat evaluation consumption and retained samples as explicit accounting categories, not unexplained shortages. Practical reconciliation links each sampled unit or quantity to its source population, evaluation purpose, custody, and final state. Distinguish material destroyed during testing from intact samples still held, and avoid counting either as available inventory. Connect sample handoff records with the relevant stock adjustments. Reconcile using a consistent unit of measure, and explain any conversion or partial-unit consumption so the affected population remains accountable.
Primary sources
Want to see how Nonconforming Product (21 CFR §820.90) could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
