vialroom

#vendor-verification 2026-06-03

Wednesday49 messages13 participantstimes are UTC
Highlights from this day
  • VialBot — verification revoked: Qingdao Sigma Chemical · lot QS-2604-08 · Medutest 88.4% against a claimed 99.2% · two independent confirmations · status VERIFIED → REVOKED… 21:24
  • blank_run — for the record: an 88 percent lot is a manufacturing and QC failure. it is not evidence of fraud and i want that on the log in those words 21:47
  • blank_run — and that is what the log looks like afterwards. all four entries stay up 22:12
  • protein_floor — that is why this log is worth reading 22:19
  • blank_run — Homopeptide variance is the widest of anyone with this many entries. it is a consistency problem and it has been for two years 22:27
KK

a supplier improving shows in the log as later entries, not as earlier entries being edited

if the evidence is thin the entry says the evidence is thin. that is more useful than a score

11😂1

ok so two labs a point or two apart on one lot is normal. both go in the log with both numbers, for what its worth

VV

if you want to help, buy a lot, test it, and post the report with the lot number. that is the whole contribution, your mileage will differ

11
KK

what counts: an independent report, on a lot you bought yourself, with the lot number, from a lab the room recognises

do blinded submissions carry more weight than open ones

OO

for the archive we refresh on new evidence, not on a clock. an old verification with no recent results says so on the entry

somebody once offered to fund the testing programme in exchange for an entry. the offer is in the log

VB

verification revoked: Qingdao Sigma Chemical · lot QS-2604-08 · Medutest 88.4% against a claimed 99.2% · two independent confirmations · status VERIFIED → REVOKED (lot scope)

QH

the lot is off the list. read the bot line again, it says lot scope

we revoke at the narrowest level the evidence supports. one bad lot is not a company-wide verdict

HL

i submitted the first result. 88.4 on purity against a sheet claiming 99.2

BR

two labs, two vials, same lot, 0.7 apart. that is a confirmed failure and there is no arguing with it

HL

they replied in nine days, said they would investigate the lot, and asked for the report

which i sent. no response since

BR

for the record: an 88 percent lot is a manufacturing and QC failure. it is not evidence of fraud and i want that on the log in those words

BR

a bad batch is a process that went wrong. a scam is a person who never intended to ship what they sold

the QSC lot arrived, it was the right compound, the mass was in range, the purity was poor. that is a batch

QH

it does not. the lot stays revoked forever, that is the historical record

the vendor gets new entries on new lots, and the log shows both. nothing gets deleted here

BR

and that is what the log looks like afterwards. all four entries stay up

EntryVendorLotClaimedMeasuredLabStatus
VER-2026-0388Qingdao Sigma ChemicalQS-2602-1199.0%98.6%JanoshikVERIFIED
VER-2026-0402Qingdao Sigma ChemicalQS-2604-0899.2%88.4%MedutestREVOKED
VER-2026-0404Qingdao Sigma ChemicalQS-2604-0899.2%89.1%PeptideMeterREVOKED
VER-2026-0419Qingdao Sigma ChemicalQS-2607-0299.1%98.9%JanoshikVERIFIED
HL

it did. i bought it specifically to see, and i paid for the test myself

that is the honest outcome and i am not going to bury it because it is less dramatic

TA

same shape of thing happened with Homopeptide two lots in a row last winter, then it settled

BR

Homopeptide variance is the widest of anyone with this many entries. it is a consistency problem and it has been for two years

QH

and they have never once failed to ship, which is why they are here and not there

BR

on entry count over 5, the flattest spreads are JEEP and Xi'an Mokemei. Mokemei only has six entries so treat that lightly

22:40revocation policy summary pinned
OO

how long does a verification stay current before it needs refreshing

LL

sorry to jump in a good result with bad sample handling gets logged with a note about the handling. context is part of the record

verification is revoked on a confirmed failure and the revocation stays in the log permanently, thats just me