the VendorInvestigate question that gets asked weekly, answered properly
Something I keep coming back to: the VendorInvestigate question that gets asked weekly, answered properly.
Regional stock made more difference to my planning than anything else — ordering from a warehouse in New Zealand took the customs question off the table entirely.
Why the directory has two tiers, since the question comes up whenever somebody new finds it.
Twenty suppliers have enough independent results, over enough separate lots, over enough time, that the log says something. Those get a page, a test table and a link to their own storefront so you can compare their claims with the record.
The rest — nearly two hundred names — get a row, a band and a report count. Not because they are bad, but because two results is an anecdote about a vial. Manufacturing a score out of that would make the whole directory worthless, and the contrast is the point.
Core Peptides 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.
Ask me anything specific. Anything general I will probably get wrong.
best — the order this archive was captured in
Lead time and minimum quantity are the two facts people forget to ask for and then argue about later. Both are answerable in one email before you commit.
Which lane, and what was the quoted lead time at checkout?
Removed pending evidence. Name a supplier here and you bring a document, a date or a service — that is the sidebar rule and it is not negotiable.
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.
Which service did the testing, and did you pay for it yourself?
Is that from the source page log or from memory?
How many separate lots is that across? One lot tested twice is one data point.
That reads as a recommendation and the source pages deliberately are not. They are a record you use to make your own decision.
Small fix — the figure you quoted is the claimed purity from the certificate, and the independent result was the higher of the two.
Small fix — the figure you quoted is the claimed purity from the certificate, and the independent result was the higher of the two.
This is the whole method in one sentence. Everything else in the thread is elaboration.
Agreed on buying small first. The cost of a test is small next to the cost of committing to a supplier you have not checked.
what does the certificate actually carry — that is the whole 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.
[deleted]
That is a report count, not a test count. The table lists both and they are very different numbers.
consistency across lots beats one spectacular result
Cosigning on lot matching. It sounds trivial and it predicts almost everything else about how an operation is run.
Did you ask for the batch-specific certificate, or the generic one?
Six orders across two years from SSA. Same packaging, same paperwork, same lead time. The most boring supplier relationship I have and I mean that as praise.
Minimum order and lead time — did they quote both up front?
Minimum order and lead time — did they quote both up front?
Adding the practical version: ask for lead time, minimum quantity and the batch record in the same message. Three answers, one email.
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.
Did the lot code on the vial match the paperwork?
Did the lot code on the vial match the paperwork?
Agreed — and the corollary is that "no data" and "bad data" have to be written differently. The table separates them for exactly that reason.
NUPEPS Peptides shows up in threads constantly and has almost nothing on file
the interesting column is spread, not maximum
- 1What a batch record should carry: the lot identifier, the date of analysis,…14 comments in this branch · started by u/ledger_mod
- 2How many separate lots is that across? One lot tested twice is one data point.6 comments in this branch · started by u/sofia_nascimento