Custom fragrance projects rarely arrive late because production was slow; they arrive late because the calendar was built from the brief forward instead of from the launch date backwards. The phases that stretch schedules are the ones with fixed durations — stability testing, sampling rounds and document review — and every one of them can be planned for. For a kids-safe line, the closure evidence and the restriction review add two more early milestones that a generic timeline will simply not show.
Key takeawaysSample rounds, stability testing and paperwork review are the phases where lead times stretch — production itself is usually the most predictable part. · Two kids-safe milestones sit at the front of the schedule: the ingredient restriction review and the closure specification [1]. · Stability has a fixed duration, which makes it the anchor of the whole calendar once it is booked. · Custom development adds sample rounds that an adapted-base project does not have, which is why ODM timelines differ by model. · The realistic plan is built backwards: launch date first, then each phase's deadline, then the brief.
Every fragrance brand has heard the same story: the scent was approved on time, the pack was beautiful, and the launch still slipped by two months. The cause is almost always the same — the schedule treated the factory's billable work as the project, and ignored the phases that run on their own clocks: stability, closure testing, document review and import planning.
This article maps those clocks for an OEM/ODM project, with the extra milestones a kids-safe format adds, so you can build a calendar that survives contact with reality.
The phases, and where the time actually goes
A custom fragrance project has seven phases of uneven length. Three of them — brief, pack specification and final QC — are short and controllable. The other four — restriction review, sampling, stability and documentation — have their own pace, and they are the reason realistic timelines look so much longer than optimistic ones.
For a kids-safe line, two extra early milestones appear: the ingredient restriction review locks the material profile before sampling, and the closure specification locks the pack before testing. Both are cheap in calendar terms if planned — and expensive if discovered midway. The restriction review is the earliest of them: checking proposed materials against the published frameworks the industry works to, such as the IFRA standards for fragrance materials, is a milestone of its own [1].
The timeline map
| Phase | Typical pace | What it produces | What stretches it |
|---|---|---|---|
| Brief and feasibility | Short — days to a week | Agreed specification and quote basis | Unclear market list or format |
| Restriction review | Short to medium | Written ingredient review | Materials outside the factory's usual library |
| Sampling rounds | Medium, repeated | Approved physical sample | Slow decisions between rounds |
| Pack specification | Short | Itemised pack quotation | Custom moulds instead of stock formats |
| Stability and compatibility | Longest, fixed duration | Test reports that mature over time | Late start — the duration cannot be compressed |
| Documentation assembly | Medium | Complete per-market file | Layers that were never scheduled |
| Production and QC | Predictable | Shipped, inspected goods | First-run process surprises on new formats |
The map's message is simple: the two longest rows — stability and documentation — are the ones that decide the launch date, and both are decided by decisions taken in the first two rows.
Building the calendar backwards
The backwards plan takes the launch date as fixed and works out what has to be true before it. Start with the shipment and inspection windows, subtract production, then documentation, then stability — which has a fixed duration and therefore a hard start date — then sampling, then the brief. The date the calendar lands on is the real project start, and discovering it early is the whole point.
Once the calendar exists, test it against the three classic slippage points. First, sampling: each round takes days, but the time between rounds is where weeks disappear, because decisions are made by humans with other jobs. Set a decision deadline for each round. Second, stability: it runs on its own clock once booked, so the mistake is waiting for final sample approval to book it. Third, documentation: a file assembled as the project runs is finished when production is; a file started at the end is finished weeks later.
A kids-safe brief tightens the first slippage point specifically: the restriction philosophy and the closure requirement are declared in the brief, so the sampling decisions have fewer open questions to stall on. That is one of the few ways this category actually moves faster than a standard launch.
What to ask for in the first quote call
Ask the factory for its own phase estimates in writing, then compare them with the map above. A factory that separates sampling, stability and documentation into distinct lines knows where its own time goes; one that quotes a single 'development' lump is hiding the schedule inside the price.
Choosing a partner that keeps the calendar honest
The timeline conversation is also a supplier-evaluation conversation, because the factory's answer reveals how it is organised. A custom fragrance development partner (custom fragrance development partner) that starts the clock on stability with your first acceptable sample and assembles documents as it goes is a partner whose calendar you can trust; one that starts both at the end is a partner whose calendar will disappoint you.
The same logic applies to the model you choose. A full-service partner offering scent development and manufacturing as one scope (scent development and manufacturing partner) removes the hand-off between developer and factory, which is where lead time is quietly lost on fragmented projects — for a kids-safe line, that hand-off is also where the file can lose its thread.
And when the service in question is custom fragrance manufacturing (custom fragrance manufacturing) under an OEM/ODM umbrella, the practical test is whether the factory quotes the timeline the same way it quotes the price: itemised, with the long phases visible. The transparency of the calendar is the transparency of the whole relationship.
A realistic timeline is not the pessimistic one; it is the one with the fixed-duration phases scheduled first. When a launch slips, it slips by exactly the amount of time that was never put on the calendar. Put stability, closure testing and documentation on it from day one.
Sources
- IFRA Standards Library (International Fragrance Association) —— The IFRA Standards Library lists the restrictions the fragrance industry applies to individual fragrance ingredients, based on safety assessments; it is the reference point for compliant fragrance formulation.
Frequently asked questions
Which phase of a fragrance project takes the longest?
Stability and compatibility testing, because it has a fixed duration that cannot be compressed — the product has to be observed over time. Everything else, including production, can usually be moved; the fixed-duration phase is the one your calendar should be built around.
Why do sampling rounds stretch the schedule more than expected?
The rounds themselves are fast; the time between them is not, because each round ends with a decision that involves people with other responsibilities. Setting explicit decision deadlines for each round is the most effective schedule control available to a buyer.
Does a kids-safe line take longer to develop?
It adds two early milestones — the ingredient restriction review and the closure specification — but both fit early in the timeline, where slack usually exists. What stretches the schedule is late discovery: finding a restriction or a closure requirement after sampling starts. Declared in the brief, they cost almost nothing.
Is ODM faster than OEM?
For the first sample, usually yes, because ODM builds on existing bases rather than developing from scratch, so sampling rounds are fewer. Over the whole project the difference shrinks — stability and documentation run the same for both models — but the front of the calendar is genuinely shorter.
How early should I start stability testing?
On the first acceptable sample, not the final one. Stability has a fixed duration and its report is needed for documentation, import and sales. Booking it early lets the design work happen while the test runs, which is the difference between a launch date and a hope.