Cyclic Peptide Requests: Specify the Bond, Residues and Acceptance Evidence
Cyclic peptide is a family of structural requests, not one complete specification. A supplier needs to know which atoms or residues are connected and what remains free or modified. The buyer also needs to understand what evidence will support the requested topology. Defining these details before quotation helps avoid a product that has the right sequence text but the wrong connection.
Name the bond and the endpoints
State the intended linkage type and identify both endpoints using a numbered sequence and a drawing where appropriate. Do not rely on the word cyclic alone. GenScript’s cyclic-peptide service description illustrates that cyclization encompasses different linkage requests. It is background, not an Apex capability statement. Ask the actual supplier to evaluate the precise structure and explain which parts of the requested scope are feasible.
Control numbering and terminal state
Provide one agreed numbering convention and identify whether terminal groups participate in the ring. Record modifications and any remaining free termini. A drawing and sequence annotation must agree; if they do not, correct the specification before approving work. When the supplier adds a residue or linker to enable a proposed route, review the revised structure explicitly. Do not treat an extra structural element as only a price adjustment.
| Field | Required entry | Review question |
|---|---|---|
| Variant | Project / structure version | Distinct from other topologies? |
| Linkage | Bond type and endpoints | Exact connection defined? |
| Numbering | Annotated sequence | Drawing and text agree? |
| Termini | Free, modified or participating | Any silent change? |
| Evidence | Requested structure-supporting scope | Which question does each test address? |
| Acceptance | Reviewer-approved requirements | Limitations explicit? |
Define the evidence question before choosing a percentage
Ask how the proposed analytical scope addresses the requested bond or topology. Identity support and chromatographic purity are separate questions. A suitable purity result does not automatically answer which endpoints are connected. The project reviewer should decide the evidence needed and identify what remains unverified. Do not assume every general MS or HPLC statement constitutes complete structural characterization of every cyclic isomer.
Compare the proposal against one version
A quote should reference the accepted sequence and connection map, including deviations. If several possible topologies are under discussion, assign each a distinct variant reference and request separate proposals. Keep feasibility assessment, final structure and analytical deliverables together. This reduces the risk that a supplier quotes one variant while the laboratory compares evidence against another. Ask for clarification before accepting an ambiguous combined description.
Leave a structure-specific approval trail
Store the numbered sequence, drawing, quote and acceptance criteria under the same version. Record any scope limitation about connection evidence. Later revisions should show which endpoint or modification changed and trigger appropriate review. This checklist is a laboratory procurement framework, not a biological-performance guarantee or a claim that all requested cyclic structures can be supplied. Confirm availability and analytical scope for the individual project.
Before closing this review
- Bond and endpoints are explicit.
- Sequence and drawing agree.
- Different variants have separate references.
- Analytical limitations are accepted knowingly.
Continue with record terminal requirements; submit a structure review request. Save the relevant product or guide link alongside the written response so another reviewer can reconstruct the decision.
Editorial scope: research-material procurement and document review. Not medical guidance, dosing instructions or a claim of suitability for human use. Requirements and availability must be confirmed for the quoted material.
