Abstract: Every supplier answers your technical questions. Far fewer answer them in a way that proves someone in the building understands your process. Here is how to tell a real answer from a polished one, using only the replies already sitting in your inbox.
Two replies, one question
You send the same question to two intermediate suppliers: “We see an unknown peak at 0.12% in your last three batches by our method. What is it, and can you control it?”
Supplier A writes back the next morning: “Our product meets all specification requirements. Purity is above 99% and the COA confirms compliance. Please rest assured.”
Supplier B replies two days later, in slightly awkward English but unmistakably from a chemist: “That peak is likely the des-chloro impurity from step three when the reduction runs long. It sits at 0.08–0.15% in our batches and we have not seen it move downstream in customers’ routes. If you need it below 0.05%, we would adjust the quench and recrystallize — about four extra days, but we have done it before.”
Both suppliers “answered”. Only one told you something you could act on. And telling them apart took no audit, no site visit, no questionnaire scored out of a hundred. Just reading the reply carefully.
That is the subject of this article. Your supplier evaluation process — the five-step evaluation and the audit checklist behind it — establishes whether a supplier is qualified. But between qualification and every shipment you buy, you are mostly reading replies. Judging those replies is a separate skill — the one buyers use most and practice least.
Why polished answers are the default
Most suppliers have someone whose job is to make the company sound competent in writing. Large ones answer technical questions from templates. Smaller ones have a salesperson forwarding your email to a lab manager, then rewriting the blunt two lines into something smoother.
Nothing about this is malicious. It is how organizations work. The problem is that the smoothing strips out exactly what you need — the uncertainty, the mechanism, the caveat — and leaves the reassurance. A buyer who judges suppliers on how confident they sound will prefer the better writer to the better manufacturer.
This is also why the reply is such a useful test. It is unscheduled. Nobody has a script for the specific impurity question you happened to ask. What comes back is closer to the real organization than any capability deck.
What a real technical answer contains
Real answers share recognizable features. They are specific about place and cause: which step, which reagent, which parameter. They name uncertainty where it exists. And they usually volunteer something you did not ask for — a downstream consequence, a rough cost, a condition under which the answer would change.
The most reliable marker is a mechanism. “The peak is below our specification limit” is a status report. “The peak comes from the imine intermediate hydrolyzing on storage, so it grows if the material sits warm” is an explanation, and an explanation implies someone has watched it happen. You cannot fake a mechanism without understanding it — which is why the discipline of tracing where impurities go separates suppliers who know their process from those who merely test it.
Second marker: willingness to say no, or not yet. A chemist who has not run your exact condition says “I would need to test that” or “we have not seen it, but here is where I would look.” A sales-written reply almost never admits a gap, because admitting one feels commercially dangerous.
Your question | Sales-shaped answer | Chemist-shaped answer |
What is this unknown peak? | “Product meets specification.” | Names the step, the likely impurity, its historical range |
Can you hold it below 0.05%? | “Yes, we can meet your requirement.” | “Yes — quench plus recrystallization, four extra days, and here is the yield cost” |
Has the route changed recently? | “Our process is stable and unchanged.” | “We changed the solvent recovery vendor in March; the profile did not shift, here are the comparison batches” |
Can you transfer the method? | “We can provide full support.” | “We will send the method with the validation summary; the column is unusual and we will flag the alternative” |
What if it fails at scale? | “We have never had a problem.” | “Scale-up is where the exotherm bites; here is what we watch in the first two batches” |
The follow-up is where the truth lives
One reply rarely settles it. The real diagnostic is the second message — what happens when you ask a follow-up the supplier could not have anticipated.
Ask for the raw material behind a claim. If they say the impurity has always been below 0.05%, ask to see the last ten batches’ numbers. A supplier who knows their process sends a small table within a day. One who does not will send a representative COA and a paragraph about their quality system — and a representative certificate is exactly what the certificate verification checks exist to catch. The distance between those replies tells you more than any questionnaire score.
Ask a question whose answer would be inconvenient: “If we scaled to three tonnes a year, what part of your process would struggle first?” Suppliers who have thought about their own capacity answer immediately, often with a self-critical detail. The others answer with capacity figures and lead times — a non-answer dressed as data.
One habit worth building: keep technical replies in a folder per supplier, and re-read them after the first three batches arrive. You will see which promised specifics actually showed up. That folder becomes the most honest input your supplier scorecard will ever have — what they said, next to what they did.
What the reply is being screened against
Judging answers is not about catching liars. It is about checking whether the supplier’s understanding matches your technical demand. Two suppliers can both be honest and competent, yet only one suited to you.
The reply shows where their attention sits. A supplier fluent on assay and moisture but vague on impurity control is likely running a well-controlled routine operation rather than a development-capable one. If your requirement is a standard grade at a steady specification, that is fine — arguably preferable, since you are not paying for development depth you do not need.
If your route needs a tight chiral specification, the same reply is a warning. Conversely, a supplier whose answer dwells on developing and validating the analytical method to see your peak is engaged with your problem — but may also be telling you the material is new to them, which means their batch history is thin. Read for capability and maturity together.
Questions worth asking before you commit
Most buyers send a long questionnaire and get a long, smooth document back. A shorter set produces sharper replies, because each is hard to answer without knowing the process:
- What is the impurity most likely to fail if our route stresses your material harder than you do?
- Which step in your process has changed in the last two years, and why?
- If we need this specification in eighteen months, what would have to change on your side?
- Who would I speak to if this material caused a problem in our plant — and what is their background?
- What is the least reliable part of supplying us, in your view?
That last question is uncomfortable and unusually revealing. Suppliers who answer with a real constraint — a single reactor train, a difficult raw material vendor, a drying step that varies with humidity — describe an organization that knows itself.
Those who declare nothing is unreliable have either not thought about it or will not say, and both leave you exposed. It is the same information that technology transfer projects stumble over months later, at much higher cost.
When the answer reveals a scale gap
One pattern deserves care, because it is common with capable but smaller suppliers. The technical answers are excellent — mechanism-rich, clearly from someone who could discuss your chemistry for an hour. Yet they keep implying small quantities: bench allotments, trial runs, “we can prepare a few hundred grams.”
That supplier may be technically stronger than the larger one you also considered, and still wrong for a tonne-scale program — not because they misrepresent themselves, but because technical excellence and manufacturing capacity are different capabilities, and the reply reveals only the first.
Where the two diverge is exactly what scale-up work exists to solve, and buyers often discover the gap only when their first commercial order arrives late and off-specification. If the replies are strong but the scale hints are small, ask about occupied reactor volume, batch sizes run, and current utilization. It is an ordinary commercial question — and the quality of the answer is informative in itself.
Six signs the reply is not from a chemist
- Every question receives the same sentence about specifications and certificates.
- Impurity questions are answered with “meets pharmacopeia” when you asked about a specific peak.
- Numerical requests are declined on principle — batch data is “confidential”, though it is the one thing you can share without risk. Legitimate reasons to withhold exist, but they concern how results were generated, not whether the numbers exist.
- Admitting uncertainty never happens, on any topic.
- Follow-ups get faster and vaguer, as if a script is exhausted.
- The reply never mentions your downstream process, only their own product.
- Specification questions come back with a limit quoted but no basis for how it was set — the gap that specification settingis meant to close.
None of these alone disqualifies a supplier. Together, they describe an organization where the person answering you lacks access to the people who run the plant — a risk you will feel on your first deviation, when the conversation needs to reach someone technical quickly. If you want a structured way to examine the whole relationship rather than single replies, the compliance verification workflow is the natural next step, and it pairs well with reading the certificates arriving with each shipment.
Frequently asked questions
Can I judge a supplier’s technical capability without an audit?
Not completely. A site visit verifies equipment, housekeeping, and how people actually work. But replies tell you what an audit cannot: how the organization behaves on ordinary days, without preparation. Use replies to decide who is worth the cost of an audit, and the audit to confirm what they suggested.
What is the single strongest signal in a technical reply?
A mechanism. When a supplier explains why a result occurs and not only what it is, someone has engaged with the process rather than the paperwork. Mechanisms are hard to fake and easy to verify on the next batch.
Should I worry if a supplier’s English is imperfect?
No — often the opposite. Polished English usually means the reply passed through a sales or export team, which is where technical content gets thinned. Rough phrasing with a precise mechanism beats fluent prose with none.
How many suppliers should I question this way?
Two or three is usually enough, because replies differentiate quickly. Send the same questions to all candidates and compare them side by side. This is the same impulse behind writing a precise RFQ: the clearer your question, the more the answer reveals.
The takeaway
You do not need a scoring system to start. Send two or three technically specific questions to each candidate, then read what comes back with one question in mind: does this reply contain something only someone who knows the process could have told me? Suppliers who pass tend to keep passing — through deviations, through scale-up, through the difficult quarters.
We manufacture pharmaceutical intermediates for buyers across India, Bangladesh, and Pakistan, and we are happy to be judged this way. Send us a technically hard question about a current project and see what comes back.