ERP — community confrontation after the JEEP results
This is one entry from the TitrateLab Vendor Graveyard, a dated, primary-source archive of peptide-market shutdowns, exit scams, and enforcement actions. Documented as April 2026. Sources for this entry are named inline below and numbered in full on the parent archive page.
The follow-on wave to the JEEP scandal. After the JEEP endotoxin results made the community-testing-pays culture visible, attention shifted to other high-volume vendors who had been similarly exempt from independent batch-level scrutiny. ERP became the next target. Our editorial position on this entry is more measured than the JEEP entry above — we have less evidence on ERP’s batch-level contamination and more evidence on ERP’s response posture.
ERP (Shanghai ERP Peptide Biotechnology) has been one of the most-recommended international vendors in the 2025-26 GLP-1 grey market, particularly for retatrutide and tirzepatide. They historically posted fresh COAs on a roughly 3-day cadence; the most recent batch in our corpus tested with a −49.5% quantity deviation on Retatrutide (March 25, 2026) (finnrick COA, 2026-03-25), the kind of single-batch outlier that wouldn’t trigger archive-level concern in isolation but contributes to the broader picture.
Timeline: - Through early April 2026 — ERP appears in our corpus as a stable, high-volume vendor with above-average purity but with at least one notable single-batch underdose flagged in March. - April 19, 2026 — A community-published analysis at krysia0430.substack.com/p/the-trouble-with-erp documents what an independent analyst frames as ERP’s “lousy response” to community questions about endotoxin testing on their products. The post is shared on glp1forum.com in a thread titled “JEEP isn’t only endo concern. ERP would like a word.....” - April 19 onwards — The 89-post thread accumulates as the community discusses (a) what specifically ERP said vs. what was being asked, (b) whether independent endotoxin testing should now be expected as table-stakes for any high-volume international vendor, (c) whether ERP’s response pattern (deflection, refusal to publish independent endotoxin data at the batch level) is a leading indicator of a broader quality issue. - Late April 2026 — Our forum-incident detector flags ERP at 8.6× baseline mention volume in the trailing 7-day window vs. the prior 4 weekly windows. The signal is real; the substantive batch-level evidence has not yet emerged the way it did for JEEP.
What we have, what we don’t: - We have: 89-post community discussion, an independent-analyst long-form post, evidence that ERP’s response pattern is being interpreted by serious community members as evasive. - We don’t (yet) have: an LS / Liquilabs / Janoshik-confirmed endotoxin failure on a specific ERP batch the way we have for JEEP. The community is asking for one; ERP has not provided one; no independent customer has yet published a third-party endotoxin result.
This is exactly the evidentiary gap that distinguishes the JEEP entry above (specific batch, specific lab, specific numbers) from the ERP entry here (operator-response pattern + analyst critique, no per-batch lab confirmation yet).
We're flagging ERP for elevated buyer scrutiny pending either (a) ERP publishing independent batch-level endotoxin data, (b) a community-funded LS / Liquilabs / Janoshik test surfacing a confirmed contaminated batch, or (c) the response-pattern story resolving in ERP's favor with a substantive operator engagement. Until one of those three resolves, we treat ERP catalog routing the same way we treat any vendor with unresolved community complaints: in the catalog for transparency, but not actively recommended.
Primary sources: the community thread documenting the substack post and ERP’s response posture; the independent-analyst long-form post on substack (linked from the thread).