The Lot Number Ties Vial to Document
ON THIS PAGE
Key findings
- Federal manufacturing rules define a batch as a specific quantity produced under one manufacturing order during one cycle, and a lot as that batch, or a specific identified portion of it, with uniform character and quality. A lot number's entire job is to name that one production event, nothing wider.
- Regentide's own catalog does not apply the field consistently even within one laboratory's output: its retatrutide 10mg certificate, read 2026-08-25, prints a lot number, while its Klow 80mg certificate, from the same laboratory, prints that field as "n/a."
- American Peptides' certificate lot number, read 2026-08-26, matched the laboratory's own hosted copy of the document on inspection, but the vendor's file and the lab's file differ in size by more than 400,000 bytes, an unexplained discrepancy this ledger records as open rather than resolved.
- Capstone Peptides' own certificate index, read 2026-08-26, lists a lot number for a compound no longer sold anywhere on the site, while the flagship compound's 30mg size sells today behind a real, lab-confirmed certificate that never made it into that index at all.
A lot number is the smallest field on a certificate and the one doing the most specific work. Purity, identity, and potency describe a measurement. The lot number says which physical production run that measurement was taken from, and it is the only field on the page that can be checked against something printed on the vial itself.
What the field is actually naming
Federal manufacturing rules define the two words precisely. A batch is "a specific quantity of a drug or other material that is intended to have uniform character and quality, within specified limits, and is produced according to a single manufacturing order during the same cycle of manufacture," under 21 CFR 210.3. A lot is "a batch, or a specific identified portion of a batch, having uniform character and quality within specified limits." Read together, a lot number is not a claim about a compound, a supplier, or a catalog. It names one production event, bounded by one order and one cycle, and a document that reports a purity or potency figure without naming which lot it measured is a document describing an event nobody can identify.
When the field is simply blank
Regentide's own site shows what an inconsistently applied lot field looks like from the inside, not across different vendors but within one. Its Retatrutide 10mg product page, read 2026-08-25, renders a widget labeled Document Available and Active Certificate, carrying a chromatographic purity figure, a tested quantity, a laboratory name, and a lot number. The Klow 80mg certificate, read the same day and issued by the identical laboratory, reports quantities only, no purity figure at all, and prints its lot number field as "n/a." Nothing about the laboratory changed between the two documents. The field that would let a buyer tie either certificate to a specific vial is present on one and empty on the other, decided somewhere between the lab and the page rather than by anything about the compound itself.
A lot number that checks out, and the loose end anyway
American Peptides' certificate, read 2026-08-26, shows the field doing its job in the ordinary case: the lot number, the printed dates, and the signature on the vendor's copy match the laboratory's own hosted copy of the same document on inspection. Two different template generations of the certificate appear across this vendor's catalog, one using LC-MS/MS for identity confirmation on August-dated lots and one using MALDI-MS on June-dated lots, and both are attributed to the same laboratory, Bioviridian, with no explanation on the site for the change. That difference sits beside the file itself: the vendor's copy of the 48mg certificate runs 2,204,973 bytes against 1,796,062 bytes for the laboratory's own copy, though the printed data, dates, lot number, and signature match on both. A lot number matching at the source is the strongest single check available to a buyer, and it is what this document passes. It does not explain why the two files carrying identical printed content are not the same file, a discrepancy this ledger records as open rather than resolved either way.
When the index and the shelf disagree
Capstone Peptides' certificate page, read 2026-08-26, lists 25 rows across three product groupings, each carrying a purity figure, a lot number, and a verification code. One of those rows, AOD-9604 5mg, is fully documented, purity 99.73 percent, lot 1060, verification code GDH8-X86G, for a product that does not exist anywhere in the site's own product listing; the direct product URL for it returns a not-found page. The index runs stale in the other direction on the same page: the site's flagship compound is sold in two sizes, and while the certificate table carries a fully documented 10mg row, the 30mg size, an actively sold product with its own SKU, has no row in the certificate index at all, even though a real certificate for that 30mg lot exists and is independently confirmed at the laboratory's own lookup. A lot number is a record of one production event, and a certificate index built to track those records can drift out of sync with the shelf in both directions at once, listing a lot for something no longer for sale while omitting one for something that is.
What a buyer can actually check
The lot number is the cheapest field on a certificate to verify and the one most often skipped. A buyer can check whether the number printed on the certificate appears anywhere on the vial, the shipping label, or the order confirmation, since a certificate with no way to connect it to what actually arrived has not been tied to anything. Where a laboratory publishes its own lookup, the same lot number, entered independently of the vendor's page, either returns a matching record or it does not, and that check does not depend on trusting the seller's own account of what the document says. Where a vendor's own certificate index exists, comparing it against the current product catalog in both directions, checking for a listed lot with no matching product and a sold product with no listed lot, catches the kind of drift Capstone Peptides shows above. None of these checks requires owning a laboratory account or reading a chromatogram.
Limitations and open questions
This piece describes four cases read on 2026-08-25 and 2026-08-26, and a storefront's certificate index or catalog can change at any time after those dates; this piece makes no claim about any of the four vendors' current state. The file-size discrepancy on American Peptides' certificate is recorded here as an open question because this ledger did not establish its cause, and this piece takes no position on whether it reflects anything beyond two different file-handling steps producing the same printed content. A lot number matching at the source, as it does for American Peptides, confirms that the document is not altered from what the laboratory issued. It does not confirm anything about the underlying compound beyond what the certificate itself measured.
Everything else on a certificate describes a measurement. Only the lot number says which vial that measurement belongs to, and it is the field most often left out.
Sources
21 CFR 210.3, the 2025 edition published at govinfo.gov, read 2026-09-18, for the batch and lot definitions quoted above. Supplier observations are this publication's own, from the dossier record in ledger/vendors.json: Regentide, read 2026-08-25; American Peptides and Capstone Peptides, both read 2026-08-26. Vendors are named here, never linked, per site policy.
Email updates
New articles and news by email, at most once a day or once a week, whichever you pick.
Respond to this analysis
Corrections, contradictions, and anything you have seen yourself. Responses are read and checked. Verified ones become entries in the ledger or corrections to this page. Nothing posts unverified, and no response is published with anything but the handle you type, or the display name of the account you sign in with. Reporting an error, or asking for this article to come down? Use the Report form below.
Report an error or request a takedown
Reports go to the site's administrators. Nothing is removed automatically.