VendorInvestigate — what its reports establish
VendorInvestigate: Documentation and supplier-practice review. What a report from this service does and does not establish, and how we cite it.
Scope
VendorInvestigate — Documentation and supplier-practice review.
This page describes how this community reads and cites reports from this service. It is not an assessment of the service and we have no relationship with any of the four we cite.
What a report contains
VendorInvestigate reviews documentation and supplier practice rather than testing vials. Its findings on our vendor pages therefore look different from the others: internal consistency of certificates, traceability of lot identifiers, whether a method is identified specifically enough to reproduce, and whether a specification has been reported in place of a measurement.
This is the only one of the four services that can tell you something about a supplier's systems. It is also the one that cannot tell you anything about what is in a container, and our vendor pages say so explicitly where a review is the only record available.
An "insufficient to verify" finding from a documentation review is not a negative finding about a product. It means the documents did not contain enough to check. We use exactly that wording for that reason.
How we cite it
On a vendor documentation page, an entry citing this service records: the compound, the lot identifier, the date, the method as reported, the result, and the state — verified, unverified or disputed. An entry missing any of those is incomplete and gets moved to the discussion rather than the record.
"Unverified" means the available material did not contain enough to check. It is not a negative finding about a product, and we use that wording deliberately.
Limits
One service, one laboratory, one vial, one date. Agreement between two independent services on the same lot is a much stronger statement than a single high number, and our records mix services for exactly that reason.
None of these services can tell you whether something is safe to use. That is a different question and it is not an analytical one.
Revision history
| 2026-04-11 | titration_diary | Reverted an unsourced change and asked the editor to re-apply it with a citation. |
| 2025-11-19 | PharmNotes_Whitfield | Plain-language pass on the opening section after feedback from a newcomer. |
| 2025-10-06 | g.pemberton_uk | Restructured into shorter sections so the outline navigation is usable. |
| 2025-07-25 | customs_ledger | Updated a dated claim and added the date explicitly, per the maintenance convention. |
| 2025-04-15 | a.salcedo | Added cross-references to the two topics that most often ask this question. |
| 2024-12-07 | dexa_twice_yearly | Added the limitations paragraph. The page previously implied more certainty than the sources carry. |
| 2024-11-06 | impurity_table | Initial promotion from the source topic. Structure taken from the marked solution. |
Every edit to a maintained document records its author and a note explaining the change. An edit without a note may be reverted by any wiki editor under R9, and the revert is logged. Disagreements about content belong on the source topic rather than in the revision history (R10).
Related documents
- Janoshik Analytical — what its reports establishJanoshik Analytical: Chromatographic purity and mass-spectrometric identity on submitted samples. What a report from…
- Medutest — what its reports establishMedutest: Combined purity and identity reporting. What a report from this service does and does not establish, and how…
- PeptideMeter — what its reports establishPeptideMeter: Purity analysis plus structured, dated supplier verification records. What a report from this service…