A buyer may send a China supplier photographs, test evidence, order details, and a description of a product problem, then receive a short reply stating that the factory has checked the issue. The buyer still may not know what complaint reference the supplier created, which lot or shipment scope the supplier reviewed, whether it examined the buyer evidence, whether an investigation was recorded, or what follow-up record applies. A quick response can be helpful, but it is not a substitute for a clear record path.
China supplier complaint investigation records are buyer-side evidence links for a documented product issue. They can connect the buyer’s complaint, product or revision, supplier site, order, lot, carton or shipment scope, supplier assessment, evidence reviewed, investigation reference, action or follow-up record, supplier response, and unresolved issue. They do not establish that a complaint is valid, what caused it, whether an investigation is required or adequate, whether an action will work, whether goods are safe or conforming, or whether a recall, release, or regulatory report is necessary.
Current 21 CFR 211.198 requires drug-product complaint procedures and complaint records. Where known, records include product name and strength, lot number, complainant, nature of complaint, and reply; if an investigation occurs, findings and follow-up are included, while a decision not to investigate must state the reason and responsible person.1 Current 21 CFR 820.35 requires current device complaint review, evaluation, and investigation records for certain complaints and identifies specific record fields.2 FDA’s Complaint Files presentation provides historical device educational material but refers to pre-QMSR 820.198 provisions, so it should be treated as background only, not a description of the current device rule.3 These sources do not create general commercial requirements for China suppliers. They support a limited buyer method: define the issue, request a record path, preserve exceptions, and route root cause, safety, quality, regulatory, legal, recall, and release decisions to qualified owners.
Define the complaint, product, and shipment scope
A buyer must give a supplier enough context to identify the issue. A statement such as “the product is defective” does not identify the order, product version, material, quantity, event, or evidence the supplier should review. Before asking for a formal response, record the buyer’s complaint wording and the product or shipment scope it concerns.
| Scope field | Buyer record purpose |
|---|---|
| Buyer complaint reference | Links supplier replies to the buyer’s original issue |
| Product, assembly, or material ID | Identifies the item under review |
| Revision or specification reference | Links record request to the stated baseline |
| Supplier legal entity and site | Identifies the responding production source |
| Purchase order, invoice, or shipment reference | Identifies the commercial scope |
| Lot, batch, date code, carton, or unit scope | Identifies the product population described, if known |
| Complaint date and discovery date | Distinguishes buyer report from stated occurrence timing |
| Complaint description | Preserves the buyer’s allegation without converting it into a conclusion |
| Buyer evidence list | Identifies photos, samples, report references, or communications provided |
| Buyer record owner and intended decision | Names who reviews the file and why |
The buyer should separate observed facts from conclusions. “Carton A has a torn label” is an observation. “The factory used poor materials” is a conclusion that may or may not be supported. Clear records help the supplier understand what it is being asked to assess and help the buyer keep later response documents attached to the correct issue.
Request intake and supplier assessment evidence
The first supplier record should show that it received and understood the complaint scope. It can identify the supplier complaint ID, receipt date, product and lot scope, source of complaint, responsible role, initial assessment, and stated decision about whether a supplier investigation is planned. A buyer should not assume that an acknowledgment means the supplier accepts liability or has determined root cause.
| Intake or assessment evidence | What it can show | What it cannot prove alone |
|---|---|---|
| Supplier complaint or case ID | Supplier created a retrievable record | That supplier assessment is complete |
| Receipt date | Supplier recorded the buyer communication | When the underlying product event occurred |
| Product and lot scope | Supplier identified the stated item or batch | That the issue affects all units in scope |
| Complaint description | Supplier captured a stated allegation | Validity of the complaint |
| Buyer evidence reference | Supplier identified material it received | That evidence demonstrates a cause |
| Supplier responsible role | Supplier named an owner for response | Competence or outcome quality |
| Initial product or shipment status | Supplier recorded a stated temporary status | Safety, conformity, or release decision |
| Investigation decision or reference | Supplier stated whether it will investigate | Adequacy of the decision |
| Similar or prior issue reference | Supplier identified an earlier record | That issues share a root cause |
The pharmaceutical complaint rule provides a useful discipline: the record should name the complaint and product scope, and, if there is no investigation, include the stated reason and responsible person.1 A commercial buyer can request that level of clarity while recognizing that it does not apply a drug regulation to a general supplier relationship.
Request investigation, action, follow-up, and response records
If the supplier states that it investigated, the buyer can request the reference to its investigation file, the stated records or samples reviewed, scope reviewed, supplier findings, action reference, follow-up reference, and reply. The buyer should not equate a supplier’s stated finding with a verified root cause or an effective corrective action.
| Investigation or follow-up evidence | Buyer question |
|---|---|
| Investigation reference | Which supplier record documents the stated review? |
| Product, lot, or shipment scope | What population did the supplier state it reviewed? |
| Records or samples reviewed | What source evidence does the supplier identify? |
| Supplier-stated findings | What did the supplier record without buyer endorsement? |
| Action or corrective-action reference | Which supplier action record is associated? |
| Completion or target date | What timing did the supplier state? |
| Follow-up or effectiveness reference | Is there a later supplier record, where maintained? |
| Supplier response to buyer | What answer was sent to the buyer? |
| Similar-complaint reference | Did the supplier cite an existing record? |
| Exception or unresolved-status record | Was a gap, disagreement, or open item recorded? |
The current device QMSR describes complaint records concerning review, evaluation, and investigation for complaints involving possible failures and requires certain information for defined categories.2 It is device-specific. It nonetheless illustrates why a product identity, complaint details, action, and reply should be distinguishable in a record file. A sourcing team should request evidence links, not conduct a regulated-device complaint evaluation.
Link the complaint record to product and logistics scope carefully
The supplier may link its investigation to a production traveler, material lot, inspection record, packaging record, carton range, shipment, return, or retained sample. It may only be able to identify some of these. Buyers should preserve the exact level of linkage rather than assume an issue affects, or does not affect, every unit.
| Related record | Buyer use | Limit |
|---|---|---|
| Production traveler or work order | Identifies stated production scope | Does not establish product cause or conformity |
| Material or component lot | Connects supplier review to a stated input | Does not prove material caused the issue |
| Inspection record | Shows a stated control or observation record | Does not prove an issue was absent |
| Packaging or carton record | Connects problem to stated physical grouping | Does not prove all cartons are affected |
| Shipment allocation | Connects product scope to logistics handover | Does not release later shipments |
| Return or sample record | Identifies supplier access to a stated item | Does not prove sample representativeness |
| Complaint history | Shows an earlier or similar supplier record | Does not prove a common root cause |
| Change-control or action record | Makes a stated change visible | Does not prove action effectiveness |
FDA’s historical Complaint Files material stresses complaint review, evaluation, investigation, action, and reply in a device setting.3 It is useful for understanding the sequence of a supplier record response, but it is not current operational advice for non-device suppliers. The buyer should write its own commercial request and route specialized conclusions appropriately.
Keep allegation, finding, action, and decision separate
A practical evidence file uses distinct layers. This helps prevent a supplier’s initial response from being recorded as a confirmed cause, or a buyer’s allegation from being recorded as a verified defect.
| Record layer | Appropriate statement |
|---|---|
| Buyer complaint | Buyer reported an observed issue and stated scope |
| Supplier acknowledgement | Supplier confirmed receipt and recorded its understanding |
| Supplier evidence | Supplier identified records, samples, photos, or data reviewed |
| Supplier investigation record | Supplier recorded its stated review and findings |
| Supplier action record | Supplier identified a stated correction or follow-up action |
| Technical, safety, or root-cause conclusion | Qualified owner documents a conclusion within defined limits |
| Buyer decision | Authorized owner records commercial, quality, or release action |
A supplier’s email can be a useful communication record. It does not alone establish a technical root cause, corrective-action effectiveness, product safety, or contractual responsibility. Preserve the supplier’s exact language, request supporting record references, and keep final buyer decisions with authorized owners.
Control no-investigation, duplicate, late, and unresolved exceptions
Complaint files often become confusing when the supplier does not investigate, links the issue to a similar complaint, cannot identify a lot, receives evidence late, or leaves an action open. A buyer record should capture these facts without deciding what they mean for product quality or liability.
| Change or exception | Record the known facts | Next owner action |
|---|---|---|
| No supplier investigation | Supplier-stated reason, responsible role, and source record | Decide whether additional evidence or review is needed |
| Similar or duplicate complaint | Earlier and current supplier record references | Preserve each scope and avoid assuming common cause |
| Unknown product or lot | Available product, order, carton, or shipment identifiers | Log evidence gap and request clarification |
| Incomplete buyer evidence | Missing sample, photo, record, or context | Record the gap and decide whether more evidence is needed |
| Lost or unavailable sample | Supplier-stated item scope and availability status | Route technical question to qualified owner |
| Late supplier response | Complaint ID, expected and actual timing | Preserve timeline and open status |
| Changed product or production scope | Prior and current references and effective point | Confirm which records apply to the issue |
| Action-record mismatch | Conflicting complaint, action, or lot identifiers | Reconcile records without overwriting sources |
| Recurring reported issue | Distinct complaint references and known scope | Route trend or systemic question to qualified owner |
| Unresolved status | Known facts, next owner, and planned follow-up | Keep complaint record open until an authorized decision |
A no-investigation decision or an unresolved record does not establish that a supplier ignored the issue or that the buyer’s claim is correct. It describes the current evidence state. The buyer should decide whether to request more documentation, take a commercial action, place an authorized hold, or obtain qualified technical or legal advice.
Assign each decision to the appropriate owner
| Decision area | Typical owner | Supplier contribution |
|---|---|---|
| Record completeness | Buyer sourcing or quality owner | Provide complaint, assessment, investigation, and action links |
| Product and lot identity | Supplier production or quality owner | Explain product, lot, carton, and shipment references |
| Root-cause or technical question | Qualified engineering, technical, or quality owner | Preserve source records and stated findings |
| Safety or product-use question | Qualified safety, quality, or technical owner | Provide relevant product and issue scope |
| Corrective-action effectiveness | Qualified quality or technical owner | Provide action and follow-up references |
| Compliance, reporting, or legal question | Qualified specialist | Preserve records and follow escalation procedure |
| Recall, release, or commercial action | Authorized buyer owner | Maintain stated product and logistics status |
This route allows the sourcing team to check whether the supplier delivered the agreed record path without deciding whether the supplier found the right cause or action. It gives the supplier a practical way to record limitations before the buyer relies on a short response.
Use precise supplier request wording
For [buyer complaint reference, product or material ID, revision, supplier site, order, lot/batch/carton/shipment scope, and complaint date], provide the agreed complaint investigation records. Identify the supplier complaint ID, receipt date, stated product and lot scope, supplier understanding of the issue, records or samples reviewed, investigation reference if any, supplier-stated findings, action or corrective-action reference, follow-up record where maintained, current status, reply to buyer, and any exception or unresolved item. Buyer review of these records does not establish complaint validity, root cause, action effectiveness, product safety, product conformity, compliance, legal responsibility, recall need, or shipment release.
The wording requests a record path rather than an unsupported admission. If the buyer needs a technical failure analysis, product-safety review, legal assessment, regulatory reporting decision, or release decision, it should state that separately and send it to qualified owners.
Frequently asked questions
What are China supplier complaint investigation records?
They are supplier records linked to a buyer-reported product issue. They can identify the complaint, product or lot scope, supplier assessment, records reviewed, investigation reference, supplier-stated findings, action, follow-up, response, and any unresolved item. They do not establish a root cause or product conclusion.
Does a supplier response prove the root cause?
No. A supplier response can record its stated findings or explanation. A root-cause or technical conclusion requires qualified review within defined scope. The buyer should keep the response separate from the evidence and final decision.
What if the supplier says no investigation is needed?
Ask for the supplier’s stated reason, responsible role, product or shipment scope, and any record reference. Document the current evidence state. The buyer can then decide whether the agreement calls for more information, a commercial action, or qualified review.
Should buyers request a corrective-action report for every complaint?
Not necessarily. Define the complaint scope, intended decision, product risk, agreement, and evidence gap. An isolated record question may need an explanation, while a recurring or technically significant issue may require a more detailed supplier response and qualified review.
Can a similar prior complaint be used to close a new complaint?
Only if the supplier identifies the earlier record and the basis for its stated connection. A similar complaint does not automatically prove the same product, lot, cause, action, or outcome. Preserve both records and route technical conclusions to qualified owners.
Does review of a complaint file release new or existing shipments?
No. The review can support later sourcing, quality, or commercial decisions. It does not establish product conformity, safety, regulatory status, recall need, customs readiness, or final shipment release.
Review the record path before relying on a supplier response
China supplier complaint investigation records help a buyer ask a specific question: which supplier records connect this complaint to this product scope, assessment, investigation, action, and follow-up? A proportionate file links the buyer allegation, supplier acknowledgement, evidence reviewed, findings, action, response, and known exceptions. It also separates record review from technical or legal conclusions.
Start with one documented issue and define the product, lot or shipment scope, buyer evidence, desired supplier response, exception route, and buyer owner. Supplier Ally can help buyers organize supplier complaint requests, product and shipment links, exception notices, and cross-border communication. Use qualified safety, engineering, laboratory, quality, regulatory, legal, corrective-action, and release owners for decisions beyond record review.
EN 
ES 