Create a sample evaluation record
A useful evaluation begins with a record that identifies the sample and the question you are trying to answer. Use one record per version. If several people evaluate it, keep their observations identifiable and combine the priorities before returning revision instructions.
Copy this record into your project notes:
Project / product:
Sample ID and version:
Date received:
Carrier or base, if known:
Stated concentration, if known:
Intended application and agreed instructions:
Evaluator and evaluation date:
Evaluation setting and conditions:
Comparison reference and its version:
Observation times or stages chosen for this evaluation:
Scent character observed:
Desired features that are present:
Differences from the brief or reference:
Application / base experience:
Packaging or dispensing observations, if applicable:
Features to retain:
Changes requested, in priority order:
Open questions for the developer:
Decision: revise / provisionally accepted / approved for the stated scopeUse the same reference and a consistent setting when comparing versions. Unknown formula details can remain “not provided”; they should not be guessed from the scent or appearance.
Evaluate against the intended application
Follow the agreed instructions for the particular sample. An evaluation strip can be part of a perfume scent discussion, while shampoo, cream, home fragrance and other applications need their own agreed use and assessment method. Do not use a development material on skin, hair or in another application unless it is identified and instructed for that use.
Record the scent direction, the features you like or dislike and the gap from the brief. Separate those observations from the base feel, appearance, dispensing and packaging. A perfume, rinse-off product and solid balm can carry a related scent identity while creating different experiences. This buyer evaluation record does not replace an agreed safety, stability, compatibility or other technical checking programme.
Write actionable revision feedback
Tell the developer what should stay before listing changes. Give each change a priority, a reference point and the conditions in which you observed it.
| General reaction | More useful revision direction |
|---|---|
| “Too sweet” | “Keep the floral middle; reduce the sweet opening relative to reference A.” |
| “Not premium enough” | “Retain the clean wood character; make the fruit impression less prominent.” |
| “Does not last enough” | “At the recorded observation point, the intended dry character is less noticeable than reference A under the same conditions.” |
| “Wrong texture” | “The scent direction is accepted; the base feels heavier than the agreed reference.” |
These examples show feedback structure, not instructions for a specific formula. If several requested changes conflict, rank them so the next sample has a clear target.
Approve the reference and remaining conditions
Approval should name the actual accepted version and what has been approved. Copy this short confirmation when the scope is ready:
Project / product:
Approved sample ID and version:
Formula / base / concentration reference, as applicable:
Approved characteristics and intended application:
Linked fill and physical pack specification version:
Linked artwork version:
Approved by and date:
Approval scope:
Remaining conditions before production:
Required checks / documents still to confirm:
Quantity and delivery items still to confirm:A scent approval can be recorded while a pack decision remains open, provided the open item is clear. The final production confirmation should connect both. Do not interpret a general “we like it” message as approval of every formula, packaging and delivery condition.
Keep development and production confirmation linked
When a formula, carrier, concentration, fill, dispenser or pack changes, review the approval items affected by that change. Keep the older versions so the team can understand which reference is current. The quality discussion can then establish the agreed checks against that production reference.
This guide helps the buyer evaluate and communicate. The separate sample process covers arranging samples, development scope, fees, revisions and scheduling with Fravanta. Send your feedback or sampling brief with its sample ID or the fragrance brief so the next discussion has a clear starting point.
At our factory, the accepted sample and formula version connect to the raw-material and component references, first-piece confirmation, in-process checks and batch record. We retain batch samples for three and a half years to support traceability. If a reorder or quality question arises, send the batch and approved sample references so we can compare the relevant records and retained material.