Product Development
Supplement Sampling Process: A Practical Buyer Guide
Sampling Process Guide · 6 min read · Published 2026-09-04 · Updated 2026-10-14
A supplement sample is useful when you know what you want to learn from it. Agree the review questions first, then record which taste, texture, appearance or serving features you accept and which need changing.
Keep the sample number with the feedback. Otherwise “the version we liked” can become difficult to identify when the formula or packaging changes.
Decide what this sample round should answer
Choose a manageable set of questions. A gummy round might compare chew and aftertaste. A powder round might compare sweetness using the same preparation method. A capsule review might examine size and the proposed serving count.
Tell the supplier which requirements must stay the same and where you can consider alternatives. The project brief checklist helps collect those inputs.
Record the version before the review
- Sample reference, formula revision and receipt date.
- Pack version, or a note that the sample arrived in temporary packaging.
- Stated storage and preparation instructions.
- Attributes to assess and the person collecting feedback.
If comparing versions, make the preparation and review conditions consistent. Record any differences that might affect the comparison.
Describe what you observe
Write the observation before suggesting a fix. “The aftertaste is too bitter for our brief” is clearer than “change the flavor.” For gummies, record initial bite, chew and surface finish. For powders, record the mixing method, visible dispersion and mouthfeel.
Use the intended customer setting. A powder prepared with a shaker and cold water may produce different feedback from one stirred into a warm drink. Agree which preparation the sample is intended to represent.
Discuss dietary or cultural preferences as specific requirements, not assumptions about an entire market. Ask whether any ingredient change needed to meet them requires another sample.
Example: powder sample feedback
This fictional record shows how to request one clear revision. It is not a customer case or a test result.
| Field | Example note |
|---|---|
| Version | Sample A, formula revision 01; receipt date recorded |
| Preparation | Same sample weight, water volume, temperature and mixing method for both versions |
| Observation | Sweetness is stronger than the agreed reference |
| Requested change | Reduce perceived sweetness; retain the flavor direction |
| Other attributes | Record mouthfeel and dispersion separately |
| Decision | Revision requested; accepted attributes listed individually |
| Contact | One buyer contact consolidates feedback |
Check the pack in the way it will be used
Where a candidate pack is available, review opening, resealing and removing the serving. Record whether the sample uses the final component or a temporary container. Packaging conclusions need to match the pack actually assessed.
Agree the separate testing and stability work. A tasting session cannot establish ingredient content or shelf life. Label wording also needs its own destination review; FDA label-claims guidance is a US reference.
Turn mixed feedback into one revision request
If one reviewer finds a gummy too sweet and another likes it, keep both comments. Before requesting a change, separate what each person noticed from whether they liked it. The agreed product brief gives the team a basis for deciding which feedback should become a development instruction.
“Stronger sweetness than the agreed reference” describes a comparison. “I prefer the sweeter version” records a preference. Food research organisation Campden BRI explains the distinction between sensory characteristics and consumer liking. A few colleagues reviewing a sample can inform your next discussion; their preferences alone do not establish what customers in your target market will prefer.
| Keep in the record | What the supplier needs |
|---|---|
| Sample and preparation | Sample reference and formula version; how it was prepared, handled and stored |
| Observation | The feature noticed and the comparison used, in the reviewer’s own words |
| Preference | Whether the reviewer liked that feature; keep this separate from its perceived intensity |
| Brief requirement | The agreed taste or texture goal that the observation relates to |
| Requested revision | One clear change, accepted features to retain and questions for the developer |
Start by checking whether everyone reviewed the same version in comparable conditions. For a powder, a comment from a cold-water shaker review and one from a warm-drink review belong to different uses. Keep the preparation details beside each comment. If both uses matter to the project, describe them as separate review questions rather than merging them into one result.
Use the words your intended buyers understand. “Less sweet” leaves room for interpretation; a named reference and a description of the difference give the developer more to discuss. For an international team, explain a local flavor comparison or send the agreed reference information. Do not turn one reviewer’s preference into a claim about a whole country.
Where reviewers agree on the observation but disagree on liking, the unresolved question may be the desired taste profile. Settle that goal before instructing the supplier to reformulate. Where the observation itself differs, retain the individual notes and review the sample conditions before deciding that the formula needs changing.
A revision request can name the result you want without prescribing an ingredient change. The developer can explain feasible options and any effects on features already accepted. SGS lists sensory analysis separately from ingredient, microbiological and stability testing. Keep those technical questions with the appropriate testing work; the feedback table is an internal development aid, not a test report.
Send one consolidated feedback record
Separate “accepted for this version,” “revision requested” and “question for technical review.” Name the relevant feature in each line. “Berry flavor accepted; softer chew requested” gives a clearer instruction than “sample approved with changes.”
Ask whether a revision affects other accepted features, testing or packaging. Before production, confirm the formula and pack versions, finished-product specification and any changes made since sample review.
Questions buyers often ask
How many revisions should I expect?
It depends on the formula and requested changes. Agree the sample plan, included rounds and additional revision charges before development.
Does sample approval settle MOQ or timing?
No. Ask for the commercial terms and schedule for the agreed formula, pack and quantity.
Agree the next sample or production discussion
Return the sample reference with your accepted features, requested changes and unanswered questions. Explore the OEM / ODM project path, or contact VITHELO to discuss the sample requirements.