Regulations and compliance · Practical guide

GDP computerised systems: which evidence is needed in medicinal product distribution?

Distribution systems influence which medicines are accepted, stored, returned or supplied. A functioning warehouse application gives limited evidence about those decisions. Connect the GDP requirements for human medicines, electronic stock records and appropriate tests, taking care to distinguish wholesale distribution from manufacturing.

Table of contents

At a glance

Do computerised systems used in GDP medicinal product distribution need validation?

Before use, suitable validation or verification must demonstrate that the system delivers the intended results accurately, consistently and reproducibly. EU GDP guidelines also call for an up-to-date system description, controlled access, data protection and backup, and arrangements for failure. The distribution process and its risks determine the evidence. Installation or a supplier certificate alone does not cover these tasks.

  • The GDP guidelines contain specific requirements for computerized systems.
  • Electronic storage status and actual handling of medicines must be consistent.
  • Distinguish accepting returned goods, assessing them and returning them to saleable stock.

1. Determine the GDP foundation for your area of responsibility

The basis is the EU Guidelines 2013/C 343/01 on good distribution practice for human medicinal products, dated 5 November 2013. These guidelines apply to the described wholesale distribution channel. Manufacturers must also take into account the relevant GDP requirements for the distribution of their products.

This article does not deal with the separate active substance GDP area or the production and QP certification of a drug batch. Even if the same ERP supports several activities, the appropriate technical basis for each function is to be determined.

Start with the process: Which decision is made by the system? Examples include the selection of an authorized recipient, the blocking of a recalled batch, or the assignment of a temperature log. From this, the relevant system scope is determined.

Sources: [1]

2. Translate GDP requirements into specific validation questions

Section 3.3.1 requires that appropriate validation or verification of intended results be performed prior to use. A current written description shall, among other things, explain the purpose, security measures, scope, key functions, and interrelationships with other systems.

The following matrix links these requirements to practical evidence. The format is flexible; a specific document series with predefined abbreviations is not required. What is essential is that the selected scope adequately covers the intended use.

GDP-relevant system functions work matrix
AreaProcess questionAppropriate testing
Inventory status Can stock that is not saleable be selected for delivery? Permitted and prohibited combinations of status and selection
Returns Is the assessment prior to re-saleability taken into account? Acceptance, open evaluation and justified decision-making differ
Data access Who is authorized to enter or modify relevant data? Check roles and specific change permissions
Sales record Is the product, quantity, counterparty, and required identities traceable? Trace the transaction from receipt to the intended output
Failure Are required data recoverable and procedures available? Test recovery and actual usability

Sources: [1]

3. Do not equate electronic separation with spatial separation

The GDP guidelines permit the use of an electronic system for specific separation purposes, provided it offers equivalent security and has been validated. This does not constitute general authorization to replace any physical separation with a screen status.

Section 3.2 identifies counterfeit, expired, recalled, and rejected medicinal products within the supply chain that must be physically segregated and stored in a designated area. In contrast, Chapter 5.5 permits an equivalent electronic segregation for the immediate removal of expired medicinal products from the saleable inventory. Determine the specific case before deciding whether electronic blocking is sufficient; both physical and electronic segregation measures must be considered in the design of the storage process.

The system validation should reflect the actual workflow: Which labels, storage locations, and picking routes are utilized? An electronic lock is only an appropriate control when the intended workflow cannot practically be circumvented.

Sources: [1] [2]

4. A return is not considered saleable upon entry booking.

The following example considers the return of 20 packages. According to the defined return procedure, complete documentation and a duly authorized positive assessment are available for twelve packages in the specific case. For eight additional packages, the required storage documentation remains pending.

The figure of twelve is an assumption for this example. It is not a regulatory acceptance criterion. Assess all conditions applicable to the specific return under section 6.3, including condition, identity, origin and a suitable assessment.

The test addresses the decision within the system: incoming does not equal reissue. Identical article numbers do not justify making the entire return history available collectively without considering its distinct documentation and traceability requirements.

Example: Return case with different assay levels
StepExpected result in this exampleWhere the inspection begins
Entrance Record 20 packages as a return shipment No automatic saleability granted solely through access
Positive assessment 12 packages meet all relevant requirements Authorized decision and appropriate inventory allocation
Outstanding evidence 8 packages not yet assessed for re-sale No premature selection for a shipment
Quantity reconciliation 12 plus 8 yield the 20 incoming packages No lost or duplicated subset entry
Later decision Only modify open subset after appropriate assessment. Original state and new decision traceable

Sources: [1]

5. Maintain sales records in a clear and accessible manner

Chapter 4 outlines the required records for received, delivered, or forwarded medicinal products. The information included shall comprise, among other details, date, medicinal product, quantity, and relevant business partners; batch numbers must be explicitly documented for medicinal products bearing the specified safety features. Additional product- or process-specific requirements remain to be considered.

Check whether a subsequent report actually contains these informations and their relationships. A delivery record table lacking an identifiable shipping address or a lost linkage between return and original shipment may complicate reconstruction.

PIC/S PI 041-1 expands the GDP perspective on data integrity: the relevant data context and process usage determine the necessary controls. Not every technical metadata is automatically equally important; however, required information must not be lost due to a reduced export.

Sources: [1] [2]

6. Operation, modifications, and service providers to be included

GDP guidelines require protection against unintended or unauthorized modifications, regular review of the accessibility of stored data, backups, and recovery procedures. Chapter 4 specifies a minimum retention period of five years for documents, subject to national requirements; Section 3.3.1 also includes a minimum retention period for backup data. This does not establish a general data deletion deadline for any data type after five years.

Section 3.3.2 requires a documented risk-based determination of the qualification and validation scope. Significant changes must be considered. A new status rule or interface could be relevant, even if the software version remains unchanged.

For actually outsourced GDP activities, the specific rules in Chapter 7 apply, including contract, responsibility, and audit requirements. The mere fact that a software vendor provides software does not automatically constitute an outsourced GDP activity. Assign specific functions accordingly, rather than treating every IT supplier relationship uniformly.

Sources: [1] [2]

7. Checklist for the GDP Computerized System

Use the checklist for an inventory review or prior to a change. The effort is based on the relevant functions and existing credible evidence, not on the total number of screen masks.

  • GDP activities and differentiation from manufacturing or active ingredient distribution described.
  • System purpose, functions, interfaces, and security measures currently documented.
  • Appropriate validation or verification documentation available prior to use.
  • Stock items and required physical or electronic separation clarified.
  • Return acceptance and decision on re-sale eligibility separated.
  • Authorized entries and modifications with role verification performed.
  • Relevant distribution records can be reconstructed in full.
  • Appropriate demonstration of security, accessibility, and recoverability.
  • Significant changes and outsourced GDP activities are controlled.

Sources: [1]

8. Preparing camp, responsible person and IT together

For a smaller distributor, an inspection of the actual data and product flow is often a valuable starting point. Follow an inbound shipment, a blocked position, a return, and an outbound delivery. The responsible person and relevant staff explain the technical decisions; the IT team describes the implementation.

Only thereafter can it be meaningfully assessed which supplier documentation is appropriate and which of our own cases are missing. A general assurance "GDP-compliant" does not replace the evaluation of your configuration and operational practices.

Keep manual transfers in mind. A printed record, an email release, or an external temperature log may constitute part of the evidence. The assignment, use, and retention must remain clear within the actual workflow.

Sources: [1] [2]

Project experience and collaboration

Check stock status against the actual decision to supply

With warehouse management, Quality and IT, we trace stock from receipt through blocking and release to dispatch. We test whether the system enforces the required decision and makes exceptions visible. Electronic segregation may work in a suitable case. Other stock types or process conditions need additional physical controls. We distinguish these cases and test the relevant transitions so that a formally correct posting cannot conceal an unauthorised delivery.

Frequently asked questions about Computerised systems under GDP

Is GDP validation required only for large distributors?

No. Section 3.3.1 bases the validation on the intended computerized system and its intended results, not on a general company size. An appropriate scope takes into account the specific process, its risks, and existing reliable evidence.

Sources: [1]

Must we necessarily use Annex 11 as the legal basis?

The GDP guidelines contain specific requirements for computerized systems. Annex 11 may provide additional methodological guidance or be relevant for a GMP process actually involved. It should not unreviewed replace the specific GDP foundation.

Sources: [1]

Is a technical installation qualification sufficient?

It may constitute part of the evidence. Additionally, the intended use must function reliably, for example, inventory control, return evaluation, and relevant records. Verify which technical functions the validation actually covers.

Sources: [1]

Can we always only electronically segregate medicines when they are locked?

No. The guideline distinguishes equivalent electronic controls for certain purposes from explicitly required physical segregation of specific stocks. Assign the specific stock type to the appropriate section 3.2 before determining the technical solution.

Sources: [1]

Can a return be immediately re-issued for commissioning?

Not solely based on incoming booking records. Prior to return to saleable inventory, the relevant prerequisites from Section 6.3 must be met and assessed. The system must properly support the prescribed process.

Sources: [1]

Which roles must be verified within the system?

In particular, verify who is authorized to enter, modify, and initiate inventory decisions. The scope shall align with your responsibilities and workflows. A role name alone does not constitute evidence that actual permissions are appropriately restricted.

Sources: [1]

Does every GDP data record have an exact retention period of five years?

No. The guideline contains minimum requirements and refers to national requirements. Assign documents and backup data to their specific purpose and consider other applicable provisions. A minimum retention period does not constitute an automatic deletion instruction.

Sources: [1]

Must the restoration actually be verified?

The guideline requires procedures for system failure and a system for data recovery. An appropriate demonstration should show that the required data and functions can be made available again. The mere existence of a backup file does not address this question.

Sources: [1] [2]

Does every software supplier require an automatic GDP audit according to Chapter 7?

It is essential to determine whether and which GDP activity is actually outsourced. For these activities, Chapter 7 includes specific audit and contract requirements. A pure software sale cannot be equated with the assumption of an outsourced sales process without further evaluation.

Sources: [1]

What needs to be verified after the implementation of a new return policy?

Assess the impact on acceptance, evaluation, status, selection for delivery, and traceability. Derive appropriate cases therefrom, including open justifications and invalid early release. Existing relevant documentation may be reused.

Sources: [1] [2]

Sources and review date

Source: 7 October 2026. EU-GDP for the wholesale distribution of medicinal products for human use. Active substance GDP, QP certification and production are not equated. National additions have to be taken into account separately. Tables and case studies are own work aids, no product tests carried out.

  1. European Commission: GDP Guidelines for Human Medicinal Products2013/C 343/01 of 5 November 2013, published 23 November 2013 and applicable from 24 November 2013. Official German text. The introduction and sections 3.2, 3.3.1–3.3.2, 4.2, 6.3, 7.1–7.3 and 11 address computerised systems, segregation, records, returns and outsourced GDP activities.
  2. PIC/S: PI 041-1, Data Management and IntegrityPIC/S PI 041-1, 1 July 2021. Sections 3.1–3.7, 9.1.1–9.1.6, 9.1.10 and 9.2–9.3 provide supplementary GMP and GDP data integrity guidance on process context and controls.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Capture GDP requirements in actual system operation

We support you in defining relevant functions, evaluating existing evidence, and reviewing your actual storage and data pathways. The scope is tailored to your activities and outstanding questions.

  • 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 →