A question you hope nobody asks
A wholesale café reports that a bag of your espresso tastes of smoke, or has a foreign object in it. The café wants to know whether it is one bag or the whole delivery. Your food safety adviser, or a buyer at a larger account, asks the obvious follow up: which other customers received coffee from the same roast?
You can find the roast log for that day. You can find the orders that shipped that week. What you cannot easily do is connect them, because on a busy day three batches of the same coffee were roasted, tipped into the same tubs, and bagged across web, subscription and wholesale orders over the next two days.
The link breaks at the bagging bench
Traceability usually holds up to the roaster and then falls apart. Roasted coffee rests in tubs or bins labelled with the coffee name and maybe the date. Bags are filled from whichever tub is open. The bag label shows the roast date, but not the batch, and the order record does not say which tub the bag came from.
- Several batches of the same coffee are mixed in one resting tub.
- Bag labels carry a roast date but no batch code.
- Packing records list orders, not the coffee that went into them.
- Wholesale bulk bags are filled from a different container than retail.
Why it matters beyond the worst case
A genuine recall is rare, but the same gap causes everyday trouble. When a customer complains about a single bag, you cannot tell whether to worry about the rest of the batch, so you either ignore it or overreact. Larger wholesale and retail buyers increasingly ask suppliers how they trace product, and "we would work it out" is a weak answer. And without the link, you cannot learn from complaints, because you cannot see whether they cluster on particular roasts, lots or roast days.
Building the chain from lot to order
- Each roast gets a batch code when it is logged, tied to the green lot it was charged from. If you log roasts in a tool such as Cropster, we pick the batch up from there.
- Resting tubs are labelled with the batch code, and if you combine batches into one tub, the tub gets a combined code that remembers its parts.
- When bags are filled, the packer scans or picks the tub code, so every run of bags is tied to a batch.
- The bag label prints the batch code next to the roast date, small and readable.
- Each packed order records the batch codes that went into it, whether it is a single retail bag or a 6 kilo wholesale tub.
- A trace screen lets you search from either end: from a batch to every order and customer, or from an order back to the batch and green lot.
| Question | Answer today | Answer with the chain |
|---|---|---|
| Which lot was in this roast? | Roast log, usually | Recorded against the batch |
| Which batch is in this bag? | Roast date only | Batch code on the label |
| Who received this batch? | Guess from dispatch dates | List of orders and customers |
| Are complaints linked? | Not visible | Complaints grouped by batch and lot |
Living with traceability day to day
For the packer, the change is one scan per tub. For the roaster, it is a code that is generated rather than written. For the business, a question that used to take a day of digging becomes a search, and complaints are logged against a batch rather than just a customer. What you do with a trace result, and whether a problem needs further action, remains a decision for you and your advisers. The system makes sure the answer to "who got it" is available when you need it.
Could you trace a batch today?
- Batch codes do not appear on your bags.
- Resting tubs are labelled by coffee and date only.
- A larger buyer has asked how you trace product.
- Complaints are logged against customers, not roasts.
- Tracing a delivery back to a green lot would take hours.