THE SHORT ANSWER
A professional e-liquid flavour brief should identify the intended product, market, sensory objective, technical constraints and change-control process. Keep concentrate development, finished-product evaluation and market requirements as separate decisions with named owners.
Who is this briefing guide for?
This guide is for professional product-development and technical teams. It covers the information and decisions needed for a flavour-development conversation. It is not a consumer mixing guide, exposure method or recommendation to use a material in a particular device.
State the product scope and intended markets at the beginning. Explain whether you are exploring a new sensory direction, matching an agreed reference or considering a change to an existing product. These objectives need different information and should not drift into one another without updating the brief.
What should we share with the developer?
Provide the formulation context and relevant technical information through an agreed confidential channel. Identify the material versions, sensory target, restrictions and the people responsible for evaluation and release. Flag information that is still unavailable rather than filling the gaps with assumptions.
Ask what the supplier needs before sending materials. Confirm preparation, storage and handling instructions for any samples. A name shared with a food flavour or fragrance does not establish that the same material can be used in this application.
How should we describe the sensory target?
Separate the desired character from the reference you are using to explain it. Specify which features of a reference matter and which do not. If the objective changes during development, record the revised target and tell everyone working on it.
Keep descriptive observations separate from preferences and technical acceptance. A sample can move closer to the creative direction while other questions remain open. Avoid allowing the word approved to stand in for several different decisions.
What belongs in the change-control record?
Make it possible for another person to identify exactly what changed and why. The following fields are a project record, not a technical specification or a testing protocol.
| Field | Record |
|---|---|
| Project | Product scope and intended market |
| Version | Concentrate and relevant product references |
| Objective | The question this round should answer |
| Change | What changed from the previous version |
| Evaluation | Responsible people, agreed method and observations |
| Decision | Creative, technical and commercial status separately |
Does a flavour sample complete the market review?
No. Development of a concentrate does not by itself settle the requirements for a finished consumer product. MHRA provides guidance on e-cigarette and refill-product requirements within its scope. The responsible team needs to check the actual product, market and current rules.
Do not assume that an existing notification, document or assessment covers a modified product. Assign the review to the appropriate regulatory and technical owners. This article does not determine which notification, classification or other obligation applies to your particular formulation.
How do we approach FÜNK with a professional brief?
Start with e-liquid flavour development and our development approach. Bring the intended use, target and technical questions together. Keep document requirements connected to the selected material and version.
Start a project and state that it concerns a professional e-liquid development brief. Agree the scope, handling and evaluation arrangements before materials are prepared or exchanged.
Sources & further reading
General guidance for project planning. Technical requirements depend on the actual formulation, intended use and market.
