Custom Synthesis

Multi-Chain Peptide Projects: A Chain Map Before a Synthesis Quote

A multi-chain project needs a map, not only several sequence strings in one message. Define each chain and the intended connections, then state whether the deliverable is separate chains or an assembled material. That distinction affects the quantity statement and analytical scope and should be settled before quotations are compared.

Assign stable chain identifiers

Use chain A, chain B or another consistent scheme and attach a complete structure to each. Include termini, stereochemistry and modifications. Number residues within each chain and preserve any source-reference mapping separately. A supplier should not have to guess where one chain ends or whether a line break is merely formatting. The hypothetical worksheet demonstrates identifiers, not a validated target or a claim that the example is a feasible assembly.

State connections with both chain and residue

For an interchain connection, specify the two endpoints, connection type and relevant structural detail. For intrachain connections, identify the chain as well as the positions. A total bond count does not encode the map. Keep covalent assembly distinct from a requested mixture of independent chains. Do not use assembled peptide and chain blend interchangeably simply because the same sequences are present somewhere in the preparation.

Fictional chain-map notation; not a synthesis design
Field Illustrative record Review question
Chain A Full sequence and positions A1…An Termini and modifications explicit?
Chain B Full sequence and positions B1…Bm Independent identity defined?
Connection A-position ↔ B-position; type stated Endpoints match accepted map?
Delivered state Separate chains or assembled target Not an ambiguous mixture description
Evidence Chain scope plus assembly scope Which questions remain open?

Define the actual delivered state

Ask whether the offer covers separate chain materials, an intended assembled target or both. If the laboratory requests components and final material, give them independent line identifiers, amounts and documents. Equal total mass does not establish the amount of a particular assembled identity. Keep any proposed assembly limitations explicit rather than converting a target description into a claim that every delivered molecule has the intended connection pattern.

Choose evidence at the correct level

Chain-level reports address component samples; they do not automatically establish the finished assembly. Ask which records address the requested connections and assembled identity, and let the laboratory decide the necessary scope. Keep purity and quantity bases clear for the actual deliverable. If only partial characterization is feasible, retain that limitation and obtain review before treating the project as meeting all acceptance requirements.

Version the map before synthesis approval

Attach the accepted chain map to the quote and retain a revision history. Changes to a chain, terminus, connection endpoint or delivered state require a marked proposal. Avoid relying on an old drawing if a later sequence file differs. The final schedule should let receiving staff reconstruct the target and match its documents without solving a structural puzzle. This is a definition framework, not an assembly protocol or guarantee of synthesis outcome.

Before closing this review

  • Chain identifiers and numbering are stable.
  • Connections include both endpoints.
  • Mixture and assembled identity are distinct.
  • Component records do not certify the assembly.

Continue with prepare the project RFQ; review the project planning guides. 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.