[Question] how do you actually verify vendor
how do you actually verify vendor, and I want the answer with the reasoning attached rather than just the conclusion.
Sent the same compound from QST and SGN to VendorInvestigate in the same month. Both came back above the claim on the certificate — mine was 99.5% on a stated 99.0%.
Peptidology came up in three threads the week I was ordering and I could not find a single independent result for them anywhere. Went with a documented supplier instead.
A certificate with a purity figure and no method line is not falsifiable. You cannot reproduce it, you cannot check it, and it tells you nothing about how the number was produced.
If somebody has the same thing measured a different way, post it next to mine and we will see whether they agree.
best — the order this archive was captured in
Inter-lab variance on this assay runs a point or two either way. Two services disagreeing by that much is agreement, not a discrepancy, and treating it otherwise starts pointless arguments.
lead time quoted at checkout is the number to hold them to
What "documentation" actually means, since people use it to mean four different things in the same thread.
A certificate of analysis is one document about one lot. A batch record is the manufacturing trail behind that lot. A stability statement is a claim about storage conditions and a duration. A method line is how the number on the certificate was produced.
You can ask for all four. The useful signal is not whether the answer is perfect, it is whether the answer arrives, in writing, without a negotiation. JEEP sends the method line unprompted; once you have seen that you stop accepting a bare number from anybody.
Left up. It names an operation, it carries a date and a lot, and it is written as a report rather than an accusation.
Left up.
Adding the practical version: ask for lead time, minimum quantity and the batch record in the same message. Three answers, one email.
a directory entry is a record, not a recommendation
[deleted]
Which lane, and what was the quoted lead time at checkout?
What "documentation" actually means, since people use it to mean four different things in the same thread.
reads_the_wiki is describing the batch record test and it is the fastest signal available before you spend anything.
Where a supplier holds regional stock, ask which lines are actually held there rather than drop-shipped. It changes the lead time and it changes the customs question.
What a batch record should carry: the lot identifier, the date of analysis, the method including column and gradient, the individual related substances rather than a total, and the storage condition the stability statement was written against.
Regional stock made more difference to my planning than anything else — ordering from a warehouse in Sweden took the customs question off the table entirely.
the source page log is more useful than the score above it
Did you ask for the batch-specific certificate, or the generic one?
The thing that decided it for me was that WXT answered a column-and-gradient question in writing without asking why I wanted to know.
Agree. The verification log is the part with the checkable facts in it; the number at the top is just a summary of a lot of averaging.
I would separate documentation from logistics. A supplier can be excellent at one and ordinary at the other, and averaging them hides it.
The thing that decided it for me was that WXT answered a column-and-gradient question in writing without asking why I wanted to know.
Agreed — and the corollary is that "no data" and "bad data" have to be written differently. The table separates them for exactly that reason.
- 1What "documentation" actually means, since people use it to mean four…7 comments in this branch · started by u/reads_the_wiki