Before Requesting Flavour Samples: A One-Page Brief for Product Development
Define the decision, the product context and the evaluation criteria before requesting the next sample round.
A sample request should make the next decision easier
“Please send a good peach flavour” describes a direction, but leaves the development team guessing about the product and the purpose of the trial. A useful brief connects a sensory ambition to a defined next decision: choose a flavour direction, refine a reference, or select candidates for a pilot.
Public industry guidance describes development as starting with defined objectives and considering formulation, application and market requirements together.[1][2] The practical framework below is Galbora’s editorial proposal for organising that conversation. It is a working document that a product developer and supplier can complete together, even while parts of the project remain undecided.
Separate the project goal from this sample round
A launch objective might be “develop a peach iced tea for the Turkish market.” The first sample round needs a narrower purpose: “compare a fresh-fruit direction with a rounder, ripe-fruit direction in the agreed base.” Those are useful, different decisions.
Write one primary question at the top of the brief. Identify what is fixed, what may change and what is unknown. If sweetness is still being developed, say so. Otherwise, a change in the base can be mistaken for a difference between flavour samples. Record the base version and sample codes so that later feedback remains traceable.
A reusable one-page brief
Copy this table into a project sheet. Keep entries concise; use a controlled attachment for detail. Supplier sample forms commonly ask for application, flavour direction, format and technical requirements.[3] The table adds decision ownership and a defined outcome for each round.
Field | Information to agree before requesting samples |
Project control | Project code, brief version, date, technical contact and decision owner. |
This round’s decision | The single question to answer; what is fixed, flexible or unknown. |
Consumer and occasion | Sales country, target audience, serving occasion and temperature. |
Sensory direction | Two or three desired attributes, unwanted notes and a reference if available. |
Product base | Category and relevant composition ranges; pH where relevant; base version. |
Manufacturing route | Actual or planned process, addition point and known critical conditions. |
Flavour format | Liquid or powder; required dispersion or solubility; carrier restrictions. |
Pack and storage | Intended pack, distribution conditions and target shelf life. |
Market requirements | Intended label wording, allergens, dietary needs and required documents. |
Economics | Target flavour cost per kilogram of finished product; agreed dosage basis. |
Supply and timing | Trial quantity, expected annual volume range, sample date and pilot window. |
Evaluation and handover | Reference, assessors, agreed criteria, feedback date and next decision. |
Use sensory language that another person can act on
“Premium,” “authentic” and “strong” need interpretation. For a peach direction, descriptors such as “ripe flesh, soft floral top note, limited candy character” give a clearer starting point.
Name what the reference is for. A commercial benchmark may illustrate fruit character while its sweetness is intentionally different from the new concept. State that distinction. Share the reference’s identity, batch or purchase date and storage history when available. A reference is useful only if both teams understand which characteristics should be retained and which should change.
Share enough technical context while protecting the recipe
Begin with nonconfidential information: category, desired sensory direction, target market, format and a summary of the production route. Do not put a proprietary recipe in a public comment, open form or broadly circulated presentation.
Where composition affects the work, propose relevant ranges or an unflavoured base first. If those are insufficient, agree who needs the exact formula, through which secure channel and under what confidentiality arrangements. Mark an alternative base as a surrogate and record how it differs. That keeps an early screening result from being treated as evidence for a formula the supplier has never seen.
The brief should also distinguish an intended claim from a verified requirement. In the EU, natural flavouring terminology has specific conditions; a desired label statement needs regulatory review and appropriate supplier information.[4]
Make process, cost and timing usable
“Heat stable” is less useful than describing the process the sample will encounter. Provide the available temperature and holding-time information, sequence of addition, mixing conditions and packaging route. Mark estimated parameters as provisional. Trial planning should connect process conditions with documented objectives.[6]
For commercial comparison, state whether dosage is by mass in the finished product. On the same mass basis, flavour cost per kilogram of finished product equals price per kilogram of flavour multiplied by its mass fraction. Include other relevant costs separately. A lower purchase price does not establish a lower cost in use.
Separate the date samples are needed from the pilot date and intended launch. Ask the supplier to confirm preparation time and availability; record shipping assumptions and approvals that could affect the plan.
Agree what a successful sample round looks like
Define the evaluation question before tasting, and select assessors who can answer it. Descriptive assessment and consumer liking address different questions.[5] An internal technical screen should produce a clear revision direction; it should not be presented as proof of market preference.
Agree the preparation method, reference, serving conditions and coded presentation. For each candidate, record the base version, actual dose and processing history. Use the same defined attributes and record individual observations before group discussion.
An outcome can be “advance,” “revise” or “stop,” with a reason and owner. For example: advance the direction that meets the agreed fruit-profile criteria; revise the candidate with excessive confectionery character; pause a candidate whose documentation is incomplete. Set project-specific criteria together rather than borrowing universal score thresholds.
Passing this round is permission for the next development step. Shelf life, manufacturing suitability, food safety and final labelling still require validation in the intended product and process.
Close the loop with one version and one next action
Return a short feedback record tied to the brief version and sample codes. Describe the observation, its importance and the requested change. “Reduce the lingering candy note while retaining the ripe-fruit character” is more actionable than “make it better.”
If the base, process or target changes, update the brief before ordering another round. Keep one current version accessible to the relevant team. A well-run sample request ends with a recorded decision, an accountable person and a next action—not simply another parcel.
For a Galbora project discussion, start with the nonconfidential fields in this table. Share detailed formulation information only through an agreed private channel.
Sources and editorial note
The field table, examples and sample-round decision framework are original editorial recommendations. The sources provide industry and methodological context; no supplier partnership, proprietary test result or completed product validation is implied.
[1] Symrise — Science-powered flavor creation begins with a project brief [2] dsm-firmenich — Application & Formulation [3] Mosaic Flavors — Flavor Brief — How to request your flavor sample [4] European Flavour Association (EFFA) — Flavouring Legislation [5] Iowa State University Extension and Outreach — Sensory Testing in the Winery: Part 2 [6] Tetra Pak — From idea to commercial product
Comments