ERP & Warehouse Management
Enterprise Resource Planning
An ERP is the transactional backbone of the business: materials, orders, inventory, planning, procurement, finance. Within that span sits a GxP-relevant core that regulated organisations must treat as a validated system — material and batch master data, batch status management, expiry and retest dating, material genealogy, goods receipt against approved suppliers, and the warehouse movements that put physical product where its status says it may be. The warehouse management layer, whether a module or a companion system, executes the physical side: putaway, picking, staging, and shipping under the same status controls.
What this page does not claim
A system class is not a product. SPEQ describes what a CTMS or a LIMS is; the vendor directory at /tools lists the products that implement one, and a GAMP category is a property of an implementation, not of a class.
What a ERP & Warehouse Management actually is
An ERP is the transactional backbone of the business: materials, orders, inventory, planning, procurement, finance. Within that span sits a GxP-relevant core that regulated organisations must treat as a validated system — material and batch master data, batch status management, expiry and retest dating, material genealogy, goods receipt against approved suppliers, and the warehouse movements that put physical product where its status says it may be. The warehouse management layer, whether a module or a companion system, executes the physical side: putaway, picking, staging, and shipping under the same status controls.
The load-bearing function is batch status. A batch in quarantine must be undispensable, unpickable, and unshippable until a quality decision releases it — and the ERP is the mechanism that makes the decision physically effective. The decision itself belongs to quality; the ERP executes the status change and gates every subsequent transaction on it. The same machinery enforces expiry and retest dates, first-expiry-first-out picking, and the genealogy that answers the recall question: which suppliers' lots went into this batch, and where did every unit of it go. 21 CFR Part 211 frames these as warehousing and distribution controls; the ERP is how they operate at scale.
Distribution pulls the class into GDP. The EU GDP guidelines (2013/C 343/01), WHO's TRS 957 Annex 5, and MHRA's GDP expectations make wholesale storage and transport a regulated activity in its own right: temperature-managed storage locations, quarantine segregation for returns pending disposition, falsified-medicine controls at receipt, and shipment records that support recall to customer level. In the United States, DSCSA adds serialised traceability obligations that the ERP meets in concert with a dedicated serialisation system. A warehouse operator working a pick list is executing regulated activity through the system's controls.
Validation is a scoping exercise before it is a testing exercise. An ERP is vast, and most of it — general ledger, payroll, procurement negotiation — has no GxP impact; a documented GxP assessment separates the functions that touch product quality and patient safety from those that do not, and the validated scope follows the assessment. The GxP core is typically configured commercial software in GAMP 5 terms, with the custom code most large deployments accumulate treated on its own merits. Master data governance is the standing risk: a wrong shelf-life value or an unapproved supplier flagged approved propagates through every transaction that reads it.
WHERE THE BOUNDARY ACTUALLY SITS
Not the batch record. The ERP knows a process order exists and what it consumed; the electronic batch record holds the evidence of how the batch was actually made.
MES / EBR owns it →Not where the release decision is made. Quality decides disposition in its own records; the ERP executes the resulting status change and gates transactions on it.
eQMS owns it →Not the serialisation repository. Serial number generation, aggregation, and regulatory reporting events belong to the dedicated serialisation layer, exchanging shipment context with the ERP.
Serialization & Track-and-Trace owns it →Not exempt because it is a business system. The finance modules are out of GxP scope; batch status, genealogy, expiry control, and distribution records are not, and the assessment separating the two must be documented, not assumed.
WHAT IT HOLDS, AND WHAT CROSSES ITS BOUNDARY
CORE RECORDS
- Material and supplier master data, including approved-supplier status and quality info records
- Batch records in the inventory sense — status, quantity, location, expiry and retest dates
- Material genealogy linking supplier lots through production batches to finished goods
- Goods receipt records against approved suppliers and purchase specifications
- Warehouse movement history — putaway, picks, transfers, staging, and the status checks each passed
- Distribution and shipment records supporting customer-level recall traceability
- Returns, quarantine, and destruction records with their dispositions
DATA FLOWS OUT
Process orders, bills of material, and batch-managed material identities for dispensing and execution
Inspection lots raised at goods receipt and batch creation, triggering sampling and testing against specifications
Delivery and shipment events providing the transactional context for aggregation and regulatory reporting
Goods-receipt discrepancies and supplier-performance data feeding supplier complaints and requalification
HOW THIS CLASS IS USUALLY VALIDATED
- SPEQ synthesis: the GxP core of an ERP is configured commercial software — GAMP 5 Second Edition (2022) Category 4 — but nearly every mature deployment carries custom code that is Category 5 on its own merits. The category describes each element of the implementation, not the product, and the documented GxP assessment that scopes which functions are validated at all matters more than the category assigned to them.
- Batch-status gating is the control to verify hardest: the tests that matter are the negative cases — that quarantined, expired, and rejected stock cannot be dispensed, picked, or shipped through any transaction path, including the exceptional ones.
- Master data governance is part of the validated state. Shelf-life values, retest intervals, and approved-supplier flags are entered by people and read by everything; controlled maintenance with second-person verification is a validation deliverable, not an operational nicety.
- Upgrades are the standing threat to the validated state — ERP platforms patch frequently, so a risk-based regression approach tied to the GxP assessment keeps revalidation proportionate without letting release cycles erode the controls.
SPEQ synthesis, not a rating. This is SPEQ’s reading of how this system class is commonly approached, offered to help you scope your own work. A GAMP category is a property of a specific implementation, not of a product class, and one deployment routinely spans several. It is not a classification service and does not replace your own documented risk assessment.
- Stage 1 · Reactive
Inventory truth lives in spreadsheets reconciled against a system nobody fully trusts. Batch status is enforced by labels and floor discipline, genealogy is reconstructed by hand during recalls, and expiry control depends on whoever picks the stock.
- Stage 2 · Defined
The GxP scope is assessed and validated: batch status gates transactions, expiry dates block picks, and goods receipt checks supplier status. But master data maintenance is thinly controlled and warehouse execution still leans on paper travellers.
- Stage 3 · Controlled
Status, expiry, and genealogy controls are enforced end to end including the warehouse layer; master data changes run through controlled workflows with verification; and a mock recall resolves to customer level from system records alone, in hours.
- Stage 4 · Predictive
Inventory and distribution data is used predictively — supplier performance trends feed requalification, temperature and excursion data integrates with disposition, and slow-moving stock nearing retest dates is surfaced before it becomes a write-off or a deviation.
- Stage 5 · Adaptive
The ERP operates as the reconciled spine of a connected architecture: MES, LIMS, serialisation, and quality systems exchange status without manual rekeying, and recall, shortage, and continuity scenarios are rehearsed against live system data.
SPEQ’s shared five-stage progression, labelled synthesis. It is not the FDA QMM rating scale and not the scored maturity-assessment domains — assess your quality system for those.
WHAT AN INSPECTION PROBES, AND WHERE IT GOES WRONG
INSPECTION SIGNALS
- Whether quarantined or rejected stock can actually be shipped — inspectors ask for the negative demonstration, not the SOP.
- Recall readiness: how fast, and from system records alone, distribution can be reconstructed to customer level for a named batch.
- Who can change batch status, shelf-life master data, and approved-supplier flags, and what evidence each change carries.
- Whether goods receipt enforces the approved supplier list or merely records what arrived.
- Reconciliation between physical warehouse reality and system inventory, and how discrepancies are investigated.
COMMON RISKS
- Master data errors — a wrong retest interval or shelf life — propagating silently through every batch that inherits them.
- Custom code and user exits that bypass status checks in edge-case transaction paths nobody tested.
- Treating the whole ERP as out of GxP scope because finance owns it, leaving batch-status logic unvalidated.
- Warehouse processes drifting to workarounds — status overrides, negative-stock corrections — that unpick the gating the validation demonstrated.
- Upgrades applied on the vendor's cycle without regression against the GxP-critical functions.
WHO WORKS IN IT, AND WHERE IT IS SHAPED
ROLES
- Warehouse operator / material handler
- Supply chain and master data planner
- Responsible Person (GDP) / distribution quality
- ERP business process owner
- Master data steward
- CSV analyst
DELIVERY-LIFECYCLE PHASES
[ POSITION IN THE FRAMEWORK ]
6 OF 7 DIMENSIONS · 25 LINKSThe transactional backbone for materials, batches, and inventory — where batch status physically gates what can be dispensed, picked, and shipped, and where the GxP core must be validated even though finance is not.
06 · QUALITY MATURITY — ERP & WAREHOUSE MANAGEMENT, REACTIVE TO ADAPTIVE
Inventory truth lives in spreadsheets reconciled against a system nobody fully trusts. Batch status is enforced by labels and floor discipline, genealogy is reconstructed by hand during recalls, and expiry control depends on whoever picks the stock.
The GxP scope is assessed and validated: batch status gates transactions, expiry dates block picks, and goods receipt checks supplier status. But master data maintenance is thinly controlled and warehouse execution still leans on paper travellers.
Status, expiry, and genealogy controls are enforced end to end including the warehouse layer; master data changes run through controlled workflows with verification; and a mock recall resolves to customer level from system records alone, in hours.
Inventory and distribution data is used predictively — supplier performance trends feed requalification, temperature and excursion data integrates with disposition, and slow-moving stock nearing retest dates is surfaced before it becomes a write-off or a deviation.
The ERP operates as the reconciled spine of a connected architecture: MES, LIMS, serialisation, and quality systems exchange status without manual rekeying, and recall, shortage, and continuity scenarios are rehearsed against live system data.
SPEQ’s shared five-stage progression, labelled synthesis — not the FDA QMM rating scale. Where does your organization sit? Score your quality system →
07 · REGULATORY & EVIDENCE
GOVERNING STANDARDS · 8
Derived from the 8 standards SPEQ maps to this subject, across 6 regulatory bodies: FDA, EMA, ISPE, EC, WHO, MHRA.
RECORDS & OBJECTIVE EVIDENCE
- Material and supplier master data, including approved-supplier status and quality info records
- Batch records in the inventory sense — status, quantity, location, expiry and retest dates
- Material genealogy linking supplier lots through production batches to finished goods
- Warehouse movement history — putaway, picks, transfers, staging, and the status checks each passed
- Distribution and shipment records supporting customer-level recall traceability
COMMON INSPECTION FINDINGS
- Quarantined or rejected stock that can still be shipped through some transaction path
- Distribution that cannot be reconstructed to customer level from system records for a named batch
- Master-data errors — a wrong retest interval or shelf life — propagating through every batch that inherits them
- Goods receipt recording what arrived rather than enforcing the approved supplier list
- The whole ERP treated as out of GxP scope because finance owns it, leaving batch-status logic unvalidated
Choosing, validating, and living with ERP & Warehouse Management
FREQUENTLY ASKED
Is an ERP a GxP system?
Partially — and the partition must be documented, not assumed. Finance, payroll, and procurement negotiation have no GxP impact. Batch status management, material genealogy, expiry and retest control, approved-supplier enforcement at goods receipt, and distribution records are GxP-critical, because they decide what physical product can be used, where it went, and whether it was within date. A documented GxP assessment scopes the validated functions; the validated core then falls under 21 CFR Part 11 and EU GMP Annex 11 like any other regulated computerised system. "It is a business system" has never survived contact with an inspector examining batch status.
Who owns batch release — the ERP or the quality system?
Quality owns the decision; the ERP executes it. Batch disposition is a quality judgement made by the authorised person on the evidence — batch record review, testing results, deviation status — and recorded in the quality domain. What the ERP contributes is enforcement: until the status changes, the batch cannot be dispensed, picked, or shipped, and after rejection it can only move toward return or destruction. The integration between the release decision and the status change is therefore among the most safety-critical interfaces on the site, and the negative case — released nowhere else, blocked everywhere — is the one to verify.
Do warehouse operations really require a validated system under GDP?
The EU GDP guidelines (2013/C 343/01) expect computerised systems used in wholesale distribution to be validated or verified as fit for purpose before use, and MHRA and WHO carry the same expectation. In practice the obligations that bite are concrete: quarantine segregation that the system enforces rather than floor tape approximates, first-expiry-first-out picking, returns held from saleable stock until disposition, and shipment records that let a recall reach customers quickly. A warehouse management system whose status checks were never verified is a GDP finding waiting for its inspection.
How does the ERP relate to serialisation and DSCSA?
They divide the work. The ERP manages batches, quantities, and logistics — what was made, what is in stock, what shipped where. The serialisation system manages unit-level identity: serial number provisioning, commissioning, aggregation of units into cases and pallets, and the regulatory event reporting DSCSA requires in the US and the Falsified Medicines Directive drives in the EU. The two must reconcile — a shipment in the ERP needs matching serialised aggregation data, and quality status changes must reach the serialised record — but merging them into one system is rare; validated interfaces carry the joint obligation.