Custom Synthesis

From mg to g in a Custom Peptide Project: Reconfirm the Scope Before Scaling

Increasing requested quantity changes the procurement scope even when the sequence stays the same. A small project can provide useful experience, but it does not automatically settle the price, documentation or format of a larger one. A scale-up RFQ should state what must remain fixed and ask the supplier to identify which assumptions need renewed review.

Define the requested quantity basis

Write the target amount and whether it refers to nominal supplied material or another agreed content basis. Convert units carefully: one gram is one thousand milligrams, but that arithmetic does not establish equivalence between different content bases. Record container arrangement separately. If the larger request combines lots or requires aliquots, identify those conditions explicitly rather than treating them as automatic consequences of the total amount.

Carry forward the accepted structural version

Use the approved sequence, modifications, terminal groups and chemical-form requirements from the earlier project. Do not transfer approval using only a project nickname. Ask for changes to be marked, including revised form or packaging. The supplier’s feasibility assessment should refer to this structure and quantity. A completed mg-scale order does not establish that every larger requirement is available on the same commercial terms.

Scale-up scope comparison
Field Earlier project Larger request
Structure Accepted version Confirm unchanged or mark revision
Quantity Basis and units New amount on explicit basis
Lots Earlier sample connection Proposed lot structure
Analysis Agreed records Current deliverables and coverage
Packaging Container arrangement Required arrangement and feasibility
Commercial Historical offer New price, timing and validity

Reconfirm analytical and document scope

State identity, purity, content or other project-specific requirements separately. Ask whether records will address one supplied lot, several lots or another defined sample scope. Agree which deliverables are included and which need separate evaluation. Do not assume a previous report can support the larger supply. Bachem’s custom-synthesis description lists distinct analytical services, illustrating why scope should be explicit rather than summarized as testing included.

Review format, timeline and price as a new offer

Request a current quotation with price denominator, validity and relevant dependencies. Compare packaging arrangements against laboratory handling needs. Preparation, documentation and delivery periods should retain their conditions. A numerical scale ratio does not justify a promised proportional price or schedule. This article does not publish scale-up capacity, minimum quantity or guaranteed timing for Apex; the individual project must be evaluated and confirmed.

Approve the revised package before proceeding

Use a change card showing earlier scope, larger requested scope and supplier response. Assign technical and purchasing review to the appropriate roles. Save the accepted version and any limitations. If the project changes again, refresh the scope rather than adding quantity to a previous order without review. At receipt, connect the delivered quantities and lot records to the larger accepted package, not just the original sample file.

Before closing this review

  • Unit conversion and content basis are separate.
  • Structural version is explicit.
  • Lot and evidence scope are refreshed.
  • The larger offer has its own approval.

Continue with review project checkpoints; request a revised project scope. 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.