Testing programmes for vendors and clinics

A single certificate is a data point. A programme is a claim about how you operate, which means the design of the programme matters more than the result of any one test in it.

By Canada Peptide Testing. Published September 1, 2026, updated September 13, 2026. 10 minute read.

Organisations start testing for one of two reasons: something went wrong and they need to know what, or a customer asked a question they could not answer. The first produces a one-off submission. The second produces a programme, and a programme has design decisions a one-off does not.

Getting those decisions wrong is expensive in a specific way: you end up with a folder of genuine certificates that do not support the claim you have been making with them.

Plan how units will be selected before extending an individual result to a batch. What testing one vial tells you explains the difference between sample evidence and batch-wide conclusions.

Start from the claim, not from the test

Write down the sentence you want to be able to say. The sentence determines the programme. Compare:

• “This vial was tested.” One unit, one certificate. Straightforward, cheap, and supports a statement about exactly that unit.
• “Every lot we sell is tested.” Requires a submission per lot, a defined trigger for when a lot is tested, and a record connecting each certificate to the lot it belongs to.
• “Our lots meet a specification.” Requires all of the above plus a written specification with a stated source, and a sampling plan sufficient to say something about a lot rather than about one vial from it.
• “Our products are safe.” Not supportable by analytical testing at all. No panel on this site establishes safety, and a programme presented as though it does is a liability rather than an asset.

The gap between the second and third sentences is where most published testing programmes actually sit: making a lot-level claim on unit-level evidence.

Sampling: the decision that sets everything else

A result applies to the sample received. Extending it to a lot is a statistical argument, and the strength of that argument is fixed by decisions made before anything is mailed, not by how good the instrument is.

Three things to settle in writing:

1. How many units. More units means a stronger lot-level statement and a higher cost. The decision is a budget decision informed by how strong a claim you need, and it should be recorded as one.
2. Where in the fill sequence. Units drawn from the start, middle, and end of a fill test something different from three consecutive units off the same tray. If uniformity is part of the claim, the draw has to reflect that.
3. Against what criteria. A specification with a stated source, agreed before results arrive. A limit chosen after seeing the numbers is not a specification.

Cadence: what triggers a submission

A programme needs a rule, not a habit. The common triggers, roughly in order of how much they cost and how much they support:

Most workable programmes combine two: qualification testing on a new source, then periodic sampling with a defined interval, with lot-level testing reserved for products where the claim requires it.

Publishing results your customers can actually check

A published PDF is worth considerably less than a published PDF that resolves. Anyone can produce a document; a verification record is what lets a customer confirm the document matches the issuing laboratory’s own record without having to contact anyone.

Where you publish results, three practices make the publication mean something:

• Publish the verification link, not only the file. The report number resolving to a live record is the part a sceptical customer can act on.
• Use the certificate badge. Every public certificate page has embed code for a small badge showing the compound, purity and report number. It links to the live record and turns to “revoked” on its own if the certificate is ever withdrawn, so an old badge cannot keep vouching for a withdrawn result.
• Connect the certificate to the specific lot. A certificate floating free of the product it describes invites the assumption that it covers everything, which it does not.
• Publish the limitations alongside the number. A page presenting a purity figure with no method conditions and no scope statement is doing the same thing a weak certificate does, one level up.

The stronger move, counter-intuitively, is publishing what the testing did not cover. A vendor page that states plainly “this lot was tested for identity and purity; it was not tested for endotoxin or elemental contaminants” reads as more credible than one implying comprehensive testing, and it is the version that survives a customer reading the certificate carefully.

Independence is the property being purchased

An in-house result can be perfectly accurate and is not third-party testing. The specific thing a customer is trying to obtain when they ask for a COA is that the laboratory producing it has no stake in the outcome.

Canada Peptide Testing does not sell the materials it tests. That is the whole of the independence claim, and it is deliberately narrow. It says nothing about the quality of anyone’s products, only about who produced the measurement.

Practical setup

Multi-sample submissions are handled under one accepted scope, with each sample analysed and reported individually and a sample ID per unit. The same test across several samples in one request earns the volume rate automatically (3+ $279 · 6+ $265 · 12+ $255 CAD per sample for peptide analysis); custom method work is quoted separately. Scope, quantity per unit, calculation basis, and rates are all confirmed in writing before anything ships.

For a recurring programme, the useful conversation to have at the start is not about price. It is about which sentence you intend to be able to say, because that determines how many units and how often, and those determine the price.

Common questions