Supplier Corrective Action Request

When a defect repeats, replacing one bad shipment may not be enough. A supplier corrective action request moves the discussion from a symptom to its cause and prevention, and the buyer and supplier need a shared description of the problem.

A fictional packaging buyer finds weak seams in three deliveries and asks the supplier to investigate the sealing process, not merely ship new cartons. Open a request when the issue's risk or recurrence justifies the effort: a minor isolated typo may need a simple correction, while a safety-critical or repeated failure may need immediate containment and a formal investigation.

Record the requirement that was missed and objective evidence such as purchase order, specification, lot, date, sample size and measured result, and avoid blaming a person before the facts are known. Containment limits immediate harm, since the supplier may stop shipment, segregate lots, inspect stock or arrange replacements, protecting operations while the deeper investigation proceeds.

A fictional supplier holds the next batch and checks finished goods before release, and does not label that temporary screening a permanent fix. Root-cause analysis asks why the process allowed the failure and, where relevant, why controls failed to detect it; a cause should be supported by evidence, not guessed from one meeting, and multiple contributing causes can exist.

A fictional team traces seam failures to a drifting temperature sensor and a missed calibration check, so both production and detection controls require attention. Separate correction from corrective action: reworking bad units corrects an immediate condition, while changing the underlying process to prevent recurrence is a different step.

A fictional supplier re-seals affected cartons, then adds an automatic temperature alarm and calibrates the sensor on a defined schedule. Lockheed Martin's supplier guidance asks for containment, root-cause details, corrective actions and effectiveness evidence, and EBA&D's supplier instructions likewise emphasise sufficient root-cause analysis and verified action, though their particular form fields are examples, not universal requirements.

The request should name owners and dates for responses, implementation and verification, and an extension can be agreed if a technical test genuinely takes longer, but a date set only to fill a slot must not masquerade as completed work. A proposed fix needs risk review, because a stronger seal might damage packaging or slow the line and a new inspection step may miss other failure modes, so test the change against the original specification.

Evidence of effectiveness is more than a signed action plan: check subsequent lots, error rates, audits or controlled test results over a suitable period, with a sample and duration that fit the risk. Closure is a decision, not merely receipt of a supplier reply: confirm containment is complete, the cause is credible, actions were implemented and effectiveness has been checked, and keep open items visible, as when a fictional supplier sends training slides but no proof staff used the revised process and the buyer keeps verification open.

A supplier may disagree with the initial finding, so share data, test methods and traceability before assigning responsibility, as when a fictional supplier shows that a damaged carton was crushed after carrier pickup and the parties handle transport damage separately. Contractual remedies are separate from the quality investigation, since credits, replacement, recall costs or suspension depend on the agreement and the facts and a SCAR does not itself establish a monetary debt, and some industries impose regulatory reporting, validation or recall duties, so a fictional medical-device distributor follows its regulated procedure for a serious defect rather than relying only on a procurement email, while a register of SCARs with severity, age, cause, actions, owner and closure evidence shows trends across sites or products without gaming closure.