Gia Lai Coffee Export: Sample Approval and Lot Traceability
Sample approval is the point at which a buyer records what was actually evaluated. Traceability is the record that connects that evaluation to a defined coffee identity and later movement. For Gia Lai coffee export, the two controls should use the same identifiers. Approval of an unlabeled sample, or approval that does not state its scope, creates room for a later substitution to be mistaken for the accepted coffee.
State the decision the sample is meant to support
Before sending or receiving a sample, write its purpose. It may be a type reference, a pre-shipment sample, a production-lot sample or a retained comparison sample. Each purpose has a different meaning. A type reference helps a buyer decide whether to continue. A lot sample supports a decision about a defined lot. Do not let a generic sample silently become a shipment approval.
Include the intended product form, use, destination and review stage. Add the requested roast or test method, the people who will review it and the date by which the result is needed for planning. These fields keep a sample from being judged against an unstated standard and help the supplier select a sample that answers the buyer’s question.
Label and retain the physical sample
The label should carry the supplier reference, buyer reference, date received, sample purpose, product form, crop or period if supplied and any lot or batch connection. Record packaging condition and quantity. Photograph the label before opening when practical. Assign a retained portion under the buyer’s control so that a question about the evaluation can be revisited.
Do not remove the supplier code after adding an internal code. Keep both in the working record. If the sample is divided, note the new container references. A sample that has lost its identity cannot reliably support a later traceability check, even when the cup notes are detailed.
The ISO 4072 sampling standard provides a primary reference for sampling green coffee in bags. Its availability does not choose a method for every transaction. Agree a method appropriate to the lot, record who performed it and state any limitation. For a technical laboratory method, consult the competent laboratory or the applicable standard owner.
Write a repeatable approval note
An approval note should identify the sample, date, reviewer, method, preparation, observations, decision and scope. State whether the result is approved for further commercial discussion, approved as a reference, conditionally accepted or rejected. If the buyer uses a score, include the scale and the meaningful observations; a score without method is difficult to interpret later.
Record what the approval does not cover. It may not cover a changed process, a different lot, a different packaging condition or a later crop. This boundary is not a weakness. It tells both parties when a new sample or a targeted confirmation is needed.
Keep the note next to the specification version reviewed. If the specification changes, flag the approval for review. A small change in product reference can have a larger effect than a small change in prose, so the code and version should be visible at the top of the record.
Connect the sample to the proposed lot
Ask how the sampled coffee maps to a lot or assembly. The mapping may use intake references, processing batch, warehouse or packing codes. The buyer should not invent a connection. If the supplier cannot yet provide a final lot, mark the sample as pre-allocation and set a later confirmation gate.
The ITC Coffee Guide treats traceability and quality controls within the broader coffee trade workflow. Use it for process understanding, then obtain the transaction-specific mapping from the parties responsible for the coffee. A public description should not claim a lot connection that the controlled file cannot show.
When codes change, maintain a cross-reference table. Include old code, new code, reason, date and confirming role. If a lot is blended or reprocessed, record the event and determine whether the original approval still applies. A changed identity may require a new sample, even if the product name remains unchanged.
Set reapproval triggers before the shipment stage
Reapproval is a decision rule, not a prediction. Define triggers such as a new lot, changed process, changed specification, material storage event, failed test or a destination requirement that was not in the original brief. The quality team decides which triggers are relevant to its risk.
Make the trigger visible to purchasing and the supplier contact. A buyer can then ask one precise question: does this event fall inside the approved scope? If yes, the record should say why. If no, request a new sample or additional evidence. Avoid a blanket statement that an approval remains valid forever.
Keep sensory and technical evidence together but distinct
Record roast method, sample preparation, rest time and evaluation participants. Note observations that matter to the intended product, such as behaviour in the blend or the consistency across repeats. Keep physical measurements and documents in linked sections rather than merging them into one “quality” number.
Sensory notes are not a certificate of origin, and a traceability record is not a sensory guarantee. A strong file lets the buyer see how both types of evidence contributed to the decision. This is especially important when a sample is used for a regional story: the story can explain context while the approval note remains about the tested coffee.
Use a traceability ledger
| Event | Reference | Evidence | Review action |
|---|---|---|---|
| Sample received | Supplier and buyer codes | Label, date, condition photo | Confirm purpose |
| Evaluation | Sample code and protocol | Roast/test record | Record decision |
| Lot proposed | Lot or batch reference | Specification and mapping | Check representativeness |
| Packing or movement | Final packing reference | Cross-reference and record | Review changes |
| Shipment file | Commercial and transport refs | Final versions | Close or reopen gate |
The ledger should show who made each entry and when. Keep old values when a reference changes. A chronological record helps resolve whether an issue was present in the sample, introduced during handling or caused by a mismatch in the file.
Worked example: a lot changes after approval
This hypothetical case begins with an approved green Robusta sample linked to a preliminary lot reference. Before loading, the supplier proposes a different assembled lot because the first reference is no longer available. The buyer checks the new specification, asks how the new lot maps to the approved sample and reviews whether the defined reapproval trigger applies.
The buyer decides that the new lot needs a fresh sample. The original approval remains in the archive with its original scope; it is not deleted or silently reused. The new sample receives a separate code and a new decision. This protects the transaction record and gives the supplier a clear answer about what the buyer can accept.
Avoid five approval failures
An unlabeled sample cannot be reliably matched to a document. An approval without purpose cannot tell anyone what was accepted. A lost roast or test method cannot support a repeat. A lot substitution without notice breaks the link between test and shipment. A cupping note without scope can be mistaken for a guarantee. Each failure is solved by a small record field and a named review gate.
Do not use the word “approved” when the team has only said that a sample is interesting. Use “received”, “under evaluation”, “reference accepted”, “conditional” or “approved for the defined lot” as appropriate. Clear status words reduce the chance that a commercial message will overstate a technical decision.
Brief Vinh Hiep for traceable sample work
State the product form, intended use, destination, evaluation method and the identifiers you need on the sample. Ask whether the sample is a type reference or a proposed lot, which specification applies and what event would require reapproval. Link the request to the Gia Lai origin guide, the buyer verification guide and the Robusta specification guide.
Traceability handoffs that a buyer can review
List the handoffs that matter to the coffee’s identity: collection or intake, processing, drying, storage, grading, packing and shipment. Not every transaction uses the same sequence, so ask which events occur and which record identifies each one. A handoff record can be a batch log, warehouse reference, packing mark or another controlled identifier. The buyer’s task is to understand the link, not to prescribe a record the supplier does not use.
At each handoff, note the responsible party, date, quantity or scope, reference carried forward and any event that could change the product identity. If coffee is combined, record the aggregation rule. If it is separated, record the new references. The ledger should make it possible to answer what changed between the approved sample and the proposed shipment. Where the answer depends on a confidential system, request a suitable summary or inspection route rather than asking for unrestricted access.
Close the approval file only after the final references are recorded. If a shipment is split, make a copy of the relevant approval context for each resulting reference. If a container is delayed or repacked, add the event and decide whether a new review is required. A traceability file is not finished because a box has been labelled; it is finished when the buyer can explain the identity and scope of the coffee being received.
For internal training, invite quality, purchasing and logistics to review one hypothetical ledger together. Ask each person to identify the sample, lot, document version and next action. Differences in interpretation show where a label or handoff description needs clarification. This exercise is more useful than assuming every team reads a code in the same way.
Make the approval visible to the right teams
Share the approval status with purchasing, logistics and the person managing the supplier relationship. They do not need every sensory note, but they do need to know the sample code, approved scope and reapproval triggers. A short status line can say “reference accepted; final lot confirmation required” or “lot approved under specification version 3”. Clear status language prevents a technical note from being read as an unconditional commercial instruction.
At receipt, compare the final marks and documents with the approved references before the coffee is released to the next process. If a field is different, record the difference and decide whether it is administrative or material. The decision should be attributable to a reviewer. This last check completes the chain from sample approval to shipment record.
Use an approval gate in the purchase timeline
Place the sample decision before commercial release and before the final document check. The gate can be simple: the reviewer confirms the sample code, specification version, proposed lot and open conditions. If any of those fields is absent, the file remains conditional. This does not slow every purchase; it makes the point of uncertainty visible so that the team can resolve the right question.
Keep the approval record available to the person who will answer a later buyer question. If the original reviewer is unavailable, the next person can see the method, evidence and limits instead of relying on memory. That continuity is especially useful when a sample is discussed across language, purchasing and logistics teams.
Use a dated decision label so that a later team member can distinguish a current approval from an archived one.
This note belongs in the controlled purchase file.
Frequently asked questions
What belongs in a sample approval note?
Record the sample and lot references, date received, purpose, preparation or test method, reviewer, observations, decision and limits. Add the specification version and any reapproval trigger. The note should tell a later reader what was accepted and what remained outside the decision.
When is a new sample needed?
Request one when the proposed coffee is a different lot or process, the specification changes materially, storage or packaging conditions raise a question, the prior sample is no longer representative or the buyer’s destination requirement calls for a new check. Use the agreed trigger rather than guessing from the product name.
How should a lot change be recorded?
Keep the original approval, record the old and new identifiers, state why the change occurred, and ask the responsible reviewer whether the original scope still applies. If it does not, open a new sample decision. Never overwrite the history to make the new lot look continuous.
Are cupping notes enough on their own?
No. They describe an evaluation under a method and sample condition. They do not identify the complete lot or prove origin, documentation or future consistency. Use them together with the sample identity, specification and traceability record.
Continue through the Gia Lai coffee export hub and Gia Lai coffee origin guide. Related guides: Gia Lai Coffee Export: What Buyers Should Verify Before a Request, A Buyer’s Guide to Gia Lai Coffee Export Documentation, Gia Lai Coffee Export and Robusta Specifications: A Practical Reading Guide. For a current request, send Vinh Hiep the product form, destination and the evidence your team needs to review.
