.webp)
A UK QA Director at a specialty pharma distributor told me in June that her team had an MHRA inspection scheduled for October. Her cold chain data lived across three spreadsheets, a manufacturer's cloud portal she could not export from cleanly, and a filing cabinet of printed temperature reports.
Her operations were fine. Her audit trail was not.
That gap between operational reality and audit-ready evidence is where most cold chain compliance failures actually live. MHRA data shows around 30 percent of GDP inspection findings relate to temperature excursions or the documentation of them. Not because temperature control fails at that rate, but because operators cannot prove control at inspection time.
This article is a candid 2026 buyer's guide for QA Directors, Ops Directors, and COOs running cold chain operations in the UK or USA. What the software actually needs to do. UK GDP and US DSCSA compliance requirements. Real IoT sensor economics. Buy vs build cost bands. And the failure modes that surprise operators three months after go-live.
What Cold Chain Software Actually Needs to Do
Six capabilities distinguish audit-ready cold chain software from an operational monitoring dashboard.
Continuous temperature capture and logging. Sensor readings ingested at 1 to 5 minute intervals depending on shipment risk. All readings persisted with timestamp, sensor ID, GPS position, and shipment ID.
Real-time excursion detection and alerting. Threshold breach detected within one minute, alerting to on-call QA within five. Escalation logic (repeated breach, sustained breach, high-value shipment) baked in.
Immutable audit trail. Every reading, every alert, every intervention, every override logged with user, timestamp, and reason. No editing. Ever. This is what turns an operational tool into an audit-ready one.
Chain of custody documentation. Who received the shipment, when, at what temperature, from what carrier. Handoffs between the manufacturer, distributor, and dispensing pharmacy fully documented.
Cold chain risk assessment. Route risk, seasonal risk, carrier risk analytics that flag high-risk shipments before dispatch. Enables proactive rather than reactive excursion management.
Inspection-ready reporting. Ability to export the last 24 months of temperature data, excursion history, and interventions for any specific shipment, product, or route within minutes.
Off-the-shelf platforms cover most of this. Custom becomes the answer when your compliance model has cross-border or multi-regulator complexity SaaS treats as edge cases.
UK GDP and US DSCSA Compliance Requirements
UK operators face the MHRA GDP Inspectorate inspection framework. The MHRA "Green Guide" (Guidelines on Good Distribution Practice of Medicinal Products) is the definitive document. Key software-relevant requirements:
Temperature-mapped storage areas with continuous monitoring
Temperature recording resolution of 0.1 degrees Celsius
Temperature monitoring during transport for cold chain products
Documented deviations with root cause analysis
Qualification and validation of monitoring equipment
US operators face the FDA Drug Supply Chain Security Act, which mandates traceability of prescription drugs through the supply chain via serialised product identifiers, transaction data, and interoperable electronic tracing. Software must support:
Product identifier verification
Transaction information, transaction history, and transaction statement exchange
Suspect and illegitimate product investigation workflows
Electronic Product Code Information Services (EPCIS) data structure
For UK+USA operators shipping across both markets, software must handle both simultaneously. This is where off-the-shelf SaaS platforms sometimes fall short and custom builds win.
IoT Temperature Sensors: Real Cost and Selection
Four sensor categories with real 2026 economics.
Single-use data loggers. £2 to £8 per shipment. USB or Bluetooth readout at destination. Best for low-value, low-risk shipments where per-shipment cost matters. Sensitech LogTag, Elpro Libero range.
Reusable Bluetooth sensors. £25 to £70 per sensor, 2 to 5 year lifespan. Data pulled at handoffs via mobile app. Best for regular routes with defined handoff points.
Real-time cellular sensors. £80 to £250 per sensor plus £3 to £8 monthly connectivity. GPS plus temperature streamed continuously. Best for high-value shipments, clinical trial samples, and unpredictable routes. Controlant, Roambee, Berlinger cellular ranges.
Multi-parameter sensors. £150 to £400 per sensor. Temperature plus humidity plus shock plus light. Best for biologics, vaccines, and specialty pharma where multiple parameters matter.
Match sensor tier to shipment value and regulatory tier. A £5 vaccine dose shipment does not need a £250 real-time sensor. A £50k clinical trial batch does.
Buy vs Build: Real 2026 Cost Bands
Off-the-shelf SaaS. Sensitech, Berlinger Cold Chain IP, Controlant, Roambee, Elpro Business Suite. Pricing £15 to £40 per vehicle or monitored asset per month plus per-sensor cost. Setup 6 to 12 weeks. For most operators under 200 monitored assets, off-the-shelf wins.
Custom build on IoT platform (AWS IoT, Azure IoT, Google Cloud IoT) plus your own dashboard.
Proof of concept: £30k to £70k over 8 weeks
Pilot: £80k to £180k over 3 to 5 months (one route, one sensor category, live data ingestion)
Production: £200k to £450k over 6 to 9 months (multi-route, multi-sensor, full compliance module, inspection reports)
Add ongoing platform run cost £1k to £5k monthly (AWS or Azure IoT ingestion plus storage) plus £2k to £10k monthly engineering for tuning and compliance updates.
Custom becomes defensible when you operate across MHRA plus FDA plus TGA or similar, when your sensor mix is unusual (multi-parameter across low-volume routes), or when your operation needs client-facing portals with per-client compliance reporting SaaS does not cover cleanly.
What We Learned Building TrackVid's Evidence Retrieval
TrackVid is our video proof and claim management platform. Sellers use it to defend against claims with time-stamped, order-linked packing video that is retrievable at claim time in under 30 seconds. Not cold chain, but two engineering lessons transfer directly.
Immutable audit trail matters more than pretty dashboards. In TrackVid, our earliest sellers judged us on the dashboard UI. Our first regulatory-adjacent client judged us on whether we could produce time-stamped, unmodified video at three months post-dispatch. We rebuilt for immutability first, UI second. Same lesson applies to cold chain. Inspectors do not care about your dashboard aesthetics. They care whether the January 2024 excursion reading is bit-for-bit identical to what the sensor sent.
Retrieval speed matters as much as capture reliability. We spent a full quarter making sure any TrackVid seller could retrieve any packing video for any order in under 30 seconds. In cold chain, an MHRA inspector asking for a specific shipment's temperature trace should get it in under two minutes, not two hours of searching. Design retrieval architecture from day one.
You can see TrackVid at our portfolio. If you want a candid conversation about your specific cold chain operation, book a cold chain audit with WhiteStone.
Common Failure Modes in Cold Chain Programmes
Four failure modes we see repeatedly.
Sensors deployed without alerting configured. Temperature captured but nobody notified in real time. Excursion discovered at handoff, product destroyed. Common in year one deployments.
Data captured in vendor cloud with no export. Some sensor vendors lock temperature data in their own cloud with weak export APIs. Passes inspection while contract active. Nightmare at contract renewal or vendor switch.
Manual override without justification. Operator sees a sensor "false alarm" and marks the excursion as invalid without documenting why. MHRA finds it. Non-compliance.
Reporting built around what the software makes easy, not what regulators need. Excellent operational dashboards, terrible inspection-ready reports. Fix the reporting requirements before you sign a contract.
Frequently Asked Questions
What does GDP or HACCP compliance actually require in software?
GDP requires continuous temperature monitoring during storage and transport of medicinal products, temperature resolution to 0.1 degrees Celsius, documented deviation with root cause, and validated monitoring equipment. HACCP requires critical control point identification, monitoring, corrective action, and record-keeping for food safety. Both require immutable audit trails and inspection-ready reporting.
How much do IoT temperature sensors add to cost?
Single-use loggers £2 to £8 per shipment. Reusable Bluetooth £25 to £70 per sensor for 2 to 5 years. Real-time cellular £80 to £250 plus £3 to £8 monthly connectivity. Multi-parameter £150 to £400. Match sensor tier to shipment value and regulatory tier; do not use a £250 sensor for a £5 vaccine.
How do we handle temperature excursions in software?
Threshold breach detection within one minute, alert to on-call QA within five. Documented deviation with root cause analysis, corrective action, and preventative action. Automated escalation for repeated breach, sustained breach, or high-value shipment. All logged immutably for MHRA or FDA review.
Buy or build for cold chain software?
Off-the-shelf (Sensitech, Berlinger, Controlant, Roambee, Elpro) at £15 to £40 per asset per month wins for most operators under 200 monitored assets with standard MHRA or FDA requirements. Custom build (£200k to £450k for production) becomes defensible for cross-border multi-regulator operations, unusual sensor mixes, or per-client compliance portals SaaS does not cover.
How long does a cold chain platform rollout take?
Off-the-shelf: 6 to 12 weeks from contract to first live route, plus 3 to 6 months to reach full operational maturity. Custom build: 6 to 9 months from kickoff to production, plus further 3 months to complete IQ, OQ, and PQ validation for regulated environments.
The One Thing to Remember
Cold chain compliance failures at inspection are almost never about temperature control. They are about audit trail integrity and evidence retrievability. Design your software programme for the inspector who arrives 18 months from now asking for a specific shipment's temperature trace. If your system cannot produce it in under two minutes with cryptographically verified integrity, you have a compliance liability regardless of how good your operations are today.
If you want a candid audit of your specific cold chain gap, browse our custom software development services or come to the audit call.
