Short answer
Organize a perfume formula library with five tools used consistently: a formula code that never changes, a version that changes with every edit, a status that says where the formula is in its life (draft, testing, approved, production, archived), a small number of collections for browsing, and controlled tags for everything else. Mark favorites, lock approved formulas, and archive rather than delete. Then any formula can be found in seconds and nothing approved can be changed by accident.
Codes: the one identifier that never changes
Names change ("Summer citrus" becomes "Riviera"), get duplicated and get misspelled. A code does not. Give every formula a short code at creation — for example a prefix and a number, "EX-001", or a project code and a number — and never reuse one, even for a formula you deleted. Write the code on every trial vial, batch sheet and document.
Accords and bases used inside other formulas get codes too, so a formula can refer to "ACC-014 v3" unambiguously.
Versions and statuses
The code identifies the formula; the version identifies a particular state of it. Every change that alters materials or amounts makes a new version, and old versions remain readable. A status records where the formula stands. A simple, widely used set:
| Status | Meaning |
|---|---|
| Draft | Being written; not yet made |
| Testing | Trials made and under evaluation |
| Approved | Accepted against its brief; locked |
| Production | Made in batches for sale |
| Archived | No longer active, kept for reference |
How to number versions, and when a change counts as one, is covered in perfume formula version control.
Collections: few, and for browsing
Collections are folders. Use them for the one way you most often look for formulas — by project, by client, by product line, or by type (fine fragrance, candles, accords) — and keep the number small. A formula should live in exactly one collection; anything that needs several groupings is a job for tags.
Tags: controlled, not free-for-all
Tags let one formula belong to several groupings: its family ("woody amber"), its market ("US launch"), its constraint ("natural only"), its client. Keep a written list of allowed tags and use only those — free-typed tags drift into near-duplicates that defeat searching. Review the list occasionally and merge any that have split.
Favorites and locks
- Favorites for the handful of formulas you open every day.
- Locks on approved and production formulas, so they cannot be edited or deleted by accident. Changes to a locked formula are made on a copy, as a new version.
Archive, don't delete
Deleting a formula deletes its history — and batch records, notes or other formulas may refer to it. Set old formulas to Archived instead, so they drop out of everyday views but remain searchable. Delete only genuine mistakes, such as accidental duplicates nobody has used.
Naming conventions
- Code first in any list or file name: "EX-001 Riviera v7".
- Descriptive names, not "new formula 3".
- Copies say what they are: "EX-001 Riviera v7 — lower musk trial", not "copy of copy".
- Dates in ISO format (2026-10-09) where they appear in names, so they sort correctly.
Writing these down as house rules is covered in how to standardize formula documentation.
The material library is the other half
Formulas refer to materials, so a well-organized formula library depends on a well-organized material library with one record per material and consistent codes. How to build a perfume ingredient database covers that side.
Maintenance
- Set the status whenever a formula moves on; review statuses monthly.
- Archive formulas untouched for a year that are not in production.
- Check for duplicates (same name, different code) and resolve them.
- Keep the tag list tidy.
In RUŌOD Lab
RUŌOD Lab organizes formulas in collections, with a formula code, a version number, one of five statuses (Draft, Testing, Approved, Production, Archived), tags, a favorite mark and a lock. Duplicating a formula names and marks the copy; version marks never renumber; a locked formula cannot be deleted, and a bulk delete that includes one is refused as a whole. The list can be searched, sorted and filtered, and the same principles apply in any tool. For the wider picture, see the perfume formulation software guide.
Frequently asked questions
Should I organize by client or by fragrance family?
Use collections for whichever you browse by most, and tags for the other. Trying to build both into a folder hierarchy leads to formulas being filed in the wrong place.
How many collections is too many?
If you regularly cannot remember which collection something is in, there are too many. Ten or fewer is a common comfortable range for a small lab.
Written and reviewed by the RUŌOD Lab team. This article is general education about perfume formulation and record-keeping; it is not legal, regulatory or safety advice, and the examples are illustrations, not validated commercial formulas. How we write and check these guides.