PT-141 is the one SKU in the VaultLabs catalogue where the same molecule carries a development code and a generic name in equal circulation. The vial is printed PT-141 10mg; the literature also calls it bremelanotide. They are one compound with one registry identity, CAS 189691-06-3, a cyclic peptide of the alpha-MSH analogue lineage supplied as a white lyophilised powder at a 10 mg catalogue fill. Two names on one material creates two distinct receiving hazards: a duplicate inventory row, and a purchase line nobody can match to an invoice. The identity record belongs to the PT-141 compound monograph; this page handles the catalogue and documentation side.
The duplicate-row problem
When two names circulate for one material, an inventory system will eventually hold both. Someone enters bremelanotide against a new lot because the certificate or the paper used that name, the PT-141 row already exists, and the laboratory now shows two materials where there is one. Stock counts drift, and worse, a lot gets attributed to the wrong row.
The fix is a single canonical row keyed to the printed catalogue string, with the alternate name recorded as a synonym field on that row rather than as a row of its own.
Do not let the approved-medicine fact confuse the file
Bremelanotide is an approved medicine in the United States under a specific indication. VaultLabs research material is not that product and is not supplied for human use.
Both halves of that statement need to survive into your internal record. Purchasing teams occasionally read the first half and conclude that ordinary pharmaceutical handling conventions apply, or that a manufacturer specification sheet can substitute for a lot certificate. Neither follows. What arrives is a research reference material released against its own lot documentation. Because this is a compound that attracts non-research enquiries, the order file should show the research aim, the approving signature, and the workflow the lot entered. The relevant terms are collected in the