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…
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