A peptide vendor transparency changelog is a dated record of every change to a vendor's documentary evidence: when a new batch-level certificate of analysis (CoA) appears, when an older one lapses, and when the underlying test methods change. On the PeptideTrust scoreboard, a transparency score is not a fixed verdict. It is a snapshot of verifiable evidence at a point in time, so the score moves as that evidence moves. This guide explains what makes a score rise or fall, and why a vendor - and an independent scorer - keeping a visible, dated log is a trust signal in its own right. These are research chemicals, sold for research use only, and everything here concerns documentation, not use.
What does a transparency score actually measure?
A transparency score measures a single thing: whether laboratory evidence is published, current, and verifiable at the source. It is not a rating of quality, safety, or effect. Our scoring methodology weighs ten documentary criteria - among them whether CoAs are batch-level, whether the testing lab is named and independent, whether a batch or lot number matches the vial, whether a date of analysis is present, and whether a verification code resolves on the lab's own domain rather than a vendor-hosted PDF. Because every one of these is a documentary property, not a marketing claim, each can be checked, and each can change. When a vendor adds evidence that satisfies more criteria, the score reflects that. When evidence goes missing or grows stale, the score reflects that too. The number is only ever as current as the paperwork behind it.
Why does adding new CoAs raise a score?
The most common reason a score rises is that a vendor publishes fresh, batch-level CoAs. A certificate describes one batch at one moment, so a vendor who releases a new lot and posts its matching certificate is demonstrating an ongoing habit of disclosure rather than a one-time gesture. Several improvements can lift a score at once: a CoA that now shows a full chromatogram rather than a bare purity percentage; a report from a named, independent lab instead of an anonymous "US lab"; or the addition of mass spectrometry (MS) data alongside high-performance liquid chromatography (HPLC), so identity and purity are both addressed. Because purity and identity answer different questions, documenting both is stronger than documenting either alone. A verification code or QR that resolves on the testing lab's own domain adds further weight, since it lets a reader confirm the document at the source.
Why can a score fall without the product changing?
A score can drop even when nothing about a vendor's catalogue changes, because transparency is about the state of the evidence, not the product. The most frequent cause is expiry: a CoA describes a specific batch on a specific date, so once a lot sells through and no new certificate replaces it, the published evidence no longer corresponds to what a buyer would receive. Links also decay. A verification portal that once resolved may now lead nowhere, and a broken verification mechanism is a documented red flag. Other declines follow from documents being pulled behind a login, replaced with a single generic certificate reused across every product, or moved to "available by email on request" after purchase. None of these require the vendor to change what they sell. They change what a reader can independently confirm, and the score follows the confirmable evidence.
How do method changes affect the score?
Changes to how testing is done can move a score in either direction. A vendor who moves from an unnamed testing arrangement to an ISO/IEC 17025 accredited laboratory - the international standard for testing-laboratory competence - strengthens the credibility of every certificate that follows, because accreditation is a stronger signal than an unaccredited claim. Adding a distinct method to answer a distinct question does the same: layering LC-MS identity confirmation onto HPLC purity data, or reporting net peptide content by amino acid analysis so a reader can see how much of the mass is water, salts, or counter-ions such as TFA or acetate. Conversely, if a vendor stops publishing chromatograms and reports only a percentage, or switches to a lab that cannot be found to exist, the documentary value drops. A changelog that names the method change lets a reader judge whether the shift added evidence or removed it.
What about tests a purity CoA never included?
It is worth separating what a standard peptide CoA covers from what it does not, because a score should not be penalised for the absence of a test the certificate was never meant to carry. A typical purity and identity CoA reports HPLC purity and MS identity. It usually does not include sterility or endotoxin data, and that absence is normal and must never be read as a sterility guarantee. Two separate tests exist for those questions, and passing one does not imply the other:
- Endotoxin testing - bacterial lipopolysaccharides measured by the LAL (Limulus Amebocyte Lysate) assay, reported in EU/mg or EU/mL, under USP <85>.
- Sterility testing - detection of viable microorganisms, a distinct procedure under USP <71>.
When a changelog notes that a vendor added such data, it reflects genuinely broader disclosure. When it does not, the score simply continues to describe identity and purity, which is what the document addresses.
Why is a dated changelog itself a credibility signal?
A dated changelog turns a score into an auditable history rather than an opinion. Because results describe a batch at a point in time, a log that records when a CoA was added, when one lapsed, and what method changed lets any reader reconstruct why a number is what it is. That traceability is the same principle that makes a certificate trustworthy in the first place: a claim you can check at the source beats a claim you are asked to take on faith. It also protects against selective memory, since a vendor cannot quietly withdraw a document and present an unchanged reputation. On the scoreboard side, a transparent revision history is how an independent scorer stays accountable to its own ten weighted criteria. You can compare the reasoning behind current standings on the ranked scoreboard and see that the evidence, not editorial preference, moved the score.
How should a buyer read a changing score?
Treat a score as a living reading, not a badge. A recent rise usually means fresh, verifiable evidence has appeared; a recent fall usually means a document expired, moved behind a barrier, or stopped resolving at the source. Before drawing a conclusion, apply the same literacy the changelog is built on: confirm the CoA is batch-level and dated, that the lot number matches the vial, that a named independent lab performed the work, and that any verification code resolves on the lab's own domain. Reading the underlying anatomy of a certificate of analysis lets you interpret a score movement rather than merely react to it. A number that changes with the evidence is behaving exactly as it should - a static number that never moves, despite new batches shipping, is the one worth questioning.