Knowledge · Formulation Management

Cosmetic formulation versioning: control variants with traceability instead of filenames

Formulation development depends on change. The problem is not that many versions exist, but that teams later lose why a variant changed, which tests belong to it and which version was approved. Structured versioning turns development history into usable knowledge.

By VYVA Editorial TeamEditorial policyUpdated: September 4, 2026

In short: what is formulation versioning?

Formulation versioning stores every relevant formula change as a traceable version with time, author, reason and links to tests, batches and approvals. A version is therefore more than a new filename.

Key takeaways

  • Separate version from trial variant
  • Record the reason for change
  • Attach tests to a specific version
  • Mark the approved version explicitly
  • Enable side-by-side comparison

See it with your own data

In 30 minutes we walk you through the workflow using your formulas and raw materials. No obligation, reply within one business day.

A filename is not version history

Names such as Final_v7_new.xlsx work only with very small teams. Once variants run in parallel, context disappears. A proper history captures which version came from which and why.

Branching instead of a purely linear history

Formulations often evolve along several trial branches. Two variants may test different emulsifiers or concentrations at the same time. A strong system can preserve those branches and later consolidate the preferred path.

Tests and batches belong to the version

Stability, sensory or compatibility results are meaningful only when tied to the exact formula and lab batch. Versioning is the foundation of reliable test history.

Approval is a status, not another file copy

The approved formula should emerge from the development history with decision, reviewer and timestamp. Teams can then see which alternatives were rejected and why.

Manual vs. structured versioning

IdentifierFilenameUnique version ID
Reason for changeFree text/memoryStructured history
ComparisonManualVersions comparable
TestsSeparate foldersDirect version link
Approval"Final" fileDocumented status

Frequently asked questions

Disclaimer: This article is for general information only. It is not legal advice and not a regulatory or safety assessment of any individual case. We prepare the content carefully but give no warranty as to its accuracy, completeness or currency; legislation and standards may change after the date stated. Only the officially published text is binding. Make decisions about your products with qualified support, such as your safety assessor or legal adviser. We are liable for damage arising from the use of this information only in cases of intent and gross negligence; liability for injury to life, body or health and under mandatory statutory provisions remains unaffected.

Questions about your specific use case?

Schedule a personal demo or contact our team directly.