The naming problem in peptide catalogs
Research peptides accumulate nicknames the way reagents always have. A sequence may appear under a developmental code, a USAN-like stem, an abbreviated research code, a spelling variant, and a storefront slug. Epitalon and Epithalon are the same tetrapeptide idea under spelling variants; Melanotan listings may distinguish MT-I from MT-II; GLP research compounds often carry both a generic path name and a catalog code on our site.
For lab procurement, treat the storefront title as a convenience label. Confirm identity with sequence, CAS when published, molecular formula or weight on the spec table, salt or modification notes, and the COA for the lot you receive. Ordering by vibe — or by the first autocomplete hit — is how labs burn a week and a purchase order on the wrong fragment.
This guide is for buyers who have to defend a SKU to a PI or purchasing desk. It stays inside Research Use Only framing: catalog clarity helps laboratory ordering; it does not authorize human or animal use, dosing, or therapeutic claims. See the RUO article for the use boundary we enforce across product and education pages.
Good identifier hygiene also speeds receiving. When the purchase order already lists sequence or CAS beside the storefront name, matching the vial and lot paperwork becomes a confirmation step instead of a detective story.
Layers of identity buyers actually use
Think in layers rather than in a single magic field. The marketing name gets the vial into the cart. The sequence (plus terminus and salt notes) tells chemistry what molecule you meant. The CAS, when present, hooks literature and inventory systems. The lot number hooks the COA. The URL slug is only a stable web address.
Problems happen when teams collapse those layers. A purchasing agent orders by nickname while the protocol cites a different residue count. A student files a COA under the synonym they prefer while the freezer label uses the catalog title. Months later, nobody can prove the study used one substance.
Write the layers you care about into the purchase requisition: “sequence … / CAS … if listed / lyophilized … mg / single-compound SKU, not blend.” That one habit prevents most synonym disasters before checkout.
When multiple people touch an order — PI, purchaser, receiving, technician — each role should know which layer they own. Purchasing owns the match to the protocol identifiers; receiving owns the lot match; the bench owns the notebook line that ties vial to experiment. Gaps between those roles are where wrong-compound stories hide.
Print a wallet card or wiki snippet with your lab’s canonical fields if turnover is high. People remember nicknames; systems need sequences. Make the systems easy to feed.
CAS registry numbers
A CAS number points at a specific chemical substance record in the CAS registry. When a product page lists a CAS, use it to cross-check literature, ELNs, and chemical inventory systems. It is one of the cleaner bridges between a storefront and a library database — when it exists and when it truly matches the salt and form you are buying.
Some research peptides and blends will not have a single tidy CAS — especially multi-component SKUs — so absence of CAS is not automatically a red flag. It does mean you lean harder on sequence, molecular weight, and lot identity testing. Do not invent a CAS from a related molecule just to fill a spreadsheet cell; wrong CAS is worse than blank CAS.
Do not assume two vials with similar marketing names share a CAS. Blends sold as a single SKU are not interchangeable with the single-compound pages they reference. If your protocol needs the single sequence, buy the single-compound page — for example BPC-157 or TB-500 — rather than a combination product that happens to mention the same nickname in marketing text.
Salt forms sometimes carry different registry entries than the free base or a different counterion. If your assay literature specifies a salt, verify that the CAS (or the written salt note) matches before you treat two catalog hits as equivalent.
Sequence, length, and modifications
For peptides, the amino-acid sequence (and notes about salts, acetylation, amidation, or other intentional modifications) is often the decisive identifier. Spec tables on our product pages call out sequence or residue count when relevant. If your protocol cites a specific salt form, match that on the label and lot paperwork before the vial enters a study.
Truncated research fragments in older literature can share a family name with a full-length molecule. Read the residue count. “Looks like the same research code” is not identity. The same warning applies when vendors abbreviate long sequences differently in titles while the underlying residues diverge at one position that your assay cares about.
Modifications change behavior in assays even when the core sequence string looks familiar. Acetylated N-termini, C-terminal amides, and counterion differences show up in mass and sometimes in solubility notes. Capture those details in the order comment and the notebook line — not only in a mental note from last quarter's order.
If the protocol is silent on salt form but your assay is salt-sensitive, escalate to the PI before purchasing rather than assuming the catalog default matches last year's bottle from another vendor. Defaults differ across suppliers even when the nickname is identical.
When sequences are long, paste the full string into the PO rather than a truncated display. Truncation errors in procurement emails are a classic source of wrong-fragment orders that only surface after mass spectrometry.
Synonyms, spelling variants, and folklore names
Spelling variants (Epitalon / Epithalon) and folklore names proliferate because papers, forums, and older catalogs disagree. Our storefront consolidates synonyms onto stable product pages so buyers are less likely to create duplicate mental inventory for one substance. Still, your internal alias list should map every synonym you allow to one canonical SKU and sequence.
Be careful with names that sound clinical or drug-like. RUO catalog titles are not approvals, and synonym overlap with pharmaceutical names does not make a research peptide a medicine. Keep language in requisitions technical: sequence, CAS, catalog slug — not outcome stories.
When literature uses a code name that our catalog lists under a different title, paste both into the purchase note and confirm the sequence match before anyone clicks buy. That five-minute check is cheaper than a customs or receiving argument later.
Teach new staff that autocomplete is not identity confirmation. Search suggestions optimize for speed; your protocol optimizes for the correct residues. Click through to the spec table every time until the habit sticks — especially on lookalike names that differ by a single letter or a Roman numeral.
Storefront slugs and legacy URLs
Our URLs use stable slugs such as epitalon-epithalon or mt-1-melanotan-i so synonyms resolve to one product page. Older paths redirect when we consolidate names. If a bookmark 404s, search the catalog or start from the products index rather than guessing a hyphen pattern from memory.
Slugs are for the web. They are poor primary keys for LIMS entries because marketing URLs can be remapped while the chemical identity stays the same — or, more dangerously, a slug could be reused in a redesign if someone is careless. Prefer lot numbers and sequences inside institutional systems; keep the slug as a convenience link in the purchase record.
Educational articles in this section link back to FAQs, the COA Library, and RUO policy pages so naming guidance stays tied to how we actually sell and document materials. Product examples such as NAD+, GHK-Cu, and MOTS-c illustrate how short titles still need full identifier discipline at intake.
If you share links in Slack or email, prefer the canonical product URL from the live page rather than a redirected legacy path. Redirects usually work; canonical links reduce ambiguity when someone archives the thread years later.
Single compounds vs blends
Blend SKUs exist for labs that intentionally want a labeled combination. They are a different purchasing object from the related singles. Do not assume stoichiometry, ratio, or separate COA coverage without reading the product page and the lot file. If your method needs independent titration of each component, buy singles.
Inventory systems should give blends their own item codes. Reusing the item code of a major component “because it is mostly that peptide” destroys traceability. When an assay misbehaves, you need to know whether the freezer held a blend or a single lot.
If a packing list abbreviation confuses receiving, photograph the vial and compare to the live product page before shelving. Clarifying email to orders@nextdaypeptides.com with the order number beats shelving under the wrong code.
When a protocol cites two singles, resist the urge to “simplify” into a blend unless the blend's labeled composition is exactly what the method requires. Convenience purchasing is not method equivalence.
How identifiers meet lot paperwork
Names get you to a product page; lot numbers get you to a COA. After delivery, match the vial lot to the PDF before the material enters a shared study. Our COA reading guide covers field-by-field habits; this article only stresses the identifier handoff: catalog name on the site, sequence/CAS on the spec, lot on the label, purity and identity on the lot file.
HPLC purity claims such as ≥99% describe cleanliness under a method — they do not fix a wrong sequence choice. If you ordered the incorrect synonym, a beautiful chromatogram will not make it the molecule in the protocol. Keep purity evaluation (see the HPLC purity article) logically downstream of identity confirmation.
File COAs under the canonical institutional name you chose, and store synonyms in a metadata field — not as duplicate folders that drift apart. Future you should find one binder path per substance.
When lot paperwork lists a name that differs from your freezer label synonym, add a bridging note once: “also known as … / institutional code ….” Bridging notes prevent the next technician from “correcting” a label into the wrong folder.
Procurement language that survives audit
Auditors and incoming PIs ask boring questions: what did you buy, which lot, where is the file, what was it for (research context). Answer those questions in the PO text. “Research peptide for in-vitro assay X; sequence …; catalog slug …; RUO only” is clearer than a nickname and a vibe.
Align purchasing aliases with receiving labels. If finance's vendor item description differs from the freezer label, maintain a mapping table. Mapping tables are unglamorous and extremely effective.
Shipping and fulfillment details live in the shipping policy; they do not identify the chemical. Do not let tracking numbers substitute for lot IDs in the chemical inventory.
If your institution requires chemical inventory barcodes, print them after identity confirmation — not before. Barcoding the wrong synonym locks the error into every downstream scan. Confirm sequence or CAS, then label, then shelve.
Bridging literature names to catalog pages
Papers often cite developmental codes, company codes, or outdated spellings that never appear as primary titles on a modern storefront. Build a short translation table for the compounds your lab reorders: literature string → sequence → catalog slug → institutional item code.
When a new paper enters a journal club with an unfamiliar code, assign someone to resolve identity before anyone drafts a purchase request. Enthusiasm without a sequence match is how rush orders go wrong.
Keep the translation table versioned. Synonym pages consolidate; institutional codes change after a LIMS migration. A dated table beats a tribal memory that disagrees across two freezers.
If literature cites a salt or modification your catalog page does not list, stop and clarify with the PI and, if needed, supplier support — do not assume the nearest nickname is close enough for the assay.
Quick checklist before you add to cart
Use this as a pre-checkout gate. If any line fails, pause and resolve it before payment clears — returns and time both hurt more than a short delay.
- Match the protocol's sequence or CAS to the product spec table
- Confirm fill amount (mg) and form (lyophilized vs solution)
- Note salt, acetylation, amidation, or other mods called out on the page
- Confirm whether you need a single compound or a labeled blend SKU
- Capture the storefront slug and canonical name in the PO or cart notes
- Plan to file the lot COA when the order arrives
- Keep RUO use limits in view — catalog clarity does not change lawful use
Common ordering mistakes (and calmer fixes)
Mistake one: ordering from memory after a synonym change. Fix: open the live product page and compare residue count every time for high-stakes assays. Mistake two: receiving into the wrong LIMS item because the packing list used a short name. Fix: lot-first matching, then name mapping.
Mistake three: treating two vendors' identical nicknames as identical substances without sequence checks. Fix: require sequence or CAS in every comparative quote. Mistake four: letting students create parallel alias folders. Fix: one canonical record with synonym fields.
Mistake five: skipping storage discipline after a correct order. Identity paperwork cannot rescue a vial that sat warm in a mailroom; pair this guide with the lyophilized storage article when you write intake SOPs.
Mistake six: quoting a blend price into a single-compound budget line. Fix: separate item codes and separate scientific justifications so finance and the bench stay aligned.
Bottom line
Trust sequences, CAS when real, modification notes, and lot-linked documents more than nicknames. Use storefront titles and slugs to navigate — then promote the chemical identifiers into your institutional record so the study remains interpretable when the website copy evolves.
Nextday Peptides designs catalog pages for that laboratory buyer: clear titles, synonym-aware URLs, and lot documentation pathways under RUO rules. Catalog clarity is a procurement tool. It is not medical advice, not a clinical identity system, and not permission to use these materials outside research.
If your group adopts one habit from this article, make it the layered requisition: nickname for humans, sequence or CAS for chemistry, lot for paperwork. That stack survives staff turnover better than any single clever alias.
For day-to-day ordering, open the live products catalog, confirm the spec table, and only then paste identifiers into the PO. That one extra click is cheaper than explaining a wrong fragment to a PI after receiving.
Handoffs between purchasing and the bench
Most wrong-compound stories are handoff failures, not chemistry failures. Purchasing believes the nickname matched; the bench believes the sequence matched; neither checked the same fields on the same day.
Require a written handoff line on every peptide receipt: protocol identifier cited, catalog identifiers confirmed, lot recorded, storage location assigned. Initials from receiving and from the scientist who will open the vial force the conversation to happen while the box is still on the bench.
When handoffs are email-only, quote the sequence or CAS in the email body. Attachments get lost; quoted identifiers survive forwarding.
If the bench rejects a receipt because identifiers disagree, treat that as a successful control, not as purchasing failure theater. The goal is correct material in the study, not speed of shelving.