COSMETIC SOURCING GUIDE

Peptide OEM/ODM quality agreements: who approves specifications and changes

Hytanbio Tech Editorial · Updated October 31, 2026

A quality agreement should name the decision owner at each handover. Define specification approval, release records, subcontracted work and change control before a project moves into production.

Original equipment manufacturing (OEM) and original design manufacturing (ODM) describe commercial working arrangements. They do not tell a buyer who approves an ingredient specification, accepts a deviation or authorizes a packaging change. Those decisions need named owners and an agreed record.

A useful quality agreement follows the actual work. A raw-material purchase, a cosmetic powder presentation and a finished private-label product will have different handovers. Start with the deliverable being purchased, then assign the quality responsibilities attached to it.

Define the deliverable before assigning responsibility

List what the manufacturer will supply: material, packaging components, finished packs, testing records or a combination. Identify development activities separately from routine production. Include the sites and subcontracted functions relevant to the agreement, where disclosed and applicable.

ISO 22716:2007 covers cosmetic production, control, storage and shipment. Its public scope excludes research and development and finished-product distribution. Referring to cosmetic GMP therefore does not, by itself, allocate every development or distribution duty in an OEM project.

The matrix below is an editorial procurement tool, not a reproduction of ISO clauses or evidence of a supplier’s certification. Adapt it to the actual parties and applicable requirements.

A responsibility matrix buyers can review

Replace the proposed roles with named functions in the signed agreement. A company name alone can leave a decision owner unclear. Include an escalation contact and a substitute approver for time-sensitive issues.

Make specification approval a controlled handover

Connect the commercial and technical versions

Put the supplier SKU, product description, specification number and revision into the purchase reference. Define how the quotation, approved sample and specification relate. A sample approval should identify what was reviewed; it should not silently approve every future claim about the material.

Where a result is reported as purity, assay or content, agree its meaning before acceptance criteria are signed. Our HPLC purity and peptide content guide explains why these terms cannot be exchanged without checking the measurement basis.

Define release evidence and receiving decisions

Specify which records travel with a shipment and which can be retrieved on request. Distinguish manufacturing release from the buyer’s acceptance of delivered goods. Define how a mismatch in batch number, document version or supplied presentation will be handled.

A practical acceptance record links the delivered lot to the agreed specification, accompanying COA and any approved exception. Keeping that link intact is more useful than collecting an expanding folder of documents with no decision recorded.

Write change control around real project events

A statement saying “changes require notification” leaves several questions open. Which changes? Notification before implementation or after? Who may approve? What happens to material already produced? Answer those questions for changes that matter to the agreed deliverable.

• Ingredient identity, composition or approved source changes.
• Specification or test method changes affecting comparability.
• Primary packaging, closure or artwork revisions.
• Manufacturing site or relevant subcontracted activity changes.
• Storage statements, expiry or retest policy changes.

For each category, identify the information needed for review and the point at which written approval is required. Set an agreed response process rather than assuming silence means approval. Keep the approved version accessible to both the project team and the staff arranging shipment.

A hypothetical closure change

Suppose a supplier proposes replacing the closure of a cosmetic powder pack. The notification should identify the old and new component, the reason, supporting compatibility or stability assessment as relevant, proposed implementation date and affected stock. The buyer then records the disposition against the project’s actual requirements.

The change may be acceptable. The record must show why, who decided, and which lots use the new version. An informal message saying the replacement is “equivalent” leaves those points unresolved.

Close the document-access gap

Agree how records can be retrieved if the project contact changes or the commercial relationship ends. Address relevant retention periods through the applicable requirements and contract, rather than inventing one period for every record. Clarify confidentiality, permitted recipients and the process for sharing information with an authorized assessor or authority.

Also separate an immediate containment decision from a completed investigation. An agreement should allow the parties to identify affected lots promptly while the cause is still being assessed. Record the later conclusion and corrective action in the same traceable case.

Prepare the first quality discussion

Bring the proposed deliverable, destination market, current specification, packaging scope and document list. Mark every unresolved responsibility before the production commitment. A short list of named decisions is easier to negotiate than a broad assurance that “all quality matters” are covered.

For peptide OEM, ODM and CDMO support, include the purchased format and the work your team will retain. Use the quality page to outline the evidence required, and the powder stability evidence guide when responsibility for packaging or date statements needs clarification.

Common questions