Fragrance sample approval should convert a subjective smell decision into a traceable production reference. Codes, formula revisions, evaluation conditions, consolidated feedback and sign-off prevent the wrong sample from reaching filling. The process must distinguish exploration, revision and final approval.
Code every sample and revision
Use a project code, direction, revision and date that appear on the vial and evaluation sheet. Do not approve “the blue one” or rely on courier sequence. Keep the supplier's formula reference linked internally while evaluators can remain blind to concept names during preference testing.
Standardize the evaluation
Specify substrate, application amount, time points and environment. For perfume, assess blotter and skin; for candles or diffusers, evaluate the intended base and room. Record opening, development, dry-down, diffusion and brief fit separately. Avoid comparing samples received or rested under different conditions without noting it.
Consolidate useful feedback
Appoint one decision owner to resolve conflicting comments before they reach the perfumer. Reference the exact code and observation time, describe the desired change and name what must remain. Rank mandatory corrections separately from optional preferences so each revision answers a controlled request.
Approve the finished configuration
Final scent approval should use the intended concentration, carrier and relevant packaging or delivery system. Complete required stability, compatibility, performance and compliance review before mass production. A fragrance compound smelled neat is not an approval sample for a filled consumer product.
Close approval with evidence
Use a signed record naming code, revision, product, concentration, date and authorized approver. Retain sealed references under defined storage and link them to the finished specification and purchase order. If the formula, fragrance dose, base or critical component changes, document impact and obtain renewed approval where necessary.
Write the criteria before you smell anything
Criteria written after sampling tend to describe whichever sample was preferred, which turns an evaluation into a justification. Written first, they make a decision defensible to someone who was not in the room. A usable brief states:
- Audience and price position — who buys it and at what shelf price.
- Reference territory — the olfactive direction, expressed as a family or a comparable rather than a single named product.
- Exclusions — notes or effects that disqualify a submission regardless of how well it performs otherwise.
- Application and concentration — the same accord reads differently as eau de toilette and extrait, and differently again in oil or in wax.
- Channel — a product judged at a counter and one judged from a photograph are not scored the same way.
Why references are coded
A name carries expectation into the evaluation. Coded references are judged on what they smell like rather than on what they are called, which is what makes a second opinion meaningful and what allows a decision to be repeated later. The approved sample keeps its code, and that code — tied to a specific concentration, base and pack — becomes the reference production is measured against at release and on every reorder.
Budget the revision rounds
Sampling cost sits outside unit cost, and an unbudgeted revision loop is the most common overrun in a first project. Two questions settle it before it becomes a dispute: how many rounds are included before charges begin, and how long each round takes including shipping in both directions. Distance matters here — a route that adds a week per round changes what the schedule can absorb.
Sample kit contents, charges and dispatch time are confirmed per project rather than published.
Project checklist
- Unique sample and revision code
- Controlled evaluation conditions
- Single feedback owner
- Mandatory versus optional changes
- Final-base evaluation
- Signed approval record
- Retained reference sample