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.
Revisiting: The report format the maintainers ask for, and why each field is there posts 91–109
This is a continuation of a long topic, addressed by post number rather than by page. Start at post 1.
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.
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.
Two things before anyone answers the substance.
First, the context in the first post is clear and specific. Second, the question is framed so that an answer can actually address it. Both are the norm here and both matter more than they sound.
Worth separating two things that post #93 runs together.
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.
Coming back to post #97, because the follow-up matters more than the original answer.
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.
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.
post #101 answers the question as asked. The question underneath it is different.
Multiple services on one lot: agreement across two independent laboratories is stronger than a high number from one. Our vendor pages deliberately mix services for that reason.
Practical note that does not fit anywhere else. Whatever you conclude from this topic, write down what you did and when. The single most useful thing in your own records is not any individual result; it is that they are dated and consecutive.
Collapsed as off-topic by two members at trust level 3 or above
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.
Worth separating two things that post #101 runs together.
Disputed records: when a result disagreed and was not explained, the record says disputed and stays that way. We do not remove inconvenient history; we document it.
post #105 is right about the mechanism and I think understates the practical bit.
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.
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.
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.
Collapsed as off-topic by two members at trust level 3 or above
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.
This topic was referenced in
- How the vendor documentation pages are maintained, and by whom — what changed sinceSourcing › Vendor reports · 104 replies
- [2026 update] Comparing documentation quality across the directory, tabulatedSourcing › Vendor reports · 3 replies
Suggested topics
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Filing a first vendor report: a worked example
Filing a first vendor report: a worked example Writing it up because I had to work it out twice and would rather nobody else did. A logistics question, since the answers here are usually better than anywhere…
|
+1 | 5 | 12k | 15mo |
|
One lot is one lot: when a report becomes a pattern
Posting this under the heading it deserves: One lot is one lot: when a report becomes a pattern Everything below is what sits behind that. Structured report rather than an opinion, following the format the…
|
2 | 19k | 14mo | |
|
Second pass at: What "verified" means on our vendor pages, stated narrowly
Second pass at: What "verified" means on our vendor pages, stated narrowly — setting out what I have, and where I think it stops being reliable. A logistics question, since the answers here are usually better…
|
+94 | 102 | 20k | 3mo |
|
Documenting a supplier's response to a discrepancy — does this still hold?
Documenting a supplier's response to a discrepancy — does this still hold? I have a specific reason for asking rather than idle curiosity, and the context is below. Structured report rather than an opinion,…
|
+47 | 52 | 58k | 16mo |
|
What "verified" means on our vendor pages, stated narrowly
What "verified" means on our vendor pages, stated narrowly — that is the question, and I have not found it answered plainly anywhere I have looked. I would like to talk about documentation quality as a…
|
+27 | 31 | 27k | 7mo |
Related topics — sharing the tags batch & lot numbers, Janoshik Analytical, documentation quality
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
|
Revisiting: Patterns that reliably precede a problem, documented
Posting this under the heading it deserves: Revisiting: Patterns that reliably precede a problem, documented Everything below is what sits behind that. A logistics question, since the answers here are usually…
|
+16 | 20 | 36k | 2mo |
|
A comparison of home results against a laboratory result on the same vial — does this still hold?
A comparison of home results against a laboratory result on the same vial — does this still hold? I have a specific reason for asking rather than idle curiosity, and the context is below. Working through the…
|
+2 | 6 | 15k | 11h |
|
Follow-up: Reporting a discrepancy without making an allegation
Reporting a discrepancy without making an allegation Writing it up because I had to work it out twice and would rather nobody else did. Structured report rather than an opinion, following the format the…
|
2 | 24k | 19mo | |
|
Coming back to: When a red flag was a misunderstanding, and the retraction
When a red flag was a misunderstanding, and the retraction I have a specific reason for asking rather than idle curiosity, and the context is below. A logistics question, since the answers here are usually…
|
+6 | 10 | 257 | 21h |
|
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 |