Every consumer brand receives complaints, and a beauty brand will receive some that involve a reaction on the skin. How those are handled determines whether an incident stays a complaint or becomes a regulatory matter, a recall or a claim.
The difficulty is that complaints arrive without warning and in an unpredictable order, and a brand that has not decided in advance who does what will improvise. Improvisation in this area produces inconsistent responses to consumers, incomplete records, and investigation quality that varies with who happens to open the email.
This guide explains what counts as an adverse event, what to capture at intake, how to triage and investigate, what has to be reported to a regulator and when, and how the process connects back to manufacturing.
Why the process has to exist before the first complaint
Three features of this work make prior preparation essential rather than optional.
The first is timing. A regulatory reporting obligation, where it applies, runs from the moment the brand becomes aware of the event, and awareness is not a decision the brand can defer. A brand that spends a week working out who owns the process has already consumed part of its reporting window.
The second is evidential value. The consumer's description, the batch code, the photographs and the pack are all easiest to obtain at the first contact and progressively harder afterwards. A complaint handled without a structured intake produces a record that cannot support an investigation.
The third is consistency. Without a defined severity scale and a defined response, two similar complaints received a week apart will be handled differently, which is difficult to defend if either becomes a regulatory matter.
What counts as an adverse event
A complaint and an adverse event are not the same thing, and the distinction matters because the obligations differ.
A complaint is any expression of dissatisfaction: the pump does not work, the product separated, the colour differs from the previous batch, the scent is different. These are quality matters and they are managed through the quality process.
An adverse event is a health-related event associated with the use of the product. In most regulatory frameworks a subset of these is treated as serious, and the definition typically turns on the outcome rather than on the brand's judgement of severity. Outcomes that commonly bring an event into the serious category include death, a life-threatening reaction, hospitalisation, significant or persistent disability or disfigurement, and a congenital anomaly, together with infections or reactions requiring medical intervention.
The practical implication is that severity classification should follow the defined criteria rather than a subjective assessment. A brand that classifies by how alarming the email sounded will misclassify, and the direction of the error is usually towards under-reporting.
What to capture at intake
Intake is the stage where the quality of everything downstream is determined, and the fields should be defined in advance.
The record should capture the consumer's contact details, the date of the event and the date the brand became aware of it, the product name and the variant, the batch or lot code if it can be read, where and when the product was purchased, how long it had been in use, the symptoms as described by the consumer in their own words, whether medical attention was sought, whether any other products were being used, and any photographs the consumer can provide.
Three items are commonly missed and each matters. The date the brand became aware drives the reporting clock, so it should be recorded explicitly rather than inferred from the email timestamp. The batch code is the link to the production records and to any other complaints about the same batch. And the consumer's own words should be recorded verbatim rather than summarised into a category, because a summary loses the detail that a later assessment may need.
It is equally important to record what the brand does not know, so that the gaps are visible when the file is reviewed.
Triage and severity
Triage takes the intake record and assigns it to a route, and it should produce three outputs.
The severity classification determines whether the event is serious under the applicable definition, which determines the reporting obligation. The quality classification determines whether the complaint is isolated or indicates a batch or a formula problem, which determines whether the investigation is product-related or event-related. And the response route determines who responds to the consumer and within what period.
Two principles make triage reliable. First, where the classification is uncertain, it should be escalated rather than resolved downwards, because the cost of an unnecessary escalation is administrative and the cost of an under-classified serious event is regulatory. Second, triage should be performed by a named person with a named deputy, so that a complaint arriving on a Friday evening is not delayed until Monday by the absence of one individual.
Investigating a complaint
An investigation has two parallel strands, and both should be followed even when the answer appears obvious.
The product strand examines the batch records, the retained sample, the stability data and the pack. The questions are whether the batch was within specification at release, whether the retained sample shows the same characteristic now, whether other complaints have arrived for the same batch, and whether anything changed in the formula, the process or the pack around that batch.
The use strand considers what happened after the product left the factory: how it was stored, how it was applied, whether it was used with other products, and whether the consumer's description is consistent with the product's characteristics. This strand is often treated as a way of deflecting the complaint, which is a mistake; its purpose is to establish facts, and it is frequently where the honest answer sits.
Two things should be avoided in the investigation record. Causal language, since a cosmetic manufacturer or brand is not in a position to diagnose and a stated conclusion can later be used against the brand. And selective recording, since omitting an inconvenient observation from the file makes the entire file less credible if it is reviewed.
Complaint types and their usual causes
| Complaint type | Typical underlying cause | Where the investigation usually begins |
|---|---|---|
| Skin reaction or irritation | Individual sensitivity, cumulative use, interaction with other products, or a formulation or batch issue | The batch record, the retained sample and any other complaints for the same batch |
| Product separated or changed texture | Storage outside the intended conditions, age beyond the shelf life, or an emulsion stability issue | The storage history, the retained sample and the stability data |
| Colour or odour differs from the previous purchase | Batch-to-batch variation, raw material variation, or oxidation during storage | The retained samples from the batch and the prior batch |
| Pack failure, leakage or pump not working | Component defect, filling damage, or compatibility between the formula and the pack | The pack inspection records and the compatibility data |
| Contamination visible in the product | Manufacturing hygiene, pack cleanliness, or in-use contamination after repeated opening | The batch record, the microbiological data and the pack format |
| Claimed effect not observed | Expectation mismatch rather than a defect in most cases | The published claims and the consumer's understanding of them |
Two patterns in the table are worth noting. Several complaint types can have either a product cause or a use cause, and the investigation should distinguish them before concluding. And the last row is a marketing issue as often as a technical one, because a claim that a consumer read more strongly than it was written will generate complaints that no batch investigation can resolve.
Responding to the consumer
The response to a consumer has three purposes: to acknowledge, to obtain information, and to resolve without creating a further obligation.
A useful response is prompt, specific about what the brand intends to do next, and free of confirmation of cause. Where the consumer has reported a reaction, the appropriate action is to recommend that they stop using the product and seek medical advice if the symptoms persist, without offering a diagnosis. That is both responsible and prudent, since offering a medical opinion is outside the brand's competence and may create a liability.
Where the resolution includes a refund or a replacement, it should be recorded against the complaint. Where the consumer provides a batch code and the sample is requested back, the request should be made early, because a returned sample is often the single most useful piece of evidence.
Regulatory reporting obligations
Reporting requirements vary by market, and the brand should establish the position in each market it sells in before it is needed.
In the European Union, the framework places obligations on the responsible person and on distributors in relation to serious undesirable effects, and the effect has to be reported to the competent authority of the member state where it occurred, with specified information. In the United States, the Modernization of Cosmetics Regulation Act introduced adverse event reporting for serious events, with a short statutory period measured from the date the responsible person becomes aware of the event, together with record keeping for a defined number of years, and a labelling requirement giving consumers a contact route for adverse event reporting.
Beyond those two frameworks, other markets maintain their own requirements, and some place the obligation on the importer or the local entity. The practical approach is a table listing each market the brand sells into, the obligation, the recipient and the time limit, held by whoever owns the process, and reviewed when the brand enters a new market. The current requirements should always be confirmed against the texts in force rather than from a summary, because the thresholds and periods are subject to amendment.
Corrective action and the link to manufacturing
The value of the complaint process is realised when it changes something, and the connection to manufacturing is where that happens.
A single complaint about a pack is usually a consumer service matter. A pattern of the same complaint across a batch is a quality signal that should reach the production records and the batch record review. A pattern across several batches points at the formula, the pack or the process, and should trigger a review with the manufacturer rather than a series of individual responses.
The mechanism that makes this work is the batch code. Where the manufacturer maintains batch traceability linking raw materials, process parameters and finished goods, a complaint can be traced to its cause and the affected population can be identified. Where traceability is weak, a complaint can only be answered case by case, and a serious issue becomes a whole-product withdrawal rather than a targeted one.
Corrective action should be recorded, with what was changed, when, and how the change was verified. That record is what turns the complaint process into a quality system rather than a mail queue.
Records and retention
Complaint and adverse event records should be retained for the period the applicable regulation requires, which is defined in some markets and left to good practice in others, and for at least as long as the insurance policy requires. Where the two differ, the longer period governs.
What should be retained is not only the complaint itself but the whole file: the intake record, the triage decision, the investigation, the samples or photographs, the correspondence with the consumer, the batch records consulted, any corrective action and the outcome. A file that contains only the initial complaint cannot support a regulatory review or an insurance claim.
Access should be restricted to the people who need it, because the file contains personal data and health information, and the data protection obligations apply in addition to the product safety ones.
Frequently asked questions about complaints and adverse events
Is every skin reaction a reportable adverse event?
No. Reporting generally attaches to events meeting a defined seriousness threshold. The classification should follow the defined criteria rather than a subjective assessment of how serious the description sounds.
Should we tell the consumer what caused the reaction?
No. Recommend that they stop using the product and seek medical advice if symptoms persist, and avoid offering a diagnosis. Causal statements are for a medical professional to make.
How long should records be kept?
For the period required in each market and for the period the insurance requires, whichever is longer. The requirements are specific in some markets and should be confirmed for each.
Who owns the process?
The brand, since it is the entity whose name is on the pack. The manufacturer supports it by providing batch records and participating in the investigation.
Will you support a complaint investigation?
Yes. We provide the batch records, the retained samples, the stability and microbiological data and the traceability information needed to establish whether an issue is batch-related, and we participate in the corrective action.
Next step: write the process before you need it
If you are launching a product, tell us the markets you will sell into and we will confirm the batch traceability, retained sample and documentation arrangements that support a complaint and adverse event process. Write to capsulebiotech@163.com, message the right team on WhatsApp: Capsule Series (capsules only) +86 158-7655-5319, Cosmetics Series (serum, hair care, body care, fragrance) +86 158-7655-5319, or use the inquiry form and we will reply within one working day.
Related programmes and guides: firming face cream, amino acid facial cleanser, and our guides to US MoCRA compliance and product liability insurance.