What this is
What is a supplier corrective request?
What is a supplier corrective request?
A supplier corrective request, or SCAR, asks a supplier to investigate a nonconformity in their material or service, identify its root cause, contain affected stock and implement a fix you can verify. It is raised after a rejection or repeated issue and closes on verified evidence, not on the supplier's reply.
What is the difference between containment and corrective action?
Containment stops the defect reaching further product or customers: quarantine, screening batches, checking what is already at your site. Corrective action removes the cause so it does not recur. The template scores them separately because suppliers routinely deliver the first and call it the second.
What counts as a credible root cause?
One that explains why the control that should have caught the defect did not, at a level the supplier can act on. 'Operator error' is a symptom; 'no verification step between mixing and fill, and the job card does not require one' is a cause. Root Cause Credible is scored apart from Root Cause Provided so a thin analysis can be marked Superficial.
Scope
When is a supplier corrective request required?
This record handles one nonconformity in a supplier's material or service, where you need them to investigate and prove a fix. Raised for the wrong problem it either overstates a one-off or understates a pattern.
Use this template when
- A delivery is rejected and the cause lies with the supplier, not transport, specification or your own handling
- The same nonconformance has recurred and you need the cause identified rather than the batch replaced
- A customer complaint traces to purchased material and you owe a supplier-side investigation
- An audit finding at the supplier's site needs a documented response with verified closure
- Material has failed an agreed specification and the specification itself is not in dispute
Do not use it for
- Material Rejection Report, which records the rejection decision, quantity and disposition; it triggers this request rather than replacing it.
- Supplier Improvement Plan, which addresses sustained underperformance across many deliveries with dated actions on both sides.
- Supplier Audit, which assesses the supplier's systems on site, where the concern is capability rather than one nonconformity.
- Certificate of Analysis Review, which checks batch documentation; a false certificate may trigger this request but is recorded there.
- Supplier Scorecard, which aggregates performance over a period; this record feeds it but is not a substitute.
Compliance mapping
Which ISO 9001 cl.8.4.3 requirements does this satisfy?
ISO 9001 cl.8.4 requires control and evaluation of externally provided processes and products; cl.10.2 governs how nonconformity is reacted to and its causes eliminated. Between them they set what this record must capture.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 9001 cl.8.4.1 | Evaluate, monitor and re-evaluate external providers, retaining documented information of the results and actions arising. | Our assessment |
| ISO 9001 cl.8.4.2 | Determine and apply the verification necessary to ensure externally provided processes, products and services meet requirements. | Our assessment |
| ISO 9001 cl.8.4.3 | Communicate to external providers the requirements for control, performance monitoring and approval of their processes and products. | Header |
| ISO 9001 cl.8.7 | Identify and control nonconforming outputs to prevent unintended use or delivery, and document the nonconformity and actions taken. | The problem |
| ISO 9001 cl.10.2 | React to the nonconformity, evaluate the need for action to eliminate its causes, and review the effectiveness of the corrective action. | Supplier response |
| ISO 9001 cl.9.1.3 | Analyse and evaluate data on the performance of external providers as an input to improvement. | Our assessment |
What it does not cover
- A credit note and an apology, which settles the loss on one consignment and evidences nothing about why the defect happened or whether it recurs.
- A reply blaming operator error, which names the person nearest the failure rather than the control that was absent, and should be marked Superficial.
- An 8D with D4 to D7 left 'in progress', which starts a method but leaves cause and verification unevidenced, so Evidence Of Implementation Provided is at best Promised.
- Retraining the supplier's operators, which restores expected behaviour without changing the process that permitted the error; Action Strength scores it 1.
- A closure based on written confirmation alone, which is Statement only, scored 0, and will not survive a customer audit asking how you checked.
Global
Supplier Corrective Request requirements by country
The duty to obtain and verify supplier corrective action sits in several sector regimes, not just ISO 9001. Which applies determines how much of the record must survive external inspection rather than internal review.
21 CFR 820.50 — Purchasing controls (medical devices)
Manufacturers must establish requirements suppliers must meet, evaluate suppliers on their ability to meet them, and document the results of that evaluation.
An FDA investigator reads closed requests as evidence of ongoing evaluation. Closures on a supplier statement with no verification are a standard 483 observation, which is why Statement only scores zero.
EudraLex Volume 4, Part I, Chapter 5 (Production) and Chapter 8 (Complaints and product recall)
Requires materials to be bought from approved suppliers, defects investigated for root cause, and corrective and preventive actions taken with their effectiveness assessed.
In pharmaceutical and API supply the effectiveness check is mandatory. Verified Effective and Other Affected Batches Identified are what inspectors reach for first: they show whether the investigation looked past the failed batch.
IATF 16949 cl.10.2.3 Problem solving, with cl.8.7 Control of nonconforming output
Requires a documented problem-solving process covering containment, root cause analysis with a stated methodology, systemic corrective actions and verification of effectiveness.
Customer portals here expect a structured 8D response. Root Cause Method Used carries that into the record, and None stated against a repeat issue is itself a reportable weakness.
How to complete it
How to complete a supplier corrective request, step by step
The factual half of this record is straightforward. Four judgement calls decide whether it closes cleanly and whether the supplier's behaviour actually changes.
Root Cause Provided and Root Cause Credible are deliberately separate. Suppliers under deadline will put something in the box. Score Provided as Yes when an analysis arrived, then judge credibility on its own: does the cause explain the timing, the quantity affected and why detection failed? Where it does not, record Superficial and reject the response.
This is the field with the most leverage and the most negotiation. Suppliers propose retraining because it is free and fast. Accepting it is legitimate for a one-off with a strong existing control; not where Repeat Issue is Yes. Use the score as the argument: a supplier whose last three requests closed at strength 1 has an evidenced pattern.
Verification Method is required and scores Site visit at 4 down to Statement only at 0. Choose against severity and repeat status, not convenience: a Serious severity or repeat issue should not close on a photograph. Set Verification Due Date at the same time.
Approval Status Affected scores No at 3, Conditions applied at 1 and Suspended at 0 — it describes the supplier's outcome, not your handling. The judgement is whether the nonconformity and its history warrant a commercial consequence. Conditions plus tightened inspection is usually proportionate; suspension is for where containment cannot be trusted at all.
What auditors find
Most common supplier corrective request findings
These findings recur when corrective requests are sampled by certification bodies or customers auditing your supplier controls, with the field that should have prevented each.
| Finding | Clause | What fixes it |
|---|---|---|
| The request was closed the day the supplier replied, with no verification recorded. | ISO 9001 cl.10.2 | Leave Verified Effective blank until the chosen Verification Method is executed, and let Verification Due Date govern closure rather than Response Received. |
| Root cause is recorded as 'human error' across several requests to one supplier. | ISO 9001 cl.10.2 | Mark Root Cause Credible as Superficial and reject the response. Where the pattern persists, escalate to an improvement plan rather than raising a fourth request. |
| No check was made of stock held at your site or other batches from the same run. | ISO 9001 cl.8.7 | Stock At Our Site Checked and Other Affected Batches Identified are separate scored fields; neither may be blank on a closure with Severity above Minor. |
| The request never reached the scorecard, so performance looked unaffected. | ISO 9001 cl.9.1.3 | Feeds Scorecard is a required checkbox. Confirm it before closure so the record feeds the periodic evaluation, not only the quality file. |
| Evidence sent to the supplier was described in the covering email but never kept. | ISO 9001 cl.8.4.3 | Complete Evidence Provided To Supplier positively — photographs, samples, test results, batch records or complaint details — so what was sent is on the record. |
| A repeat issue was raised as a fresh request with no reference to the earlier ones. | ISO 9001 cl.10.2 | Set Repeat Issue to Yes and complete Times In Last 12 Months. That count justifies a stronger verification method and a change to approval status. |
Case in point
Case in point: three closures, one uncaught cause
A food manufacturer raised corrective requests against a film supplier three times in fourteen months, each after a seal failure at line start-up. Every response arrived inside the deadline, each blamed an operator handling error at the slitting station, each proposed retraining, and each was accepted and closed. The scorecard showed three raised and three closed on time, which read as a functioning process.
The fourth failure reached a customer. The cause had never been the operator: the slitter's tension setting drifted with ambient temperature and no verification step followed set-up. Nothing in the earlier responses was false — retraining genuinely happened three times. What the file lacked was any record that the action was weak. Three consecutive Action Strength values of 1 against a repeat issue would have made the case for a process change before a customer made it for them.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
4 sections
- Reference
- QUA-042
- Archetype
- Record
- Record ID
- SCAR-2026-000
- Scoring
- Response quality
- Direction
- High is good
- Singleton
- No
- Basis
- ISO 9001 cl.8.4.3
- Links
- Links Vendor, Case
- Tags
- Supplier, Action
- Sections
- 4
- Fields
- 42
- Follow up fields
- 2
- Repeating sections
- 0
- Links out
- 1
Header
9 fieldsSCAR ID*
Auto sequence. Format SCAR-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date*
Completed By*
Supplier*
Vendor ID*
Format VEN-0000.
Links to FDN-005 Vendor ID
Case ID
Thread key
Trigger*
Ask For Cause, Not Apology
A credit note fixes this delivery. A root cause with evidence fixes the next twenty. Reject responses that do not identify why it happened.
The problem
9 fieldsProblem Description*
Material Affected*
Supplier Batch
Quantity Affected
Cost Impact
Evidence Provided To Supplier*
Severity*
- Minor3 pts
- Moderate1 pt
- Serious0 pts
Repeat Issue*
- No3 pts
- Yes0 pts
Times In Last 12 Months
Supplier response
12 fieldsResponse Requested By*
Response Received
Response On Time
- Yes3 pts
- Late1 pt
- No0 pts
Immediate Containment Described
- Yes3 pts
- Partly1 pt
- No0 pts
Other Affected Batches Identified
- Yes3 pts
- No0 pts
Stock At Our Site Checked
- Yes3 pts
- No0 pts
Root Cause Provided
- Yes3 pts
- Superficial1 pt
- No0 pts
Root Cause Method Used
Root Cause Credible
- Yes3 pts
- Partly1 pt
- No0 pts
Corrective Actions Proposed
Action Strength
Retraining their operator is weak. Changing their process or adding detection is strong.
- Eliminate or engineer4 pts
- Process change3 pts
- Supervision or verification2 pts
- Retraining1 pt
- Reminder or reissue0 pts
Evidence Of Implementation Provided
- Yes3 pts
- Promised1 pt
- No0 pts
Our assessment
12 fieldsResponse Accepted*
- Yes3 pts
- With clarification2 pts
- Rejected0 pts
Reason If Rejected
Verification Method*
Next delivery check, document review or audit.
- Site visit4 pts
- Record review3 pts
- Photograph2 pts
- Statement only0 pts
Verification Due Date
Verified Effective
- Yes3 pts
- Partly1 pt
- No0 pts
Inspection Level Tightened
Feeds Scorecard*
Approval Status Affected*
- No3 pts
- Conditions applied1 pt
- Suspended0 pts
Quality*
Signature*
Procurement*
Second Signature*
QUA-042 · record IDs look like SCAR-2026-000 · Links Vendor, Case
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
Raising the request is the quick part. Chasing the response, judging its quality honestly and actually executing the verification weeks later is where the process fails.
Owns the request end to end: raises it from a rejection, holds evidence against the vendor record, and keeps it open until Verified Effective is set.
Connects it to the supplier lifecycle — scorecards, approval status, improvement plans — so weak responses reach procurement before the next order.
Handles consequences at your own site: tightened inspection levels, stock checks on affected batches, and the goods-in changes that follow a suspension.
Tracks response and verification dates, flags requests closed with no effectiveness check, and holds every write for your approval before it touches a record.
This template lives in KnowQuality — quality and food safety. HACCP, nonconformance, traceability, laboratory and customer complaints.
Meet KnowQuality→Glossary
Supplier Corrective Request definitions and key terms
- SCAR
- Supplier corrective action request: the instrument asking a supplier to investigate a nonconformity, state its cause and prove the fix, keyed as SCAR-2026-000.
- Containment
- Immediate action to stop the defect reaching further product or customers — quarantine, screening, checking stock — taken before the cause is known.
- Action strength
- How permanently an action removes the failure mode, ranked from elimination down to a reminder. The best predictor of whether the defect returns.
- Effectiveness verification
- Your own check that the action worked, by the chosen method after implementation, rather than assumed from the supplier's report.
- Repeat nonconformance
- The same defect recurring within a defined window, counted in Times In Last 12 Months and the trigger for stronger verification.
FAQ
Frequently asked questions about supplier corrective request
How long should a supplier be given to respond?+
Set Response Requested By against severity, not habit. Containment information is reasonable within a few working days; a credible root cause with evidence rarely is. Use a two-stage deadline — containment quickly, full response in two to four weeks — and record the second date here.
What if the supplier disputes that the defect is theirs?+
Resolve it before requiring a root cause. Evidence Provided To Supplier and Problem Description exist to make the case concretely. Where the dispute is genuine — transport damage, an ambiguous specification, your own handling — withdraw the request and raise the correct record.
Does every rejected delivery need a corrective request?+
No. A single rejection with an obvious, contained cause is handled by the material rejection report alone. Raise a request when the defect could recur, when it nearly reached a customer, or when it is the second occurrence.
Should the supplier's approval status change automatically?+
No, and the template does not make it automatic. Approval Status Affected is a recorded judgement. What should be automatic is visibility: the request feeds the scorecard, and a pattern of conditions or suspensions drives approval review.
How does this relate to a supplier improvement plan?+
This record fixes one nonconformity; the plan addresses a performance trend. Where a third or fourth request lands against the same supplier, the escalation is a plan with dated actions on both sides, cross-referenced to these requests.
Can the template be changed?+
Yes. Every field, option, score and conditional rule is editable, including the Action Strength ranking and the verification hierarchy, and the vendor register and case links come with it.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Supplier Quality Assurance
Modern Slavery and Labour Standards Assessment
Assesses the site and its labour supply chain for forced labour, debt bondage, withheld documents and unlawful deductions
Transport Provider Assessment
Assesses a haulier for licensing, driver management, vehicle standards, temperature capability and load security
Supplier Environmental Assessment
Assesses a supplier's environmental performance and certifications
Vendor and Contractor Register
Holds every supplier, contractor and service provider you work with, including their status and approval level
Material Rejection Report
Rejects incoming material that fails inspection
Supplier Approval Record
Records the decision to approve a new supplier, with the evidence behind it
More in Suppliers
Supplier Approval Record
Records the decision to approve a new supplier, with the evidence behind it
Supplier Questionnaire
Collects information about a supplier's systems, certifications and controls
Supplier Audit
Audits a supplier's site against your requirements
Supplier Scorecard
Scores a supplier on quality, delivery, responsiveness and cost over a period
Material Specification Record
Holds the agreed specification for each material you buy, including tolerances and test methods
Certificate of Analysis Review
Checks the certificate supplied with a material against the agreed specification
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 9001:2015 — cl.8.4 Control of externally provided processes; cl.8.7 Control of nonconforming outputs
- ISO 9001:2015 — cl.10.2 Nonconformity and corrective action; cl.9.1.3 Analysis and evaluation
- IATF 16949:2016 — cl.10.2.3 Problem solving; cl.10.2.4 Error-proofing
- 21 CFR 820.50 — Purchasing controls, US Food and Drug Administration
- EudraLex Volume 4 — EU GMP, Part I Chapter 5 and Chapter 8
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.