When Should a Distributor Escalate an Issue to the Manufacturer?

This answer covers technical issues with industrial chemical products bought through a distributor, such as lubricants, coatings, adhesives and process fluids. Where a distribution agreement, a customer's supplier quality manual or a regulator such as medical device or pharmaceutical rules sets its own escalation trigger, that trigger comes first. ISO 10002:2018 (Edition 3, confirmed 2023) gives guidelines for the complaints-handling process within an organization (ISO, 2023).

Which conditions decide whether a distributor escalates a technical issue?

Four conditions decide whether a distributor escalates a technical issue to the manufacturer: whether your own tests and data can close it, how long the customer can wait, whether the evidence points at the product rather than the application, and what your earlier actions showed. Fix the four answers before anyone argues about who owns the problem, because each one answers a different question. Your tests answer whether you can close it. Customer wait time answers how fast it must move. Product suspicion answers whether only the manufacturer can finish it, since the manufacturer holds the batch records, retained samples and formulation knowledge. Earlier actions answer whether more of the same work will help.

Manufacturers write the same order into their own policies. A door manufacturer's claims policy states: "The distributor is responsible for the initial investigation of any claim, including researching the order details, determining possible root cause, visiting the jobsite (if required), and offering possible solutions" (VT Industries, 2025). The same policy routes the claim to the manufacturer's territory sales manager when it is "assessed as a VT manufacturing issue and further inspection required" (VT Industries, 2025). A software reseller agreement sets a similar gate: the reseller escalates only after "performing reasonable diagnostic analysis" (Stalwart Labs, 2026).

Write the four answers down at the start of each case, with the date. A decision made from written answers can be checked later; a decision made from the most insistent phone call cannot.

Can the distributor close the technical issue with its own tests and data?

A distributor can close a technical issue with its own tests and data when the cause is confirmed against the technical data sheet (TDS), the certificate of analysis (CoA) and field measurements, without information only the manufacturer holds. Typical in-house closures are application causes: a wrong dilution, a substrate outside the TDS range, a cure temperature below the TDS minimum, contamination introduced on site, or product used past its shelf life.

Three checks tell you whether your own data closes the technical issue:

• The cause is confirmed by a measurement, not inferred from the symptom. A refractometer reading, a film thickness or a site temperature log confirms a cause; "probably the dilution" does not.

• The fix was tried on the customer's line and the symptom stopped. Closure means the corrective step worked, not that it should work.

• The CoA values for the lot sit inside the specification, and the complaint does not involve a property the CoA leaves out.

When any check fails, the issue is not closed in house, whatever the time pressure. Past cases help you start: if the same symptom on the same product was closed before by an application fix, test that cause first, then confirm it again on this case instead of copying the old conclusion. ICH Q7 leaves the owner of the investigation open, saying the investigation into the cause of a complaint "should be conducted and documented by the appropriate party" (ICH Q7, 2000, section 17.71).

How long can the customer wait before the issue goes to the manufacturer?

The customer can wait while the technical issue causes no loss that cannot be undone; once production stops, a safety question opens or affected product keeps shipping, the issue goes to the manufacturer the same day as an urgent escalation. The customer's situation sets the wait time, not your investigation schedule.

Ask three questions at first contact and write the answers down:

• Is the customer's line stopped, slowed or running with workarounds?

• Is there any safety, health or environmental exposure, such as a leak, fumes, skin contact or a product behaving unlike its safety data sheet (SDS)? If yes, apply the first-aid, accidental-release and exposure measures in SDS sections 4, 6 and 8 first, and call the emergency telephone number in SDS section 1 at once, before the written escalation (Regulation 1907/2006, Annex II).

• Is affected product still in use, in stock or in transit to this or other customers?

Customers that buy under supplier quality procedures often set the clock for you. One equipment maker's 8D procedure requires that "Within 24 hours of notification, the supplier must implement containment" and that root cause analysis is "required within 15 calendar days of the 8D initiation" (Oshkosh OSK-P3000, 2023). Another sets the containment plan due within 24 hours of receiving the supplier corrective action request (Graco supplier page, viewed 2026). Where such a clock applies and your own tests will not finish inside it, escalate at the start, not near the deadline. A manufacturer told at the first contact can check its retained samples and batch records while you test on site; one told late starts from the beginning with less time.

What signs point to the manufacturer's product rather than the application?

Signs that point to the manufacturer's product rather than the application are signs that follow the lot, not the site: the same symptom at several customers on one lot, a fault in unopened containers, a retest outside the specification, and a change the customer did not make. When these signs appear, only the manufacturer can finish the investigation, because it holds the batch record, the retained sample and the formulation.

• Same lot, different sites. Two customers with different processes reporting the same symptom on one lot point to the product.

• Fault in an unopened container. Separation, gelling, an off odor or an off color in a sealed container cannot come from the application.

• Retest outside specification. A property measured outside the CoA range by the method the specification names, on a properly drawn sample.

• Change without a customer change. The symptom started with a new lot, new packaging or a change notice, while the customer's process stayed the same.

• New hazard information. Anything suggesting the product is more hazardous than its SDS describes.

The last sign is a legal duty in the EU, not a judgment call. Under REACH, each actor must communicate "new information on hazardous properties, regardless of the uses concerned" up the supply chain, and "Distributors shall pass on that information to the next actor or distributor up the supply chain" (Regulation 1907/2006, Article 34). The same article covers information that calls into question the risk management measures in an SDS, for identified uses.

What do the distributor's earlier actions tell you about escalating?

The distributor's earlier actions tell you whether more in-house work will help: when repeated corrective steps based on one assumed cause have not stopped the symptom, the assumption is likely wrong, and the case should go to the manufacturer. Read earlier actions as evidence, not as effort already spent.

Look at three things in the case history:

• What was tried and what changed. A corrective step that changed nothing rules out the cause it targeted. Record it as a ruled-out cause, so the manufacturer does not repeat it.

• Whether the symptom moved. A symptom that shifts with the lot, not with your corrective steps, points to the product.

• Whether the symptom returns. An issue that closes and comes back, or appears only now and then, often needs data only the manufacturer has, such as lot-to-lot variation in raw materials.

Earlier actions also decide what the escalation must carry. The software reseller agreement cited above requires that escalations "include a detailed description of the issue, steps taken to diagnose, relevant logs or configuration details, and the End Customer's environment information" (Stalwart Labs, 2026). The chemical equivalent is the symptom, the tests run and their results, the corrective steps tried, and the customer's process conditions. An escalation that states what was already tested lets the manufacturer start where your troubleshooting stopped, instead of at a question you already answered.

Escalation table: distributor handling versus manufacturer support

The escalation table maps the four conditions to one of three decisions: handle in house, escalate routine or escalate urgent. Read it row by row and take the most severe decision any row gives; one urgent row makes the whole case urgent. Urgency applies once the case is escalated; a case the first row closes stays in house unless the product or hazard row also applies.

The table decides whether a technical issue stays with the distributor or goes to the manufacturer, and how fast.

The row that most often changes the decision is the product row: a fault in an unopened container, or on one lot at several sites, goes to the manufacturer at once, even when the customer could wait.

When rows disagree, the most severe row wins, and its reason goes into the escalation itself. Record the date of the decision, who made it and which row triggered it. If the manufacturer later asks why a case came in urgent, or why it came in late, the row answers. Review closed cases against the table at a fixed interval, for example each quarter (illustrative); a row that keeps producing wrong decisions needs a sharper condition.

What to agree with the manufacturer before the first technical escalation

Agree four things with the manufacturer before the first technical escalation: the contact route, what an escalation must contain, response times by severity, and who tells the customer what.

• Contact route. A named technical contact and a backup, plus the channel for urgent cases outside office hours.

• Escalation content. The minimum fields: product and lot, symptom, process conditions, tests and corrective steps with dates, and the samples available. VT Industries, for example, points distributors to an online claim submission form (VT Industries, 2025).

• Response times by severity. Ask what the manufacturer commits to for urgent and routine cases, and write it down.

• Customer communication. Who replies to the customer, and whether the manufacturer may contact the customer directly. ICH Q7 asks 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.

Lubinpla works this decision as a case built from your own TDS, past cases and field measurements: it fixes the four conditions first, judges with cited evidence whether the issue closes in house, and returns one document stating in-house handling or escalation and its urgency for you to approve.