IT systems · Practical guide

Validating EPG LFS in a GxP warehouse: testing blocks at each relevant stock movement

A warehouse may move a batch that is still blocked for manufacturing. In EPG LFS, trace quality codes, partial quantities, reservations and confirmations to the specific action permitted. The quantity example helps QA, warehouse managers and IT check the critical paths in both manual and automated warehouse areas.

Table of contents

At a glance

How do you validate EPG LFS for a GxP warehouse process?

Assess the installed LFS configuration against warehouse decisions and their risks. Verify that batch identity, quality status and quantities survive stock splits, transfers, reservations and feedback to ERP. Permission for an internal movement must not allow unauthorised withdrawal for production. Supplier evidence can contribute. The installed release, enabled modules, interfaces, roles and procedures determine the tests needed.

  • Check the blocking effect based on action and execution path, not solely on status designation.
  • Track the subset, batch, unit of measure, and quality status together.
  • Correlate technically relevant ERP, WMS, and automation feedback data.
  • Stock availability and regulatory release are separately defined.

1. LFS, EPG ONE WMS and Your Actual Installation

EPG runs LFS as a warehouse management system for manual and automated bearings. The current English main page uses the name EPG ONE WMS; public industry information and the EPG Academy continue to use LFS. For your validation project, the concrete installation is decisive: Product designation in the contract, build, database, clients, modules and shared extensions belong in the system description.

The current product page references on-premise as well as Cloud/SaaS environments, implying that responsibilities for updates, backup, and operations are not identical across these environments. It is essential to clarify who operates each environment and who announces, evaluates, and implements changes. A brochure number available online, such as R4-0, does not constitute a reliable proof of the software version in use.

Publicly available information does not provide the current numerical LFS release currently asserted. Therefore, request version-specific functional descriptions and relevant known limitations for your scope of supply. This prevents testing from assuming functions that are missing or operate differently in your configuration.

Sources: [1] [2] [3] [10]

2. Limit the GMP-relevant decision pathway

The primary scenario addressed in this guide pertains to inventory and production supply for a human medicinal product manufacturer. Critical control points arise, for example, where the system determines which batch of raw material can be assigned to a production order. An inventory fill-level indication has a different impact than the decision to release blocked inventory for use.

EU-GMP Annex 11 is the relevant guideline for computerised GMP activities. The current version in the Human Medicinal Product Directive is the 2011 revision. Scope and validation evidence are justified based on specific usage and risk assessment. A wholesale warehouse requires additional or alternative consideration in accordance with GDP; GMP and GDP are not interchangeable labels.

EPG describes industry-specific functionalities for pharmaceutical and healthcare sectors. However, the promotional claim regarding GAMP 5-certified processes neither replaces an evaluation of the actual documentation supplied nor constitutes your decision to use such processes. Assess which requirements are truly covered by supplier documentation and which arise specifically at your site due to configuration, equipment, interfaces, or workflows.

Sources: [4] [9] [10] [14]

Further reading:

3. Translate quality status into allowable actions

The EPG Academy outlines quality attributes and quality codes, locked and released stocks, and their impact on reservations, transfer, picking, and packaging. This provides clear starting points. The specific combination your installation actually implements remains a property that requires definition and verification.

The following work aid distinguishes purpose of movement from material usage. It defines specific reviewer expectations; it does not describe a predefined LFS configuration. Chapter 3.21 requires, for a system replacing physical quarantine, equivalent levels of security. A visible lock symbol alone does not suffice to address this requirement.

Work aid: separately define permitted storage actions and unauthorized subsequent actions
SituationPermitted procedure in the exampleUnacceptable consequenceTargeted evidence
Starting material under review Identified reallocation to the intended quarantine location Reservation for production solely due to the new storage location Compare destination site, quality code, and sample withdrawal procedure
Sealed pallet is split Two uniquely assignable loading units form A subset inadvertently receives free status Verify the origin and status of both units.
Order already created Put the order on hold or reschedule it under control Further processing of a batch that is no longer eligible for use Test an existing order and a new order separately
Technician moves goods in case of emergency Authorized, documented movement under emergency procedures Movement confirmation is interpreted as material release. Reconcile physical location, posting and release evidence
Released batch Withdrawal under the specified conditions Bypassing a relevant date or identity check Boundary cases for each intended issue path

Sources: [5] [13] [12] [10]

4. Batch, loading unit, and date retain their significance

A storage location is not a batch. A pallet can be split, a container repackaged, and a loading unit re-labeled. Define the identifiers that link these activities. Manufacturer documentation outlines batch, expiry date, and serial number handling; older LFS documentation also references splitting and repackaging. Confirm these functions for your current scope.

For test data, you need at least two visually similar batches and one intentionally erroneous scan. Verify whether the booking uses the scanned identity or inadvertently retains a previous screen value. During conversions between containers, units, and kilograms, the original unit and conversion factor must remain clearly visible.

Do not confuse minimum shelf life, expiration date, and retest date. Chapter 5.34 addresses the use of released starting materials within their retest validity period. Whether and how LFS implements this rule must be specifically defined. A general minimum shelf life field does not yet establish appropriate retest logic. Verify date boundaries and permitted exceptions against professionally defined expectations.

Sources: [3] [4] [5] [12]

5. ERP and LFS: successful transfer is still not a valid booking

EPG covers in its training transfer jobs, interface fields, feedback keys, and error handling. For SAP, there is a dedicated description including IDocs and RFC configuration. These integration capabilities do not indicate a specific repetition logic in your integration. Even a standardized connection requires a professional agreement regarding content and responsibility.

Prepare a concise agreement for each critical message type, including: leading system, object identity, unit of measure, status meaning, allowed sequence, success criterion, and responsible error handler. Distinguish between received, processed, and professionally booked. A technical transport protocol may be considered successful, while the target booking may be rejected.

Target a specific validation of a lost confirmation, a duplicate message, and a correction following error remediation. These are standalone testing recommendations. The expected control may be implemented technically or as a justified, controlled procedure; automatic one-time processing is not required. The final comparison must include quantity, batch, status, and order reference, not merely the count of green messages.

Sources: [6] [7] [10]

Further reading:

6. Verify authorities and history for critical changes

The Academy includes user and menu administration, as well as a history of locked and released items. This does not yet fully describe the required change traceability for your installation. Review specific cases to determine which information remains visible: affected inventory, previous and new states, user, timestamp, and reason for the change.

Separate the authority to physically move goods from the authority to change their usage status. This can be managed within small teams through appropriate roles and procedures. A specific job title or universal secondary signature is not required. Standing-in and privileged interventions also require clearly defined boundaries.

For the review, a risk-based selection is recommended: unexpected releases, status corrections, quantity changes, and administrative interventions are distinct events from routine warehouse transfers. Define who investigates anomalies and how actions are documented. An unusual booking serves as a trigger for investigation, not automatic evidence of misconduct.

Sources: [8] [5] [10] [11]

7. Example: Divide a locked pallet and repeat feedback

The following case does not constitute a completed product release. A manufacturer stores Batch A consisting of 240 sealed containers, each containing 2.5 kg: a total of 600 kg. Batch A is locked for production. Batch B comprises 40 released containers of 2.5 kg each, amounting to 100 kg. A production order requires 300 kg.

The scheduled batch A may be transported to the intended quarantine zone and divided into two loading units; no material withdrawal shall take place. The table considers the time point prior to actual release to production; therefore, reservation does not affect the physical inventory.

Perform the relevant portion both at the intended mobile work location and via the affected automation pathway. A failure would, for example, be a new available inventory after a split. Document such deviations including the initial state and actual impact. A status correction without root cause investigation is insufficient as evidence of a successful repeat test.

Example: Split matrix for reservation, reservation, and double confirmation
Test stepAction or failureIndependently calculated expected resultJustified effect
Initial condition Locked, B available A 600 kg + B 100 kg = 700 kg physically Only B is available for this task.
Split A 80 containers on A1, 160 on A2 A1 200 kg + A2 400 kg = A 600 kg Both portions remain locked and Batch A is assigned.
Internal Transport A1 reaches quarantine status Further 700 kg total inventory Storage location changes, usage status does not change
Approval is missing The movement of 80 containers is reported again A1 remains at 200 kg; no additional 200 kg Repeat occurrences are detected or investigated and resolved.
Allocate stock to the order 300 kg requirement; only B permitted 100 kg reserved, 200 kg shortage No automatic completion from locked A
Comprehensive inspection Upon reservation, prior to release 600 kg locked + 100 kg reserved = 700 kg Quantities, units, batch, status, and order are consistent together

Sources: [5] [3] [6] [10] [12]

8. Feed handling equipment, mobile clients, and emergency operation to be included

LFS can collaborate with automation components. Therefore, do not set a boundary on the screen: scanning, transport order, physical movement, confirmation, and inventory booking can occur in different components. Define which state is considered secured following a disruption and specify who identifies unclear loading units.

A useful test interrupts communication after an actual movement has occurred but before its confirmation is returned. Upon retry, neither a second transport nor a conflicting inventory status should occur uncontrolled. The specific behavior must be clarified with the supplier and automation partner; public product pages do not define a general retry sequence for this purpose.

An emergency procedure should specify which activities may continue, which must be halted, and how subsequent data entry will be coordinated. Paper lists are only useful if identity and status can be unambiguously reconstructed at a later time. The rollback to normal operations must be equally evaluated as the deviation itself. Temperature monitoring and physical storage conditions require their own appropriate controls.

Sources: [2] [1] [10] [13]

9. Plan and involvement in SMEs appropriately allocated

The effort arises primarily from variations: multiple storage areas, different sampling routes, customer-specific quality codes, interfaces, and historical data. A small installation with numerous manual exceptions can be more complex than a larger, uniformly controlled process. Therefore, plan based on critical decisions and edge cases.

The responsible party for storage provides actual work procedures and exceptional cases; the relevant quality functions define usage criteria; IT and suppliers clarify job responsibilities, roles, and data flows. Additionally, identify responsible parties for automation limits and emergency operation. Manufacturer documentation may provide supporting evidence but must align with your specific requirements and the version in use.

When changes are made, compare affected quality rules, masks, interfaces, and device pathways with the previous batch release basis. An update requires a justified impact assessment and appropriate validation activities. Include open interface defects, support cases, and unclear status corrections in routine evaluations. This ensures visibility into areas where the original assumptions no longer hold in practice.

Sources: [10] [1] [8]

10. Checklist for a sustainable LFS usage decision

Use this checklist as a reference tool for the closing meeting. Each response must be based on a specific status or verifiable evidence. An open point requires a assessed impact and a responsible decision, not merely the note "after go-live."

  • Product, Build, Modules, Hosting, and all relevant configurations are specified.
  • For each quality state, allowed movements and unauthorized usages are defined.
  • Splitting, relabelling and unit changes preserve batch identity, quantity and status.
  • Missing, duplicate, and erroneous feedbacks were evaluated through a technical cross-check.
  • Authorities for movement, status changes, and privileged interventions are verified.
  • Required records remain legible and retrievable during the intended retention period.
  • Consider physical movement of goods already in motion during non-operation and restart.
  • Deviations, residual risks, training, and decision-making authority are clarified prior to use.

Sources: [10] [11] [12]

Project experience and collaboration

Verify that a stock block still applies after a split and confirmation

With warehouse staff, QA and IT, we prepare controlled stock with a known batch, quantity and quality status. We trace it through splitting, stock transfer and the relevant ERP confirmation to the intended withdrawal decision. Permission to transport stock can be valid without releasing it for production. The configuration determines whether targeted checks suffice or status transitions need clarification with the implementation partner. The test record shows where the required block has been demonstrated.

Frequently asked questions about EPG LFS

Is EPG LFS already GAMP-certified and therefore validated for our process?

Such a conclusion would be overly broad. EPG uses a corresponding marketing statement regarding processes on a sector-wide platform. For your decision, what actually was reviewed—specific versions and functionalities—and whether these meet your intended use is decisive. Please clarify the scope and assess any remaining customer-specific risks. A manufacturer's statement neither fulfills your requirements nor provides evidence of the actual configuration in use.

Sources: [4] [10]

Is EPG ONE WMS the same as our existing LFS version?

EPG lists the LFS product line on the current English product page as EPG ONE WMS; the navigation still refers to "Warehouse Management System (LFS)". This does not imply a technical identity with any existing installation. Compare contract, release, activated modules, enhancements, and operating model. For existing documentation, particular attention should be given to which functions have been modified since the documented baseline.

Sources: [1] [2] [10]

May a blocked batch be moved within the warehouse?

This depends on the intended use and controlled process. An identified transfer to an appropriate quarantine area may be required, while product withdrawal remains unacceptable. Both statements shall be specified and tested separately. If physical quarantine is replaced by another system, equivalent security of that system must be justified. Additional requirements apply to segregated storage for rejected, recalled, or returned goods.

Sources: [13] [12] [5]

How can we test whether a block survives a pallet split?

Before performing the split batch, record the unit of measure, quantity, and quality status. Subsequently, verify both new load units and their origin traceability. Repeat the unauthorized withdrawal attempt for each sub-quantity via the relevant pathways. In this article's example, 80 and 160 containers still result in 600 kg of secured product. The inspection constitutes a separate recommendation; current split functions must be verified on a system installation basis.

Sources: [3] [5] [10]

Does a successful SAP IDoc message suffice as evidence of interface functionality?

No. A technical message must be checked for its actual meaning: Transport, processing and booking can be different states. Compare the result in both systems with batch, quantity, unit, status and order. The Academy describes SAP IDoc and RFC topics, but not a universal transaction guarantee. Your test should also include troubleshooting and repetition.

Sources: [7] [10]

Must LFS automatically reject each duplicate message?

A specific technical implementation cannot be inferred from publicly available documentation. A justified approach is essential—one that prevents or promptly identifies and controls unintended dual effects. Establish measurable acceptance criteria for this purpose. For critical, direct material usage, a difference detected only later may be insufficient. Therefore, evaluate the control timing and potential process sequence.

Sources: [6] [10]

Is the existing lock history automatically a complete audit trail?

No. The described history serves as a starting point, whose actual coverage you must verify. Investigate relevant changes, deletions, user identity, timestamp, reason for change, export activities, and review actions. Any interventions outside normal screen interfaces should be included in risk assessment. The required extent depends on data usage; not every logistical display requires the same level of evidence.

Sources: [5] [8] [10]

Does the MHD control replace a retest rule for starting materials?

Not without appropriate specification and validation evidence. Expiry date, minimum shelf life, and retest date have distinct meanings. For starting materials, the use within the intended retest period is particularly relevant. Assess which field and rule your process requires, how expiry dates function, and who is authorized to make changes. A general MHD function does not yet fully address this interrelationship.

Sources: [5] [4] [12]

Who must participate in the LFS validation at SMEs?

You need expertise and decision-making authority regarding warehouse operations, material usage, IT operations, and the relevant interfaces. Depending on the organizational structure, quality functions, ERP, and automation partners may also be involved. A fixed role list tailored to each organization would be inappropriate. Define clear outcomes: who determines the blocking effect, provides test data, evaluates deviations, and decides on usage? Stakeholder representation should be included in this process.

Sources: [10] [6] [8]

What changes trigger a re-evaluation?

Evaluate in particular changes to quality codes, reservation rules, interface fields, units, mobile dialogs, and automation workflows. The need for review is driven by the potential impact and existing evidence, not solely by the magnitude of a version number. A small parameter change can alter a critical restriction. Document the rationale, select appropriate regression tests, and verify post-implementation that the change functions as intended.

Sources: [10] [5] [1]

Sources and review date

Source date: 6 October 2026. EPG uses LFS and EPG ONE WMS; a current numerical software version is not publicly documented. Academy web pages provide training descriptions only and are not equivalent to version-specific user manuals. The older LFS brochure serves only for categorization and requires current validation. EU GMP refers to the specified use in human medicinal products; GDP is considered separately.

  1. EPG ONE Warehouse Management System
  2. EPG: Warehouse Management System LFS – Factsheet
  3. EPG/Ehrhardt + Partner: LFS integrated total solution
  4. EPG: Chemical, Pharma & Healthcare
  5. EPG Academy: Quality management in LFS
  6. EPG Academy: Interfaces
  7. EPG Academy: SAP Interface
  8. EPG Academy: System Administration in LFS
  9. European Commission: EudraLex Volume 4
  10. EU GMP Annex 11: Computerised Systems, January 2011 revision
  11. EU GMP Chapter 4: Documentation, January 2011
  12. EU GMP Chapter 5: Production, Revision 2014/2015
  13. EU GMP Chapter 3: Premises and Equipment
  14. European Commission: GDP Guidelines for Human Medicinal Products

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Verify the actual LFS usage in a structured manner

We support you in integrating critical storage decisions, interfaces, and existing evidence into a robust inspection assignment.

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