What Is a Supplier Corrective Action Request?

When a defect traces back to something a supplier shipped you, fixing it on your own floor isn't enough — the cause lives at the supplier, so that's where the fix has to happen. A supplier corrective action request is how you make that happen formally: a documented request asking the supplier to investigate the nonconformity, find the root cause, and put actions in place so it doesn't ship again. Quality teams usually shorten it to SCAR.

It's one of the most important tools in supplier quality management, and also one of the easiest to do badly. A SCAR that gets a quick "we retrained the operator" reply and a closed ticket isn't corrective action — it's paperwork. This guide covers what a supplier corrective action request actually is, when to issue one, what belongs in it, how the 8D response works, and how to close it so the same defect doesn't come back next quarter.

What is a supplier corrective action request (SCAR)?

A supplier corrective action request is a formal, documented request from an organization to one of its suppliers, issued when the supplier's product, service, or process fails to meet an agreed requirement. It asks the supplier to do four things: contain the immediate problem, investigate the root cause, implement a permanent corrective action, and provide evidence that the action actually prevents recurrence.

The terminology can get confusing because "SCAR" is used for both halves of the exchange — the initial request you send, and the response report the supplier sends back. In practice they're two stages of the same record: you issue the request, the supplier populates it with their investigation and corrective actions, and you verify and close it.

A SCAR is essentially a corrective action request pointed outward. The logic is identical — nonconformity, containment, root cause, corrective action, verification — but the investigation happens at the supplier, and you're managing it across an organizational boundary rather than down the hall. That boundary is what makes SCARs their own discipline.

SCAR vs. CAR: what's the difference?

The distinction is simply where the nonconformity originates and who owns the fix:

• A corrective action request (CAR) can be internal or external. It's the general-purpose tool for formalizing corrective action on any nonconformity, wherever it came from.
• A supplier corrective action request (SCAR) is specifically external — you issue it to a supplier when the nonconformity originates outside your facility, in something they provided.

Think of a SCAR as a specialized CAR for the supply chain. The response has to come from a party you don't directly control, which is why SCARs lean harder on clear timelines, defined expectations, and structured problem-solving methods than a typical internal corrective action does.

When should you issue a supplier corrective action request?

A SCAR is a formal escalation, not a first response to every minor issue. You reserve it for supplier problems that are significant, recurring, or carry real downstream risk. Common triggers include:

• Incoming inspection failures — received material or parts don't meet spec.
• Customer complaints traced to supplier material — a defect in your product turns out to originate upstream.
• Repeated or systemic issues — the same supplier defect keeps recurring, which means the root cause was never removed.
• Specification or requirement violations — the supplier delivered something outside the agreed requirements.
• Audit findings — a supplier audit surfaces a nonconformity in their process.
• Persistent delivery or performance problems — where quality, not just logistics, is at stake.

The connective tissue is accountability. A SCAR creates a documented, auditable record that you raised the issue, the supplier owned it, and it was resolved — which is exactly the kind of evidence a quality auditor wants to see for how you control your suppliers.

Where SCARs fit in supplier quality and ISO 9001

Supplier corrective action requests are one piece of a broader obligation to control the quality of what comes into your operation. ISO 9001:2015 addresses this in Clause 8.4, "control of externally provided processes, products and services" — which strengthened the older "purchasing" requirements and expects organizations to evaluate suppliers, monitor their performance, and take action when they fall short. A SCAR is a natural mechanism for that last part: it's how you act on a supplier nonconformity and feed the outcome back into your supplier evaluation. (If you want the deeper dive on that clause, we've covered ISO 9001 Section 8.4 separately.)

Worth keeping on your radar: ISO 9001 is being revised, with the sixth edition scheduled for publication in September 2026. The revision is widely described as evolutionary rather than a rewrite, and the supplier-control expectations aren't expected to change fundamentally — but if you're documenting SCAR processes against a specific clause, confirm the reference once the final standard is published.

What to include in a supplier corrective action request

A vague SCAR gets a vague response. The request you send should give the supplier everything they need to understand the problem precisely and respond usefully. At minimum:

• Clear problem description — what the defect is and which requirement it violates.
• Objective, traceable detail — part numbers, lot or batch codes, quantities affected, and photos or supporting documentation where relevant.
• Reference documents — the spec, drawing, purchase order, or standard the material failed against.
• Containment expectations — what you need the supplier to do immediately to stop further nonconforming product from reaching you.
• Required root cause method — whether you expect 5 Whys, a fishbone (Ishikawa) diagram, or a full 8D, and to what level of depth.
• Response timeframe — when you need acknowledgment, an interim response, and the final corrective action.
• Closure criteria — what the supplier must demonstrate before you'll consider the SCAR resolved.

Setting closure criteria up front is one of the highest-leverage things you can do. It's what stops a SCAR from being closed prematurely on a plan that was never verified — and prevents the reopen-and-rework cycle that frustrates everyone.

The 8D response: how suppliers work a SCAR

For significant or recurring problems — especially in automotive and aerospace supply chains — the expected SCAR response format is 8D, the Eight Disciplines of Problem Solving. It's a structured, team-based workflow developed at Ford in the 1980s (originally called Team Oriented Problem Solving) that has become the default corrective-action format across manufacturing supply chains.

The disciplines run in order, roughly:

1. D1 — Build the team. Assemble people with knowledge of the product and process.
2. D2 — Describe the problem. Define it precisely, with data.
3. D3 — Contain it. Implement interim actions to protect the customer while the investigation runs.
4. D4 — Find the root cause. Identify both why the defect occurred and why it escaped detection.
5. D5 — Choose corrective actions. Select permanent actions that address the verified root cause.
6. D6 — Implement and validate. Put the actions in place and confirm they work.
7. D7 — Prevent recurrence. Update systems, procedures, and controls so the cause can't return elsewhere.
8. D8 — Close out and recognize the team.

The two failure modes to watch for in any 8D response are declaring containment as if it were the root cause (isolating bad parts isn't a fix), and stopping at "operator error" instead of asking why the process allowed the error to happen and go undetected. A strong SCAR response separates the cause of occurrence from the cause of escape and addresses both.

The SCAR lifecycle, end to end

Put together, a supplier corrective action request typically moves through these stages:

1. Identify and contain the supplier-related nonconformity on your side — quarantine affected material so it isn't used or shipped.
2. Issue the SCAR with full detail and clear expectations for containment, root cause, timing, and closure.
3. Supplier acknowledges receipt and confirms understanding (or asks for clarification).
4. Supplier contains on their end to stop further nonconforming product reaching you.
5. Supplier investigates the root cause using the required method and documents findings.
6. Supplier implements corrective action and reports back with a plan and evidence.
7. You verify effectiveness — confirm with objective evidence that the action worked and the defect hasn't recurred over a defined observation period.
8. Close the SCAR with sign-off, and feed the result into the supplier's performance record.

That verification-before-closure step is where discipline pays off. Closing because the supplier implemented something isn't the same as confirming it worked.

Managing SCARs in a QMS

The biggest practical headache with supplier corrective action requests is inconsistency. Every supplier replies in a different format, on a different timeline, with a different idea of what counts as adequate root cause — and if you're tracking it all in email and spreadsheets, reconstructing the trail for an audit is painful. Standardizing the SCAR workflow in a quality management system fixes most of that: one template, defined expectations, linked records, and a due date the system actually tracks.

Isolocity handles supplier corrective actions inside its CAPA module, which includes supplier quality management and a supplier contribution portal — so suppliers can respond directly into the record, corrective actions link back to the originating non-conformance or complaint, and everything carries a full audit trail through to closure. Supplier performance metrics feed the same system, so a SCAR isn't an isolated event but part of how you evaluate the supplier over time. If you'd like to see how it runs a supplier corrective action request start to finish, you can book a demo.

The point of a SCAR isn't to assign blame — it's to make sure a supplier problem gets solved at the source and stays solved. Issue it clearly, expect a real root cause, verify the fix, and close it with evidence. Do that consistently, and your supply chain gets measurably more reliable.

‍