What peptide molecular weight does on a catalog page
Peptide molecular weight on a research peptide spec table lets a lab buyer cross-check literature, ELNs, and mass-related method notes against the SKU in the cart. It is one identity layer beside sequence, CAS when present, and lot paperwork. It is not a purity grade and it is not a personal-use calculator.
People copy MW from the first Google hit for a nickname and then argue with the product page. The live spec table for that SKU wins. Internet tables often show free-base formula weights while catalogs list a salt or a modified sequence.
This article is for laboratory procurement. Read the disclaimer. Nothing here is medical advice. Research peptides in the catalog remain RUO materials whether or not MW is printed in large type.
Examples such as MOTS-c, SS-31, Selank, and SNAP-8 illustrate short titles that still need full spec literacy at intake.
Using MW as a sanity check, not a verdict
If the protocol cites a monoisotopic or average mass, compare it to the spec table before checkout. A large mismatch is a stop: wrong fragment length, wrong modification, or wrong salt family. A small mismatch may be rounding, average vs monoisotopic, or counterion inclusion.
Do not treat MW agreement as proof you have the right lot. Lots still need lot numbers. MW agreement plus a wrong lot file is still a paperwork failure.
When MW is absent, lean harder on sequence and CAS. Absence is not automatically a red flag for every research listing, especially blends. It does mean you should not invent a number from a related molecule.
The identifiers article covers name collisions. MW is the numeric cousin of that discipline.
Why salt and modifications move the number
Acetate, TFA, and other counterions add mass relative to a free-base sequence string. Amidation, acetylation, and other intentional modifications also move MW. If you compare a catalog number to a Wikipedia free-base formula, you may think the page is “wrong” when it is describing a different object.
Write down which convention your method uses: free base, salt-inclusive, average, monoisotopic. Then buy the SKU that matches that convention or document the conversion in the notebook — do not convert silently in your head at the dock.
Blends do not have a single honest MW in the same way a single sequence does. If a blend page lists a number, read the caption. Do not use a blend MW to confirm a single-compound order.
If two catalog sizes of the same slug show the same MW, that is expected: fill amount changed, identity did not. If two nicknames show the same MW and different residue counts, stop and re-read sequences.
MW versus HPLC purity
HPLC purity percentages describe how a method sees impurities, not whether the peak is the sequence you wanted. Identity and purity are different questions. See HPLC purity and the lab purity overview.
Mass spectrometry in a destination lab can use MW as a starting expectation. Catalog MW still does not replace your method’s acceptance criteria. Storefront education will not set those criteria for you.
A COA may list MW or formula. File it with the lot. Do not average MW across lots to make a “house number.” Lots differ.
Use the COA library after a lot exists. Spec-table MW is the pre-purchase check; lot files are the post-purchase check.
Putting MW on the purchase order
When the method cites MW, copy the spec-table value onto the PO with the slug. Receiving can then see a mismatch without opening a paper. If finance truncates numbers, put MW in a comment field that packing staff still print.
Do not use MW as a substitute for sequence on long peptides. Truncated sequences in emails are a classic wrong-fragment source. Paste the full string when it matters.
Institutional item masters can store expected MW as a reference. Update it when you change SKUs, not when a vendor rounds differently on a reprint.
- Copy MW from the live product page on the day you order
- Note whether the number is described as average, monoisotopic, or salt-inclusive if the page says so
- Keep blends on separate item codes
- Match receiving labels to the PO before shelving
Receiving and relabeling
At intake, you are not re-measuring MW. You are matching documents. If the vial insert disagrees with the PO MW you copied from the page, quarantine and photograph. Contact orders@nextdaypeptides.com with the order number.
Secondary labels should carry lot and item code. MW can go on the item master rather than every tiny vial if space is tight — but then the item master must be correct.
Shipping condition notes belong beside the lot, not instead of identity fields. See the shipping policy.
Frost-damaged labels need an immediate identity transfer. An unreadable MW printed on a sticker is a nuisance; an unreadable lot is an emergency for traceability.
Catalog MW stays in the RUO procurement lane
Catalog molecular weights are not for personal-use calculators, “IU” folklore, or gadgets aimed outside laboratory methods. If a spreadsheet wants MW to turn a research peptide into non-lab guidance, that spreadsheet is out of scope for this site.
Laboratory methods that use mass to prepare solutions belong in signed institutional SOPs. We do not publish those recipes. About us and the RUO explainer state the lane.
Keep Slack comments technical: “spec table MW versus protocol MW — mismatch, hold order.” That sentence is procurement. Outcome stories are not.
If a PI asks customer service which MW to use for people, the answer is that we do not sell for that purpose. Ask the method owner which identity the assay named.
Bottom line
Treat molecular weight as a cross-check in a stack of identifiers. Buy on match, receive on match, file the lot. Do not promote MW into a purity score or a use instruction.
When numbers disagree, stop. Disagreement is cheaper at the cart than at the mass spec.
Reorder from the live spec table, not from last year’s screenshot.
Worked habits on live catalog pages
Open MOTS-c and copy the spec-table MW into a note with the date. Do the same for SS-31, Selank, and SNAP-8 if those SKUs are on your panel. Dated copies beat arguing with a screenshot from last spring.
If the protocol’s MW and the page MW disagree by a wide margin, stop and compare sequences character by character. Wide misses are usually length or modification errors, not rounding. Rounding arguments belong to tenths, not to entire residues.
If they disagree by a salt-sized chunk, check whether the protocol used free base. Write the convention you chose. Do not keep both numbers in play without a sentence that relates them.
Print or PDF the product page into the PO folder when MW is a method-critical field. Pages change. Your folder should show what you ordered against.
Blends and combination titles should not donate an MW to a single-compound row. If you need the single, buy the single from the catalog and use that spec table only.
What destination instruments do not owe the catalog
Your mass spec, HPLC, or other identity method has its own acceptance windows. Catalog MW is a purchasing cross-check. It does not set your pass/fail. Do not email the store asking it to bless an instrument result.
If a lot file lists a mass-related result, file it under the lot. Do not paste it onto the item master as if every future lot will match. Lots differ. Item masters hold expected catalog MW; lot records hold lot data.
Students sometimes treat catalog MW as a calibration standard. It is not. Calibration belongs to certified standards your method named. Research peptide listings are RUO materials, not calibration kits, even when the spec table looks official.
When an instrument result is unexpected, the first documentation move is lot + SKU + method, not a rewrite of the catalog number. Changing the item master to match a surprise result hides the surprise.
Keep personal-use calculators out of the MW conversation. If a spreadsheet tab converts catalog MW into non-lab guidance, delete the tab. The disclaimer is the boundary; the catalog will not provide a friendlier version of that math.
Training purchasing staff to read spec tables
A fifteen-minute onboarding that walks through one product page — slug, sequence, MW, amount, RUO line — prevents months of nickname ordering. Do it with a live page, not a slide.
Quiz with a lookalike pair if you have one in the catalog. The point is to feel the miss before it costs a week. Shame-free drills beat angry receiving emails.
PIs should reject requisitions that omit MW when the method cites one. That rejection is a teaching moment, not a personality conflict.
Keep a lab glossary: average vs monoisotopic, salt-inclusive vs free base, catalog MW vs measured mass. Five definitions remove most Slack arguments.
When staff rotate, record who is allowed to change expected MW on the item master. Identity fields need fewer editors than quantity fields. Tight permissions are documentation quality.
Notebook sentences that keep MW honest
Write one sentence when you order: “Purchased slug X, spec-table MW Y on date Z, protocol cites W, convention C.” That sentence prevents three months of reconstruction from browser history.
Write one sentence when you receive: “Label and PO MW match / mismatch, lot L, location code.” Receiving is not the time to re-argue Wikipedia. It is the time to match documents.
If a later instrument result surprises you, add a third sentence that points at lot and method IDs. Do not edit the first two sentences to make the story smoother. Smooth stories hide mismatches.
Keep those sentences in the same ELN entry as the SKU URL. URLs for MOTS-c or Selank are part of the methods trail, not decorations.
Share the template with students as a required block, not an optional nicety. Optional blocks disappear at 11 p.m. Required blocks survive. The disclaimer still sits above any temptation to turn MW into personal-use math.
Reorders and silent spec-table edits
Vendors sometimes tighten rounding or add salt-inclusive notes. Reorders should recopy MW, not assume last year’s number. Recopying takes ten seconds and catches silent catalog edits.
If MW changed and sequence did not, ask whether convention text changed. If sequence changed, you are not on a reorder — you are on a new identity. New identities need new item codes.
Do not let procurement systems “helpfully” copy an old MW into a new PO without opening the live page. Helpful defaults are a source of wrong-fragment orders.
When two sizes of the same slug show the same MW, that is expected. When two sizes show different MW, stop. Different MW with the same nickname is a stop sign, not a rounding story you tell yourself at the dock.
Archive the dated spec table with the PO. Future you will not remember which convention was on the page. The archive will. Pair it with the shipping timestamp only as logistics context, never as identity.