A certificate whose chromatogram axes do not match its stated method — one year on posts 31–60
This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1 · go to the accepted answer.
Certificate whose chromatogram axes is well covered in the tag pages, and the older discussions are better than the recent ones because they were argued out properly. Worth twenty minutes before adding to this one.
Patterns that reliably precede a problem: underdosing (less active material than stated, documented by independent testing), mislabelling (wrong compound, wrong strength, or wrong batch on the label), and failure to provide documentation when asked.
It is the kind of thing that is obvious once and never again.
A document with no method identification is not evidence of anything wrong. It is evidence that the document cannot be checked, which is a different and weaker statement.
Where I would look next, rather than where I would stop.
Post #32 is the version of this I will quote in future. One addition.
Reporting something here requires the batch, the date, the method and the document, which is exactly what makes the reports worth reading two years later.
Where I part company with post #34, and it is a narrow parting.
Keep the two claims separate. "The result on this lot did not match the certificate" is a report that can be checked. "This supplier is dishonest" is an allegation about intent and nothing in a chromatogram supports it.
The reason certificate whose chromatogram axes keeps being re-asked is that the answer is conditional and people quote it without the condition. It is not that the answer is unknown.
An unexplained discrepancy that the supplier declined to address is a legitimate thing to record, stated as exactly that and nothing more.
I would rather say I do not know than round it up to an answer.
Worth separating two things that post #38 runs together.
Documentation quality as a signal: a supplier that reports method identifiers, distinguishes specification from result, and states the counter-ion form is telling you something about systems behind the document. A certificate that is a number and a signature tells you less.
Someone will know this better than I do and I hope they say so.
I have no financial interest in anything named in this thread and I want to say so before I comment on certificate whose chromatogram axes, because it is the sort of subject where it matters.
Prices well below the rest of the market are a fact rather than a finding. They are worth noting and they do not establish anything on their own.
A weak preference rather than a position.
This follows post #44 rather than contradicting it.
Genuine question rather than a rhetorical one: has anyone here actually observed certificate whose chromatogram axes, as opposed to read about it? The thread is long and I cannot tell.
Practical answer on certificate whose chromatogram axes, since the theoretical one is upthread: do the simplest check first, write down the result, and only then decide whether the complicated explanation is needed. It usually is not.
Evasion when asked: if a supplier does not clarify when asked specifically for method details, counter-ion form, or batch origin, that itself is a red flag worth documenting.
That matches what I was told, which is not the same as knowing it.
On post #47 — agreed on the reasoning, with one qualification.
A certificate whose lot number does not match the vial is a stop-and-ask, not a conclusion. Most such things are warehouse paperwork.
Evasion when asked: if a supplier does not clarify when asked specifically for method details, counter-ion form, or batch origin, that itself is a red flag worth documenting.
Fair, and the limits you put on it are the part I will remember.
Collapsed as off-topic by two members at trust level 3 or above
Where somebody posts a concern, ask what would resolve it before arguing about it. Half of these threads end with a document nobody had asked for.
The claim is narrower than it sounds, and deliberately so.
Confirming post #50 from a second method, which matters more than confirming it from a second person.
Where the same certificate image appears with different lot numbers, that is a documentation finding worth reporting with the images attached.
I had written a reply contradicting post #53 and deleted it. Here is what survived.
Documentation quality as a signal: a supplier that reports method identifiers, distinguishes specification from result, and states the counter-ion form is telling you something about systems behind the document. A certificate that is a number and a signature tells you less.
Correct me on the arithmetic if it is wrong; I would rather know.
The strongest single signal available cheaply is what happens when you ask a technical question. A quantitative answer inside a working day is difficult to fake at scale.
The guidelines draw that line for a practical reason as much as a fair one: reports accumulate into something useful and allegations do not.
Post #54 is right about the mechanism and I think understates the practical bit.
Keep the two claims separate. "The result on this lot did not match the certificate" is a report that can be checked. "This supplier is dishonest" is an allegation about intent and nothing in a chromatogram supports it.
Stating my assumptions rather than smuggling them in.
The arithmetic in post #58 is right; the assumption feeding it is the part to check.
A certificate that reports a specification in the result column is a documentation defect, and it is a defect people should be able to recognise without it being called anything worse.
Answering the question post #56 raises rather than the one it answers.
Reporting something here requires the batch, the date, the method and the document, which is exactly what makes the reports worth reading two years later.
One case, stated as one case.