Two peptides can share the same residue string while differing at one or both ends. A reagent request should name each required terminal state explicitly instead of leaving the supplier to infer it from a product nickname or a previous order.
State each end independently
GenScript’s modification catalogue separates N-terminal options, including acetylation, from C-terminal options, including amidation. It also lists terminal labels and conjugates, illustrating that “modified peptide” is not a complete molecular description.GenScript — Peptide Modifications (opens in a new tab)
For an original request, specify the sequence in one field, the N-terminal state in a second and the C-terminal state in a third. A blank field is ambiguous: it may mean unmodified, unspecified or omitted accidentally.
If the intended material has an unmodified terminal group, state that requirement directly. Do not assume a supplier’s default is universal or that it matches the construct used in a cited experiment.
The purpose of this request is documentary precision. It is not an instruction to choose a particular terminal modification for stability or biological activity.
Make the attachment position part of the requirement
| Ambiguous wording | Clarification needed |
|---|---|
| Acetylated peptide | Which site is acetylated, and what is the other terminus? |
| Amidated version | Confirm the C-terminal group and the complete sequence |
| Biotin-labelled peptide | State attachment site and any intervening linker |
| Same as last time | Identify the dated specification and confirm both terminal fields |
A label attached through a linker is not fully described by naming the label alone. The agreed molecular description should make the connection understandable without guessing from a diagram’s appearance.
If a request includes several peptides, repeat or clearly map the terminal requirements for each entry. A general note at the top of a spreadsheet can be missed or interpreted as applying to only part of the order.
Where text and a drawing conflict, identify the conflict for resolution. Neither should silently take precedence merely because it looks more formal.
Check that confirmation covers the actual endpoints
A reply confirming “sequence correct” may refer only to residue order. Ask for explicit confirmation of the terminal states if they are essential to the study’s molecular definition.
For example, a quotation that reproduces a sequence but omits the requested terminal label leaves an unresolved requirement. A matching quoted mass may be useful context but should not replace a written molecular description.
If the supplier proposes a different terminal form, preserve it as an alternative with its rationale. The researcher should assess the change before it becomes the selected study material.
Carry the agreed form into the material record
Keep the confirmed terminal specification linked to the quotation, received-material identity and any subsequent study documentation. This allows a reader to distinguish what was requested from what the supplier reported delivering.
When a later experiment uses another terminal form, record the difference explicitly rather than treating it as an administrative variation. Whether the forms behave similarly is an experimental question.
A clear request ends with a complete description of both endpoints, any attachments and their locations. It gives analytical identity evidence a precise target to address without claiming that the request itself verifies the delivered molecule.
Sources and further detail
- GenScript — Peptide Modifications (opens in a new tab)
Manufacturer modification catalogue checked for separate terminal categories and attachment options. Used to illustrate specification fields, not to recommend a modification or adopt broad stability claims.
Sources checked 20 September 2026. Request examples are original illustrations, not actual orders, supplier commitments or Novum product specifications. This article has not undergone independent scientific peer review.