Bluum Peptides Review: 141 COAs, Six Named Labs, and What Actually Verifies
An independent Bluum Peptides review covering a public 144-entry COA index, 141 document-backed records, and 113 certificates that resolve independently at Freedom Diagnostics, Horizon Analytical, or BioRegen.
Bluum Peptides is now a curated vendor on PeptideBenchmark. Most vendors we review show one certificate per product page. Bluum’s public COA lookup exposes 144 index entries instead; 141 currently resolve to attributable documents, including evidence going back well past the products currently in stock. That wider archive let us check much more evidence than usual, including a mismatch the vendor’s own widget did not catch.
Reviewed August 1, 2026. PeptideBenchmark has no affiliate, coupon, sponsorship, or paid-placement relationship with Bluum Peptides. The vendor sells research-use-only products; this is an evidence and commercial-transparency review, not human-use guidance or medical advice.
A widget that ships the whole database
Most vendor COA-lookup tools return one record per search. Bluum’s /pages/coa-lookup page exposes 144 index entries before anyone types a lot number. That let PeptideBenchmark process the available history in one pass rather than guessing lot numbers one at a time.
We split it by relevance: 90 current-batch documents were downloaded and processed — 25 PDFs through text extraction and 65 flattened images through OCR. Another 51 historical documents remain available as continuity records instead of disappearing when batches rotate. Three index entries currently lack an attributable document, and nine document-backed records have no exact current-product match; PB keeps those states explicit rather than counting a filename as a certificate or silently attaching evidence to the wrong product.
What actually verifies
Of the 90 current-batch records, 78 resolve independently at the issuing laboratory:
| Lab | Verified certificates | How it resolves |
|---|---|---|
| Freedom Diagnostics | 46 | Public lookup at coas.freedomdiagnosticstesting.com, gated on the Bluum Peptides / Bluum LLC client name |
| Horizon Analytical | 21 | Public verification API at horizonanalytical.com/verify-coa |
| BioRegen | 11 | Credentials read off the document, confirmed at BioRegen’s public report endpoint |
A sample of what resolved:
| Compound | Lab | Batch / accession | Purity | Tested |
|---|---|---|---|---|
| Retatrutide 15mg | Freedom Diagnostics | RET152607-117A |
99.74% | 2026-07-30 |
| GHK-Cu | Horizon Analytical | GHK502607-122A |
99.57% | 2026-07-12 |
| Ipamorelin | Horizon Analytical | IPA102607-122A |
99.38% | 2026-07-12 |
| Mazdutide | BioRegen | 425912 |
99.92% | 2025-10-23 |
| PT-141 | BioRegen | 513212 |
99.82% | 2025-10-23 |
Average purity across the 90 current-batch records is approximately 99.38%. All 90 report HPLC, 89 report identity, 76 report net content, and 58 report endotoxin. Those counts are panel-specific; PB does not infer sterility or heavy-metals testing where a document does not report it.
The remaining 12 current-batch documents name a lab without resolving through it: nine Freedom Diagnostics reports, one Horizon document, one MZBiolabs report, and one Vanguard Laboratory certificate. The historical archive adds 35 provider-verifiable records and 16 named-lab documents. Seven of those historical images name Janoshik Analytical; they remain document-named evidence because this pass did not independently resolve them through Janoshik’s provider route. No document receives a provider badge merely because a laboratory name appears on it.
The lot that didn’t match its own listing
Here is the part that made the wider scrape worth doing. One lot in the index is filed under the BPC-157 product page, with a batch code of GLO702607-122A — the GLO prefix belongs to Bluum’s GLOW blend, not to BPC-157 on its own. When we submitted that batch code to Horizon Analytical’s public verification API, the lookup succeeded but rejected the match: Horizon’s own record says the compound on file is GLOW, not BPC-157.
That is not a fabricated certificate — it is a real, resolvable Horizon Analytical report — but it is filed against the wrong product on Bluum’s own site. We excluded it from the provider-verified count and logged it as a vendor-side lot-mapping error rather than either dropping it silently or crediting BPC-157 with a certificate that belongs to a different product. It is exactly the kind of error that only shows up when you check the batch code against the lab instead of trusting the vendor’s own label.
Pricing
All 66 in-stock Size variants normalize to a per-mg comparison on the pricing board. A few things needed care:
Every dosage is its own row. Bluum lists dosage as a “Size” variant option (10mg, 15mg, 20mg, …) rather than a single min-price per product, so a five-size product produces five separate catalog rows — 66 in-stock rows across 42 distinct products.
Two branded codes needed CAS-number mapping. GLP1-S and GLP2-T are Bluum’s own product names, not standard peptide names — but their product descriptions publish CAS 910463-68-2 and 2023788-19-2 directly, which resolve unambiguously to semaglutide and tirzepatide.
Support supplies are out of scope. Acetic Acid Water, Phosphate Buffered Saline, and a Reconstitution Solution are lab supplies sold by volume rather than peptide vials, so they are excluded from the pricing board entirely.
Access
Bluumpeptides.com serves an age-gate cookie before any HTML page or the products.json feed resolves. A plain curl or a bare fetch is refused; a real browser session that clicks through the gate reads the public catalog and the coa-lookup page’s embedded dataset without further blocks. PeptideBenchmark drives an actual browser rather than spoofing the age-gate cookie by hand, and a hosted-runner test confirmed the full catalog and lot index read live once the session warms up.
Why Bluum Peptides is curated
Curated does not mean endorsed. For Bluum it means:
- an openly priced 66-row Shopify catalog with expanded per-dosage pricing;
- a public COA-lookup widget that exposes 144 index entries and 141 attributable documents rather than one record at a time;
- 113 certificates confirmed independently across three provider routes, including 78 of 90 current-batch records;
- a caught vendor-side lot-mapping error (GLOW batch filed under BPC-157) excluded rather than silently attached to the wrong product; and
- 51 historical documents preserved as continuity evidence instead of being erased when a product’s current batch rotates.
The live Bluum Peptides profile carries the current score and trust band; the COA database carries the preserved certificates.
Bottom line
Bluum published more raw evidence than most storefronts expose, and checking the full available archive surfaced both a strong result (113 records resolving through three provider routes) and a real product-mapping error. Both are more informative than a single “COA available” badge would have been.
Common questions
Is Bluum Peptides legitimate?
PeptideBenchmark does not issue binary legitimacy or product-safety endorsements. Bluum Peptides is a Wyoming-registered Shopify storefront whose public COA lookup currently exposes 144 index entries and 141 document-backed records. Of those records, 113 resolve independently at Freedom Diagnostics, Horizon Analytical, or BioRegen. That is a genuinely checkable evidence trail; it does not establish the identity, condition, or safety of a physical vial.
Does Bluum Peptides publish COAs?
Yes. Its /pages/coa-lookup page exposes 144 index entries rather than returning only the lot a shopper searches for. PeptideBenchmark currently retains 141 attributable documents: 90 current-batch records and 51 historical records. Three index entries do not currently expose an attributable certificate document and are not counted as COA records.
Are Bluum's COAs independently verifiable?
Most current-batch records are. Of 90 current-batch documents, 78 resolve independently: 46 at Freedom Diagnostics, 21 at Horizon Analytical, and 11 at BioRegen. Across current and historical evidence, 113 of 141 records are provider-verifiable. Seven historical images name Janoshik Analytical but remain named-lab evidence because this pass did not independently resolve them through Janoshik's provider route.
Did every lot match its labeled product?
One did not, and Bluum's own lookup widget caught it for us. A lot filed under the BPC-157 product page carries a batch code prefixed GLO — and when we submitted it to Horizon Analytical's verification API, Horizon's own record rejected it because the certificate is actually for the GLOW blend, not BPC-157. We excluded it from the provider-verified count and logged it as a vendor-side mapping error rather than attaching it to the wrong compound.
Does PeptideBenchmark have an affiliate relationship with Bluum Peptides?
No. At the time of this review, PeptideBenchmark had no affiliate, coupon, sponsorship, or paid-placement relationship with Bluum Peptides.