Lot matching: confirm the lot number on the certificate matches the lot number on the vial. A result from a different lot is not evidence about your vial.
Documenting a supplier's response to a discrepancy posts 31–50
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.
Thank you for the correction. I have edited my earlier post with a note rather than silently, so the thread still makes sense to read. The error was mine and it was the kind that comes from remembering a figure instead of looking it up.
Temporal patterns: if results from a supplier were good two years ago but have deteriorated recently, that is information. If they have been consistent over years, that is also information.
On post #33 — agreed on the reasoning, with one qualification.
Structured report format: compound, lot, independent testing service, method as reported, result, and the certificate figure for the same lot. One lot is one lot. It becomes a pattern at three or four, and it becomes a disputed record when asked and not explained.
Collapsed as off-topic by two members at trust level 3 or above
post #37 answers the question as asked. The question underneath it is different.
Blind submission is worth the effort: have someone else relabel the sample so neither you nor the laboratory knows which supplier it came from until the result is back. Blind results change minds; self-selected results do not.
I read post #37 twice before replying, because I had assumed the opposite.
Testing service selection: Janoshik gives purity with chromatogram. Medutest gives combined purity and identity. PeptideMeter gives verification records as well as results. VendorInvestigate reviews documentation. They answer different questions.
This follows post #37 rather than contradicting it.
What "verified" means on our pages: specific lots were independently measured on stated dates by named services and results were consistent with the supplier's documentation. It is not a recommendation and does not extend to untested lots.
Coming back to post #40, because the follow-up matters more than the original answer.
Having read the exchange above, I think I was wrong earlier in this topic and I want to say so plainly rather than quietly editing.
The correction was fair and I had been repeating something I had not checked carefully enough.
post #42 answers the question as asked. The question underneath it is different.
What "verified" means on our pages: specific lots were independently measured on stated dates by named services and results were consistent with the supplier's documentation. It is not a recommendation and does not extend to untested lots.
Date the report: when the analysis was done matters. Material can degrade in storage. A report from two years ago is still useful but is not evidence about the current state of the same supplier's stock.
Collapsed as off-topic by two members at trust level 3 or above
This follows post #42 rather than contradicting it.
Dosing and purity: a vial that is 99% pure might contain 80% of its label claim if the other mass is water, counter-ion, and excipient. Purity and content are different. Both matter for different reasons.
I disagree with the reply above, and I think the disagreement is substantive rather than terminological.
The distinction being drawn does not survive when you look at the published data for this specific question. I would be glad to be shown wrong on this, because the version I am arguing against is more convenient.
Pattern across lots: a single result is a data point. Three or four results from the same supplier showing a consistent pattern becomes a record worth discussing. Two results that disagree might just be measurement variation.
Blind submission is worth the effort: have someone else relabel the sample so neither you nor the laboratory knows which supplier it came from until the result is back. Blind results change minds; self-selected results do not.
Structured report format: compound, lot, independent testing service, method as reported, result, and the certificate figure for the same lot. One lot is one lot. It becomes a pattern at three or four, and it becomes a disputed record when asked and not explained.
This topic was referenced in
- One lot is one lot: when a report becomes a patternSourcing › Vendor reports · 2 replies
Suggested topics
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Revisiting: Filing a first vendor report: a worked example
On the subject in the title: Revisiting: Filing a first vendor report: a worked example Working notes rather than a conclusion. Structured report rather than an opinion, following the format the maintainers…
|
2 | 60k | 11mo | |
|
Coming back to: Why our vendor pages link the storefront and mark it sponsored
Why our vendor pages link the storefront and mark it sponsored I have a specific reason for asking rather than idle curiosity, and the context is below. Structured report rather than an opinion, following the…
|
2 | 22k | 8h | |
|
The report format the maintainers ask for, and why each field is there — what changed since
The report format the maintainers ask for, and why each field is there — what changed since Writing it up because I had to work it out twice and would rather nobody else did. Structured report rather than an…
|
+29 | 35 | 6.6k | 13mo |
|
Reporting a good result: why nobody bothers and why they should
Reporting a good result: why nobody bothers and why they should — setting out what I have, and where I think it stops being reliable. Structured report rather than an opinion, following the format the…
|
2 | 3.5k | 17h | |
|
Reporting a good result: why nobody bothers and why they should — one year on
Posting this under the heading it deserves: Reporting a good result: why nobody bothers and why they should — one year on Everything below is what sits behind that. Structured report rather than an opinion,…
|
+19 | 27 | 4.7k | 18mo |
Related topics — sharing the tags third-party testing, documentation quality, batch & lot numbers
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
A payment that went through twice: how it was resolved
A payment that went through twice: how it was resolved Writing it up because I had to work it out twice and would rather nobody else did. I would like to talk about documentation quality as a signal,…
|
+20 | 24 | 55k | 3mo |
|
About the Vendor reports category
Structured reports on named suppliers. Batch, date, method and document, or it stays in the unverified column. This post is a community wiki: any member at trust level 3 or above can edit it, and every edit…
|
4 | 65k | 18mo | |
|
Revisiting: Aggregate verification data across the directory, with caveats
Revisiting: Aggregate verification data across the directory, with caveats — setting out what I have, and where I think it stops being reliable. I would like to talk about documentation quality as a signal,…
|
+22 | 26 | 23k | 17mo |
|
Reporting a good result: why nobody bothers and why they should
Reporting a good result: why nobody bothers and why they should — setting out what I have, and where I think it stops being reliable. Structured report rather than an opinion, following the format the…
|
2 | 3.5k | 17h | |
|
A supplier who responds to a discrepancy with silence
On the subject in the title: A supplier who responds to a discrepancy with silence Working notes rather than a conclusion. Structured report rather than an opinion, following the format the maintainers asked…
|
2 | 6.1k | 16mo |