Research & Formulation

Sample Version Control: Stop Approving the Wrong Formula

A development project can lose clarity when several almost identical samples circulate at once. Version control connects the bottle on the desk with the brief, the feedback and the decision that belongs to it.

Anadoris editorial concept artwork; not a photograph of a facility or customer installation.
Anadoris editorial concept artwork; not a photograph of a facility or customer installation.

From Anadoris. This guide comes from the team behind Manufacturing & Development: formulation, packaging and production for other brands, from brief to finished batch. About the group.

Give every sample a usable identity

Agree a sample code with the development team and put it on the container and the accompanying record. Include the date and the intended purpose of the round. Avoid naming everything final, improved or latest; those labels stop being meaningful as soon as another version appears.

Record which formula version and packaging configuration belong together. A sample in a temporary lab container may be useful for a sensory review, but that should not be confused with an approved commercial pack. State the limits of the sample clearly so different reviewers do not assume different questions have been settled.

Attach feedback to the version

Collect comments under the exact code rather than in disconnected message threads. Ask the reviewer to state the use context and the specific observation. Where a photograph is useful, show the identifying label as well as the detail being discussed so the image can be connected to the right sample.

Keep the decision status explicit: under review, changes requested, approved for a defined next step or superseded. Approval for further development is different from release for commercial production. The quality and technical teams should define their own release requirements rather than allowing a broad “looks good” message to stand in for them.

Close a round before opening another

Summarise the agreed feedback and name the owner of the next action. Preserve a record of what changed and why. When several stakeholders disagree, resolve the decision against the brief instead of asking the lab to infer a compromise from conflicting messages.

Before an approval meeting, ask every participant to confirm the same sample code. This small check prevents a familiar failure: one person approving the new texture while another refers to the previous fragrance. A clear record saves discussion time and gives the next team a reliable account of the decision.

Questions

Is a sample code enough on its own?

No. It needs to connect to a record containing the version, purpose, feedback and decision status. An isolated number does not explain what has been approved.

Can a sensory approval release production?

Not by itself. Commercial release should follow the organisation’s defined technical, quality and regulatory requirements and the authorised approval process.

Your next chapter

Talk to the team behind this.

Manufacturing & Development: Formulation, packaging and production for other brands, from brief to finished batch.

Discuss manufacturing