A cold research parcel can lose small amounts of time outside its labelled range. See how delays add up and what a logger record can and cannot show.

Time out of range is the total time a cold parcel of research peptides spends outside the temperature range on its label. Short delays at handovers, customs, weekends and the last mile each add a little, and a data logger records the sum. A receiving laboratory then compares that record with the supplier's stated limits.
A cold parcel of research peptides is built to hold its range for a set time. Most journeys fit inside that time. Delays eat into it. They tend to come from a few familiar places.
| Source of delay | What happens | What the record may show |
|---|---|---|
| Handover gaps | The parcel waits on a dock or in a van between carriers and sorting sites | Slow rises that start at a handover time |
| Customs holds | The parcel stops while paperwork or contents are checked | A long period outside range that lines up with a stop in the tracking |
| Weekends and holidays | The parcel sits at a hub until the next working day | A long climb that spans a weekend |
| Last-mile waits | A failed delivery attempt or a closed receiving desk | A rise near the end of the trip |
Handover gaps are built into most routes. A parcel seldom travels in one vehicle. It moves from a collection point to a hub, from a hub to another hub, and from there to a local depot. Each step ends in a wait for the next one.
Customs holds can be long, and the parcel often cannot move until they end. The post on what a customs hold does to a refrigerated parcel looks at this case in detail.
Weekends matter because the network slows down. A parcel that reaches a hub late on a Friday may wait until Monday. Public holidays work the same way.
The last mile is often the least predictable stage. If nobody can receive the parcel, it may ride in a van or wait in a depot for another attempt.

No single delay may look serious. A short wait at a dock is not alarming. A few hours at a hub is not alarming either. The trouble is that the effects are not separate.
Think of the cooling in a parcel as a bucket of water with a small hole. The cold packs and the insulation set how fast it drains. Time in warm surroundings drains it faster. Nothing refills the bucket between handovers. Each delay takes a little more.
When the cooling runs low, the parcel warms faster. So a delay late in the journey can cost more than the same delay at the start.
Two things matter for each period outside range: how far from the limit the reading went, and how long it stayed there. A small step beyond the limit for a long time and a sharp peak for a short time are different events. Neither can be judged from the highest reading alone.
Some reports also give a mean kinetic temperature, a calculated value that sums up a changing temperature history. The post on mean kinetic temperature explains it. It is a helpful summary, but it does not replace a count of the time outside the limits.
A data logger is a small device packed with the parcel. It measures temperature at a set interval and stores each reading with a time stamp. Before the trip, it is set with the limits that apply to the product. After the trip, its file is read out as a table and a graph.
From that file a reviewer can find:
The sum of the periods is the time out of range. The reviewer adds each period, not just the longest one. This is why the interval between readings matters. A short event can start and end between two readings and leave no trace. The post on reading a parcel temperature logger trace goes through the steps for reading the file.

The logger's clock matters too. If its clock is wrong, a rise may be matched to the wrong handover. A reviewer checks the time zone and any known offset, then lines the readings up with the tracking events.
A logger record is only half of the picture. A laboratory needs something to compare it with. It uses two things.
The supplier's stated limits. These are the labelled range for the pen or parcel, and any stated allowance for time outside it. The comparison is simple on its face: did the readings stay inside the range, and if not, for how long?
The supplier's stability information. This is the supplier's own account of how the peptide behaves under storage conditions. The post on the difference between a certificate and a stability study explains why the two documents answer different questions. A certificate describes one lot at one time. Stability information describes how the material holds up over time and under stress.
If the supplier gives no allowance for time outside range, the laboratory should ask. It should not guess a number. The decision on what to do with an affected parcel belongs to the laboratory's quality procedure.
A tidy working method looks like this:
The wider shipping process is described on the shipping page.

A logger record is useful, and it has limits. Being plain about both makes it more valuable.
What it can show.
What it cannot show.
Only stability information and laboratory testing can say more about the peptide itself. A record that stays inside the range is good news about the journey. A record that goes outside is a reason to look closer, not a verdict.

Transit delays add up. A handover gap, a customs hold, a weekend and a missed delivery can each cost a little time outside the labelled range, and the total is what a laboratory reviews. A data logger records the readings and the times. The laboratory compares them with the supplier's stated limits and stability information, and it keeps in mind that the record shows conditions at the sensor and not the state of the material.