Resources
Peptide Quality Documents: COA, Specification, TDS and SDS
A buyer-focused comparison of peptide quality documents, batch evidence, analytical attachments and document-control questions.
A buyer-focused comparison of peptide quality documents, batch evidence, analytical attachments and document-control questions.
What is the difference between a specification, COA, TDS and SDS?
The specification defines the agreed identity, tests, methods or references and acceptance criteria for a product. The COA reports results or release status for a particular batch against that specification. A TDS summarizes standard product characteristics, application or handling guidance, while an SDS supports workplace hazard communication and safe handling. These records are complementary and cannot substitute for one another. A generic TDS does not prove that a batch passed testing, and a COA without an identifiable specification revision may be difficult to interpret. Buyers should check product name, form, lot number, dates, units, methods, approval status and issuing entity across the document set. Additional analytical records are selected according to material and risk.
- Specification: requirements and criteria
- COA: batch results and release
- TDS: standard technical guidance
- SDS: workplace safety communication
Which analytical attachments may be relevant?
Relevant attachments depend on the peptide, intended use and agreed release package. HPLC or UPLC chromatograms can support purity results, while mass-spectrometry data support molecular identity. Peptide content, amino-acid analysis, water, counter-ion, residual solvent, bioburden, endotoxin or sterility records may be appropriate only for certain grades and projects. The presence of a test name in a marketing page does not establish that it was performed for the supplied batch. Request the method reference, result, acceptance criterion and batch linkage needed for your risk assessment. Raw data may be controlled or redacted, so define access expectations before ordering. When a customer method is mandatory, establish method transfer, comparability or third-party testing responsibilities before approval.
- Purity: chromatographic method and integration
- Identity: mass or sequence-related evidence
- Composition: content, water and residuals
- Special controls: project-qualified microbiological tests
How should document versions and changes be controlled?
Document control prevents a buyer from approving one product definition and receiving another. The specification should carry a revision or effective date, and the batch COA should identify the applicable product and test framework. Retain approved copies with quotations, quality agreements and purchase orders so later lots can be compared consistently. Define which changes require advance notice, including manufacturing site, synthesis route, raw materials, analytical method, acceptance criteria, packaging or storage. A revised document date alone does not prove technical change, so ask for a change summary when the impact is unclear. Electronic files should remain legible, attributable and protected against casual alteration. During periodic review, confirm that supplier contacts, certificates, safety documents and destination-market requirements remain current.
- Version: revision and effective date
- Linkage: product, batch and method
- Notification: defined reportable changes
- Retention: approved records and decisions