QUICK ANSWER

When a peptide product complaint arrives, treat it as a regulated record from the first minute: log it the same day, decide quickly whether it is also a reportable adverse event, investigate whether product quality or a batch failure is implicated, then document your rationale and any corrective action. Under 21 CFR 211.198 you must maintain written complaint procedures and a complaint file; if the complaint involves a serious, unexpected adverse event and you hold an approved application, the 15-day FDA reporting clock under 21 CFR 314.80 may already be running.

---

A customer emails to say your peptide made them nauseous. Or a clinic reports that a vial arrived cloudy. Or a distributor forwards a message about a lot number that “doesn’t look right.” It feels like customer service. It is not. The moment that message lands, you are holding a regulated record. Depending on what it says, one or more federal reporting clocks may already be counting down without you knowing it.

This is the failure mode that puts small peptide companies in front of FDA. Not the complaint itself, which is normal and expected, but the days that quietly pass while a founder treats it as an inbox item instead of a quality event. Here is how to make sure the first 72 hours protect you instead of exposing you.

A complaint is a record, not a message

FDA does not care how a complaint reaches you: phone, email, a chat widget, a distributor relay, a comment on a social post. Under 21 CFR 211.198, any written or oral communication alleging deficiencies related to the identity, quality, durability, reliability, safety, effectiveness, or performance of a drug product is a complaint, and you are required to have written procedures for handling it. The regulation also requires that you keep a complaint file and that you decide, for each complaint, whether it represents a failure of the product to meet its specifications and, if so, whether an investigation under 21 CFR 211.192 is warranted.

The practical translation: a complaint is not closed when you refund the customer. It is closed when it is logged, assessed, investigated as needed, dispositioned with a documented rationale, and, where a trend emerges, escalated. Skipping the paper trail is the single most common way a routine complaint becomes an inspectional finding.

Hour zero: capture it the same day

Speed of intake is the cheapest insurance you will ever buy. Every complaint should be logged the same business day it is received, into a single controlled log rather than scattered across personal inboxes. At minimum, capture: the date received and the date of the event, the reporter’s contact details, the specific product and lot or batch number, a verbatim description of the problem, whether any injury or health effect is alleged, and the name of the person who took it in.

The lot number is the hinge the whole file turns on. Without it you cannot link the complaint to a batch record, you cannot tell whether other units from the same lot are implicated, and you cannot make a defensible recall decision later. Train everyone who might receive a complaint (sales, support, the founder’s cell phone) to ask for it first.

The fork in the road: is it also an adverse event?

This is the assessment that most often goes wrong. A product-quality complaint (“the cap was cracked,” “the powder was discolored”) and an adverse event (“I had heart palpitations after the injection”) are handled under different rules, on different clocks, and a single message can be both at once. Your triage step has to consciously ask: does this describe harm to a person?

If it does, the reporting obligation depends on your regulatory pathway, and you need to know yours cold before a report ever comes in. If you hold an approved NDA or ANDA, serious and unexpected adverse events are subject to 15-day “Alert” reporting under 21 CFR 314.80, submitted on a MedWatch 3500A into FAERS. If you operate as a 503B outsourcing facility, adverse event reporting to FDA is a condition of that status. Even where formal reporting is not mandatory, a documented medical assessment of every alleged harm is expected. The safe operating posture for a small peptide company is simple: assume the clock is running until a qualified person has confirmed it is not.

Investigate the product, not just the person

Once intake and adverse-event triage are done, the quality question remains: is the product itself implicated? Pull the batch record for the lot in question. Check the retain sample. Review the release testing and the certificate of analysis. If the complaint plausibly points to a specification failure (potency, sterility, endotoxin, appearance), then 21 CFR 211.192 requires a documented investigation, and “we couldn’t reproduce it” is not a conclusion. It is the beginning of one.

Peptides carry failure modes small-molecule playbooks miss: aggregation, deamidation, oxidation, adsorption to the vial, and degradation from a broken cold chain. A complaint of “cloudy” or “less effective than the last vial” can be the only outward sign of a stability or handling problem that affects the entire lot. Treat the single complaint as a potential sentinel for the batch.

Close the loop and watch the pattern

Every complaint file should end with a documented disposition and, where the investigation reveals a systemic cause, a corrective and preventive action (CAPA). But the highest-value step is the one founders skip: trending. Three “minor” complaints about the same lot, or the same failure mode across lots, is a signal, and FDA expects you to detect it. Periodic review of your complaint log for patterns is not optional polish; it is how you catch the problem while it is still a complaint and not yet a recall.

What actually turns a complaint into a 483

In warning letters and inspection observations, the complaint is rarely the violation. The violation is the vacuum around it: no written complaint-handling procedure; complaints received but never logged; no assessment of whether a specification failure occurred; no investigation where one was clearly warranted; adverse events not evaluated for reportability; and no evidence that anyone ever looked across complaints for a trend. Each of those is a documented gap an investigator can find in an afternoon, and each is entirely preventable with a procedure and a log you set up before the first complaint arrives.

The first-72-hours checklist

• Log the complaint the same business day into one controlled complaint file, never a personal inbox.
• Capture the lot/batch number and the date of the event, not just the date received.
• Triage for harm: decide whether it is also an adverse event and whether a reporting clock has started under your pathway.
• Pull the batch record and retain sample; decide whether 21 CFR 211.192 requires an investigation.
• Document the disposition and rationale, including why no investigation was needed, if that is the call.
• Open a CAPA where a systemic cause is found, and review the log periodically for trends across lots.

Frequently asked questions

Is a complaint that comes in by phone or social media still a regulated complaint?

Yes. 21 CFR 211.198 covers any written or oral communication alleging a deficiency in a drug product, regardless of channel. A phone call, a direct message, and a chat-widget note are all complaints and must be handled under your written procedure.

What is the difference between a product complaint and an adverse event?

A product complaint alleges a deficiency in the product (appearance, packaging, potency, sterility). An adverse event alleges harm to a person. A single report can be both. Adverse events may carry mandatory reporting deadlines depending on your regulatory pathway; product complaints must be investigated and documented under CGMP.

How fast do I have to report a serious adverse event?

If you hold an approved application, serious and unexpected adverse events are subject to 15-day Alert reporting under 21 CFR 314.80. Other pathways, including 503B outsourcing facilities, carry their own reporting expectations. Because the clock can start the moment you become aware, the safe posture is to escalate any alleged harm to a qualified reviewer immediately.

Do I really need a written SOP if I only get a complaint every few months?

Yes. The requirement to have written complaint procedures does not scale with volume. A company that gets two complaints a year and cannot show a procedure is more exposed, not less, because the gap is obvious the moment an investigator asks.

Current Peptide Compliance builds complaint-handling systems for peptide developers and distributors: written procedures, intake and triage tools, adverse-event reportability logic, and complaint-file audits. Book a 30-minute complaint-handling review to see where your first 72 hours stand.

This article is for general informational purposes and is not legal advice. Current Peptide Compliance provides regulatory and quality consulting; consult qualified counsel for legal questions.