The Peptide CommonsEst. May 2024
Independent. We sell nothing and are affiliated with no manufacturer or pharmacy. Every moderation action is logged in public
Sourcing · Red flags

Documentation that appears only after payment

Solved
Solved by e.lokken in post #3
Patterns that reliably precede a problem: underdosing (less active material than stated, documented by independent testing), mislabelling (wrong compound, wrong strength, or wrong batch on the label), and failure to provide documentation when asked. I would want the raw data before agreeing with my own summary of it.

Jump to the accepted answer →

AZ
an.zamoraTL24 Aug 2025#1

Documentation that appears only after payment Writing it up because I had to work it out twice and would rather nobody else did.

Proposing that documentation deserves a maintained page rather than a recurring topic, and drafting the skeleton here so that the argument about scope happens before the writing rather than after.

What I think belongs on it, what does not, and the three claims that would need a citation each.

14 likes 12mo
LF
l.ferreiraTL27 Aug 2025#2

The opening post is the version of this I will quote in future. One addition.

Adding a reference point for documentation. Mine is a single case, collected without controls, and I am posting the method alongside it so it can be discounted appropriately.

1 like 12mo
EL
e.lokkenTL2 Solution10 Aug 2025#3

Patterns that reliably precede a problem: underdosing (less active material than stated, documented by independent testing), mislabelling (wrong compound, wrong strength, or wrong batch on the label), and failure to provide documentation when asked.

I would want the raw data before agreeing with my own summary of it.

7 likes 12mo
AA
an.adeyemiTL212 Aug 2025#4
an.zamora, post #1: Documentation that appears only after payment Writing it up because I had to work it out twice and would rather nobody else did. Proposing that documentation deserves a maintained page rather than a recurring topic, and drafting the skeleton here so that the argument about scope happens before the writing rather than after. What I think… Go to post

Documentation is a question about a distribution, not about a value, and treating it as a value is what produces the confident wrong answers.

18 likes in reply to #1 12mo
JS
j.sorensenTL214 Aug 2025#5

Summarising the documentation thread so far, since it is long and the answer is buried: the first reply has the method, the fourth has the correction to it, and the rest is people agreeing at length.

4 likes 11mo
CR
c.rasmussenTL216 Aug 2025 · edited#6

Building on post #5 rather than restating it.

Where somebody posts a concern, ask what would resolve it before arguing about it. Half of these threads end with a document nobody had asked for.

Speaking for myself and not for anyone else who has posted here.

0 likes 11mo
CR
c.ramosTL218 Aug 2025#7
e.lokken, post #3: Patterns that reliably precede a problem: underdosing (less active material than stated, documented by independent testing), mislabelling (wrong compound, wrong strength, or wrong batch on the label), and failure to provide documentation when asked. I would want the raw data before agreeing with my own summary of it. Go to post

Since documentation keeps coming up, it should probably be a maintained page rather than a recurring thread. I am happy to draft it if someone with more direct experience will review it.

26 likes in reply to #3 11mo
JC
j.castellanosTL220 Aug 2025#8
l.ferreira, post #2: The opening post is the version of this I will quote in future. One addition. Adding a reference point for documentation. Mine is a single case, collected without controls, and I am posting the method alongside it so it can be discounted appropriately. Go to post

Documentation quality as a signal: a supplier that reports method identifiers, distinguishes specification from result, and states the counter-ion form is telling you something about systems behind the document. A certificate that is a number and a signature tells you less.

Written in the hope of being told what I have missed.

12 likes in reply to #2 11mo
AW
a.wikstromTL221 Aug 2025#9
j.castellanos, post #8: Documentation quality as a signal: a supplier that reports method identifiers, distinguishes specification from result, and states the counter-ion form is telling you something about systems behind the document. A certificate that is a number and a signature tells you less. Written in the hope of being told what I have missed. Go to post

The strongest single signal available cheaply is what happens when you ask a technical question. A quantitative answer inside a working day is difficult to fake at scale.

The short answer was in the first line; everything after is the working.

17 likes in reply to #8 11mo
JM
j.mwangiTL4 Moderator23 Aug 2025#10

The most useful reply I ever got about documentation was a request to state my units. It sounds like pedantry and it has saved me twice.

7 likes 11mo
TI
t.ibarraTL225 Aug 2025#11
a.wikstrom, post #9: The strongest single signal available cheaply is what happens when you ask a technical question. A quantitative answer inside a working day is difficult to fake at scale. The short answer was in the first line; everything after is the working. Go to post

Building on post #10 rather than restating it.

Careful with the language on documentation. "Not detected" and "not present" are different findings and the first is a statement about the method.

0 likes in reply to #9 11mo
I
IsaksenTL3Regular26 Aug 2025#12

Post #8 put the caveat in the right place and I want to underline it.

Nothing here should be read as an accusation against a named company, and the guidelines exist so that reports remain reports.

Genuinely open to being wrong about this one.

5 likes 11mo
TB
t.batistaTL228 Aug 2025 · edited#13

On documentation the community has more anecdote than the confidence in this thread implies, and I include my own contribution in that.

19 likes 11mo
BP
bench_peakTL3Regular30 Aug 2025#14

The practical version of documentation is three sentences long. The rigorous version is three pages and reaches the same conclusion with the conditions attached.

0 likes 11mo
MA
m.adebayoTL231 Aug 2025#15
bench_peak, post #14: The practical version of documentation is three sentences long. The rigorous version is three pages and reaches the same conclusion with the conditions attached. Go to post

Post #14 is the version of this I will quote in future. One addition.

Prices well below the rest of the market are a fact rather than a finding. They are worth noting and they do not establish anything on their own.

I am confident about the direction and much less about the magnitude.

0 likes in reply to #14 11mo
LC
l.chevalierTL3Regular2 Sep 2025#16
e.lokken, post #3: Patterns that reliably precede a problem: underdosing (less active material than stated, documented by independent testing), mislabelling (wrong compound, wrong strength, or wrong batch on the label), and failure to provide documentation when asked. I would want the raw data before agreeing with my own summary of it. Go to post

Documentation looks different depending on whether you are reading the primary literature or the summaries of it, and the difference is not in our favour.

2 likes in reply to #3 11mo
PB
p.boatengTL23 Sep 2025#17

Small methodological point on documentation: repeating a measurement is cheap and resolves most of what is being argued about here at no cost to anyone.

13 likes 11mo
T
TavaresTL1Member5 Sep 2025#18

Answering the question post #16 raises rather than the one it answers.

A certificate that reports a specification in the result column is a documentation defect, and it is a defect people should be able to recognise without it being called anything worse.

Caveat: everything above assumes the paperwork is what it says it is.

27 likes 11mo
RC
r.chukwuTL26 Sep 2025#19

Having read the whole documentation thread before replying: the question in the first post has not actually been answered yet, and three of us have answered a nearby one instead.

4 likes 11mo
B
BramleyTL2Member8 Sep 2025#20

An honest declaration on documentation: I have a prior here and it is strong enough that you should weight what I say downward. Stating it rather than hiding it.

13 likes 11mo
FH
f.haddadTL29 Sep 2025#21

The most useful contribution to this subcategory is a resolved case written up with the resolution, because the unresolved ones are all anyone remembers.

The claim is narrower than it sounds, and deliberately so.

0 likes 11mo
PN
p.novotnyTL2Regular10 Sep 2025#22

Building on post #21 rather than restating it.

Documentation has been discussed here with more heat than it deserves, mostly because two definitions have been in play the whole time.

19 likes 11mo
ZS
z.szaboTL212 Sep 2025#23

Everything in post #21 holds. The case it does not cover is the one I have.

Exaggerated claims without documentation: every compound has limits. No peptide is "100% pure" because purity is measured to finite precision. A supplier claiming implausible perfection without backing evidence is overreaching.

Correct me on the arithmetic if it is wrong; I would rather know.

8 likes 10mo
ER
eire_readerTL2Regional · IE13 Sep 2025#24
j.sorensen, post #5: Summarising the documentation thread so far, since it is long and the answer is buried: the first reply has the method, the fourth has the correction to it, and the rest is people agreeing at length. Go to post

Unresponsiveness: a supplier that does not reply to reasonable requests for documentation or clarification is showing you something about how they operate.

2 likes in reply to #5 10mo
FY
f.yildizTL215 Sep 2025#25

I changed my mind about documentation after someone here asked me for the source and I could not produce one. That is worth saying out loud because it is the ordinary way it happens.

27 likes 10mo
W
WendelboeTL2Member16 Sep 2025 · edited#26

Two claims get bundled together under documentation and they need separating. The descriptive one — this is what was observed — is usually well supported. The causal one — this is why — usually is not.

Almost every disagreement in threads like this one dissolves once you say which of the two you are making.

13 likes 10mo
MN
ma.nascimentoTL217 Sep 2025#27
a.wikstrom, post #9: The strongest single signal available cheaply is what happens when you ask a technical question. A quantitative answer inside a working day is difficult to fake at scale. The short answer was in the first line; everything after is the working. Go to post

Useful. I have added it to my own notes with the date on it.

4 likes in reply to #9 10mo
CP
citation_peakTL3Regular19 Sep 2025#28
e.lokken, post #3: Patterns that reliably precede a problem: underdosing (less active material than stated, documented by independent testing), mislabelling (wrong compound, wrong strength, or wrong batch on the label), and failure to provide documentation when asked. I would want the raw data before agreeing with my own summary of it. Go to post

Post #25 answers the question as asked. The question underneath it is different.

The guidelines draw that line for a practical reason as much as a fair one: reports accumulate into something useful and allegations do not.

The general case is well covered; this is the awkward specific one.

0 likes in reply to #3 10mo
NI
n.ibarraTL220 Sep 2025#29

The strongest argument against my own position on documentation, stated as well as I can state it, since nobody else has yet.

20 likes 10mo
SS
system_suitabilityTL3Analytical chemist21 Sep 2025#30

Safety documentation absent: a supplier that cannot provide information about sterility testing, endotoxin testing, or safety documentation when asked is raising flags.

8 likes 10mo