Introduction
Picture this: a pharmaceutical shipment arrives at port after a 30-day ocean voyage. The reefer unit powered down twice during transit. Nobody noticed. The cargo looks fine — but without an independent temperature record, the receiving quality team has no way to verify what actually happened inside that container. The shipment gets rejected. Compliance violations follow.
This scenario plays out regularly in global cold chain logistics, and it illustrates a critical point: temperature control and temperature documentation are not the same thing.
FAO reports that roughly 14% of the world's food — valued at approximately $400 billion annually — is lost between harvest and retail. Cold chain failures account for a large share of those losses — and the fallout extends beyond spoiled cargo into regulatory penalties and broken commercial relationships.
This guide gives you everything you need to choose, deploy, and get compliant results from a reefer container temperature data logger.
Key Takeaways
- A data logger creates an independent, verifiable temperature record — separate from the reefer unit's built-in controls
- WHO pharmaceutical transport benchmarks require ±0.5°C accuracy and six readings per hour minimum
- FDA 21 CFR Part 11 mandates tamper-evident, time-stamped electronic records for regulated shipments
- Place loggers at the warmest zone, not near the evaporator — placement directly affects data quality
- Multi-use loggers reduce per-shipment cost; single-use loggers provide tamper-evident proof for regulated cargo
What Is a Reefer Container Temperature Data Logger?
A temperature data logger is a standalone electronic device placed inside a refrigerated container that records internal temperature — and sometimes humidity — at set intervals throughout a shipment. It operates independently of the container's built-in cooling unit, which is precisely what makes it useful.
The Logger vs. the Reefer's Onboard Controller
The reefer unit maintains temperature. The data logger creates a verifiable record of what the cargo actually experienced during transit. These are fundamentally different functions.
A reefer's onboard thermostat or telematics system monitors and controls the cooling unit. It can tell you what setpoint was programmed and, in some cases, transmit live operational data. What it cannot do is produce an independent, cargo-level compliance document that satisfies regulatory audit requirements.
That compliance gap is exactly what a dedicated data logger addresses — sitting with the cargo, not managing the equipment.
How It Works
The mechanism is straightforward:
- Sensors capture readings at a programmed interval — every 5, 10, or 30 minutes, for example
- Data stores in internal memory throughout the voyage, with no connectivity required
- At destination, connect via USB to generate a PDF and CSV report automatically
- Review the report for excursions before accepting or releasing cargo
Realogview's TempTrail loggers, for instance, generate both PDF and CSV reports automatically upon USB connection — no proprietary software required. Any recipient with a standard PDF reader can open and verify the record immediately.
Why Temperature Data Loggers Are Essential for Reefer Containers
Reefer containers are capable, but not foolproof. Temperature excursions occur for reasons that have nothing to do with the cooling unit's programming:
- Door seal failures that allow warm air infiltration during transit
- Power interruptions at port or during vessel transfer
- Improper loading that blocks airflow channels
- Human error during pre-cooling or stuffing
None of these events generate automatic documentation from the reefer's onboard system. And without documentation, you can't defend a cargo claim, respond to an audit, or make a confident product disposition decision.
Financial and Reputational Stakes
Disputed cargo claims are resolved on evidence. Independent temperature records are as much a financial safeguard as a compliance requirement. Without a temperature log, a shipper arguing that their pharmaceutical shipment remained within range during a 40-day ocean voyage is arguing without a single verifiable record.
The World Bank reports that approximately 55% of fruit and vegetable losses in sub-Saharan Africa are attributed to lack of cold-chain infrastructure. When temperature records don't exist, losses become impossible to attribute, prevent, or recover.
End-to-End Traceability
Beyond financial protection, a data logger creates a continuous temperature timeline from origin to destination — something no carrier-provided record can replicate with full independence. That timeline:
- Supports insurance claims with objective evidence
- Enables dispute resolution without relying on carrier-provided records
- Satisfies regulatory audit requests with a single document
- Provides customers with transparent proof of transit conditions
The Regulatory Driver
GDP (Good Distribution Practice), HACCP, and FDA regulations in the US each mandate documented, verifiable temperature records throughout the cold chain. A standalone data logger is often the primary mechanism for satisfying these requirements. The records it produces are independent and time-stamped — not generated by the same system responsible for controlling the temperature, which is precisely what regulators require.
Key Features to Look for in a Reefer Container Temperature Data Logger
Choosing the wrong logger creates compliance gaps, report delays, and cargo disputes. Here are the specifications that determine whether a logger actually holds up in reefer container conditions.
Temperature Range and Accuracy
WHO TRS 961 Annex 9 specifies that temperature-monitoring sensors in pharmaceutical transport should be accurate to ±0.5°C, calibrated and positioned at worst-case locations in the qualified load zone. This is the defensible pharma benchmark.
For standard reefer applications, Realogview's TempTrail Classic and XL achieve ±0.2°C accuracy — well within that threshold — across a range of -30°C to +70°C. For ultra-low pharmaceutical shipments requiring monitoring down to -85°C, the TempTrail Glacial covers that range.
Match the logger's range to your cargo's storage requirements before purchasing.
Data Storage Capacity and Logging Interval
WHO guidance calls for at least six temperature records per hour per sensor position for pharmaceutical transport — that's a 10-minute interval. Here's how capacity translates into coverage:
| Model | Capacity | At 10-min intervals | At 30-min intervals |
|---|---|---|---|
| TempTrail Classic | 11,000 points | ~75 days | ~229 days |
| TempTrail XL | 32,000 points | ~220 days | ~667 days |
For trans-Pacific or Europe-Asia routes running 30-45 days, the Classic covers standard intervals comfortably. The XL handles extended voyages or more frequent recording requirements.
Software-Free PDF and CSV Report Generation
At port of arrival, you need a report immediately — not after installing software on a port authority laptop. Loggers that auto-generate PDF and CSV reports on USB connection remove that friction:
- Any recipient opens the record in a standard PDF reader — no proprietary tools required
- CSV exports are ready for direct import into quality management or ERP systems
- No software installation means no IT dependencies at customs or inspection points
Build Durability and Ingress Protection
Reefer environments involve condensation, temperature shock, and rough handling. Look for:
- IP67: Complete dust protection + water immersion up to 1 meter for 30 minutes — standard across most TempTrail models
- IP68: Continuous submersion beyond 1 meter — the TempTrail HiTemp rating for the harshest environments
Realogview's TempTrail loggers also carry DO-160G certification — an aviation-grade standard that tests performance under vibration, mechanical shock, extreme temperature fluctuation, and pressure variation. For cargo moving across sea, road, and air in a single journey, this certification confirms the logger won't fail between the first leg and the last.
Alarm Configuration and Certifications
Regulated shipments require loggers with documented compliance. Verify the logger holds:
- FDA 21 CFR Part 11 — required for pharmaceutical electronic records
- CE, FCC, RoHS — standard regulatory marks
- DO-160G — durability under extreme environmental conditions
All TempTrail models carry FDA 21 CFR Part 11 compliance explicitly. Multi-use models offer user-configurable alarm thresholds and logging intervals; single-use models come pre-configured (with custom settings available on request).
Types of Temperature Data Loggers for Reefer Containers
Single-Use vs. Multi-Use Data Loggers
Three logger types suit different reefer container use cases. The right choice depends on two factors: whether the logger needs to travel with cargo as tamper-evident proof, and how frequently you're running the same lane.
| Type | How It Works | Best For |
|---|---|---|
| Single-use | Pre-programmed at shipment start, travels with cargo to recipient | Pharmaceutical cold chain, tamper-evident compliance documentation |
| Multi-use | Retrieved at destination, downloaded, reconfigured, redeployed | High-frequency routes where lower cost per shipment matters |
| Wireless/IoT | Transmits near-real-time data via cellular or satellite | Active monitoring on high-value shipments with reliable signal coverage |
Realogview's single-use options — the TempTrail Classic (11,000 data points) and TempTrail XL (32,000 data points) — are built for pharmaceutical and food shipments where chain-of-custody documentation is non-negotiable. The reusable lineup includes the TempTrail Glacial, Display (Model M), and Humidity & Display (Model M), all with user-replaceable batteries and configurable parameters.
Wireless loggers add visibility but come with higher cost and signal dependency. For the majority of reefer applications, standalone loggers that store data locally and upload at destination are the more practical and reliable choice.
How to Use a Temperature Data Logger in a Reefer Container: Best Practices
Pre-Trip Setup
Before loading, complete this checklist:
- Set the logging interval based on cargo sensitivity — 10-minute intervals for pharmaceuticals, 30-minute for standard food shipments
- Program alarm thresholds to match the cargo's specified storage range
- Confirm battery life exceeds the longest expected journey duration
- Check memory capacity by calculating: trip duration × readings per hour against the device's total data points
- Record calibration status — GDP compliance requires documented proof
One timing mistake undermines the entire record: starting the logger after the container is sealed creates a data gap at the most critical moment. Start it before the container closes.
Placement Strategy Inside the Container
Where you place the logger determines what temperature you're recording — and that distinction has real compliance consequences.
A logger positioned near the evaporator will record colder readings than cargo at the rear of the container. That's not the worst-case temperature the cargo experienced. For compliance purposes, you need the worst case.
Recommended placement:
- Center or rear of the container, away from the evaporator airflow
- Not directly against the container wall (which experiences more temperature variation)
- Within or adjacent to the cargo, not in free airspace
For large or high-value shipments, use multiple loggers at different positions — a practice called temperature mapping. This detects hot spots caused by improper stacking, blocked airflow channels, or uneven loading.
Keep cargo below the maximum load line to allow air circulation. A fully packed container with blocked airflow can develop temperature stratification that a single logger positioned in one spot will miss entirely.
Post-Trip Data Retrieval
At destination:
- Connect the logger via USB to a Windows PC
- Review the PDF report for excursion events before accepting or releasing cargo
- Retain the CSV file for any required data analysis
- For FDA-regulated shipments, the report becomes part of the batch record — retain it for at least one year after batch expiration (or as required by the applicable predicate rule)
Regulatory Compliance and Temperature Data Logging in Reefer Containers
FDA 21 CFR Part 11
This regulation governs electronic records used in FDA-regulated industries — pharmaceuticals, biologics, medical devices. It requires that electronic records be trustworthy, reliable, and equivalent to paper records. Specifically, 21 CFR Part 11 requires:
- Validated systems for accuracy and consistent performance
- Secure, computer-generated, time-stamped audit trails
- Protection against invalid or altered records
- Authorized access controls
- Accurate and complete human-readable copies
Part 11 governs the record system, not just the device. Compliance depends on the validated logger-plus-process combination — controlled access, record integrity, retrieval, and retention — not a feature checklist alone.
Reefer shipments frequently cross regulatory jurisdictions, so FDA requirements are rarely the only standard that applies.
GDP and HACCP Requirements
Two additional frameworks govern most cold chain operations:
- EU GDP (2013/C 343/01): Storage conditions must remain within defined limits during transport; temperature-monitoring equipment must be maintained and calibrated at least annually; temperature-controlled vehicles and containers must be qualified.
- HACCP: Monitoring procedures and documented records are required for each critical control point. When temperature is a CCP in your hazard analysis, the specific monitoring mechanism must align with your documented HACCP plan.
Practical Compliance Checklist
When evaluating a data logger for regulatory use, verify the report includes:
- Device serial number and calibration reference
- Start and stop timestamps
- Logging interval used
- Complete temperature curve (all data points)
- Alarm events and excursion records
Quality teams and auditors use these fields to verify chain of custody and confirm no excursions were missed. TempTrail loggers generate FDA 21 CFR Part 11-compliant PDF and CSV reports that include all of these elements automatically, without requiring external software.
Frequently Asked Questions
What temperature range should a reefer container data logger support?
Standard reefer containers operate between -30°C and +30°C, but match the logger to the cargo, not the container. Pharmaceutical cold chain may require coverage down to -85°C for biologics and dry ice shipments. Always verify the logger's specified range against the product's storage requirements before deployment.
What is the difference between a data logger and a reefer container's built-in telematics system?
Built-in telematics monitor and control the cooling unit, sometimes transmitting live operational data. A standalone data logger creates an independent, cargo-level temperature record that functions as a verifiable compliance document. Both can be used together — the telematics manages the unit, the logger documents what the cargo actually experienced.
How do I know if a temperature data logger is FDA compliant?
Look for loggers that explicitly state FDA 21 CFR Part 11 compliance in their product documentation, not just as a marketing claim. The logger must produce tamper-evident, time-stamped electronic records as part of a validated system — verify this in the device's technical datasheet, not just the product page summary.
How often should a temperature data logger record readings inside a reefer container?
WHO pharmaceutical transport guidance specifies at least six records per hour per sensor — a 10-minute interval. Standard food transport may accept 30-minute intervals. Shorter intervals provide more granular excursion data but consume memory faster. Calculate trip duration against device capacity before configuring.
Can I reuse a temperature data logger across multiple reefer shipments?
Multi-use loggers are designed to be retrieved, downloaded, reconfigured, and redeployed. They're cost-effective for high-frequency routes. Single-use loggers are preferred when the device must travel with the cargo to the recipient as independent, tamper-evident proof of the full journey.
Where is the best place to position a data logger inside a reefer container?
Place it at the warmest zone — typically the center or rear of the container, away from the evaporator airflow — to capture the highest temperature the cargo actually experienced. For larger loads or high-value shipments, deploy multiple loggers at different positions to detect hot spots from blocked airflow or uneven stacking.
