A supplier corrective action request (SCAR) is a formal, documented demand that a supplier finds the root cause of a non-conformance, contains the defective product and proves a permanent fix within agreed deadlines. In quality management, the SCAR is the step that turns a logged defect into a supplier obligation. In this blog we explain what a SCAR is and what it is not, why spreadsheets and email chains leave SCARs open for months, and the seven steps that take a SCAR from NCR trigger to verified closure. We also list the 12 fields every SCAR form needs, show how a SCAR connects to NCRs, 8D reports and CAPA, and summarise what ISO 9001, IATF 16949, EU GMP and ISO 13485 expect from you.
What Is a Supplier Corrective Action Request (SCAR) in Quality Management?
A supplier corrective action request is a controlled quality record that a buying organisation issues to a supplier after a non-conformance report (NCR) confirms a defect in delivered parts, materials or services. The SCAR names the defect, the affected lots and quantities, the containment deadline and the evidence the supplier must return: a root cause analysis, a corrective action plan and proof that the fix works, usually measured in PPM (defective parts per million) after closure. ISO 9001:2015 clause 10.2 requires exactly this cycle of reacting, finding the cause, acting and reviewing effectiveness; the SCAR extends that requirement to the supply base.
So what is a corrective action request in general? A corrective action request (CAR) is the same mechanism raised internally, against your own department or process. The word "supplier" changes who owns the fix: with a SCAR, the supplier carries the root cause work, and you verify it.
A SCAR is not a debit note, a chargeback or an invoice dispute. Those settle the cost of a bad delivery. A SCAR governs the supplier's process so the same defect does not arrive again. Financial tools close the money question; a SCAR closes the quality question.
That difference is why SCARs belong in supplier relationship management, not in accounts payable. In supplier relationship management, every SCAR is evidence: it shows how a supplier responds under pressure, how fast it contains a problem and whether its fixes hold. Over a year, that history says more about a supplier than any annual review.
Why Do Excel Trackers and Email Chains Fail to Close SCARs on Time?
Who chased the packaging supplier last Tuesday? Which version of the 8D report is the final one? Is the containment still in place? In most quality teams we speak to, nobody answers these questions without opening three inboxes and a shared drive.
The typical SCAR lives in four places at once: the NCR in the ERP or a quality log, the SCAR form as a Word file, the supplier's reply in someone's email, and the status in an Excel tracker that one person updates on Fridays (when they remember). The result is predictable:
- Deadlines slip silently. A spreadsheet does not send reminders or escalate. A 48-hour containment deadline becomes two weeks because nobody noticed the supplier never replied.
- Root causes repeat. Without a searchable history, the supplier sends "operator error, retraining done" for the third time, and nobody spots the pattern.
- Verification gets skipped. Once the supplier's reply arrives, the SCAR is marked closed. Nobody checks the PPM over the following 90 days, so the defect returns.
- The audit trail breaks. When an ISO 9001 auditor or a customer asks for the evidence chain from NCR to effective fix, the team spends days rebuilding it from attachments.
- Supplier performance stays invisible. SCAR data never reaches the supplier scorecard, so the supplier with six open SCARs keeps the same status on the approved supplier list as the one with none.
An Excel tracker is like a filing cabinet: it stores SCARs, but it does not govern them. Closing SCARs on time takes one shared record that the buyer, the quality engineer and the supplier all work in, with deadlines that enforce themselves.
The 7-Step SCAR Process: From NCR Trigger to Verified Closure in 30–90 Days
A well-run supplier corrective action request process follows seven steps, each with an owner and a deadline:
- Raise the NCR and decide if a SCAR is needed
- Issue the SCAR with evidence and deadlines
- Contain the problem within 24–48 hours
- Find the root cause with 5 Whys, Ishikawa or 8D
- Agree a corrective action plan with owners and dates
- Verify effectiveness with PPM data and a re-audit
- Close the SCAR and update the supplier scorecard
The timelines below reflect common practice in regulated manufacturing, pharma and food. Your quality agreement with each supplier sets the binding deadlines, so write them into it.
Step 1: Raise the NCR and Decide if a SCAR Is Needed
Every SCAR starts with a documented defect. Goods-in inspection, a production line stoppage or a customer complaint triggers a non-conformance report that records what was found, where and in which batch. Not every NCR deserves a SCAR. A single cosmetic defect on a low-risk part usually needs only a note to the supplier.
Issue a SCAR when at least one of these is true: the defect affects product safety, patient safety or regulatory compliance; the same defect has occurred before; the defect stopped your production or reached a customer; or the quantity affected crosses the threshold in your quality agreement.
How to fix it: write these criteria down. When the decision depends on who is on shift, minor issues get SCARs and serious ones get emails.
Step 2: Issue the SCAR with Evidence, Severity and Deadlines
The SCAR goes to a named contact at the supplier, not to a generic sales inbox. It includes the NCR reference, a clear problem statement (what, where, when, how many), photos or measurement data, affected lot or batch numbers, a severity rating and the response deadlines for each step.
A good problem statement is specific: "412 of 5,000 aluminium housings from lot 24-0917 measured 0.3 mm over the bore tolerance of Ø12.00 ±0.05 mm" works. "Parts out of spec" does not.
How to fix it: use one SCAR template for every supplier, so every request carries the same fields and the same deadline structure.
Step 3: Contain the Problem Within 24–48 Hours
Containment protects your production and your customers while the root cause is still unknown. The supplier quarantines suspect stock at its site and in transit, sorts or 100% inspects inventory at your site, and confirms which lots are clean. In 8D terms, this is D3: interim containment action.
Most quality agreements give the supplier 24 hours to acknowledge the SCAR and 24–48 hours to confirm containment. In pharma and food, where a defect reaches patients or consumers, containment often runs in hours, not days.
How to fix it: track containment as its own deadline. A SCAR with a root cause due in two weeks and no containment date leaves defective stock moving in the meantime.
Step 4: Find the Root Cause with 5 Whys, Ishikawa or 8D
The supplier now proves why the defect happened and why its controls did not catch it. Three methods dominate:
- 5 Whys for simple, single-cause problems: ask "why" until you reach a process cause, not a person.
- Ishikawa (fishbone) diagram to sort possible causes into man, machine, method, material, measurement and environment.
- 8D report for complex or repeat defects. Automotive customers under IATF 16949 expect it by default.
A root cause analysis typically takes 7–14 days. Reject answers like "operator error" or "human mistake" on their own: a process that depends on nobody ever making a mistake is the real root cause. Ask for both the occurrence cause (why the defect was made) and the escape cause (why it left the supplier's site).
How to fix it: compare the root cause with the supplier's previous SCARs before accepting it. If the same cause appears twice, the first corrective action did not work.
Step 5: Agree a Corrective Action Plan with Owners and Dates
The corrective action plan removes the root cause permanently. Each action names an owner at the supplier, a due date and the evidence that proves it is done: an updated control plan, a revised work instruction, a new poka-yoke fixture, a changed sub-supplier or a training record backed by a process change.
You review and accept the plan before the supplier starts. Plans that rely only on "retraining" or "increased inspection" treat the symptom; inspection catches defects, it does not stop them being made. Ask for at least one action that changes the process itself, plus a preventive action that applies the fix to similar parts and lines.
How to fix it: set a due date for every action in the plan, not one date for the whole SCAR. Large plans hide one late action behind four finished ones.
Step 6: Verify Effectiveness with PPM Data and a Re-audit
This is the step most teams skip, and the reason the same defect comes back six months later. A SCAR is effective when the defect no longer appears, not when the supplier says the actions are complete.
Verify with data from at least 30–90 days or three consecutive deliveries after implementation: incoming PPM for the affected part, goods-in inspection results and, for serious cases, a process audit at the supplier's site. ISO 9001 clause 10.2 and ISO 13485 clause 8.5.2 both require you to review the effectiveness of corrective action, and auditors ask for the evidence.
How to fix it: schedule the effectiveness check the day you accept the plan. When verification has no date, it has no owner.
Step 7: Close the SCAR and Update the Supplier Scorecard
Closure is a sign-off by your quality lead, with the verification evidence attached. Then the SCAR feeds back into how you manage the supplier. The number of SCARs, the time to containment and the time to closure belong on the supplier scorecard next to OTIF and PPM, because a supplier that delivers on time but needs three SCARs a quarter is not a strong supplier.
Repeat SCARs also trigger a review of the supplier's status on the approved supplier list: conditional approval, increased inspection, or a planned second source.
How to fix it: define the scorecard and ASL consequences of SCARs in the quality agreement, so suppliers know a slow response costs them more than one complaint.
What Belongs on a Supplier Corrective Action Request Form? 12 Mandatory Fields
A supplier corrective action request form needs 12 fields to carry a SCAR from trigger to closure with a complete audit trail:
| # | Field | Filled in by | Why it matters |
|---|---|---|---|
| 1 | SCAR number and issue date | Buyer | Unique reference for audits and the supplier's history |
| 2 | Supplier name and contact | Buyer | A named person, not a shared inbox |
| 3 | Part number, batch or lot number | Buyer | Defines the scope of containment |
| 4 | NCR reference | Buyer | Links the SCAR to the original evidence |
| 5 | Problem description | Buyer | What, where, when, how many, against which specification |
| 6 | Quantity affected | Buyer | Sets severity and the cost of poor quality |
| 7 | Severity and response deadlines | Buyer | Containment, root cause and plan dates |
| 8 | Containment actions | Supplier | Quarantine, sorting and clean-lot confirmation |
| 9 | Root cause (occurrence and escape) | Supplier | 5 Whys, Ishikawa or 8D output |
| 10 | Corrective and preventive actions | Supplier | Owner and due date per action |
| 11 | Verification of effectiveness | Buyer | PPM and inspection data after implementation |
| 12 | Closure sign-off | Buyer | Name, date and decision |
A form is a good start, and here is its limit: a form does not chase anyone. It does not remind the supplier that containment is overdue, it does not warn you that this is the supplier's third SCAR on the same part, and it does not move the result onto the scorecard. With 500 suppliers and dozens of open SCARs, the form becomes one more file to track.
SCAR vs NCR vs CAPA vs 8D: How the Four Quality Records Connect
These four terms get mixed up in almost every quality team, yet each answers a different question. The NCR records the defect, the SCAR hands the fix to the supplier, the 8D report is the method the supplier uses, and CAPA is the quality system that governs all corrective and preventive actions.
| NCR | SCAR | 8D report | CAPA | |
|---|---|---|---|---|
| Question it answers | What went wrong? | Who must fix it, and by when? | How was it solved? | How does the organisation prevent problems systematically? |
| Raised by | Buyer's quality or goods-in team | Buyer, to the supplier | Supplier (in reply to a SCAR) | Any department, internal or external |
| Scope | One defect, one batch | One supplier, one problem | One problem, eight disciplines | The whole quality system |
| Output | Disposition: reject, rework, use as is | Verified, closed corrective action | Root cause and permanent fix | Trends, preventive actions, management review |
So, SCAR vs CAPA? A SCAR is one corrective action owned by a supplier. CAPA is the umbrella process, required by ICH Q10 in pharma and by ISO 13485 in medical devices, that tracks every corrective and preventive action, including SCARs. And NCR vs CAR? The NCR documents the non-conformance; the CAR or SCAR demands its elimination.
SCAR Requirements Under ISO 9001, IATF 16949, EU GMP, ISO 13485 and BRCGS
No standard uses the exact word "SCAR", but every major quality standard in regulated industries requires what a SCAR does: control of external suppliers, correction of non-conformances at the source, and proof that the fix is effective.
| Standard | Sector | What it expects from supplier corrective action |
|---|---|---|
| ISO 9001:2015 | All manufacturing and services | Clause 8.4: control externally provided products and monitor supplier performance. Clause 10.2: react to non-conformities, find causes, act and review effectiveness. |
| IATF 16949:2016 | Automotive | Clause 10.2.3: documented problem solving, usually an 8D report, with containment and root cause. Clause 8.4.2.4: supplier monitoring, including delivered quality and disruptions. |
| EU GMP (EudraLex Vol. 4) and ICH Q10 | Pharma and biotech | Chapter 5: qualification of starting-material suppliers. Chapter 7: control of outsourced activities. ICH Q10 section 3.2.2: a CAPA system that covers supplier-related deviations. |
| ISO 13485:2016 | Medical devices | Clause 7.4.1: supplier monitoring and actions proportionate to risk. Clause 8.5.2: corrective action with effectiveness verification. |
| BRCGS Food Safety (Issue 9) | Food and beverage | Section 3.5: supplier and raw material approval and monitoring. Section 3.7: corrective and preventive action with root cause analysis. |
For companies that also sell into the US, the FDA's cGMP rules for drugs (21 CFR Part 211) and its Quality Management System Regulation for devices (21 CFR Part 820, aligned with ISO 13485 since February 2026) apply the same logic. Auditors under all of these standards ask the same three questions: did you contain the problem, did you find the real cause, and do you have evidence that the fix worked?
Supplier Corrective Action Request FAQs
When should you issue a supplier corrective action request?
Issue a SCAR when a non-conformance affects safety or compliance, repeats, stops production, reaches a customer or exceeds the quantity threshold in your quality agreement. One-off minor defects are handled with the NCR and a note to the supplier.
How long should a supplier have to respond to a SCAR?
Common practice is 24 hours to acknowledge, 24–48 hours to confirm containment, 7–14 days for root cause and the corrective action plan, and 30–90 days to verify effectiveness and close. The binding deadlines belong in your quality agreement.
What happens if a supplier rejects or ignores a SCAR?
Escalate in defined stages: from the quality contact to the supplier's quality manager, then to its management, with the buyer involved. A SCAR that stays unanswered moves the supplier to conditional status on the approved supplier list, increases incoming inspection at the supplier's cost where the contract allows it, and starts second-source qualification.
Can an ERP system manage supplier corrective actions?
No. An ERP records the goods receipt, the quality block and the return to supplier. It does not run root cause analysis with the supplier, track containment and plan deadlines, verify effectiveness or connect the SCAR history to supplier performance. Those steps need a system built for the supplier relationship, not for the transaction.
From Scattered SCAR Files to One Supplier Record: Where LeanLinking Fits
Every step above depends on the same thing: one place where the defect, the supplier's response and the supplier's track record sit together. When NCRs live in one system, SCAR forms in another and scorecards in a third, the root cause pattern stays hidden and the auditor's evidence chain breaks.
LeanLinking's Supplier Cockpit gives each supplier a single record. Non-conformances, performance scores such as OTIF and PPM, documents and supplier communication sit side by side, so your quality and procurement teams see the full history before they accept a root cause or renew an approval. A supplier with three NCRs on the same part shows up as a pattern, not as three unrelated emails.
That is the job of supplier quality management software built for regulated supply chains: turning supplier quality data into decisions you defend in front of an auditor.
Book a demo and we will show you how the Supplier Cockpit brings your supplier quality data into one place.
