Cosmetic formula changes: keep the product, lot and evidence on the same version

A file date is not a product version

A newer PDF is not necessarily evidence about a newer formula. A laboratory may reissue a report to correct an address while leaving the tested sample unchanged. A supplier may change a formulation before updating its supporting documents. These are different events, and they should not be represented by one “last updated” date.

The workflow below is our recommended operational approach. It is not a claim that cosmetic law prescribes a particular software system, identifier format or approval sequence. Its purpose is to make the evidence understandable when commercial, manufacturing and document changes happen on different schedules.

The need for that distinction is visible in established references. FDA’s cosmetic self-inspection checklist discusses written production instructions, material and batch identity, and control records. The checklist is guidance for self-inspection, not a substitute for identifying applicable binding requirements. FDA’s GMP checklist.

Give different things different identifiers

Use a product identifier for the commercial item, a formula reference for composition, a packaging reference for the relevant configuration, and a lot identifier for a particular manufacturing batch. Give documents and review decisions their own identifiers. One record can then point to several related records without forcing them to share a lifecycle.

For example, Product BA-014 might continue to be sold under the same name while Formula F-03 replaces F-02. Several lots may use F-03. A report issued as revision 2 may still concern a sample made with F-02. This is an invented illustration of the record structure, not a production record or a prescribed numbering scheme.

The structure should make a basic question easy to answer: “Which formula and package were used for the lot in this request, and which exact documents were reviewed?” If that answer requires someone to remember which email thread contained a substitution, the relationship is not yet adequately recorded for operational use.

• Product: the item the business recognizes and markets.
• Formula: the identified composition supplied or manufactured.
• Package: the identified configuration relevant to the question.
• Lot: the particular batch connected to manufacturing and sample records.
• Document: the exact issued file and its revision history.
• Review: the decision, scope, conditions, reviewer and evidence considered.

Describe the change before deciding its significance

Our suggested change record begins with facts: what is changing, why, who proposed it, when it is intended to take effect, and which products or lots may be affected. Separate confirmed details from assumptions. If a supplier says a material is “equivalent,” request the supporting identification and explanation instead of treating the adjective as the assessment.

The initial coordinator does not need to decide whether every change requires testing. The coordinator needs to route a sufficiently clear description to the person who can decide. That distinction keeps the process useful for a small brand without transferring scientific judgment to whoever happens to receive the supplier email.

Changes worth describing can include composition, ingredient source, manufacturing site, process, contact packaging, intended use and labeling. This is a suggested intake scope, not a rule that each listed change has the same consequence. The reviewer may find a change immaterial to one report and important to another.

Do not use the ingredient list as the whole formula history

A consumer ingredient declaration and a formulation record serve different purposes. FDA’s labeling summary describes ingredient-declaration requirements, including ordering and permitted exceptions. A label therefore should not be treated as a complete manufacturing formula or a record of every supplier decision. FDA’s labeling summary.

In practical terms, compare the records relevant to the change, not just the text visible on the carton. Two versions can look similar to a shopper while the manufacturer is asking you to accept different underlying materials or proportions. Ask the supplier to explain the change in the records it controls and connect that explanation to the product.

Likewise, a new marketing claim deserves its own review even if the formula remains unchanged. Intended use affects US classification; FDA gives examples of products regulated as both drugs and cosmetics. Route claim changes through the appropriate review instead of assuming that a stable formula means a stable regulatory position. FDA’s classification explanation.

Review applicability instead of deleting older evidence

Create a list of records potentially affected by the change. This might include an ingredient statement, a study, a specification, artwork, or a previous supplier declaration. Mark applicability as awaiting review until the authorized person records the conclusion. The older evidence still describes what was issued or tested; it should remain available as history.

EU safety-report guidance gives a concrete example of why identity matters: it calls for evidence that the composition tested for stability corresponds to the product placed on the market. That provision is an EU reference. We use it here to illustrate the broader operational value of showing what a study actually examined, not to impose an EU dossier on every US brand. European Commission Annex I guidance.

A review can distinguish evidence that still applies, evidence that applies only with an explanation or condition, and evidence that does not support the changed configuration. Preserve the reasoning and the evidence used to reach it. Do not infer that every change automatically invalidates every document, or that a prior acceptance automatically carries forward.

A hypothetical fragrance substitution before a reorder

Imagine a body lotion manufacturer proposing a fragrance substitution before the next production run. The product name and packaging artwork have not changed. The supplier forwards an updated ingredient statement and says the earlier testing remains usable. This scenario is hypothetical; it is not a technical judgment about fragrance substitutions.

The brand opens a change record and asks the supplier to identify the old and proposed formula references, the affected material, the intended implementation point and the basis for its statement about existing evidence. The coordinator attaches the existing reports without altering their sample identifiers.

The reviewer then assesses the relevant information and determines what further explanation, review or testing is needed. Any label or claim implications are routed to the appropriate person. The production plan and commercial deadline remain visible, but neither is treated as evidence that the proposed version is ready.

If the change proceeds, the record links the implemented formula to the affected lots and the reviewed documents. If the supplier later corrects the ingredient statement, that becomes a document revision linked to the same change history. The team can explain both what changed in the product and what changed in the paperwork.

Make acceptance specific to a purpose

We recommend that each review decision name the request or decision it addresses. “Accepted for this retailer ingredient request” is narrower than “product approved.” A reviewer may accept an ingredient statement as a response to one question while another evidence gap remains unresolved. The system should show both facts.

Capture the reviewer, date, document revisions considered, conclusion, conditions and follow-up. If the decision relies on a supplier clarification, include that clarification in the record rather than leaving it only in someone’s inbox. A future colleague should be able to understand the decision without reconstructing the conversation from fragments.

When something changes after acceptance, retain the earlier decision and open the new review. Do not silently revise the historical conclusion to make it appear that the reviewer considered information that arrived later. This approach supports an honest account of what was known and decided at each stage.

Freeze the evidence set used in an external response

Before sending a response to a buyer, distributor or other authorized recipient, record which versions it contains. Retain the request, the shared files or their stable references, the relevant review decision and any stated limitations. A live folder that changes every week may be useful for collaboration, but it is not by itself a record of what was sent.

Be precise about administrative evidence too. A registration or listing confirmation is distinct from the scientific reports and product-specific decisions in the same response. Avoid using a broad package title that suggests all those documents establish the same conclusion.

If a correction is needed after sharing, preserve the earlier response and document the replacement. Identify the affected item and explain the scope of the correction. This prevents an updated file from circulating without anyone knowing whether it replaced a spelling error, a formula reference or a substantive result.

Start with one product and a retrieval exercise

Choose a product with a recent change and reconstruct its history. Find the request, the supplier explanation, the before-and-after identifiers, the review decision and the first affected lot if applicable. Record missing links as open work. This is a practical starting exercise rather than a maturity score or regulatory audit.

Then make the next change easier: agree identifier conventions with the supplier, assign an owner for each review question, and establish how corrections are issued. A consistent process is more valuable than a complicated naming scheme that only one person understands.

BeautyAssured supports document collection, supplier follow-up and review context for beauty brands. Its role is to keep the evidence and its status understandable. The responsible people still decide whether a change is acceptable and whether the available evidence supports the product or request in question.