Product quality complaint reporting and adverse event reporting meet in the same inbox and then have to leave on different paths. A pharmacist calls about a cracked vial. A site writes that the infusion pump alarmed and the subject later had chills. Quality wants the lot. Drug safety wants to know whether a person was harmed. If both teams assume the other one opened the case, nobody owns Day 0.
What a product quality complaint is
A product quality complaint, often shortened to PQC, is a report that something is wrong with the product as a product. Typical complaints:
- Appearance: discoloration, particles, cloudiness, a leaking container.
- Packaging or labeling: wrong carton, missing warning, illegible lot.
- Identity or strength: a tablet that does not match the description, a suspected mix-up.
- Device or delivery: a pen or pump that did not fire, a kinked line, a sterile barrier that arrived open.
The quality system records the complaint, holds the lot if needed, checks batch records, and looks for a trend. That work is complaint handling. It is not pharmacovigilance case processing, even when the same person is on call for both because the company has twelve employees.
When the complaint is also an adverse event
Add a patient outcome and the quality complaint can also be an adverse event. The test is the usual one. Is there an identifiable patient, an identifiable reporter, a suspect product, and an untoward occurrence? A cracked vial found in the warehouse has no patient. A cracked vial that was administered, followed by a fever, has an event until a clinician shows the fever had another cause.
Both files should point at each other. The complaint record holds the lot, the returned sample, and the batch. The safety case holds seriousness, coding, causality, and expectedness. Copying the safety narrative into the complaint, or the batch record into the safety case, without saying which system owns which decision, is how the two files drift.
Seriousness still uses the ICH criteria. A device malfunction that could have killed someone may be medically important even if this patient recovered in an hour. That call is a drug-safety call. The decision to quarantine a lot is a quality call. They can be true on the same afternoon.
What intake has to capture so both teams can start
The intake form for a mixed report needs the event verbatim, the receipt date, and the product identifiers quality will ask for: lot or batch, expiry if stated, and a description of the defect in the reporter's words. Photos belong with the quality file. The safety case needs to say that a defect was alleged, not to become the photo archive.
Do not wait for the batch investigation to decide whether the event is an SAE. The safety clock, if there is one, runs on the event. The investigation explains it later. Follow-up can correct causality. It cannot invent a receipt date you failed to write down. The inbox note is the version of this failure that happens in email.
Field alerts and other quality notices are a third path
Some marketed-product quality problems trigger a Field Alert Report. Under 21 CFR 314.81, NDA and ANDA holders notify FDA about certain issues with distributed drug product, including labeling mix-ups and significant chemical, physical, or other change, on a clock measured in working days. That notice is not an ICSR, and it is not the complaint form. Biologics and devices have their own defect and malfunction duties. If you are the holder of the application, your quality lead should own the decision. A case-intake tool should not be where that decision is improvised.
What AE Connect will and will not do with a PQC
If the text in front of you describes an adverse event, the AE Connect workspace can draft seriousness, a suggested MedDRA term, causality, expectedness, and a timeline for a person to review. Paste the narrative. Mention the defect in the text so the draft can see it. The workspace still does not know your batch record, and it will not trend complaints, issue a recall, or file a Field Alert Report.
A complaint with no patient is out of scope. Put it in the quality system. Do not create a fake adverse event so the safety tool has something to code.
PQC reports also do not become aggregate safety reports by accumulation. A cluster of quality defects may belong in a signal discussion or a periodic safety report if patients were involved. The complaint log itself is not a PSUR.
Open a case in the workspace
Paste or upload a source at the AE Connect workspace. A company email starts a 14-day sandbox trial with unlimited cases. You accept or override every field. AE Connect can feed any safety database, including Oracle Argus, ArisGlobal LifeSphere, and Veeva Vault Safety, or it can be the safety database for the full ICSR and the E2B(R3) file.
FAQ
What is a product quality complaint?
A product quality complaint is a report that the product itself is defective or not what it should be: appearance, packaging, labeling, particles, a device that did not operate, a wrong strength. It is a quality-system record. It is not, by itself, an adverse event report.
When is a PQC also an adverse event?
When a person had an untoward medical occurrence and the defective product is a suspect. Fever after a cloudy vial, an infection after a suspected non-sterile lot, or injury from a device malfunction can be both a complaint and an AE. Quality and drug safety both need the story. One inbox does not make them one process.
Does AE Connect run product quality complaint reporting?
No. AE Connect is not a QMS. It does not manage deviations, batch records, returns, or complaint trending. If the narrative includes an adverse event, you can paste that text into the workspace and review a draft assessment. The quality file still lives in the quality system.
Is a product quality complaint the same as a Field Alert Report?
No. A Field Alert Report is a specific notice certain NDA and ANDA holders must send FDA about distributed product with a quality problem, on a short clock under 21 CFR 314.81. It is not an ICSR and it is not something AE Connect files.