Audit-ready cold chain data requirements include accurate temperature records captured at regular intervals throughout a shipment, clear documentation of any excursions, and records stored in a tamper-evident, accessible format. These requirements apply to any organization shipping temperature-sensitive goods, from fresh produce and pharmaceuticals to flowers and chemicals. The sections below break down exactly what auditors look for, how long to keep records, and what to do when data is incomplete.
What data must be captured for a cold chain audit?
A cold chain audit requires a continuous log of temperature readings taken at defined intervals throughout the entire shipment journey, from dispatch to delivery. The record must include timestamps, the identity of the shipment, the sensor used, and the acceptable temperature range for that product. Without these elements, an auditor cannot verify that the cold chain was maintained.
In practice, this means your cold chain monitoring solution needs to capture and store the following:
- Temperature readings at consistent intervals — typically every 5, 10, or 15 minutes depending on the product’s sensitivity and the length of the journey
- Start and end timestamps — confirming exactly when monitoring began and ended
- Shipment identification — linking the temperature log to a specific batch, order, or consignment number
- Device identification — confirming which logger captured the data and that it has been calibrated or certified
- Defined temperature limits — the upper and lower thresholds that define an acceptable shipment
For many sectors, EN 12830 certification is the recognized standard for temperature recording instruments used in the transport of chilled, frozen, and deep-frozen goods. A logger that meets this standard gives auditors confidence that the data is accurate and the measurement methodology is sound.
How long must cold chain temperature records be retained?
Cold chain temperature records should generally be retained for a minimum of two years, though the appropriate retention period depends on your product category and the expectations of your customers or trading partners. Pharmaceutical shipments and certain food categories may warrant longer retention periods to support traceability across the full product lifecycle.
Rather than working to a minimum, many quality managers adopt a practical rule: keep records for at least as long as the product could still be in use or on the market. For a fresh vegetable shipment with a shelf life of two weeks, a short retention period is reasonable. For a pharmaceutical product with a shelf life of several years, records should be available for the equivalent period.
Cloud-based storage makes long-term retention far more manageable than paper printouts or USB-downloaded files. When temperature data uploads automatically to a dashboard at the moment of reading, records are timestamped, searchable, and accessible without requiring physical filing systems or manual archiving processes.
What format do auditors accept for temperature data?
Auditors generally accept temperature data in any format that is tamper-evident, clearly structured, and traceable to a specific shipment and device. The most widely accepted formats are PDF reports and structured digital records exported from a certified monitoring system. Paper printouts from certified loggers are also accepted but are increasingly being replaced by digital alternatives.
The key qualities auditors look for in a temperature record are:
- Tamper-evidence — the data cannot have been altered after recording
- Completeness — no unexplained gaps in the timeline
- Traceability — the record links clearly to a shipment, a device, and a date
- Legibility — the data can be read and interpreted without specialist tools
Digital cloud reports score well on all four criteria. Because the data uploads directly from the logger to a secure platform, there is no manual handling step where records could be altered or lost. Auditors can be given access to a specific shipment report without needing to search through filing cabinets or request files from a colleague.
What happens if cold chain data has gaps or excursions?
If cold chain data contains gaps or temperature excursions, the shipment may be flagged for further review, and in serious cases the product may be rejected or quarantined. A gap in monitoring data is treated as a period of unknown risk, which is often handled the same way as a confirmed excursion. The response depends on the severity, duration, and the product involved.
When an excursion is identified, the standard response involves three steps:
- Document the excursion — record exactly when it occurred, for how long, and how far outside the acceptable range temperatures went
- Assess the impact — determine whether the product was likely affected based on its known stability profile and the nature of the excursion
- Make a disposition decision — decide whether to release, quarantine, or reject the shipment based on the assessment
Gaps in data are often caused by logger failure, battery depletion mid-journey, or human error in starting the logger. This is one area where the battery quality of the logger matters significantly. Paper-based loggers use a lithium-free battery chemistry that is optimized for the single-use monitoring task, with no risk of battery drain from prior use or recharging cycles. Traditional single-use electronic loggers use lithium batteries that, while generally reliable, are subject to performance variation in extreme cold. A logger that runs out of power mid-shipment leaves exactly the kind of gap that auditors flag.
The best way to avoid gaps is to use a logger that starts automatically, records continuously, and confirms a complete data set at the point of delivery. When a receiver can tap a label with a smartphone and immediately see an unbroken temperature graph for the entire journey, there is no ambiguity about what happened during transit.
How Tapp helps you stay audit-ready
Tapp’s paper-based data logger technology is designed to meet the practical demands of cold chain audits without adding complexity to your workflow. As the only provider of paper-based data logger technology, Tapp combines EN 12830-certified accuracy with a format that is fundamentally simpler to use and easier to audit than traditional electronic loggers.
- Complete, certified temperature records — every shipment produces a full, timestamped log that meets EN 12830 standards
- Automatic cloud upload via NFC tap — any NFC-enabled smartphone reads the label instantly, with no app required, and the data uploads automatically to the TappOS dashboard
- Accessible to both sender and receiver — reports are available in the cloud the moment the label is read, making them easy to share with auditors or trading partners
- Lithium-free battery — eliminates the risk of battery-related data gaps mid-shipment, a common cause of incomplete records
- Recyclable through standard paper waste streams — no e-waste disposal process required, supporting your sustainability reporting alongside your quality documentation
If you want to see how paper-based cold chain monitoring fits your audit process, contact the Tapp team for a sample or a product demonstration.
Frequently Asked Questions
How do I know if my current cold chain logger meets audit requirements?
Check whether your logger carries EN 12830 certification, as this is the most widely recognized standard for temperature recording instruments used in chilled, frozen, and deep-frozen transport. Beyond certification, verify that your logger captures readings at consistent intervals, records start and end timestamps, and links data to a specific device ID and shipment. If your current solution cannot produce a tamper-evident, traceable report on demand, it is worth reviewing whether it would hold up under auditor scrutiny.
What is the difference between a temperature excursion and a data gap, and which is more serious?
A temperature excursion is a confirmed period where readings fell outside the defined acceptable range, while a data gap is a period with no readings at all — meaning the temperature during that time is simply unknown. In practice, auditors often treat data gaps as seriously as excursions, because an unknown risk cannot be dismissed. A confirmed excursion at least gives you data to work with for a stability assessment; a gap leaves you with no basis for a disposition decision.
Do I need a different logging interval for different product types?
Yes — the appropriate logging interval depends on the sensitivity of the product and the length of the journey. Highly sensitive products such as certain pharmaceuticals or fresh seafood may require readings every 5 minutes, while less sensitive goods like bulk frozen products can typically be logged every 15 minutes. When in doubt, consult your product’s stability data or your customer’s quality agreement, as trading partners often specify a minimum logging frequency as part of their supplier requirements.
Can I share cold chain records directly with auditors or customers without manual preparation?
With a cloud-based monitoring system, yes — records can be shared via a direct link or dashboard access without any manual file preparation, printing, or emailing of attachments. This is one of the practical advantages of automatic cloud upload: the moment a shipment label is read at delivery, the full temperature report is already available and shareable. Giving an auditor or trading partner direct access to a specific shipment report eliminates the risk of records being lost, delayed, or questioned for completeness.
What should I do if a logger fails to start or stops recording mid-shipment?
First, document the failure immediately — note which shipment was affected, which device was used, and at what point the data stops. Then treat the unmonitored period as an unknown excursion and follow your standard disposition process: assess the product’s likely condition based on ambient conditions, transit time, and known stability data before making a release or quarantine decision. To prevent recurrence, review whether the failure was caused by battery depletion, incorrect activation, or device fault, and consider whether your current logger technology is suited to the temperature range and journey duration involved.
Are paper-based cold chain loggers accepted by regulatory auditors in the same way as electronic ones?
Yes, provided they meet the same certification and data quality standards. Auditors evaluate the record itself — its completeness, traceability, tamper-evidence, and legibility — rather than the physical format of the logger that produced it. A paper-based logger that carries EN 12830 certification and uploads a complete digital report to a cloud platform meets all the same criteria as a traditional electronic logger, and in some cases produces a simpler audit trail because there are fewer manual handling steps between data capture and report generation.
How should I handle cold chain record-keeping if I work with multiple trading partners who have different requirements?
The most practical approach is to maintain records that meet the most stringent requirement across all your partners, rather than managing different retention periods or formats for each relationship. Standardizing on a cloud-based system makes this easier, since the same report can be formatted and shared in whatever way each partner requires without duplicating your record-keeping process. It is also worth including temperature monitoring requirements explicitly in your supplier or customer quality agreements so that expectations are documented and consistent across your network.
