Read this guide in
BUYER PROJECT NOTE
Swiss Tabletop Sweetener Samples: How a Prototype Round Works
This guide describes how a prototype round works. It does not report tasting results. That distinction matters: dispatching samples is the start of tasting, not its outcome. What follows is the process — brief, prototypes, documents, dispatch, and the tasting step that comes after — illustrated by a Swiss tabletop sweetener project for coffee, matcha and tea. Use it as the checklist for your own round.
Start with the brief, not with a sample request
A Switzerland-based team worked with Hengliyuan on tabletop sweetener prototypes for coffee, matcha and tea. The brief did not ask for "a sugar replacement" and stop there. It asked to compare several sweetener formulations, and it separated sweetness from aftertaste, cooling sensation, mouthfeel and dissolution. It also asked about prototype documents, shipping and future packaging from the start. That separation is the first step of the process, and it is worth doing before anything is made. "Sugar replacement" is not a sweetness specification: the comparison target has to be clarified in the exchange, not assumed from the phrase. A team that skips this step will compare samples against different targets and call the disagreement a taste difference. Before prototypes are made, define: the drink or drinks, the comparison target, the dimensions to be judged separately (sweetness, aftertaste, cooling, mouthfeel and dissolution), and the document, shipping and packaging questions. You do not need a complete recipe, a final pack design or a confirmed order quantity to begin. Add known ingredient restrictions, packaging, quantity, document and sample needs as they become available.
Prototypes, documents and dispatch are three separate steps
Hengliyuan developed the initial prototypes and sent the corresponding COA, SDS and sample photographs. The buyer acknowledged those files. Sample identity, document scope and transport arrangements were handled as separate steps — and that separation is the point. A document pack is not a sample, a sample is not a document pack, and neither is a shipping confirmation. In this project, the buyer chose to receive the completed prototypes first rather than wait for an additional formulation direction. That was the sample scope agreed for this project, not a rule every buyer must follow. Sequencing is a decision: your round can send completed prototypes first, or hold dispatch until another formulation direction is ready. What matters is that the choice is made explicitly, so the dispatch scope and the next step are both clear. Dispatch itself has a precise meaning here. Hengliyuan dispatched the prototypes, and the buyer acknowledged the shipping update. The buyer already had the COA, SDS and prototype photos before that update. Dispatch closes the making-and-documents stage. It does not close the project.
The tasting step: how to make feedback usable
The step after dispatch is to try the selected formulations in the intended drinks and share feedback. That step is still open in this project, and this guide describes how to run it rather than reporting its outcome. Keep the same sample identity in the document pack and in the trial notes. Coffee, matcha and tea are different bases: compare candidates within each drink rather than treating one drink's result as the answer for all three. Agree the reference and the preparation conditions before interpreting any sweetness difference — otherwise the same sample will produce different verdicts in different hands.
| Record for your project | What to make clear |
|---|---|
| Reference and dose | The chosen sugar or current-formula reference, drink volume and measured sample dose; do not infer a replacement ratio from a product name. |
| Material and documents | Sample code or formula version, batch where available, and the applicable specification or other supplied files. Confirm file scope for the selected material. |
| Preparation and serving | The actual drink base, mixing method, temperature and serving conditions, held consistent for the comparison being made. |
| Useful feedback | Sweetness, aftertaste, cooling, mouthfeel and dissolution observations linked to that sample and drink, followed by the difference you want the next prototype to address. |
Good feedback ends with a direction, not just a verdict. "Too much aftertaste in matcha at this dose" tells the next prototype what to change; "didn't like it" does not. Link every observation to its sample, its drink, its dose and its preparation — or the next round will repeat the same ambiguity.
Documents and packaging are separate decisions
The Swiss project shows a prototype document exchange, not a standard file pack for every order. Tell us which documents your team needs and confirm their availability, scope and matching material. A COA, an SDS and a sample photograph serve different purposes; none replaces your assessment of the finished drink or retail pack. Packaging can be discussed while application trials develop. Keep a bulk blend request separate from a request for filled retail packs, so the sample identity, document needs and later quotation refer to the same agreed route. A prototype round that mixes the two routes will produce samples, documents and prices that do not belong to the same product.
The decision sequence, in one place
The useful lesson of this project is its sequence: define what the drink needs, connect the paperwork to the prototypes, and agree which samples to send. Then taste within each drink, record feedback against the sample identity, and let the next prototype address a named difference. That is the whole process. It works because each step has one job, and no step is asked to do another step's job — documents do not taste, dispatch does not approve, and one drink does not decide for three.
| Step in this project | Why it mattered |
|---|---|
| Clarify the comparison target | The exchange clarified what “sugar replacement” meant instead of treating that phrase as a complete sweetness specification. |
| Connect prototypes and files | The COA, SDS and photographs accompanied the developed prototypes; the buyer acknowledged those files before the shipping update. |
| Choose the dispatch scope | The buyer selected the completed prototypes first, leaving the intended coffee, matcha and tea comparison as the next application step. |
Start your own prototype round
Tell Hengliyuan which drink you are developing and the taste or handling difference you want a sample to resolve. Distinguish your company location, the sample destination and the final sales market when they differ. The first discussion can establish which formulation direction and comparison would be useful, and which documents, samples and packaging questions need answers first.
Common questions
What do we need to define before prototypes are made?
The drink or drinks, the comparison target, and the dimensions to judge separately: sweetness, aftertaste, cooling, mouthfeel and dissolution. Add the document, shipping and packaging questions at the same time, so the round is planned once instead of renegotiated at each step.
Do we have to wait for every formulation direction before samples ship?
No. Dispatch scope is a decision, not a fixed sequence. In the Swiss project the completed prototypes went first and a further formulation direction stayed open. Your round can sequence it either way, as long as the scope is agreed before dispatch.
What documents come with prototypes?
In this project: the corresponding COA, SDS and sample photographs, acknowledged before the shipping update. For your project, confirm which files are available and their scope for the selected material. Documents describe the sample; they do not replace tasting the finished drink.
How should our team record tasting feedback?
Keep the sample identity, actual drink, measured dose, reference and preparation conditions with every comment. Report sweetness, aftertaste, cooling, mouthfeel and dissolution for that sample in that drink, and end with the difference you want the next prototype to address.
Can one drink's result decide for all drinks?
No. Coffee, matcha and tea are different bases. Compare candidates within each drink, and agree the reference and preparation conditions before interpreting a sweetness difference.
Do we need a finished formula and pack design to start?
No. Start with the drink, the final sales market and the comparison goal. Add ingredient restrictions, packaging, quantity, document and sample needs as the discussion develops.
Is a dispatched sample an approval?
No. Dispatch closes the making-and-documents stage and opens the tasting stage. The result of a round is the feedback it produces, not the shipment itself.
What do we send to start a prototype round?
The drink, the market, the comparison goal, and the taste or handling difference you want a sample to resolve. Distinguish company location, sample destination and final sales market when they differ, and add restrictions, packaging, quantity, document and sample needs as available.
