Häufig gestellte Fragen
Is a standard ERP enough for pharmaceutical wholesale or is an industry solution needed?
A pure standard ERP without pharma-specific functions is not sufficient in practice, because central obligations such as securPharm verification, a GDP-capable audit trail and separate narcotics (BtM) inventory management must be covered. These functions are either natively included in a pharma industry solution or added via a suitable add-on on top of a generalist, for example SAP S/4HANA or Microsoft Dynamics 365 Business Central with the audit mode activated. The specific setup depends heavily on assortment depth, company size and the existing IT landscape. What ultimately matters is whether the system can prove seamlessly in a regulatory audit that all regulated processes are running correctly.
Which securPharm obligations must an ERP cover in pharmaceutical wholesale?
securPharm is the German implementation of the EU Falsified Medicines Directive 2011/62/EU together with Delegated Regulation (EU) 2016/161, which has been binding since 9 February 2019. Wholesalers must verify prescription-only packs on a risk basis, in particular for returns from pharmacies or other wholesalers and for goods not obtained directly from or on behalf of the manufacturer. The ERP must integrate this verification via the Data Matrix code into the goods receipt and dispatch processes and be able to post reversals correctly in the event of an error. Manual workarounds without a direct interface connection to the national verification system are considered insufficient.
What requirements does GDP place on warehousing, temperature and documentation in the ERP?
The EU GDP guideline (2013/C 343/01) requires seamless, tamper-proof temperature monitoring with calibrated sensors, separated by temperature ranges such as 2–8 °C for refrigerated goods and 15–25 °C for room-temperature assortments. The ERP should ideally take this temperature data into the record per batch and keep an ALCOA+-compliant audit trail for every regulated posting, with user, timestamp, and old and new values. Added to this are qualification and training records, a deviation and CAPA process, and documented segregation of duties between operational and quality assurance roles. Inspectors regularly examine these points as focus areas, which is why missing standard reports can become expensive in an audit.
How must an ERP handle narcotics (BtM) in wholesale?
Under Section 17 of the BtMG, every holder of a narcotics licence must keep continuous records, separately for each site and each individual narcotic, of every receipt, every issue and the balance resulting after each movement. A suitable pharma ERP therefore maps narcotics as a separately managed area with its own posting documents and separate inventory management, so that, for example, returned narcotics remain cleanly and traceably segregated from the rest of the goods. The narcotics records, or the corresponding EDP printouts, must be retained for three years. This segregation serves the seamless control by the Federal Opium Agency at the BfArM and is a frequent checkpoint in audits.
Must an ERP in pharmaceutical wholesale be validated and what does that cost?
GxP-relevant IT systems in the regulated pharmaceutical environment must undergo computer system validation (CSV), with the risk-based approach of GAMP 5 and the requirements of EU Annex 11 providing the framework. Validation is not a one-off event but an ongoing lifecycle, in which every software or customising change must also be documented and tested. Typically, the validation and test concept covers GxP-relevant processes such as batch management, audit trail and permissions, through to performance qualification under real conditions. Costs vary greatly with complexity; for larger projects, an initial clearly five- to six-figure amount plus ongoing maintenance should be expected, with licences often making up only a smaller part of the total costs.
How does an ERP support FEFO and expiry date control in the pharmaceutical warehouse?
The EU GDP guideline requires that stock is moved primarily according to the First Expired, First Out (FEFO) principle, so that packs with the shortest remaining expiry leave the warehouse first, and that deviations from this are documented. To this end, a pharma ERP carries the batch and expiry date on every stock item and in every document, and automatically prioritises the earliest-expiring batch during picking. At the same time, batch traceability ensures that every movement remains traceable in both directions from the supplier to the pharmacy. This makes it possible to quickly identify, block and, in the event of a recall, specifically trace expired or defective batches.