What Do Manufacturers Need From a Distributor Complaint?

This method covers complaints about industrial chemical products, such as lubricants, coatings, adhesives and process fluids, that a distributor passes to the manufacturer. Medical device, pharmaceutical and food contact complaints follow their own regulated record rules, which add fields to this list.

What do you need before you escalate a complaint to the manufacturer?

Before you escalate a complaint to the manufacturer, you need four groups of facts in hand, each with a source and a date: the symptom, the process conditions and recent changes, the product and lot, and the actions already taken. Gather them before you write the escalation.

Collect these items:

• The customer's complaint as received, with the date it arrived and the name of the person who reported it.

• Your own visit notes, measurements and photos, each with the date taken.

• The order, the delivery note and the lot number for every container involved.

• The revisions of the technical data sheet (TDS), safety data sheet (SDS) and certificate of analysis (CoA) the customer holds.

• The tests and corrective steps already tried, with their results.

• Samples: what you hold, how much, in what container, and how it was stored.

Regulated sectors write these items into rules, and their lists are a useful model for industrial chemicals. ICH Q7, the good manufacturing practice guide for active pharmaceutical ingredients, lists complaint record contents that include the "Date complaint is received" and the "Action initially taken (including dates and identity of person taking the action)" (ICH Q7, 2000, section 15.11). A complaint that reaches the manufacturer with these items lets its technical team open the batch record on the day it arrives.

Step by step: writing a complaint escalation the manufacturer can act on

Writing a complaint escalation the manufacturer can act on takes five steps, each filling one part of the request.

1. State the symptom. Describe what is wrong in measurable terms: what, where, how much and since when. "Blistering on 30% of panels from line 2 since 2026-10-14" (illustrative) tells the manufacturer more than "coating failure".

2. State the process conditions and recent changes. Give each application condition the TDS sets a limit for, the value measured on site, and every change at the site before the symptom started.

3. Identify the product and lot. Give the product name as printed on the label and the SDS, the lot or batch number from each container, the delivery note and the quantity affected.

4. List the actions taken. Give each test and corrective step with its date, its result and who did it, including steps that changed nothing.

5. Source and date each fact. Mark every fact as observed, reported or unconfirmed, with who supplied it and when.

Close the request with the question you want answered and the samples you can send. Customers that run 8D problem solving expect the same opening facts from their own suppliers: one equipment maker's procedure says it will "communicate the part numbers, quantity affected, and the magnitude of the problem" when it opens a case (Oshkosh OSK-P3000, 2023). A distributor complaint that answers those three before the manufacturer asks saves a round of email.

How do you identify the product and lot in a complaint escalation?

You identify the product and lot in a complaint escalation by copying the product name, the lot or batch number and the container size from the labels of the containers actually used, then matching them to the delivery note and the CoA. Product and lot let the manufacturer pull the batch record and the retained sample, so a wrong lot sends the investigation to the wrong batch.

Record for each product in the complaint:

• Product name and grade exactly as on the label and SDS, not a nickname or a site code.

• Lot or batch number from each container, photographed. A customer may run two lots on one line.

• Container size, and how many containers of that lot are affected, used up and still unopened.

• Delivery note or order number, and the delivery date.

• Manufacturing or expiry date when the label shows one.

Unopened containers of the same lot matter most: they show the product as it was before the site touched it. Say how many remain and keep them on hold.

ICH Q7 records the "Complaint nature (including name and batch number of the API)" (ICH Q7, 2000, section 15.11). US device makers record "Any unique device identifier (UDI) or universal product code (UPC), and any other device identification(s)" for reportable and investigated complaints (21 CFR 820.35(a), eCFR 2026).

Which process conditions and recent changes should the complaint include?

The complaint should include every process condition the technical data sheet sets a limit for, with the value measured on site, and every change at the site before the symptom started. The manufacturer compares the two with its own data: a condition outside the TDS range points to the application, while a symptom with every condition inside the range points back to the product.

Conditions to give, as they apply to the product:

• Temperature of the product, the substrate or the system, and the ambient conditions, with the instrument used.

• Concentration, dilution or mix ratio, and how it was measured.

• Surface preparation, film thickness, cure or dwell time.

• Equipment, materials and other chemicals in contact with the product.

• Storage conditions on site and how long the product was stored.

Recent changes are the field most often missing from a complaint, and often the one that explains the symptom. Ask specifically about a new lot, a new supplier of another material, new equipment, a new operator or shift pattern, a maintenance event, a change of cleaning chemical and a change in weather. Write "no change reported" when the customer confirms none, so the manufacturer knows the question was asked. Date each change, so it can be lined up against the start of the symptom.

How do you separate what you observed from what the customer reported in a complaint?

You separate what you observed from what the customer reported by labeling every fact in the complaint as observed, reported or unconfirmed, and adding who supplied it and on what date. The label tells the manufacturer how much weight each fact can carry.

Use three labels:

• Observed: you or a colleague saw or measured it on site, with the date and the instrument. Example: "Bath concentration 3.1% by refractometer, measured by the distributor on 2026-10-16" (illustrative).

• Reported: the customer or a third party told you, and you have not checked it. Example: "Customer reports the problem started after the October delivery."

• Unconfirmed: nobody has a source for it, or the sources disagree. Keep it with its label instead of dropping it, so the manufacturer does not mistake a guess for a fact.

Two habits keep the labels honest. Quote the customer's own words for reported facts, rather than translating them into technical terms the customer did not use. Change a label only with a new source: a reported fact becomes observed when someone measures it, and the entry gets the new date.

Lubinpla builds this kind of technical support request from your own records and documents: every fact carries its source, its date and an observed, reported or unconfirmed label, and the request comes back as one cited PDF for you to approve before it goes to the manufacturer.

How do you check the complaint escalation before sending it?

You check the complaint escalation before sending it against six checks: symptom, conditions and changes, product and lot, actions taken, sources and dates, and samples. A request that passes all six lets the manufacturer start without asking back; each failed check costs at least one more exchange.

The table decides whether the complaint escalation is ready to send.

The product and lot row is the one that most often stops a manufacturer: without a lot number per container, it cannot pull the batch record or the retained sample. Fix that row first when time is short.

Then read the request once more as the manufacturer's technical team would, with no knowledge of the customer's site, and add whatever that reader would have to ask for.

Common mistakes in distributor complaint escalations

The most common mistakes in distributor complaint escalations are a conclusion in place of the symptom, a missing lot, a hidden earlier action and facts with no source. Each forces the manufacturer to ask back, and some send the investigation in the wrong direction.

• Writing a conclusion instead of the symptom. "Bad batch" tells the manufacturer what you think, not what you saw.

• Sending the complaint without the lot. A product name alone cannot be traced to a batch record.

• Leaving out what failed. A corrective step that changed nothing is evidence; leaving it out invites the manufacturer to suggest it again.

• Mixing observed and reported facts. A customer's estimate written down as a measurement can mislead the whole investigation.

• Discarding samples. Once the field sample is gone, the manufacturer can test only its retained sample, which shows the batch as made, not as used.

• Forgetting the hazard question. In the EU, "Distributors shall pass on that information to the next actor or distributor up the supply chain" when it is new information on hazardous properties (Regulation 1907/2006, Article 34). Flag it at the top of the request when it applies.

• Not recording the answer. ICH Q7 expects distributors of active pharmaceutical ingredients to keep "any response received from the original API or intermediate manufacturer (including date and information provided)" (ICH Q7, 2000, section 17.72), a record worth keeping in any sector.