A logger in a trailer produces a chart, and a chart that shows a temperature excursion tells you that something went wrong somewhere in a load of several hundred crates. Without crate identity, that is as far as it goes. With it, the record points at a grower, a block, a picking day or a specific pallet, which is what turns data into an actionable answer.
Why identity is hard on a returnable crate
A carton is printed for one consignment and then ceases to exist. A crate does hundreds of trips, so any permanent marking is wrong for most of those trips. That is the central problem: the identity has to be re-writable, and it has to survive washing, cold and handling – which rules out most of the cheap options.
The three working approaches
A label applied per trip, which is flexible and generates waste and sometimes falls off. A printed or moulded permanent code plus a per-trip label, which gives an asset number and a load identity separately – usually the most practical combination. Or a barcode or RFID tag in a recessed holder, which survives washing and costs more per crate. The choice depends on whether the loop is closed, because in an open loop the tag will not come back.
What to record against the crate
Grower or block, pick date, and the first temperature reading after packing. Those three turn a later quality complaint into a traceable event. Recording more is possible and usually becomes noise; three well-kept fields are worth more than fifteen that are sometimes filled in. Traceability design is set out further in labelling and traceability on reusable fruit boxes.
Where the temperature reading should be taken
In the produce, not the air and not on the crate wall. A probe in a representative fruit at the centre of the pallet gives the number that matters. Reading the crate is quicker and is not the same thing – it measures the room, and it is the reason records and reality disagree at receiving points.
Practical limits
In a busy season, recording per-crate data is unrealistic unless it is automatic. Most operations record per pallet or per load and accept the coarser resolution, which is a reasonable trade-off. The mistake is designing a per-crate system and then not having the labour to operate it, which produces a partial record that is worse than a consistent coarse one.
What happens to the data
Records that are never read are a cost with no return. The minimum useful loop is: record, review weekly during the season, and act on the exceptions. Where a retailer or a buyer asks for evidence, having the records already reviewed is worth far more than having them merely stored.
What to do with a partial record
A record that covers most loads is still useful, provided the gaps are known. The failure mode is a system that records reliably in quiet weeks and not at all during the peak, which produces a dataset that looks complete and is biased towards the periods when nothing went wrong. Marking which weeks are complete is more honest and more useful than presenting a full dataset.
Where the peak cannot be recorded, record the exceptions instead – the loads that were late, warm or re-worked. A short list of exceptions from the busiest weeks is worth more than a complete record of the quiet ones, because the exceptions are where the problems are.
What we can do
We supply produce crates with a recessed label area or a tag holder, and with a permanent moulded asset number if the fleet is owned rather than pooled. Tell us how identity is currently carried and whether the loop is closed.