Supplier change control for cosmetic peptide powder: a practical record

Define notification triggers around the attributes used to approve the material. For a cosmetic peptide powder, these can include declared composition, salt form, test methods, manufacturing location and the contact packaging. A change to a specification limit also needs visibility, even if the supplier says the material itself is unchanged. Identify who receives notices and who can approve them.

The practical aim is to preserve the link between a qualification decision and subsequent orders. A sample approved under one specification should not silently become the evidence for a different version. Agree which changes require notification before implementation, what information must accompany a notice and how urgent exceptions are handled. Set the timing in the quality or purchasing agreement; there is no universal notice period established here. Procurement should be able to identify a held revision without having to infer its status from several email threads.

Use a record that compares the approved state with the proposed state and assigns a decision owner. Start with exact material codes, specification revisions and the first expected affected lot. Then describe the change in plain language and identify the evidence that may no longer apply. Avoid accepting a statement such as quality unchanged without knowing what was compared.

ISO 22716:2007’s public scope covers quality aspects of cosmetic production, control, storage and shipment. It provides context for disciplined quality records, but its public summary is not a clause-by-clause change-control procedure and does not certify a raw-material supplier. The workflow suggested here is a purchasing recommendation. Tailor it to the contract and the finished-product responsibilities. Keep supplier facts, proposed actions and your acceptance decision distinguishable so later investigators can tell what was known when the revision was released.

Choose evidence according to what changed and what the original approval relied on. A revised report layout may need a document check. A changed salt form or contact material may affect the basis for formulation or stability work. Decide the comparison question first, then ask for records or testing that can answer it. There is no fixed number of comparison batches that makes every change acceptable.

The ISO/TR 18811:2018 public scope explains why cosmetic stability protocols require product-specific justification. That principle helps avoid copying an unrelated schedule into a supplier change review. Separately, Bachem’s FAQ notes that peptide content and impurity profiles can vary between batches even when production protocols remain unchanged. A numerical difference alone therefore does not identify its cause. Compare results on compatible methods and bases, and document whether the evidence supports the particular change under consideration.

Link the approval to the first affected lot and check that the delivered documents identify the accepted revision. Keep old and new stock distinguishable where the difference matters to use or traceability. If a supplier ships before the review is complete, record the hold or disposition under the agreed process instead of allowing receipt to imply approval.

Consider a hypothetical liner replacement: the supplier retains the powder code but changes the cap-liner material. Your record should connect the new component reference, the compatibility assessment decision and the first packaged lot. This is an example of traceability, not a claim that a liner change always causes a defect. After release, retain the superseded specification alongside the new version with clear status labels. For the next order, purchasing should reference the active specification explicitly, while complaint investigations remain able to reconstruct what was supplied under the earlier version.