All case studies Real implementation, anonymised

Pharmacy temperature monitoring case study: why a pharmacy group chose KRYOS

As a pharmacy cold chain monitoring case study, this anonymised implementation shows how a German pharmacy group replaced its previous cloud monitoring solution with KRYOS across seven pharmacies and 21 medicine and vaccine refrigerators.

The group already monitored fridge temperatures. The challenge was not basic measurement. The challenge was operational fit: roles, branch permissions, configurable alerts, escalation paths, notification options, ISO/IEC 17025 calibration certificate handling, external probe renewal, detailed reports, and exports that matched user access rights.

Request demo See pricing

Pharmacy cold chain monitoring case study scope

7 pharmacies, 21 refrigerators, one permissioned monitoring workflow

7 pharmacy locations

21 medicine and vaccine refrigerators

3 refrigerators per pharmacy

2-8 °C configured range

01 Branch 02 Fridge 03 External probe 04 User role 05 Alert 06 Report 07 Exports

Pharmacy cold-chain storage only: medicine-only and vaccine-only refrigerators inside the pharmacy group, not end-to-end transport monitoring.

Medicine fridge monitoring example: case identity

The pharmacy group was not starting from zero. It already had a cloud monitoring system and chose KRYOS because the implementation model fit its operation better.

Organisation: Anonymised German pharmacy group
Locations: 7 pharmacies
Assets: 21 medicine and vaccine refrigerators
Setup: 3 monitored refrigerators per pharmacy
Previous setup: Another cloud-based temperature monitoring solution
Rollout: Approximately 3 weeks
Time live: Approximately 6 months at the time of writing
Measurement: External probes placed inside refrigerators

The starting point was fit, not absence of monitoring

The pharmacy group did not need to be convinced that pharmacy refrigerator monitoring mattered. It needed a temperature monitoring system that matched how seven branches manage refrigerated medicine and vaccine storage.

The previous system covered basic monitoring

The replacement decision was not about rejecting monitoring. It was about whether the monitoring workflow could support a larger pharmacy operating model with the right roles, permissions, alerts, reports, and certificate access.

The buying question became operational

Could the group manage 21 refrigerator records, alert escalation, certificate retrieval, PDF/CSV exports, and branch-level access without making every user see or export everything?

Why KRYOS fit the group better

KRYOS was selected because several practical requirements came together. The decision was not only about temperature readings.

Configurable alerts and escalation

The group needed more flexible handling for high and low temperature excursions, disconnection notifications, alert recipients, escalation paths, and notification channels.

Role, pharmacy, and device access

Branch users and central users needed different visibility. KRYOS allowed access to be shaped by role, pharmacy location, and refrigerator or device.

Exports that respect permissions

A user can export only the records they are allowed to access. That matters when branch-level review and central group reporting both exist in the same organisation.

Calibration certificate workflow

Each external probe contains the calibrated sensor. KRYOS keeps certificate context cloud-accessible and supports a practical ISO/IEC 17025 calibration certificate renewal workflow.

External probe practicality

External probes were placed inside refrigerators. When renewal is needed, a certified probe can be exchanged by unplugging the old probe and plugging in the renewed one.

Reports, support, and price fit

The group valued PDF and CSV exports, historical measurement reports, incident or excursion reports, richer statistics, native German support, in-person onboarding, and a pricing model suited to 21 refrigerators.

How KRYOS was mapped to the pharmacy group

The implementation followed the group's real structure: branch, refrigerator, probe, user role, alert, report, and exports permission.

Branch

Each pharmacy stayed visible as its own monitoring and review context.

Refrigerator

Medicine-only and vaccine-only refrigerators were configured as separate monitored units.

External probe

External probes inside refrigerators carried the calibrated sensor context.

User role

Access could be configured around management, administration, visualisation, branch, and device needs.

Alert

High/low excursions and disconnection notifications could route to configured recipients.

Report and exports

Historical measurement reports and incident or excursion reports could be exported as PDF or CSV.

What changed in the monitoring workflow

This is the core implementation change: the monitoring record could be structured around how the pharmacy group actually worked, rather than only around a fridge reading.

Branch-level operation

Each pharmacy could keep its refrigerator context visible without losing the central group view needed for management, administration, and review.

Alert response context

Alerts could cover high excursions, low excursions, and disconnection notifications, with acknowledgement and response notes attached to the event history.

Report retrieval

When a record was needed, users could retrieve historical measurement reports, incident/excursion reports, and certificate context from the platform according to their permissions.

Audit checks the implementation supports

After a refrigerator event, the value is not only knowing the current temperature. The pharmacy group may need to explain the event by branch, device, probe, threshold, timing, user access, report, and follow-up note.

What remains a pharmacy decision

KRYOS provides environmental monitoring records, alerts, reports, exports, and sensor certificate context. The pharmacy group keeps decisions on medicine or vaccine stock use, quarantine, disposal, return to stock, inspection response, internal governance, SOPs, and final quality review.

Which pharmacy and refrigerator were involved?
Was the event above or below the configured 2-8 °C range?
When did the event start, recover, and get acknowledged?
What minimum or maximum exposure was recorded?
Was the issue a temperature excursion or a disconnection notification?
Which user could view the device and export the record?
Which report is needed: historical measurement or incident/excursion?
Which calibration certificate belongs to the probe?
What response note or follow-up was recorded?

Map your pharmacy monitoring workflow before comparing systems.

Bring your pharmacy locations, refrigerators, user roles, alert rules, notification preferences, certificate requirements, and export needs. KRYOS can help structure the monitoring record around how your group actually works.