What is dual compliance in GxP?

The pharmaceutical industry loses an estimated $35 billion annually to cold chain failures, according to IQVIA data reported by Forbes. That is medicine that never reaches the patient. Most of it preventable.

The losses persist because the traditional monitoring model was designed to document what happened – not to prevent it.

In a traditional setup, a data logger or smart label is attached to each shipment. It records temperature throughout the journey and delivers the data after arrival – or, in the case of connected devices, in real time.

This gives you one dataset: What happened to the product.

That data is useful for compliance documentation. But it has three limitations that get worse as operations scale.

It is reactive, not preventive. Most devices deliver data after delivery. By the time you see an excursion, the product is already compromised. Even when the data is live, alerts often go to the shipper – not the carrier personnel who could actually intervene.

It does not explain the cause. When an excursion shows up on a shipment logger, you cannot tell whether the warehouse failed, the aircraft failed, or the product was mishandled. You see that something went wrong, but not where or why. Without that distinction, you are guessing at what to fix.

It does not scale. Every shipment needs its own device at $20 – 200 each. More shipments mean more devices, more cost, and more complexity. Compliance costs grow linearly with volume.

Dual compliance adds a second, independent data layer: continuous environmental monitoring of the transit environments the product passes through.

The two layers

Layer one – environmental monitoring: Wireless data loggers installed permanently in warehouses, aircraft cargo holds, and trucks measure conditions continuously – typically every three minutes. This creates a validated environmental record for every product that passes through, whether or not it has its own tracking device.

A critical part of this layer is the aircraft. Warehouses have traditionally been mapped and monitored, but aircraft cargo holds have been a compliance blind spot – forcing operators to overcompensate with expensive active ULDs or accept data gaps. Continuous mapping and monitoring for aircraft changes that by treating the plane as a validated environment, with FAA-approved sensors installed permanently in the cargo hold. Data is available within minutes of landing, not days after delivery.

Layer two – shipment tracking: Smart Labels attached to high-risk or high-value shipments track temperature, humidity, GPS, shock, and tamper events in real time. These go on the shipments that actually need individual monitoring – not on every package by default.

When both layers are in place, the compliance model shifts in three ways.

You can act before products are affected. Environmental data is live. When conditions in a warehouse or aircraft trend toward limits, carrier personnel are alerted and can adjust handling before the product's stability budget is exceeded. You prevent failures instead of documenting them.

You can prove compliance without monitoring every shipment. The environmental data provides a compliance baseline for everything passing through your facilities and fleet. Individual tracking is reserved for shipments where risk demands it – high-value biologics, new routes, or regulatory-specific requirements. Both data layers merge into one automatically generated report per shipment, with environmental and shipment-level data correlated across every handoff point. No manual data stitching, no spreadsheets, no separate systems.

You can pinpoint the actual cause of excursions. When you have environmental data from the warehouse, the aircraft, and the truck alongside the shipment data from the Smart Label, you can see exactly which phase caused the problem. Not "somewhere between A and B" – but in which facility, during which window. Over time, patterns emerge: this route has issues in summer, and that handoff point is consistently problematic. Root cause analysis becomes the basis for preventing the next excursion, not just investigating the last one.

Also read: From shipment to facility control: the future of cold chain monitoring

Dual compliance aligns with existing regulatory guidance on continuous process verification.

WHO TRS 961 (2021) endorses continuous verification as superior to periodic point-in-time snapshots for temperature-controlled environments.

FDA Process Validation Guidance (Stage 3) describes ongoing process verification as an approach to maintaining a validated state through continuous monitoring – the same principle underlying continuous environmental monitoring across facilities and fleet.

EU GDP guidelines require documented evidence that storage and transport conditions are maintained within validated ranges. Dual compliance provides this evidence through continuous environmental data rather than through individual shipment logs alone.

No regulatory guidance currently mandates dual compliance specifically. But the framework supports it – particularly when organizations can demonstrate through dual verification that their environmental monitoring provides equivalent or superior assurance to universal shipment monitoring.

Also read: What is GxP in pharma?