DataDave said:

The useful checklist is about verifiability rather than presentation.

Shipping damage protocol for vendor vetting orders: if your package arrives with visible damage, temperature excursion, or broken vials:

• Photograph EVERYTHING before discarding packaging
• Note the temperature of the cold pack (liquid = possibly too warm)
• Contact the vendor within 24 hours with photos
• Request a replacement shipment or refund
• Do NOT use potentially compromised medication

Reputable vendors will replace damaged shipments without argument. If they push back, that's a red flag about the vendor.

One thing that is still open after SleepDoc_PDX’s answer:

What a vetting checklist should actually contain, as opposed to a list of things that are easy to fake?

dave_SLC said:

Shipping damage protocol for vendor vetting orders: if your package arrives with visible damage, temperature excursion, or broken vials: Photograph…

Vendor reputation tracking for vendor vetting: I maintain a personal spreadsheet with every order I've placed — date, vendor, batch number, Janoshik result, personal efficacy assessment (1-5 scale), and any issues.

After 20 orders across 5 vendors: average purity 97.4%, zero sterility concerns, 0 shipping issues (all resolved). This data gives me confidence in my current source and documentation if issues arise.

I encourage everyone to track their orders systematically. Community data aggregation makes us all safer.

Closing the loop on my own question.

Went back through my own correspondence with an earlier supplier and the warning signs were all there in the replies, weeks before the quality changed. I was reading the product and not the behaviour.

jim_asheville said:

Vendor reputation tracking for vendor vetting: I maintain a personal spreadsheet with every order I've placed — date, vendor, batch number, Janoshik…

Agreed, with a caveat about community reputation: it is a lagging indicator. Reports arrive weeks after orders, so a supplier can look excellent for a month after quality has already changed.