Your customer just sent a supplier corrective action request, and the relationship is on the line. Most SCAR guides are written for the customer. This one is written for the supplier who received it. It covers what to do in the first 72 hours, containment that is real, root cause analysis that isn't blame, corrective action that changes the process, and the evidence your customer's quality team needs to close the SCAR without a fight.
The Email That Changes Your Week
It arrives from your customer's supplier quality engineer: a supplier corrective action request, with your part number, a description of the nonconformance, photos, and a deadline. Your sales manager is nervous. Your production manager says the parts were fine when they left. And you have a few days to respond in a way that protects the relationship.
Most guides about SCARs are written for the customer who issues them. This one is for the supplier who receives one. The good news: a well-handled SCAR can strengthen a customer relationship. It shows the customer that your system finds problems, fixes them properly, and proves it.
Hour Zero: Read It Carefully and Acknowledge
Before anything else, read the SCAR and your customer's supplier quality manual. Note the deadlines for containment, initial response, root cause, and final closure, and the required format, which is often 8D or a customer-specific form.
Acknowledge receipt the same day. Name the person responsible for the response and confirm you're working on containment. Silence is the fastest way to turn a quality issue into a relationship issue.
If anything in the SCAR is unclear, such as the lot affected, the measurement method, or the requirement, ask immediately. But don't argue about whether the problem is real until you have data. Starting defensive rarely ends well.
The First 24 to 72 Hours: Containment That Is Real
Containment protects your customer while you investigate. It must cover every place suspect product could be: your finished goods, work in process, raw material if relevant, product in transit, and product at your customer's site or their customers.
For each location, decide the action: quarantine, 100% inspection or sort, or replacement. Define how sorted parts will be identified as good, for example with a certified-material label, so your customer can tell contained shipments apart.
Report containment with numbers: how many parts were checked, where, how many were found nonconforming, and what happened to them. "All stock quarantined" isn't as credible as "1,240 pieces inspected at our facility, 3 rejected; 600 pieces at customer site sorted on the 14th, 0 rejected."
Root Cause: Not Blame Theater
This is where most SCAR responses fail. Customers routinely reject root causes like "operator error," "operator not paying attention," or "inadequate training." These describe what happened, not why the process allowed it.
Do the investigation with a small cross-functional team, including someone from the floor who does the work. Use structured tools like five whys, a fishbone diagram, or is/is-not analysis. Verify the root cause with data, and if possible reproduce the defect by turning the cause on and off.
Look for two root causes. The occurrence root cause explains why the defect was made. The escape root cause explains why your inspection or controls didn't catch it before shipment. Customers increasingly expect both, and fixing only the first leaves the door open.
Corrective Action That Changes the Process
A good corrective action changes the process so the problem can't happen again, or can't escape if it does. The strongest actions are error-proofing: fixtures that only accept the part one way, sensors that detect missing features, and interlocks that stop the machine. Weaker actions rely on people remembering: retraining, reminders, and extra inspection.
Retraining and inspection have their place, especially as interim measures, but a SCAR response that relies on them alone is likely to be questioned. Pair them with a process change wherever possible.
Extend the fix. Ask where else the same cause could occur: similar parts, other machines, other shifts. Update the documents that control the process, such as work instructions, control plans, and PFMEAs in automotive work, so the change sticks.
Verification: The Evidence Customers Need to Close
The SCAR isn't closed when you implement the action. It's closed when you prove the action works. Provide objective evidence: before-and-after data, capability studies, inspection results from subsequent lots, photos of the error-proofing, and updated documents with revision levels.
Give the customer what they need to close it without chasing you: a clean, complete 8D or customer form, attachments labeled clearly, and a summary on the first page.
The 8D Format in Brief
Many customers require the 8D format. In short: D1, form the team. D2, describe the problem clearly and specifically. D3, implement containment. D4, identify and verify root causes for occurrence and escape. D5, choose permanent corrective actions. D6, implement and validate them. D7, prevent recurrence by updating systems, documents, and similar processes. D8, recognize the team and close.
In automotive supply chains working to IATF 16949, customers often have specific problem-solving requirements and portals. Follow their format exactly.
Mistakes That Get SCARs Rejected
Missing the deadline, or going silent. Blaming the operator. Containment that ignored parts in transit or at the customer. Corrective actions that are all training. No verification data. Arguing about the requirement without evidence. And responses that fix the one part number but ignore the same risk on similar parts.
How We Help
SupplySourceSync, our supply chain brand, helps suppliers on the receiving end of a SCAR: containment planning, root cause investigation, corrective actions that hold up, and responses written in language customer quality teams accept. We also help build the problem-solving capability so the next one is handled in-house.
If your customer just sent you a SCAR, see our page on this situation, or tell us what's going on.
Sounds like your situation?
“A customer just sent us a SCAR”
See exactly how we approach this situation, what you'll have at the end, and request a Situation Review with our team.
Frequently Asked Questions
How long do I have to respond to a SCAR?
Your customer sets the deadline. A common pattern is containment within 24 hours, an initial response with root cause within a few days to two weeks, and full corrective action with verification within 30 to 90 days. Always follow the dates on the SCAR or in the customer's supplier manual.
What is an 8D report?
An 8D is an eight-discipline problem-solving format widely used to respond to SCARs. It covers forming a team, describing the problem, containment, root cause, choosing and implementing permanent corrective actions, preventing recurrence, and recognizing the team.
Why do customers reject SCAR responses?
The most common reasons are "operator error" or "retrained operator" given as the root cause, containment that did not cover all suspect stock, corrective actions that do not change the process, and no evidence that the fix works.
Can a SCAR cost us the customer?
It can if responses are late, repeated, or not credible. A well-handled SCAR can actually strengthen the relationship by showing the customer that your system finds and fixes problems.
