Pharma warehouse management — batch tracking and compliance

In pharma, the batch (or lot) is the unit of quality and the unit of risk. Regulators approve batches, quality failures happen to batches, recalls target batches. So the first law of a pharma warehouse is: no anonymous stock. Every carton on every rack must be attributable to a specific batch, with its manufacturing and expiry dates known to the system — not written on a register that lives in a drawer.

In a WMS this identity is fixed at goods receipt: the operator cannot confirm a GRN without capturing the batch number, manufacturing date and expiry date, and the received stock is labelled with a scannable identity that carries the batch for its whole life in the warehouse. In Fast WMS, each received pallet or carton group becomes a uniquely numbered, barcode-labelled lot holding its batch (LPN), production date and expiry date — so every later movement is a scan against that identity, never a retyped batch number.

Two everyday consequences follow. First, the same product in two batches is two different stocks — stored, counted and picked separately, which is exactly what a drug inspector expects to see. Second, batch-wise stock reports become possible: how much of batch X remains, in which bins, at any moment.

Everything in a pharma warehouse expires, and expired stock is not merely a write-off — dispatching it is a compliance breach. The rotation rule is therefore FEFO — first-expiry-first-out — not FIFO: a batch received later can expire earlier, and expiry is the date that matters. (The distinction, and where each applies, is covered in FEFO in Indian warehouses.)

Enforcement works in two layers, both at the barcode scan. At picking, the pick list offers only the earliest-expiry eligible batch, and scanning any other batch — even of the correct product — is rejected. At dispatch, the load is validated again before it leaves, catching anything that bypassed the pick under time pressure. Between the two layers, an expired or wrong-rotation strip has no confirmed path out of the building.

Prevention runs upstream of enforcement: the lot expiry dashboard buckets every batch by time-to-expiry, so short-dated stock is flagged months ahead — while it can still be sold through faster channels or returned to the supplier under a saleable-return arrangement, rather than becoming an expiry-return dispute later.

A pharma warehouse always contains stock that must not be sold: consignments awaiting quality release, batches under complaint or market investigation, recalled goods awaiting return to the manufacturer, expired stock awaiting documented destruction, and temperature-excursion suspects. Good practice — and every audit checklist — requires these to be segregated and controlled.

The manual version of quarantine is a marked area of the floor and everyone's good intentions. The WMS version is a status: a batch or pallet placed on hold is invisible to pick lists, cannot be allocated to any order, and cannot be dispatched — the scans simply refuse. Release is an explicit, recorded action by an authorised user; both the hold and the release land in the audit trail with user and timestamp. Damage and destruction states are equally explicit, so expired stock leaves the books through a documented disposal, not a quiet adjustment.

The same status machinery covers the receiving side: material can arrive into quarantine by default and only enter saleable stock on QC release — mirroring how GDP-compliant pharma receiving is supposed to work.

Pharma compliance is ultimately about evidence. A drug inspector, a principal's auditor or a customer's quality team does not ask whether you intend to rotate stock correctly — they ask you to demonstrate what happened to a specific batch on specific dates. That demands an audit trail with three properties:

Completeness. Every movement — receipt, put-away, transfer, pick, dispatch, hold, release, adjustment — is recorded, with no off-system side doors. In a scan-driven WMS this happens naturally, because the scan is the transaction; there is no separate "writing it down" step to skip.

Attribution. Every record carries who did it and when. Role-based access means the person who holds a batch and the person who releases it are identifiable — and can be required to be different people.

Permanence. History is append-only: a pallet's location and status history accumulates; it is never overwritten. You can ask where batch X was on any past date and get an answer, which is precisely the question recalls and investigations ask.

The practical payoff is audit speed. When the evidence is a query rather than a stack of registers, an inspection that would have taken days of preparation becomes a report printed while the auditor waits.

A recall is where all four pillars are tested at once, under time pressure. The moment a batch is recalled — by the manufacturer, or by a regulator — the warehouse must answer three questions fast: How much of the batch do we still hold, and where? Which customers received the rest, on which invoices and dates? And can we prove the remaining stock is now blocked?

With batch-tracked, scan-recorded stock, the sequence takes minutes: the batch trace report lists remaining quantities by bin; a hold status blocks them from any dispatch; and the batch-wise dispatch history produces the customer list that drives the recall communication. Every step is itself logged — so the recall response is documented as it happens, which is what the post-recall review will ask for.

Beyond batch-level control, pharma regulation worldwide is moving toward unit-level identification — serial numbers or QR codes on individual packs, so any pack can be verified and traced. India has been part of this shift for years: exported pharmaceuticals carry track-and-trace serialisation requirements, and barcode/QR-code identification has been mandated on top-selling domestic brands, with the coverage direction clearly expanding rather than contracting.

For warehouse operators, the practical takeaway is not to predict the exact next notification — it is that scan discipline is the foundation serialisation builds on. A warehouse already scanning batches at receipt, picking and dispatch has the workflows, hardware habits and data structures in place; adding deeper identifiers extends the same discipline. A warehouse still running on registers faces both transitions at once.

Temperature-controlled pharma adds one more dimension — chiller-zone storage and cold-chain discipline — which is covered in the companion guide, Cold storage warehouse management.