Quality
How to Set Peptide API Specifications Together With a Supplier

Setting peptide API specifications together with a supplier is a joint technical exercise, not a price negotiation. When procurement and QA ask how to set peptide API specifications with a supplier, the starting point is a shared understanding of the intended use and the analytical methods available. Specifications should reflect what the process can reliably deliver and what the buyer needs for downstream use. Both sides should agree early on which party proposes limits, which party reviews them, and how disagreements are resolved.
The first working session should map each attribute to a method. Purity by HPLC, identity by mass spectrometry or sequencing, counterion content, water content, and residual solvents each require a defined procedure. QA should confirm that the supplier's method descriptions include sample preparation, detection, integration rules, and system suitability. Procurement should ask whether the same methods will be used for release, stability, and customer confirmatory testing. Misalignment here creates disputes later when results differ between laboratories.
Acceptance criteria need a written rationale. For each limit, ask how it was derived: batch history, process capability, compendial requirements, or downstream needs. A supplier that can show trend data across lots is easier to work with than one that offers fixed numbers without context. QA should review whether limits are statistically supported and whether they leave room for normal process variation. Procurement should confirm that the rationale is documented in a specification justification file that can be referenced during audits.
Impurity specifications deserve particular attention. Discuss how specified, unspecified, and total impurities are defined, and whether thresholds align with regulatory expectations for the intended market. Ask how the supplier assigns unidentified peaks and what happens when a new impurity appears. QA should confirm that the supplier has a process for updating the impurity profile when methods improve. Procurement should understand whether specification changes would trigger renegotiation of supply terms or require customer notification.
Water content and counterion specifications are often underestimated. Lyophilized peptides can vary in residual moisture depending on cycle and packaging, and salt form affects mass balance. QA should ask how these attributes are measured and whether limits are tied to stability data. Procurement should confirm that specification limits are consistent with the packaging configuration being purchased. A specification that is tight on paper but unsupported by process capability will generate deviations and supply delays.