FEFO compliance in Indian pharma and FMCG warehouses is the difference between regulatory survival and operational catastrophe. An expired Schedule H drug reaching a hospital. A recalled FMCG product untraceable across the distribution network. A batch of temperature-sensitive goods released without quality clearance. These are not hypothetical edge cases—they are what happens when a warehouse operates on manual batch tracking instead of system-enforced FEFO, and they happen in Indian warehouses every week.
The regulatory pressure is intensifying. CDSCO is expanding serialisation requirements across scheduled drug categories. FSSAI is moving toward digital traceability for food products. Modern trade retailers now contractually require minimum remaining shelf life at point of delivery. And q-commerce platforms impose financial penalties for expired or near-expiry inventory reaching dark store shelves.
Sources: CDSCO regulatory updates 2025 · FSSAI digital traceability framework · Industry compliance benchmarks.
This article is written for warehouse and supply chain leaders in Indian pharma and FMCG operations who need to understand what FEFO compliance actually requires at the system level, what batch traceability means across the full warehouse lifecycle, and what it takes to pass a recall test in under four hours.
Pharma: regulatory compliance is non-negotiable. CDSCO, WHO-GSP, and Schedule H requirements govern how drugs are stored, handled, and dispatched. Failure means licence cancellation, criminal liability, and—most importantly—patient harm. Every batch movement must be logged. Every operator must be traceable. Every expiry date must be respected.
FMCG: compliance is commercial rather than regulatory, but the financial impact is equally severe. B2B modern trade retailers (D-Mart, Reliance Retail, Spencer’s) contractually require seventy percent or more remaining shelf life at point of delivery. Reject the shipment and the brand absorbs the loss. Q-commerce dark stores accept thirty to forty percent remaining shelf life because the consumption cycle is shorter—but expired product on a Blinkit shelf triggers platform penalties and brand reputation damage.
The shared failure mode: the warehouse operates on FEFO in theory—the SOP says ‘pick the oldest batch first.’ In practice, pickers grab whatever is closest, whatever is easiest to reach, or whatever the supervisor points to. Manual FEFO compliance has a failure rate that grows proportionally with warehouse volume and SKU count. FEFO must be enforced at the system level—at the scan, at the pick, with the WMS blocking non-compliant selections—or it will fail.
FIFO (first-in, first-out) picks inventory based on receipt date—the batch that arrived earliest is picked first. FEFO (first-expiry, first-out) picks based on expiry date—the batch that expires soonest is picked first, regardless of when it was received.
Worked example: Batch A was received on 1 January with an expiry date of 31 March. Batch B was received on 15 January with an expiry date of 28 February. Under FIFO, Batch A would be picked first (received earlier). Under FEFO, Batch B is picked first (expires sooner). For any product with a shelf life—pharmaceuticals, food, personal care, dairy—FEFO is the correct dispatch logic.
MethodPicks Based OnUse CaseRisk if WrongFIFOReceipt date (first in)Non-perishable, no expiryN/A for non-expiryFEFOExpiry date (first expiring)Pharma, food, personal careExpired stock dispatched; regulatory failure
In Indian warehouses, the distinction matters because many legacy systems only support FIFO. They cannot differentiate between receipt date and expiry date at the pick level. This means a warehouse running FIFO may dispatch a newer batch with a longer shelf life while an older batch with a shorter shelf life sits in the rack and expires—creating write-offs, waste, and compliance failures.
Batch traceability is not a single data point. It is a chain of custody record that must be maintained across five distinct warehouse operations:
At goods receipt, the WMS must capture: supplier lot number, internal batch ID, manufacturing date, expiry date, quantity received, quality status (under testing/released), and the receiving operator’s identity. For pharma, the WMS must also capture temperature logger data if the goods are cold-chain.
During storage, the WMS must track: bin location, zone, storage conditions (ambient, chilled, frozen), and any quality status changes. If a batch is moved between locations, the movement must be logged with timestamp, operator, and reason code.
At picking, the WMS must record: which batch was picked, by which operator, at what time, for which order. FEFO enforcement happens here—the system directs the picker to the correct batch and blocks the pick if the wrong batch is scanned.
At dispatch, the WMS must record: which batches went to which customer or destination, via which carrier, with what documentation. For pharma, this includes regulatory dispatch documentation and transport temperature compliance.
When product is returned, the WMS must capture: which batch was returned, its condition, and the disposition decision (restock, quarantine, reject, return-to-vendor). For FEFO-controlled products, the system must evaluate remaining shelf life before allowing restocking.
LevelData CapturedWho Needs It1. ReceiptSupplier lot, batch ID, expiry, qty, statusQA, regulatory audit2. StorageBin location, zone, temperature, status changesWarehouse ops, GDP3. PickBatch picked, operator ID, timestamp, orderSLA tracking, audit trail4. DispatchBatches per customer, carrier, documentationCustomer service, recall5. ReturnsBatch returned, condition, dispositionQA, inventory accuracy
A recall scenario is the ultimate test of your warehouse traceability. The question you must answer within four hours: how much recalled stock is currently on hand? To which customers or distribution points was it dispatched? Has it been further distributed downstream?
Without WMS: days of manual work across spreadsheets, ERP reports, and phone calls to distributors. The answer is never one hundred percent accurate. The regulatory body does not wait.
With WMS: a full batch trace report—forward and backward, from supplier lot to every customer who received that batch—generated in minutes. Complete with operator IDs, timestamps, quantities, and destinations.
For Indian pharma operations, this is not optional. CDSCO inspectors expect real-time batch trace capability. For FMCG, a recall that takes weeks to complete instead of hours becomes a brand reputation event with national media coverage.
Near-expiry flagging and quarantine workflows. The WMS must automatically flag inventory approaching expiry thresholds—configurable by product category—and trigger quarantine workflows that remove near-expiry stock from pickable inventory.
Shelf-life segmentation by channel. Different channels accept different remaining shelf life. B2B modern trade requires seventy percent or more. Q-commerce dark stores accept thirty to forty percent. Export channels may require eighty percent or more. The WMS must route batches to the appropriate channel based on remaining shelf life automatically.
Quality status management. Stock exists in multiple states: Under Testing, Released, Quarantined, Rejected. The WMS must enforce status-based picking—only Released stock is pickable. Status conversions (e.g., Under Testing to Released) must follow multi-level approval workflows. For pharma, this is a WHO-GSP requirement.
Quality StatusPickable?Approval Required?TriggerUnder TestingNoYes — QA releaseGoods receipt (pharma, food)ReleasedYesN/A — defaultQA approvalQuarantinedNoYes — QA + mgmtNear-expiry, temp excursion, recallRejectedNoYes — disposalFailed QC, damaged, expired
CDSCO: Batch-level logging of every movement by operator and timestamp. Serial number tracking for Schedule H drugs. Audit trail available on demand. Temperature monitoring integration for cold-chain GDP compliance.
WHO-GSP: Good Storage Practices compliance including storage condition monitoring, access control logging, and deviation reporting.
FSSAI: Digital traceability for food categories including batch genealogy (forward and backward trace from supplier lot to consumer delivery) and shelf-life management with channel-specific routing.
Bin-level batch tracking with FEFO enforcement. The picker must scan the correct batch. The system blocks wrong-expiry picks. No override without supervisor approval and reason code.
Near-expiry alerts and shelf-life routing. Automatic flagging of inventory approaching expiry thresholds, with channel-based routing (modern trade vs. dark store vs. export) configured per product category.
Full batch genealogy. Forward and backward trace from supplier lot to customer delivery, generated in real time. Recall trace report available in minutes.
Serial number tracking. For expanding Schedule H mandates and CDSCO serialisation requirements—scan-at-every-touchpoint data capture ready for current and future regulatory scope.
Quality status management with multi-level approval. Under Testing, Released, Quarantined, Rejected states enforced at the system level. Status conversions require configured approval workflows.
Temperature monitoring integration. Stackbox integrates with temperature monitoring systems for cold-chain warehouses—flagging excursions and triggering quarantine workflows automatically.
Q: What is FEFO and why is it critical for Indian pharma and FMCG warehouses?
A: FEFO (first-expiry, first-out) ensures products with the nearest expiry date are picked first, regardless of receipt date. For Indian pharma, FEFO is a regulatory requirement under CDSCO and WHO-GSP—failure to comply risks licence cancellation. For FMCG, it is a commercial requirement—modern trade retailers reject shipments below 70% remaining shelf life.
Q: How fast can a WMS generate a recall trace report?
A: With Stackbox, a full forward and backward batch trace report—from supplier lot to every customer who received the batch—can be generated in minutes. This is critical for the 4-hour recall response window expected by CDSCO.
Q: Does Stackbox support CDSCO, WHO-GSP, and FSSAI compliance?
A: Yes. Stackbox provides native CDSCO audit readiness with batch-level logging and serial tracking, WHO-GSP compliant storage and access controls, and FSSAI digital traceability with batch genealogy for food categories.
Q: Can the WMS route different batches to different sales channels based on shelf life?
A: Yes. Stackbox’s shelf-life segmentation automatically routes batches based on remaining shelf life: 70%+ for modern trade, 30–40% for q-commerce dark stores, and configurable thresholds for export and other channels.
Q: What quality status management does Stackbox provide?
A: Stackbox enforces four stock states (Under Testing, Released, Quarantined, Rejected) at the system level. Only Released stock is pickable. Status conversions require multi-level approval workflows, meeting WHO-GSP Good Storage Practices requirements.
See how Stackbox enforces FEFO at the system level, delivers recall-ready traceability in minutes, and prepares your operation for CDSCO and FSSAI’s expanding digital compliance requirements—no commitment, 30-minute walkthrough.
