Customer Returns and Complaints

What Is a Customer Return?

A customer return is the record you open whenever a customer reports a problem with a product you shipped - whether the product physically comes back or the customer simply files a complaint. It tracks the issue from the first report through containment, root cause, corrective action, and a final response to the customer.

• Each return has a return number, a customer, a product, a severity (Low, Medium, High, Critical), and a status (Open, Closed, Cancelled).
• The return moves through phases, and each phase suggests the quality tools that fit that stage of the investigation.
• Everything linked to the return - NCRs, root cause analyses, CAPAs, photos, documents, and work items - stays attached so the full history is in one place.

Where to Find Customer Returns

Customer Returns is available from several places so you can start where you already are.

• Control Center: the Customer Returns tab shows open returns, KPI cards (open, critical/high, overdue containment, average days to close, cost), a repeat-customer callout, and a New Return button.
• Returns hub: the Returns page in the main menu lists every return with filters for status, severity, and text search, including closed and cancelled records.
• Customer detail: each customer page summarizes their total, open, and high/critical returns, and flags customers with three or more returns in the last 12 months.

Logging a New Return

Select New Return from Control Center or the Returns hub. The intake form captures the minimum needed to begin containment; details can be added later in the return workspace.

• Customer (required) - pick an existing customer or create one on the spot. Return date defaults to today.
• Product name and quantity returned (required); part number, lot/batch, and purchase order (optional but useful for traceability).
• Severity (required) - Low, Medium, High, or Critical. High and Critical returns are highlighted in Control Center.
• Problem description (required) - what the customer reported, in their words where possible.

Return Phases

A return progresses through phases that mirror a standard complaint-handling process. The current phase is shown on every return list and in Control Center.

1. Intake - the complaint is recorded.
2. Assessment - initial review of risk, scope, and whether an NCR is needed.
3. Containment - immediate actions to protect the customer and stop further shipments of suspect product.
4. Information Collection - gather evidence, photos, records, and similar returns.
5. Root Cause - RCA or Fishbone analysis.
6. SPC Review and FMEA Review - check process data and update risk analysis where relevant.
7. CAPA or 8D - corrective and preventive action.
8. Verification - confirm the fix worked using CAPA follow-up or SPC data.
9. Closed - the return is complete and a customer response has been issued.

The Return Workspace

Open any return to reach its workspace. Tabs organize the work so the team can see what is done and what is still missing.

• Overview - problem description, return cost panel, and Linked Artifacts (every tool, photo, and work item attached to this return).
• Assessment - the initial risk assessment; a badge appears until it is filled in.
• Containment Plan - summary of the plan with a warning badge when the target date has passed and the plan is not yet verified.
• Similar Returns - past returns from the same customer or product, so repeat problems are obvious.
• Tools - launch the quality tool recommended for the current phase (NCR, RCA, Fishbone, SPC, FMEA, CAPA, 8D).
• Evidence - photos and documents attached to the return.

Building the Containment Plan

The containment plan is a checklist that walks through everywhere suspect product could be. Set a target completion date, then work through each section and record notes.

• Customer Protection - customer notified, replacement provided, customer stock inspected or quarantined, interim response sent.
• Inventory Disposition - identify, quarantine, and inspect stock on hand; record quantities inspected, rejected, and released.
• Work In Process - is the product still in production, has production been stopped or controlled, is added inspection required.
• Shipments - review recent shipments, place holds, and note whether other customers may be affected.
• Supplier Involvement - flag supplier material and whether supplier notification is required.
• Measurement System (optional) - gauges involved, suspected calibration issues, or MSA verification needed; or mark not applicable with a reason.

When the checklist is complete, select Verify Containment. The plan records who verified it and when, and its status changes from Draft or Active to Verified. The History tab keeps a field-by-field revision log, and you can export the plan to PDF or Word.

Linking Quality Tools to a Return

The Tools tab recommends the right tool for the current phase and links the resulting report back to the return automatically. You can also link existing reports and work items.

• Intake, Assessment, Containment - Nonconformance Report (NCR) to document the defect.
• Containment, Information Collection, Root Cause - RCA and Fishbone to find the cause.
• CAPA and 8D phases - CAPA or 8D for corrective and preventive action; Verification uses CAPA follow-up and SPC.
• SPC Review and FMEA Review - SPC charts and FMEA to check process data and update risk.

Customer Response and Closing the Return

Once containment is verified and corrective action is in place, wrap up the return with a documented response.

• Generate Customer Response builds a document with Problem Summary, Containment Actions Taken, Root Cause, Corrective and Preventive Action, Verification of Effectiveness, and a Closing Statement, drawing from the linked tools.
• Close Return records the closure and moves the return out of the open lists in Control Center.
• Closed and cancelled returns stay available in the Returns hub and on the customer page for history and trend review.

Tips

1. Check the Overdue Containment KPI in Control Center daily - it counts returns whose containment target date has passed without verification.
2. Watch the repeat-customer callout. Three or more returns from one customer in a year usually means a systemic issue, not a one-off.
3. Attach photos during intake or containment while the evidence is fresh - they carry into the customer response.
4. Assign work items for containment actions so each task has an owner and shows up in the Work Queue.

Related Guides