What to Do When a Customer Reports a Reaction

The message usually comes in the same way. Someone messages your shop's page or emails you saying the face cream broke them out, or the soap left a rash, and there's a photo attached that makes your stomach drop a little. What you do in the next hour matters more than what you do in the next week, so it helps to have a plan before this actually happens rather than improvising it in the moment.

First, respond like a person, then document like a professional

Reply promptly, take the concern seriously, and do not get defensive even if your instinct says the product is fine and something else caused it. You genuinely might be right about that, but the conversation goes better if you lead with concern rather than a defense of your formula.

Then start gathering facts, calmly and specifically:

1. What product, and which batch number if they can find it on the packaging
2. When they started using it and when the reaction appeared
3. What the reaction looks like, ideally with a photo
4. Whether they used it as directed, or combined it with something else new around the same time
5. Whether they have known allergies or sensitive skin history they are willing to share
6. Whether they sought medical attention

Get this in writing wherever possible, even if the conversation started as a phone call. An email summary you send back to them, confirming what you understood, creates a paper trail and also gives the customer a chance to correct anything you misunderstood.

Pull your own batch record

This is exactly why batch numbering and record-keeping matter beyond just looking official. Once you have the batch number, pull your own manufacturing log for that batch: the formula version used, the raw material lots that went into it, and any quality checks you ran. Cross-check whether other customers who bought from that same batch have reported anything similar. A single isolated reaction against a widely-sold batch reads very differently than a cluster of reports tied to the same production run.

Look at the ingredient list with fresh eyes

Go back to your ingredient documentation and specifically flag anything with known sensitizing potential: fragrance components, essential oils carrying natural allergens like linalool or limonene, and any active with a history of individual sensitivity even at compliant concentrations. This is not about assuming guilt. It is about being able to answer, credibly, whether there is a plausible ingredient-level explanation, versus a reaction that is more consistent with an individual sensitivity unrelated to a formulation defect.

Know your reporting obligations

Depending on where you are selling and where the customer is located, there may be a formal adverse event recordkeeping duty attached to your regulatory filings. In the US, MoCRA specifically requires adverse event recordkeeping as part of the responsible person's obligations under facility registration and product listing. Even where a formal reporting duty is not immediately clear-cut for your situation, keeping your own internal record of every reported reaction, resolved or not, is good practice everywhere you sell, and it is the kind of documentation a regulator will expect to see if they ever ask.

A simple internal log to keep

Field	Why it matters
Date reported	Establishes timeline
Product and batch number	Links to your manufacturing record
Nature of reaction	Assesses severity and pattern
Customer's product usage description	Rules in or out misuse
Your response and any resolution	Shows good faith handling
Whether other reports exist for the same batch	Flags a possible batch-specific issue

Keep this log even for reactions that turn out to be unrelated to your product. A thin log with three entries over two years, all resolved and documented, is exactly the kind of thing that protects you if a pattern question ever comes up later.

When to consider a wider response

If you get more than one report tied to the same batch, or a reaction is severe enough to involve medical care, that is the point to seriously consider whether a formula review or, in a worst case, a batch-level pull from sale is warranted. This is a judgment call that weighs severity, pattern, and plausibility, and it is fine to be conservative here. A voluntary pause on a batch while you investigate costs you far less than a pattern of reactions you sat on.

Building the habit before you need it

None of this works well if you are building your traceability system for the first time in the middle of a complaint. Cosmetic Comply keeps your ingredient mapping and past filings organized under one account, so when a question like this comes up, you already have the INCI names, concentrations, and Hotlist screening results on hand rather than digging through old supplier emails while a customer waits for a reply. It will not manage the customer conversation for you, but it means your ingredient-side homework is already done when you need it most.