Coffee Roastery Traceability: A Mock Recall Protocol

Follow Ethiopian green lots through roasting, blending, packing, and wholesale delivery with a practical mock recall.

A wholesale customer sends a photograph of a bag code and asks which green coffee went into it. Coffee roastery traceability should let your team answer from records, even when the head roaster is away. The harder question follows: which other bags, blends, and deliveries used that same lot? A mock recall tests both directions before a real incident forces the answer.

What Must Coffee Roastery Traceability Connect?

Coffee roastery traceability is the recorded link between incoming coffee lots, production events, finished products, and their destinations. Each event needs an identity, a quantity, and a connection to the next event. A roast profile describes how you roast; a roast batch identifies one execution of that profile.

Start with the physical route coffee takes through your building. Include temporary totes, shared silos, grinding, sample withdrawals, contract packing, and stock sent to your own cafés. Every place where coffee is divided, combined, or given a new label needs a recorded connection.

The GS1 Global Traceability Compliance Criteria Standard, release 4.1 (2021), addresses records linking transformation inputs and outputs, product identifiers, quantities, and trading partners. Apply that linking principle to coffee handling. Buying a barcode printer alone does not create the missing relationships.

Keep IDs stable when product names change. A seasonal coffee can move from a named single origin into a house product without losing its original lot identity. Retain dated corrections and the person who made them; overwriting an old batch with a new recipe makes historical tracing unreliable.

Connect the Ethiopian Lot Before It Reaches the Hopper

Preserve the supplier's lot reference alongside your internal warehouse code. Ask for clarification while bags and documents are still available at receiving. A regional name such as Guji can appear on several purchases and cannot identify which physical delivery supplied a roast.

Three origin handoff checks deserve a place in the buyer's specification. They are practical record requests for the exporter and roaster to agree before production begins:

• Connect sample and shipment identities. Preserve the approved sample reference and the final export lot reference, including a written explanation when preparation changes the code. A cupping label should not become an assumed production identifier.
• Retain the mill allocation relationship. If coffee is split into export lots after preparation, request the link from the source allocation to each final lot. Describe only the origin detail supported by the supplier's records.
• Keep warehouse aliases visible. A supplier reference, export parcel mark, and receiving warehouse code can all describe related stock. Store the mapping so an origin query can reach the same physical coffee after relabeling or transfer.

Use the green coffee bag markings checklist to verify the physical sack identity; this article follows that identity into production. Resolve missing mappings before consolidating similar lots into a common bin.

For an Ethiopian supplier inquiry, send the exact received lot, purchase reference, delivery date, and affected production IDs. Attach the relevant bag photograph and source record. This lets an origin-connected exporter investigate a defined allocation through its sourcing network without guessing from tasting notes or a retail product name.

Preserve the Chain When Coffee Changes Form

Record actual material movements as they happen. Recipe percentages and scheduled quantities cannot prove which beans entered a particular batch. The most useful checks sit at the moment an operator pours, blends, packs, or relabels coffee.

Tote top-ups and blends

Adding a new batch to a partly filled tote creates a mixture with more than one parent. Give that mixture an identifiable record and retain every contributing batch. If operators cannot establish when the earlier coffee cleared, include the uncertain output window in the investigation.

For a blend assembled after roasting, record the weighed roasted components. For coffee blended before roasting, record each green component entering the charge. The same menu name can continue through a component change, so link each physical blend to the recipe revision actually used.

Packing, repacking, and returned stock

Every packed code must resolve to the batch or batches that filled it. Capture the start and end of the run, and record a code change when your lot policy requires it. Repacking creates another event connecting the old packed identity to the new one.

Attach packaging check results to the production interval they cover. The coffee packaging quality control workflow explains how oxygen, seal, and valve checks support a release decision and how a failed check defines stock that needs assessment.

Record coffee sent for cupping, staff use, or wholesale samples as withdrawals with a destination. Keep returns identified and segregated pending an authorized decision. Unrecorded small withdrawals can become the unexplained balance that prevents a drill from closing.

Cropster's Roast Traceability Report documentation, updated April 2026, illustrates how roast and post-roast blend records can connect transaction histories with completed orders. Whatever system you use, test that the person covering a shift can retrieve those links and identify the actual customer order.

Run a Mock Recall From One Unexpected Starting Point

A mock recall is a controlled exercise that tests how completely your records locate potentially affected coffee. Choose a starting record without preparing the answers for the tracing team. Use the exercise to expose missing links and measure retrieval time.

Assign a drill coordinator, someone to trace production, someone to reconcile stock, and someone to review customer records. Small teams can combine roles, but a second person should check the result. Mark every exercise document clearly as a simulation and agree how any external participation will be handled.

1. Set the scenario. Start from a received green lot, a packed bag code, or a packaging material lot. Write the assumed issue and boundary. A green-lot scenario tests different links from a packing-line incident.
2. Trace backward. From the chosen finished code, retrieve the packing inputs, blend parents, roast inputs, and supplier records. Record the evidence used at each step.
3. Trace forward. Follow every relevant parent into its other batches, sizes, products, samples, and shipments. Include off-site stock and coffee moved to company-owned cafés.
4. Reconcile the stages. Account separately for green input, roasted output, blending, packing, and distribution. List unknown quantities explicitly while you investigate them.
5. Test the response record. Prepare a simulated affected-product list, stock-hold list, and customer contact list. Check that the correct people can access them and that the proposed scope matches the evidence.

The Canadian Food Inspection Agency's recall procedure guidance (2023) covers affected-product identification, stock segregation, distribution lists, and effectiveness checks. It also highlights packaging materials as a possible recall source. Use the requirements applicable to your business for real incidents, including notification obligations; this operational exercise does not set a universal legal deadline.

A passing trace identifies where coffee went. Whether that coffee needs a recall, and how widely to act, requires the responsible team to evaluate the incident. If the exercise uncovers a real safety concern, move into the established incident procedure immediately.

Worked Example: One Green Lot Reaches Two Products

Reconcile physical coffee at each transformation before calculating the affected finished stock. Roasting changes mass, and blending adds mass from other lots. The quantity of a green ingredient cannot stand in for the quantity of every finished product containing it.

Consider a fictional wholesale roaster supplying cafés with an Ethiopian single origin and a house blend. The following figures are an illustrative calculation prepared by Ethio Coffee in October 2026, not customer results or industry loss benchmarks. The exercise starts with green lot ETH-26-041.

The tracing result includes 574 kg of packed coffee: all 178 kg of single origin and all 396 kg of the blend. The Ethiopian component represents 30% of the blend input, but every bag from that blend run contains the component. Multiplying finished blend stock by 30% would understate the product requiring assessment.

Split the 450 kg shipped into dispatch lines by packed code and recipient. Count the 124 kg still in finished stock by location. Keep the 240 kg of remaining green coffee on the scenario's stock list, with its own status. The QC withdrawals also need recorded destinations; a sample sent outside the business remains a distribution event.

For the example to close, the weighing and withdrawal records must support every stated movement. Never fill a missing quantity with an assumed roast-loss percentage. Use the roast weight loss and yield method for measurement details, then attach the actual batch records to the exercise.

Keep a Drill Record That Leads to Corrections

Close the exercise only after the reviewer can follow the evidence and identify any outstanding gap. A balanced total alone is insufficient if several customer destinations remain unknown. Record completeness and retrieval time separately.

• Exercise header: date, coordinator, starting code, assumed issue, tested locations, and agreed completion target.
• Evidence register: supplier references, receiving records, batch parents, packing codes, stock counts, and dispatch lines.
• Results: time to identify products, time to identify destinations, reconciled quantities, unresolved quantities, and missing contacts.
• Corrections: specific failure, responsible person, due date, action taken, repeat-check result, and reviewer sign-off.

Investigate duplicate codes, unlabeled totes, retrospective blend entries, and dispatch lines that carry only a product name. If records cannot separate potentially affected output, document the wider boundary that must be considered. Do not infer a narrow scope from an operator's memory.

Schedule exercises under your applicable quality system and repeat the relevant checks after changes to blending, packing, software, or warehouse handling. Include a cover-shift operator in the next drill. The green coffee inventory planning system can use the same lot identities, while the drill verifies their history through finished stock.

Coffee roastery traceability becomes useful when a bag code opens a complete production history and a supplier lot opens a complete destination list. Preserve the origin reference, record each transformation, and prove the connections with a mock recall. Those records give buyers a specific, defensible basis for an exporter inquiry and a wholesale response.