What cold storage management involves
Cold storage warehouse management is ordinary warehousing with two extra, unforgiving constraints: every product must be held at the right temperature, and every product is expiring. That means goods must be stored in the correct zone (frozen, chiller or ambient), stock must leave in first-expiry-first-out (FEFO) order so nothing dies on the shelf, and every batch must be traceable from gate-in to gate-out for recalls and audits. A WMS enforces all three — with expiry captured at receipt, zone-aware bin locations, and FEFO applied at the barcode scan.
The economics are what make this different from dry warehousing. In a general warehouse, a management mistake costs time. In a cold store, it costs the product: stock that expires in the racks is a 100% write-off, and a single expired dispatch reaching a retail shelf can cost the client relationship. Meanwhile the electricity meter runs regardless — so every pallet position occupied by unsaleable stock is paid-for cooling wasted on goods already lost.
Temperature zones and location design
A typical Indian cold storage facility runs three broad zones, each of which is really a set of storage conditions with its own rooms, racks and door discipline:
Frozen — around −18°C and below: ice cream, frozen vegetables and snacks, meat and seafood. Chiller — roughly 0–8°C: dairy, fresh produce, chocolates, many pharmaceutical products. Ambient / dry — normal storage for packaging material and goods that need no cooling. Larger facilities add blast-freezing rooms and controlled-atmosphere chambers for specific produce.
In a WMS, each zone is simply a group of bin locations — and that mapping is what makes zone discipline enforceable. Because every item master carries its required storage condition, put-away is directed: a pallet of ice cream is sent to a frozen-zone bin, and the handheld will not confirm put-away into a chiller bin. Zone mistakes stop depending on the loader remembering which product tolerates what.
Zone-aware locations also improve the thing cold stores care about most after product safety: door-open time. When the system knows the exact bin of every pallet, a picker enters the frozen room with a bin-directed pick list, goes straight to the location, scans and leaves. Less searching means less door-open time, less temperature fluctuation and lower energy cost. Bin structure is covered in more depth in Bin & Location Management.
Expiry capture at GRN — the make-or-break moment
FEFO has a dependency that most failed implementations ignore: the system can only rotate stock by expiry if it knows the expiry — and there is exactly one reliable moment to capture it: goods receipt. If a batch enters the cold store without its expiry date recorded, that pallet is invisible to every expiry control downstream. Six months later it surfaces in a physical count as a write-off nobody saw coming.
A cold storage WMS therefore makes batch and expiry mandatory fields at GRN. Receiving on the handheld, the operator scans the item, enters or scans the batch number, production date and expiry date — and cannot confirm the receipt without them. From that moment, the pallet's identity permanently carries its batch and expiry: through put-away, transfers, picking and dispatch.
Two-layer FEFO enforcement
First, the distinction that matters: FIFO dispatches the oldest-received stock first; FEFO dispatches the earliest-expiring stock first. They usually agree — but not always. A later delivery can carry an earlier expiry (a supplier clearing older production, a returned consignment re-received). For perishables, expiry is the date that costs money, so expiry must drive the rotation. Read the full comparison in FEFO in Indian warehouses.
The second thing that matters: a FEFO policy is not FEFO. In a manual cold store, the picker takes the nearest carton — reaching past the short-dated stock at the back. Enforcement has to live in the system, and it works in two layers:
Layer 1 — the pick. The pick list offers only expiry-eligible pallets, ordered so the earliest-expiry batch goes first, with the bin location of each. If the picker scans a different batch — even of the correct item — the scan is rejected on the spot. The wrong pallet physically cannot progress to packing.
Layer 2 — the dock. Before the vehicle leaves, dispatch validation scans the load against the order. Anything that slipped past the pick — a manual substitution, a mixed pallet — is caught at the last controllable moment, while the goods are still inside the cold chain and recoverable.
Two layers matter because each one alone has a failure mode: picks get overridden under time pressure, and dock checks alone catch errors too late to re-pick efficiently. Together, they are why a scanned cold store can genuinely claim zero expired dispatches. The mechanics are described on the FIFO & FEFO Picking feature page.
See FEFO enforced live
Expiry capture at GRN, a rejected wrong-batch scan, and the expiry dashboard — the Cold Storage WMS variant in action.
The expiry dashboard — seeing risk before it becomes write-off
Enforcement stops expired goods from leaving. But the bigger financial win is upstream: making sure goods never expire inside. That requires seeing expiry risk while there is still time to act on it.
An expiry dashboard buckets all available stock by time-to-expiry — expired, expiring this week, within 15 days, 30, 60, 90 and beyond. Fast WMS presents this as a live view across every batch in every bin. The management routine it enables is simple and powerful: review the near buckets weekly; push short-dated stock out first through discounting, transfers to faster-moving channels, or return-to-vendor agreements; and investigate why anything reached the danger bucket at all — usually a slow-moving item that was over-purchased, which is a buying lesson, not a warehouse lesson.
For a cold-storage 3PL, the same dashboard becomes a client service: a weekly short-dated-stock report per client shifts the liability conversation. The operator flagged the risk; what the client does with 45 days of shelf life left is the client's call — documented.
Hold, quarantine and batch traceability
Not all stock in a cold store is dispatchable stock. A consignment arrives with a broken cold chain and needs quality inspection; a client instructs a hold on a batch under complaint; expired goods await destruction certificates. These states must be system states, not floor conventions:
In a WMS, every pallet carries a status — available, hold or damage. A pallet on hold is invisible to pick lists: it cannot be allocated, picked or dispatched until quality explicitly releases it, and both the hold and the release are logged with user and timestamp. Contrast that with the manual version — a "do not touch" corner of the freezer room that survives exactly until a rushed picker needs stock at 7 pm.
The same identity system provides traceability. Because every movement of every pallet is recorded — receipt, put-away, transfers, pick, dispatch — the full history of any batch is a query: when it arrived, where it sat, and which customers received it. When a recall comes, the affected-dispatch list takes minutes, not a weekend of challan archaeology.
Compliance — FSSAI and audits
Food-grade cold storage in India operates under FSSAI licensing, which expects hygienic, temperature-appropriate storage and stock handling that keeps expired goods out of the food chain — and batch-level records that support traceability when something goes wrong. Pharma storage adds its own good-distribution expectations: temperature discipline, quarantine control and documented batch histories.
The honest way to say what a WMS contributes: it does not measure your room temperature — that is your refrigeration and monitoring equipment — but it provides the stock-side evidence audits ask for. Expiry and batch captured at receipt, FEFO rotation demonstrably enforced (not just claimed), expired and held stock blocked from dispatch, and a movement history per batch that can be produced on demand. When an FSSAI auditor, a client auditor or a recall asks "show me", the answer is a report rather than a reconstruction.
Multi-zone cold storage operator, Pune
A cold-storage operator in Pune running frozen and chiller zones for food brands managed expiry on registers and physical stock rotation — with periodic write-offs and one client escalation over a short-dated dispatch. After moving to Fast WMS, batch and expiry became mandatory at GRN, pick lists began enforcing FEFO at the scan with dock validation as the second layer, and the expiry dashboard drove a weekly short-dated review with clients. Since go-live, no expired stock has been dispatched, and expiry write-offs surface as early warnings on the dashboard instead of month-end surprises.
What to look for in a cold storage WMS
Cold-store requirements are specific enough that a generic WMS checklist misleads. Evaluate against these:
| Capability | Why a cold store needs it | What to check in the demo |
|---|---|---|
| Mandatory batch + expiry at GRN | FEFO is impossible without expiry captured at the door | Try to confirm a receipt without an expiry date — it must refuse |
| Zone-aware bin locations | Frozen, chiller and ambient stock must be directed to the right rooms | Put away a frozen item and see which bins the system allows |
| Scan-enforced FEFO picking | Policy-level FEFO fails under floor pressure; scans do not | Scan a newer batch against a pick — it must be rejected |
| Dispatch-level validation | The dock is the last controllable moment before the customer | Load-check a dispatch and swap in a wrong carton |
| Expiry dashboard | Write-off prevention needs risk visible weeks ahead | View stock bucketed by days-to-expiry, filtered by client |
| Hold / quarantine statuses | Blocked stock must be invisible to picking, with an audit trail | Hold a batch, attempt to pick it, then release it |
| Batch movement history | Recalls and audits need per-batch traceability in minutes | Trace one batch from gate-in to every dispatch it touched |
| Client-wise stock (for 3PL cold stores) | Multi-client facilities must isolate and report per client | Pull one client's stock and expiry exposure only |
Expiry mechanics are covered further in Lot Expiry Tracking; food-specific operations are on the Food & Beverage WMS page; and the FEFO rulebook for Indian operators — including FSSAI's evolving record-keeping requirements — is in FEFO in Indian warehouses.
