What this is
What is a customer return record?
What is a customer return record?
A customer return record documents product a customer has sent back, capturing the reason given, its condition on arrival, whether the defect is confirmed against a retained sample from the same batch, and the disposition of both the item and any remaining stock.
How is this different from a customer complaint record?
A complaint record captures what the customer reported, which may never involve the product physically coming back. A return record exists because the item did come back, and its central task is assessing the physical evidence rather than the account of it.
Who completes a customer return record?
Customer service logs the return and the customer's stated reason; quality carries out the condition and defect assessment. Both signatures are required because the record combines an administrative fact with a technical judgement on attribution.
Scope
When is a customer return record required?
This record exists only once product has physically come back. It is the wrong instrument for a reported problem where nothing returns, and the wrong one for a defect caught before despatch.
Use this template when
- A customer sends product back and it has been physically received
- A complaint has already been logged and the customer subsequently returns the item as evidence
- The return needs assessing against the batch's retained sample to determine whether the defect is real and where it originated
- Stock from the same batch may also be affected and needs tracing
- The disposition of the returned item, credit, and any onward investigation need a single record to reference
Do not use it for
- Customer Complaint Record, which logs what the customer reported, whether or not any product is physically returned.
- Product Nonconformance Report, which covers material or product found defective before it reached the customer.
- Hold and Release Record, which manages the decision on suspect stock still in the warehouse, distinct from an item already despatched and returned.
- Complaint Investigation Record, which carries the fuller root-cause work once this record has established one is warranted.
- Anything where the product never left the site, which belongs with the internal nonconformance and hold instruments instead.
Compliance mapping
Which ISO 9001 cl.8.7 requirements does this satisfy?
ISO 9001 treats a customer return as customer feedback that has to be analysed for cause, alongside the general duty to control anything found nonconforming once it is back in the organisation's hands.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 9001 cl.8.7.1 | Outputs found not conforming to requirements are identified and controlled to prevent unintended use once returned | Condition on arrival |
| ISO 9001 cl.9.1.2 | Customer perception and feedback, including complaints and returns, is monitored as a measure of satisfaction | Return |
| ISO 9001 cl.10.2.1 | Nonconformity is reacted to, its cause evaluated, and the need for corrective action determined | Assessment |
| ISO 9001 cl.8.5.2 | Outputs are identified as necessary to ensure traceability, linking the return to the batch and any affected stock | Assessment |
| ISO 9001 cl.7.5.3 | Documented information, including retained samples used as objective evidence, is controlled and available | Condition on arrival |
| ISO 9001 cl.10.2.2 | Corrective action and its results are retained as documented information | Disposition and follow up |
What it does not cover
- Customer Complaint Record, the correct instrument where the customer reports a problem but no product is returned.
- Product Nonconformance Report, which covers defective material or product identified before it left the organisation's control.
- Complaint Investigation Record, which carries the full root-cause investigation once this record has established one is warranted.
- Hold and Release Record, which manages suspect stock still in the warehouse rather than product already despatched and returned.
- Root Cause Analysis, which the investigation level field routes to once the return points beyond the individual complaint.
Global
Customer Return Record requirements by country
A customer return is not separately regulated in most regimes; it is folded into the general duty to control nonconforming product and, in food and pharma chains, into traceability obligations that apply regardless of where the product is in its journey.
FSMA traceability requirements and FDA 21 CFR 117 for food; general product liability law for other goods
No standalone return-handling regulation, but traceability rules require the batch to be identifiable and its disposition recorded regardless of direction of movement.
A returned batch must be traceable back through despatch to production with the same rigour as an outbound shipment, not treated as a one-off exception.
General Product Safety Regulations 2005 and, for food, retailer certification under BRCGS
Duty to withdraw or recall unsafe product, with returns as one of the signals that trigger that assessment.
A return revealing a batch-wide defect has to be assessed against the withdrawal or recall threshold, not closed as a single customer's problem.
ISO 9001 cl.9.1.2 and cl.10.2
Customer returns are monitored as feedback and, where nonconforming, trigger the same reaction and cause-evaluation duty as any nonconformity.
Certification audits expect returns analysed in aggregate, not just closed individually, since the trend is what cl.9.1.2 is actually asking for.
How to complete it
How to complete a customer return record, step by step
The form prompts for the physical facts well. What it cannot force is the judgement deciding whether those facts point at production or at everything that happened after despatch.
Packaging intact, temperature on arrival, shelf life and storage conditions during return exist to be read together before the defect assessment starts. A defect in a product that travelled unrefrigerated tells you about the return, not the batch.
Checking the return against a retained sample from the same batch is the fastest way to know whether the defect is present at source. Marking the sample not available and concluding anyway removes the one comparison that would settle it.
Defect confirmed answers whether something is wrong with the product as returned; fault attributable to us answers where that came from. Treating the second as automatic once the first is Yes mismatches scorecard and credit consequences against what happened, especially in poor transit conditions.
Same batch still in stock and stock affected have to be actively checked against inventory, not inferred from only one customer having complained. A batch-wide problem surfacing one return at a time looks, at each record, like an isolated incident.
What auditors find
Most common customer return record findings
Because the evidence has already travelled by the time it reaches this record, findings concentrate on whether the assessment respected that, and whether the batch-wide question was asked.
| Finding | Clause | What fixes it |
|---|---|---|
| Defect confirmed and fault attributable to us both marked without storage or transit conditions assessed first. | ISO 9001 cl.8.7.1 | Complete condition on arrival, including storage during return, before recording the defect assessment. |
| Retained sample marked not available with no note why, closing off the comparison that would settle attribution. | ISO 9001 cl.7.5.3 | Require a reason wherever the retained sample cannot be checked; treat its absence as a limitation, not a non-event. |
| Same batch still in stock not checked against inventory before closing. | ISO 9001 cl.8.5.2 | Query the batch against current stock when raised, not left to memory or a later report. |
| Return linked to an existing complaint without the complaint being updated with the physical finding. | ISO 9001 cl.9.1.2 | Write the condition and defect assessment result back into the linked complaint record once available. |
| Investigation required marked No on a return where the defect was confirmed and attributable. | ISO 9001 cl.10.2.1 | Set investigation required by potential outcome, not past occurrence. |
| Disposition recorded as retain as evidence with no subsequent decision or date, leaving the item in limbo. | ISO 9001 cl.10.2.2 | Set a review point on any evidence-retention disposition so it converts to a final decision by a set date. |
Case in point
Case in point: the return that blamed the wrong stage
A customer returned a batch of sliced ham reporting an off odour. It arrived at ambient temperature with no indication of storage since purchase, and the assessment confirmed a clear sensory fault. The odour matched a known spoilage pattern, so the record marked fault attributable to us as Yes and fed into the trend, with the retained sample field left as not available.
A later review, prompted by an unrelated second complaint, found the retained sample had in fact been checked and was conforming; the result had never been entered against this record. The two records together pointed at a distribution temperature failure rather than a production defect, but by then the batch was already reported internally as a quality event. The assessment itself was accurate; what failed was recording the comparison as unavailable when it existed.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
5 sections
- Reference
- QUA-008
- Archetype
- Record
- Record ID
- CASE-2026-000
- Scoring
- Severity band
- Direction
- High is bad
- Singleton
- No
- Basis
- ISO 9001 cl.8.7
- Links
- Links Traceability, Complaint
- Tags
- Quality, Customer
- Sections
- 5
- Fields
- 47
- Follow up fields
- 10
- Repeating sections
- 0
- Links out
- 7
Header
9 fieldsCase ID*
Auto sequence. Format CASE-2026-00000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Raised By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Batch Number*
Numeric key joining to your ERP batch record.
Links to External system reference
Product*
Production Date*
Return
7 fieldsCustomer*
Customer Reference
Return Received Date*
Quantity Returned*
Reason Given By Customer*
Complaint ID
Where a complaint was logged before the product came back.
Links to QUA-023 Case ID
Despatch Record ID
Links to QUA-075 Despatch ID
Condition on arrival
7 fieldsPackaging Intact*
- Yes3 pts
- Marginal1 pt
- No0 pts
Temperature On Arrival
Within Shelf Life*
- Yes3 pts
- Expired0 pts
Storage Conditions During Return*
Product returned in an unrefrigerated van tells you little about how it left here.
- Correct throughout3 pts
- Partly known1 pt
- Unknown or poor0 pts
Evidence Usable For Investigation*
- Yes3 pts
- Limited1 pt
- No0 pts
Photograph*
Sample Retained For Testing*
- Yes3 pts
- No0 pts
Assessment
11 fieldsDefect Confirmed*
- Yes0 pts
- Partly1 pt
- No3 pts
Defect Category
Fault Attributable To Us*
- No3 pts
- Possibly1 pt
- Yes0 pts
Retained Sample Checked*
Comparing the return against the retained sample from the same batch is the fastest diagnosis.
- Yes3 pts
- Not available0 pts
- No0 pts
Retained Sample Result
Same Batch Still In Stock*
Stock Affected By This Batch*
- No3 pts
- Yes0 pts
Quantity Affected
Hold ID
Raise the hold record, then enter its reference.
Links to QUA-003 Hold ID
Product Location
Where the affected product physically is right now.
Traceability Record ID
Links to QUA-073 Trace ID
Disposition and follow up
13 fieldsReturn Disposition*
Credit Issued
Investigation Required*
Set by potential outcome, not by what actually happened.
- No3 pts
- Yes0 pts
Investigation Level
RCA ID
Format RCA-2026-00000.
Links to FDN-013 RCA ID
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Quality*
Signature*
Customer Service*
Second Signature*
QUA-008 · record IDs look like CASE-2026-000 · Links Traceability, Complaint
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The physical assessment is usually done well. What slips is the link back to the batch, the sample check, and whether one return was ever read against the others.
Holds the return against the batch and retained sample record, flagging an attribution decision recorded without the comparison behind it.
Reconstructs despatch and transit conditions for the returned batch so storage and cold-chain fields reflect what is actually known, not assumed.
Reads returns against complaint and traceability records together, surfacing a batch-wide pattern before a second customer becomes a surprise.
This template lives in KnowQuality — quality and food safety. HACCP, nonconformance, traceability, laboratory and customer complaints.
Meet KnowQuality→Glossary
Customer Return Record definitions and key terms
- Retained sample
- Material from the same batch kept back at production, compared against a returned item to determine whether a defect is present at source.
- Attribution
- The judgement of whether a confirmed defect originated with the organisation's own production, distinct from what happened during storage or transit.
- Cold chain
- The unbroken sequence of temperature control from despatch to customer and, on a return, back again; a break anywhere can produce a defect the product did not leave with.
- Withdrawal
- Removing product from the supply chain, distinct from a recall which targets product already with the end consumer; a batch-wide defect can trigger either.
- Severity band
- The scoring used here, rating how serious the confirmed and attributable finding is, which sets the urgency of investigation and onward action.
FAQ
Frequently asked questions about customer return record
Should we assess the returned item before or after checking the retained sample?+
In parallel where possible, but treat the sample comparison as the decisive check, not an afterthought. An assessment of the returned item alone is an opinion about what probably happened, not a finding about what did.
What if the customer will not say how the product was stored after purchase?+
Record storage conditions during return as unknown or poor rather than assuming correct handling. The field exists because that information is usually missing, and assuming correct handling produces attribution decisions the evidence does not support.
Does every return need an investigation?+
No. Investigation required should be set by the potential consequence of the confirmed finding, not by whether this return escalates. A confirmed, attributable defect with food safety or allergen implications warrants investigation regardless.
How do we handle a return when the same batch has already sold through?+
Same batch still in stock will be No, but that does not close the traceability question. Record whether other customers received the batch, since a sold-through batch with a real defect is a withdrawal question, not a closed file.
Who decides the disposition, credit and destroy or return?+
Quality decides disposition from the defect and attribution findings; customer service and quality jointly manage credit, since credit is a commercial response that should follow the technical finding, not precede it.
Why keep a photograph if the retained sample comparison is the decisive check?+
The photograph is the only record of the item's condition on arrival, before further handling. The retained sample settles whether the batch was defective; the photograph settles the returned item's actual state.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Nonconformance and Complaints
Root Cause Analysis
Finds out why something happened rather than who was involved
Corrective and Preventive Action
The single action record used everywhere
Product Nonconformance Report
Records product that does not meet specification
Process Deviation Report
Records a process that ran outside its set limits, even where the product still passed
Hold and Release Record
Places suspect product on hold and records the decision to release, rework or scrap it
Rework Authorization
Authorises rework on nonconforming product and sets out exactly what will be done
More in Nonconformance
Product Nonconformance Report
Records product that does not meet specification
Process Deviation Report
Records a process that ran outside its set limits, even where the product still passed
Hold and Release Record
Places suspect product on hold and records the decision to release, rework or scrap it
Rework Authorization
Authorises rework on nonconforming product and sets out exactly what will be done
Scrap Record
Records product written off, with quantity, reason and cost
Concession Request
Requests permission to use or ship product that does not fully meet specification
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 9001:2015 clauses 8.5.2, 8.7.1, 9.1.2 and 10.2
- General Product Safety Regulations 2005 (UK)
- FSMA traceability requirements, 21 CFR Part 1, Subpart S
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.