IT systems · Practical guide

Validating liberoMANAGER: assessing shipment data for completeness and traceability

An unchanged logger report may have been linked to the wrong shipment. Several normal reports can still leave a required transport segment uncovered. In liberoMANAGER, check record originality, shipment assignment, completeness and assessment separately. The worked example exposes gaps in PDF and real-time data.

Table of contents

At a glance

How do you validate liberoMANAGER for your shipment process?

Identify the loggers, time windows, product parameters and decisions required for the shipment. Test intake, correct assignment, completeness and documented assessment of data from the PDF or real-time paths actually used. Record the software version, workflow, permissions and external interfaces. Acceptance of an original PDF or a positive software assessment does not prove that the right complete data support the shipment decision.

  • liberoMANAGER is used for transport and shipping evaluation; stationary room and equipment monitoring is a different application scenario.
  • Originality, identity, time coverage, and professional assessment address different questions.
  • Manual, API documentation and actually used build need a comprehensible version reference.
  • The lifecycle of an API message is not the retention period for source data.

1. From transport information to the specific decision

ELPRO describes liberoMANAGER as a web-based SaaS solution for cold chain and shipment data. The platform can integrate PDF-based and real-time route information. However, for your compliance evidence, central data storage alone is insufficient: Which shipment, which products, and which transport segment are assessed, and which subsequent decision is based on that evaluation?

In the distribution of human medicinal products, GDP guidelines serve as the primary reference. Chapter 9 addresses transportation conditions and handling of deviations; Section 3.3.1 outlines validation evidence for computerized systems prior to their use. A GMP-specific application in human medicinal product manufacturing is separately addressed under Annex 11. GDP and GMP represent distinct areas of applicability, even though the same data set may support multiple processes.

Therefore, describe the scientific rationale first. A temperature-based assessment is not automatically equivalent to complete product release. Similarly, an uneventful curve does not prove that all anticipated transport data have been captured. The responsible personnel require a clear and justifiable basis for the exact decision your procedure prescribes.

Sources: [1] [10] [8] [7]

Further reading:

2. Handbook, API, and actual logger paths differ

The supplier's July 2025 announcement describes version 3.0 with Gx real-time integration alongside Cx USB/Bluetooth loggers. The public user manual also identifies itself as version 3.0. The Pub/Sub documentation specifies API 1.2.0 for target release 3.1.0. These references describe different things. Verify the active customer build separately.

In the described PDF workflow, the recipient reads the logger and transmits the original report. For Gx, the manual specifies a continuous data stream rather than a mandatory manual upload to the destination. Therefore, identical data availability timestamps should not be inferred. Document the actually used devices, transmission pathways, and settings.

Prepare a concise configuration sheet including: instance, release, device variants, workflow, evaluation parameters used, roles, and associated systems. Assign manufacturer documentation to the corresponding module. A general description of the current product family does not substitute for verification that your specific combination is supported and adequately validated.

Sources: [2] [3] [4] [8] [10]

3. The Five Questions for a Usable Batch Assessment

The product page describes a review of incoming ELPRO-PDFs for unaltered original state, as well as a verification of account assignment. This constitutes a key element of data acceptance. However, it does not automatically address all the technical questions related to your shipment. Correct file format and successful receipt are additional evidence beyond assignment to the correct product and time period.

The following internal work matrix addresses these questions. In the project, specify concrete data fields, responsible parties, and review criteria. This will clearly demonstrate which supplier functions support a requirement and where additional technical or specialist controls are necessary.

Own work matrix: from the original report to the basis for decision-making
Assessment questionPotential error despite existing reportEvidence needed
Originality File altered subsequently or stored as unusable Acceptance/rejection behavior for the actual transfer pathway.
Identity Correct file type but wrong logger or shipment Unambiguous relationship between Logger, Order, Product, and Transport.
Completeness A report is missing or a time period is not covered The intended sources and required timeframe are to be determined in advance.
Assessment Inconsistent parameter or calculation value Sound scientific rationale and traceable reporting basis.
Use A subsequent system acquires a different value. The decision and the actually received information are consistent.

Sources: [1] [3] [10] [8]

4. Define completeness prior to evaluation in a subject-matter specific manner

Determine which loggers and time periods are required for the planned decision. This determination may depend on shipment structure, measurement concept and transport route. The number of files received is not sufficient replacement. A double-filed report does not supplement any other missing source.

In addition, distinguish a fully received dataset from a technically fully covered transport. A logger can generate a continuous report that only initiates after the start of the relevant section. For real-time data, additional clarification is required regarding whether further information remains. How the application represents or handles such states must be documented for the specific version and configuration.

Plan targeted countermeasures: missing logger, incorrect shipment number, delayed arrival, or inappropriate start time. Prior to testing, specify which information is missing for decision-making and how to handle it. This does not result in a universal technical block for incomplete shipments, but rather a verifiable requirement for your intended process.

Sources: [3] [1] [10] [8]

5. Sample calculation: three loggers, but still no complete foundation

For this example, three different loggers, L1, L2, and L3, are assigned to the same shipment. Each logger is responsible for covering the time period from 08:00 to 14:00 hours. All time periods share the same time reference. This results in six hours of coverage per logger, totaling 18 logger hours. This auxiliary metric evaluates only temporal coverage, neither temperature quality nor a software-based completeness formula.

The table contains independent incident cases. Prior to each error case, the specified initial state is restored. Continuous time intervals without internal gaps are assumed; the number of discrete data points is not calculated. All logger identifiers and reactions are assumed test conditions and do not represent actual liberoMANAGER results.

Calculated expected results for identity and time coverage
SubcaseIndependent calculationOwn Required Assessment
Requirement: L1, L2, L3 each from 08:00 to 14:00 3 × 6 hours = 18 logger hours Three different sources with correct shipment traceability required.
Only L1 and L2 cover 6 hours each. 2 × 6 = 12; missing 18 − 12 = 6 logger hours L3 is missing; existing reports, although inconspicuous, do not close the gap.
L1 is additionally submitted a second time. Furthermore, 2 different loggers and 12 covered logger hours Do not count duplicate imports as new sources.
Third report belongs to a different shipment For the current shipment, still 12 out of 18 logger hours remain. Originality does not replace proper assignment.
L3 is correctly assigned, but starts at 09:00. 6 + 6 + 5 = 17; missing 1 logging hour For L3, there is a gap from 08:00 to 09:00; the sum alone does not yet identify the deficiency locally.
All three valid loggers cover 08:00–14:00. 6 + 6 + 6 = 18 logged hours Temporal requirement fulfilled; temperature checks and professional assessment remain to be reviewed.

Sources: [1] [3] [10] [8]

6. Maintain traceability of evaluation basis and decision authority

liberoMANAGER is offered with configurable workflows and temperature-based evaluation. For your project, it must be defined which product parameters, time periods, and professional guidelines are to be used. The public functional description does not provide a universally applicable algorithm nor a stability calculation suitable for every medicinal product.

Assess a suitable hypothetical scenario with independently defined expectations. Subsequently, deliberately alter a relevant assumption, such as product assignment or a selected time period. The evaluation should clearly demonstrate the basis upon which the assessment was conducted. A subsequently updated parameter set must not unilaterally replace the rationale underlying a prior decision.

You must also define who may view, assess, and authorize the further use of data. The Support FAQ outlines organization-specific access rights; the specific role and workflow configuration remains to be determined. This does not result in a universal QA signature for every report nor does it grant permission to use any positive software evaluation without the intended professional context.

Sources: [1] [5] [8] [10] [9]

7. Original data, evaluation report, and retention differ

The handbook lists various file types, including Original Logger PDF, Evaluation and Shipping Reports, as well as exports. These designations already indicate that not every file serves the same function. Determine which records clearly demonstrate the data origin, the selected evaluation, and the subsequent decision.

An export should be verified for its intended use. Are logger identity, time period, relevant parameters, and evaluation status included or reliably linked? Can authorized personnel later read the required context? A PDF is therefore neither generally unsuitable nor inherently complete solely due to its format. The required documentation shall be determined by the specific process.

For GDP, data control, availability, backup, and failure recovery procedures are explicitly addressed in Section 3.3.1. Within the GMP scope, Annex 11 and Chapter 4 further define the relevant requirements. Define the applicable retention period and verify recoverability as well as data relationships. Publicly available hosting or backup information does not substitute for clarification of the agreed scope.

Sources: [3] [1] [10] [8] [9]

8. API Release and data inventory are distinct forms of validation evidence

The Pub/Sub documentation for API 1.2.0 and target release 3.1.0 describes message routing by organization, partition, and message type. The received message payload thus depends on the actual configuration. Prior to integration, verify which information an attached system requires for its function and whether the established routing path actually provides it.

The documentation specifies a retention period of three days for the described messages. This is not a regulatory retention period and does not indicate that platform data will be deleted after three days. Following a prolonged interruption in reception, it must be clarified how the target system verifies the completeness of its data and, if necessary, how missing information is appropriately replenished.

Assess changes to filters, workflow, data model, and release processes jointly with the affected process. A successful technical integration does not constitute full functional handover. Similarly, every modification does not necessitate the invalidation of all previous tests. Assign existing documentation to the relevant areas and purposefully supplement the modified transition paths.

Sources: [4] [8] [10]

Further reading:

9. What level of involvement is required for a manageable project

Prepare a real-world example as a process description: products, transport segments, required loggers, data pathways, and intended decisions. Include instance and version information as well as existing work instructions. QA and logistics should be able to explain which data they actually require; IT and supplier shall provide configuration and interface details.

Effort is particularly high due to mixed PDF and real-time pathways, multiple recipient organizations, individual evaluation rules, and external integrations. Missing assignments or inconsistent workflows may require more clarification than a larger volume of similar transmissions. Therefore, a robust planning approach should consider the diverse processes and exceptions, not solely the transport volume.

Use supplier documentation to the extent that the supplier’s capabilities and scope meet your requirements. Additional assessments may focus on your product parameters, roles, data acceptance, and decision-making processes. The internal or partner-executed activities are to be defined contractually and organizationally. Generic time, price, or outcome commitments cannot be derived from the product name alone.

Sources: [1] [8] [10]

10. Check list prior to use of a shipment assessment

This worksheet brings together the main evidence. Review each item against the intended process and record the impact of outstanding questions. Completing every field on a screen does not establish who makes the decision or on what basis.

  • Instance, release, logger types, transmission pathways, and external recipients are recorded.
  • GMP, GDP, or any other specific applicable scope is defined.
  • Required loggers, shipment assignments, and time periods are fixed prior to evaluation.
  • Originality, duplicate import, missing source, and incorrect assignment are appropriately verified.
  • Product parameters, evaluation basis, and intended decisions are understandable.
  • Access and decision-making authorities align with the actual workflow.
  • Original data, reports, and relationships remain available beyond the relevant deadline.
  • API filter, receipt outages, restarts, and changes are monitored and evaluated.

Sources: [10] [8] [9]

Project experience and collaboration

Link shipment data to the transport assessment

For liberoMANAGER, we start with an actual shipment and the information needed to assess it. With the people responsible, we identify the logger, original reports or real-time data, transport legs and assessment parameters. We can test an existing data path or plan new shipment profiles and handovers together. The decision must remain linked to the correct source data and the full period under assessment. Stationary room or equipment monitoring needs a separate assessment.

Frequently asked questions about liberoMANAGER

Is liberoMANAGER the same as elproMONITOR?

No. liberoMANAGER is designed for transport and shipment data from the cold chain. This guide addresses the acceptance, assignment, and evaluation of such shipments. Functions for stationary room and equipment monitoring must not be transferred solely because of the same manufacturer. For your project, the actually used loggers, transmission pathways, and decision-making processes must be considered, not a general summary of all ELPRO products.

Sources: [1] [2] [6]

Which version is relevant for our validation?

Your actual instance is defined by the functions and interfaces in use. The user manual specifies version 3.0; the pub/sub documentation references API 1.2.0 for target release 3.1.0. These sources indicate different states. Ensure appropriate release and configuration information is available prior to transferring detailed functionalities to your operations. A version announcement does not confirm the activation of an existing customer build.

Sources: [3] [4] [2]

Must all logger report records be manually uploaded?

No. The described Cx-PDF pathway includes the retrieval and transmission of the original report. For Gx, the handbook specifies an ongoing data stream and does not require a manual upload at the destination. Verify the actually used pathway and its prerequisites. Real-time functionalities must not be dismissed, as every PDF logger is expected to provide data during transmission.

Sources: [3] [2]

What does the inspection of an original PDF demonstrate?

ELPRO describes a check to verify whether an submitted PDF represents an unaltered original report. This supports data acceptance, but does not automatically demonstrate correct correspondence to a specific transmission or completeness of all required source materials. These attributes should be evaluated separately. Furthermore, an technically acceptable original report may still be inappropriate for a particular decision if the logger identity or time period does not align with the intended transmission.

Sources: [1] [10] [8]

Why are three received files insufficient for three anticipated loggers?

One file may be a duplicate import or belong to another shipment. Two distinct and relevant loggers still provide only two sources, even when one file arrives twice. Check unique identity and time coverage. Demonstrate automatic handling in your target configuration. The example assumes no particular built-in blocking mechanism.

Sources: [3] [1] [8]

Does a positive temperature assessment automatically constitute product release?

No, not without the defined professional context. First, appropriate data, product parameters, and the required time period must be available. Subsequently, it must be determined which decision the results support and who has the authority to make that decision. GDP requires a controlled approach to transport deviations. A software assessment neither replaces missing information nor automatically fulfills all prerequisites for the use of a product.

Sources: [1] [10] [8]

Is the three-day API time to live our retention period?

No. The documented TTL pertains to messages within the described Pub/Sub pathway. It does not constitute a statement regarding legal retention requirements nor a confirmation of platform data deletion after three days. Separate documentation and timelines for records and retention periods must be established. For connected systems, it must also be clarified how missing information resulting from reception failures will be detected and, if necessary, retrieved.

Sources: [4] [10] [8]

Is a review PDF sufficient as a complete justification?

An evaluation PDF is only sufficient if the required data context is preserved. The complete evidence must also include the necessary source data, parameter values, and assignments supporting the decision. To verify this, review the original report, evaluation report, and export as an integrated data package; the handbook assigns distinct responsibilities to each. Whether any component is required on a permanent basis should be determined based on the specific evaluation process and its documentation requirements.

Sources: [3] [10] [9]

Does each recipient require the same user permissions?

The Support FAQ describes organization-specific access settings; the product page outlines role- and permission-based access management. The functions required by a recipient depend on their specific responsibilities. The ability to view data, evaluate reports, and make decisions does not necessarily require the same level of authorization. Verify the actual configuration and associated evidence. A user registration does not imply general authorization to perform all workflows.

Sources: [5] [1] [8] [10]

What helps in defining scope and testing effort early?

Prepare a representative sample including target loggers, time periods, product parameters, and decision pathways. Include versions, data flows, roles, existing manufacturer documentation, and external interfaces. This enables visibility into different workflows and critical exceptions. The planning can then focus on actual traceability gaps, rather than treating every report equally or deriving project duration solely from outbound volume.

Sources: [1] [8] [10]

Sources and review date

Source: 6 October 2026. Manufacturer's receipts: liberoMANAGER manual 3.0, version 3.0 announcement from July 2025 and Pub/Sub API 1.2.0 with target release 3.1.0. No active customer build or concrete evaluation algorithm confirmed. EU-GDP 2013/C 343/01 and Human Medicine GMP are classified separately; Annex 11 and Chapter 4 respectively January 2011. The logger/period matrix is a separate work aid.

  1. ELPRO: liberoMANAGER – Cold Chain Monitoring Database
  2. ELPRO: liberoMANAGER software enhanced with real-time functionalities
  3. ELPRO Online Manuals: liberoMANAGER Online Manual
  4. ELPRO Online Manuals: liberoMANAGER Pub/Sub API
  5. ELPRO Support: liberoMANAGER – Access to the database
  6. ELPRO: elproMONITOR – Room & Equipment Monitoring
  7. European Commission: EudraLex Volume 4
  8. EU GMP Annex 11: Computerised Systems
  9. EU GMP Chapter 4: Documentation
  10. European Commission: GDP Guidelines for Human Medicinal Products

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Your shipment assessment verifiable safeguarding

We support you in consolidating the required data, business decision-making rationale, and the actual data transfer pathways.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →