What's on the label is the measured result — net peptide mass, not gross powder weight, plus RP-HPLC purity, on a lot-numbered COA for every batch.
Net peptide mass and RP-HPLC purity — a lot-numbered COA for every batch.
Net peptide mass + HPLC purity, per lot.
PCAC will review 7 peptides for the 503A bulks list, BPC-157, KPV, TB-500, MOTS-c, Emideltide, Semax, Epitalon. Read our briefing →
PCAC will review 7 peptides for the 503A bulks list. Read →
FDA PCAC reviews 7 peptides in July. Read →
Reference-code fill; Retatrutide identity verified per batch COA · 30 mg
Overview
GLP1-R-30 is a upstream reference code appearing in upstream-manufacturer price tables, mapped by batch documentation to Retatrutide-class tri-agonist material in a 30 mg lyophilized vial format. The 'R' designator in the code indicates Retatrutide; the '30mg' designates the fill quantity per vial. Because the code itself is a supplier reference rather than a public chemical identifier, the API identity, sequence, salt form, and CAS is verified against the released batch-specific COA before any order placement and again on batch receipt at the buyer's QC. This SKU exists in the PeptideXpo catalog primarily to support distributor partners whose own upstream price-tables reference these codes, for direct end-buyers, the named-API equivalent (the Retatrutide SKU) is generally the better procurement route because the analytical packet and documentation are unambiguously attached to a defined molecule. When a reference-code SKU is sourced, PeptideXpo verifies the API identity against the COA at receipt and reflects the verified identity on the customer-facing batch documentation.
Who buys this, and why
Most buyers in this category are 503A and 503B compounding pharmacies fulfilling metabolic and weight-management protocols, plus research labs investigating GLP-1 / GIP / GCG receptor pharmacology. The procurement decision usually hinges on three things: documented purity at scale, a regulatory team that can respond on destination-market questions in writing, and the ability to supply consistent counter-ion form (acetate by default) across recurring orders.
Primary buyer fit: regional distributors and re-sellers.
Specifications
Documentation available on request
Regulatory note
Reference code; verify API identity, sequence and CAS via batch-specific COA before order placement. Sold for research and commercial use in compliance with the buyer's local regulations.
Frequently asked questions
The GLP1-R-30 reference-code SKU exists primarily for distributor partners whose upstream procurement systems reference the supplier's internal code rather than the chemical name. For direct end-buyers, the named Retatrutide SKU is the better procurement route because its analytical packet and documentation are unambiguously attached to the verified molecule. The reference-code path is appropriate only when (1) the buyer's procurement workflow specifically requires the code, or (2) the buyer is sourcing on price with the understanding that identity confirmation happens at batch receipt rather than at catalog level.
At minimum, the released-batch documentation should include: (1) the verified API identity confirmed against the upstream supplier's code (the COA should explicitly state 'Retatrutide' or equivalent rather than just 'GLP1-R-30'), (2) the CAS Registry Number (2381089-83-2 for verified Retatrutide), (3) HPLC chromatogram with peak-integration data, (4) ESI mass spec confirming the modified peptide mass, (5) water content by Karl Fischer, and (6) counter-ion identification (acetate by default). For 503A / 503B-bound material, request additional bacterial endotoxin (LAL per USP <85>) and microbial limits (USP <61>/<62>) testing on the specific batch. PeptideXpo's regulatory team can extend the analytical scope on request, specify the destination market and intended use at quote stage.
The named Retatrutide SKU offers eight standard fill sizes (5 mg, 10 mg, 15 mg, 20 mg, 30 mg, 40 mg, 50 mg, 60 mg), so the 30 mg fill is available in both the named and reference-code paths. The economic difference between the two paths depends on order volume and whether the buyer's downstream workflow needs the named-API documentation chain or accepts the reference-code path with batch-level identity confirmation. For first-time qualification of a new supplier, the named-API route is recommended; for established distributor workflows with verified reference-code mapping, either path is operationally equivalent.
Related peptides
