Give every sample a stable identity
Start an approval record with the supplier sample code, date received, product direction, and any visible format description. Do not rename a sample casually when it moves between tasting, packaging, and document discussions. A stable code lets the buyer compare feedback and supplier responses without relying on memory or an image filename.
The record can include a supplied product photograph as a visual reference, but the photo should be labelled for what it visibly shows. It does not replace the sample code, product information, or batch-specific evidence. This distinction is especially important when several products use similar colours or ingredient forms.
Document preparation before recording opinions
Write the water or base, quantity, temperature, steep or mixing time, vessel, sweetness additions, ice, and serving format used in the review. If a cafe or retail route is being tested, prepare the product as closely as possible to that intended route. Without these conditions, sensory feedback may be difficult to repeat.
Record observations in clear language: aroma, liquor colour, appearance, texture where relevant, flavour direction, finish, and application fit. Separate an observation from a preference. For example, a reviewer can observe visible fruit pieces and separately state whether the target channel prefers more or fewer pieces.
Collect one controlled decision
Invite relevant reviewers to comment, then consolidate the result into a single buyer decision: advance, revise, pause, or decline. List the reason, requested change, and decision owner. This keeps a supplier from receiving contradictory instructions from different internal stakeholders.
Approval can also be conditional. If the tasting direction is accepted but packaging, label, or document questions remain open, state that clearly. A conditional decision is more honest and more useful than calling a route final before the connected workstreams are ready.
Track evidence questions separately
Use a dedicated section for questions that tasting cannot answer: current specification, ingredient identity, allergen information, storage discussion, packaging inputs, and any market review required by the buyer. Assign an owner and next action to each question. Avoid using a product photograph or a general supplier statement as proof that the question has been resolved.
Commercial terms, production timing, certification availability, and shipment details should also remain outside a sensory approval unless current written information has been reviewed for the defined project. The record should show what is known, what is requested, and what is still subject to confirmation.
Create a usable handoff
Before the project moves to packaging or a next sample round, save the record with the sample code, preparation notes, feedback summary, decision status, evidence questions, and supporting files. Link the relevant product page and buyer brief so a colleague can understand the route without rebuilding the conversation from messages.
This approach improves both speed and accountability. It does not create a promise about the finished product; it creates a transparent decision trail that can be updated as the sample, pack, or market requirements change.