affiliate disclosure · We earn affiliate commission on some vendor links. Audits, scores, and rankings are independent — vendors do not pay for placement and do not see drafts. read more →
Same supplier, different brand — how shared lab-test URLs reveal upstream peptide manufacturers
When two 'different' peptide vendors cite the exact same Janoshik test URL for the same product batch, they're sourcing from the same upstream manufacturer. We documented this pattern between Summit Biotech and the Peptopia community-tracker batches — confirming Geneza Pharmaceuticals as the shared upstream.
published · · 2 days ago
Quick answer
When two "different" research-peptide vendors cite the exact same
Janoshik test URL for the same product, they're not separately
testing two parallel batches — they're both pointing at one physical
batch, assayed once, by one lab. That means a shared upstream supplier.
We documented this pattern between Summit Biotech (a US storefront,
post-FDA-warning-letter rebrand of Summit Research) and the Peptopia
community testing tracker (which catalogs Geneza Pharmaceuticals
batches). Two Janoshik URLs appear on both surfaces — proof that
Summit Biotech is shipping Geneza-supplied stock under coded SKU names.
What we documented
The headline finding is two Janoshik public-test URLs that show up on
both Summit Biotech's catalog and the Peptopia community tracker.
Janoshik test 93072 — Summit Biotech labels this as Sema-1 (Semaglutide) 10mg / $50. Peptopia's community tracker labels the
same test as Semaglutide 10mg / batch G2025101201 / Blue cap.
URL: janoshik.com/tests/93072-sema10mg_OZ101201_GUAHMNTXBT7X
Janoshik test 91848 — Summit Biotech labels this as Cagri (Cagrilintide) 5mg / $45. Peptopia's community tracker labels the
same test as Cagrilintide 10mg / batch G2025091210 / Green cap.
URL: janoshik.com/tests/91848-Cagrilintide_10mg_Green_CFZIBXNAPYU9
Same lab, same test ID, same physical sample. Two storefronts cannot
both have independently submitted the same vial to Janoshik and
received the same /tests/93072-… URL — Janoshik issues one URL per
submitted assay. If the URL is the same, the underlying batch is the
same.
A second contextual signal travels with the URL: the Peptopia
batch IDs all follow the G2025… / GYC202… format characteristic
of Geneza Pharmaceuticals stock. The Cagrilintide vial above
carries G2025091210; the Semaglutide vial carries G2025101201.
The leading G plus year-month-batch-suffix structure is a
Geneza-distributor signature documented across the entire Peptopia
tracker (154 vendor batches, 30 distinct compounds — every
batch ID we sampled fits the pattern).
Putting the two facts together: Summit Biotech's catalog points to
the same Janoshik tests that the Peptopia community uses to track
Geneza-supplied batches. The simplest explanation is that Summit
Biotech is shipping Geneza stock — under coded SKU names that don't
mention Geneza or the underlying compound by its FDA-cited name.
The supply chain, drawn
The diagram is hedged on purpose. The Summit Biotech ↔ Peptopia
overlap is direct evidence on two URLs. Whether other US-domestic
storefronts also pull from the same Geneza line is a question the
same shared-URL methodology can answer when extended across our
broader 32-vendor cohort. We are not asserting the third box yet;
we are flagging it as the obvious follow-up.
Why this matters for buyers
A buyer comparing two peptide vendors wants to know whether they're
choosing between two genuinely different supply chains or between two
brand surfaces stitched onto one. Shared COA URLs settle that
question at the batch level.
If two vendors point at janoshik.com/tests/93072-…, the bottle on
the shelf came out of one fill operation, was assayed once, and was
distributed under at least two retail brands. The buyer has not made
two independent vendor choices; they have made one supply choice and
two checkout choices.
That isn't necessarily a fraud signal. Geneza Pharmaceuticals is a
real European manufacturer; selling the same stock under multiple
distributor brands is a normal supply-chain pattern in this market
(white-labeling is an established practice — see
/articles/how-to-spot-aliased-peptide-vendors
for related background on the hostname-level analog). The
audit-relevant fact is that the brand separation is at the
storefront layer, not at the supply layer. Buyers who think
"vendor diversification" by ordering from two storefronts may in
practice be doubling exposure to a single upstream batch.
The Geneza signature in the wild
The G2025… / GYC202… batch ID convention is the pattern that
made the cross-reference legible in the first place. Peptopia's
tracker (154 batches across 30 compounds) uses Geneza-style batch
IDs throughout: G2025091210 for Cagrilintide-Green, G2025101201
for Semaglutide-Blue, GYC202… for older batches. The leading G
plus year-month-batch-suffix structure is a distributor-side
identifier that survives across resellers — the resellers don't
relabel the batch.
Summit Biotech's product catalog doesn't print the Geneza batch
ID on the public-facing SKU display name. Summit Biotech's display
names are codenames: Sema-1, Cagri, R-10mg, T-30mg. But the
COA URL that Summit Biotech links from those SKUs lands on the same
Janoshik record where the batch ID is G2025101201 or
G2025091210. The Geneza signature is in the COA URL even when it's
not on the catalog page.
This is the same pattern we documented in
/articles/code-name-catalogs-fda-evasion:
the SKU display name is rebranded, but the COA URL still spells out
the actual chemistry and the actual batch. The COA URL is the
load-bearing fact; the display name is marketing.
How to apply this check yourself
Three steps, reproducible without vendor cooperation.
Right-click the COA link on the product page. Copy the URL.
What you want is the path component — for Janoshik that's
/tests/<id>-<slug> where <id> is the integer test ID. The slug
often contains the actual molecule name and batch identifier even
when the storefront SKU does not.
Search for that test ID in a community tracker. The
Peptopia testing tracker
indexes vendor-submitted COAs across compounds. Open the page and
Ctrl+F for the test ID number. If the same ID shows up under a
different vendor's row in the tracker, you have a confirmed
shared-batch finding. The community tracker is doing the
cross-vendor index work the storefronts won't do themselves.
Cross-check the batch-ID pattern. If the COA URL contains a
batch identifier matching G2025…, GYC202…, or any other
upstream-distributor signature you've seen before, that's a
secondary confirmation that the storefront is downstream of a
specific manufacturer. Geneza's G2025… is one such signature; we
expect to document others as the methodology gets applied to more
vendors.
A vendor whose COAs cluster on a single upstream-distributor batch
ID format across most of their catalog is, on the audit-relevant
question, that distributor's reseller — regardless of the brand on
the storefront.
What this changes about the alias-cluster picture
We've been documenting two prior vendor-aliasing patterns on this
site:
Codename SKU catalogs, where one storefront renames FDA-cited
compounds to codes like R-10mg, T-30mg, Sema-1 to avoid
trademark text and keyword filters. See
/articles/code-name-catalogs-fda-evasion
for the documented Particle Peptides and Summit Biotech cases.
Shared COA URLs are a third, orthogonal pattern on top of those
two. Hostname aliasing operates at the brand layer; codename SKU
catalogs operate at the product label layer; shared COA URLs
operate at the physical batch layer. A vendor can be unique on the
first two dimensions and still share a single upstream supply with
several apparent competitors on the third. The Summit Biotech
finding is exactly that case: Summit Biotech is a distinct legal
entity with its own login-walled storefront and a unique
codename-heavy SKU set, but its COAs land on the same Janoshik
records as the Geneza-tracked Peptopia inventory.
The right mental model is layered: brand layer → SKU layer → batch
layer, each with its own evasion patterns and its own evidentiary
checks. Shared COA URLs are the cleanest signal at the batch layer
because Janoshik issues exactly one URL per assay; you can't fake
the match.
FAQ
Does sharing an upstream supplier make a vendor untrustworthy?
No. White-labeling and distributor-rebranding are normal
supply-chain patterns; many legitimate consumer markets work this
way. The audit-relevant complaint is disclosure. A buyer
choosing between two storefronts that share an upstream supplier
should be told that's the case so they can price the supply-chain
diversification they're actually getting (which is none) rather than
the diversification they think they're getting.
Could Summit Biotech and Peptopia be testing the same batch independently?
No. Janoshik issues one URL per submitted assay. Two storefronts
cannot independently submit the same vial and receive the same
/tests/93072-… URL — Janoshik would assign each submission a new
ID. The matching URL strings (/tests/93072-sema10mg_OZ101201_… and
/tests/91848-Cagrilintide_10mg_Green_…) are decisive evidence that
both surfaces are pointing at one upstream submission.
Is Geneza Pharmaceuticals a fraudulent operator?
No, and we're not asserting that. Geneza is a known European
peptide manufacturer with a multi-year operating history. The
finding here is about distribution structure, not manufacturer
quality. Whether Geneza-supplied product is good product is a
separate question (one Janoshik's assay record can speak to
directly); the question this article addresses is whether two
storefronts that look distinct to a buyer are actually pulling from
the same fill line. They are.
How many other vendors are downstream of Geneza?
We don't know yet. The two confirmed shared URLs (tests 93072 and
91848) are evidence on Summit Biotech specifically. The methodology
generalises — running the same shared-COA-URL check across our
broader vendor cohort would surface other downstream rebrands if
they exist. This is on our follow-up list and will land in a future
audit-cycle article.
Geneza Pharmaceuticals — European peptide manufacturer. Mentioned factually as the upstream attribution suggested by the G2025… batch-ID convention; we are not asserting any fraud claim against Geneza.
Internal: data/audit/round-66/findings/summit-biotech-deep-dive.md — full Summit Biotech investigation, including the cross-reference of Summit's 27 Janoshik COA URLs against the Peptopia tracker and the four shared-COA findings.
Internal: Prime Research Peptides vendor profile — worked example of the hostname-aliasing pattern and how shared infrastructure is disclosed on a vendor profile.