How to Choose a Cold Storage WMS: Three Checklists for Temperature, Expiry, and Freezer Hardware

Here is the conclusion up front: when you choose a cold storage WMS, you are not buying the system with the longest feature list. You are buying the system that can hold three things together at sub-zero temperatures: temperature-zone control, expiry-date discipline, and hardware that actually works in the cold. A scorecard copied from an ambient warehouse will give you a confident-looking winner and a painful go-live, because the constraints are simply different.

I have seen this failure three times, in almost the same shape. A frozen-food operator signs for a solid ambient WMS, the demo goes well, and in the first week the floor tells a different story. Pickers in thick gloves cannot hit small touchscreen targets. Handheld batteries drain faster in the cold. Tasks mix temperature zones in a single wave, so people shuttle between a freezer and a staging area while doors open and close behind them. None of that shows up in a conference-room demo. All of it shows up on day one.

Cold Storage WMS Checklist One: Map Temperature Zones Before Locations

A cold storage WMS has to treat temperature zones as first-class data, not as a note on a location. Chilled, frozen, deep-frozen, tempering, and dock staging areas each have different rules, and the system must enforce them. Locations should carry a zone attribute. Wave planning should split by zone unless the business explicitly allows mixing, with a time limit attached. The system should track how long a task sits outside the cold zone and warn when that dwell time runs over.

Ask the vendor four specific questions. Can a zone change on a location be approved and audited? Can wave generation split by zone, configured separately by customer and product family? Can the system record out-of-zone dwell time per task? And can temperature-monitoring data feed in, so an excursion pauses task release instead of letting picks continue blindly?

One seafood project I worked on skipped exactly this step. The team asked whether locations were granular enough but never asked how zones were governed. After go-live, chilled and frozen orders landed in the same wave, and pickers ran between zones while product quality depended on people remembering the rules. Fixing it took three weeks, and the fix was not clever code. It was the zone logic that should have been in the tender from the start.

Do not forget the tempering area and the dock. Product leaving the freezer rarely goes straight onto a truck. It waits. That wait needs a clock in the system, a different limit per customer, and an alert when the limit passes. Ambient warehouses rarely need this. Cold stores live or die by it.

Cold Storage WMS Checklist Two: Treat Expiry as a Selection Criterion

The second checklist is about expiry, and I want to be precise about scope: this is selection only. How a team executes expiry-based picking on the floor is a separate subject, and this article does not go into that operation. The selection question is narrower: can the system hold expiry discipline before a single order is picked?

Confirm three things. First, is the expiry field mandatory at batch level, so receiving cannot skip production date and shelf-life data? Second, does the system keep different expiry batches visibly separate, so a planner can see at a glance which batch expires first? Third, can expiry alerts be set per customer? One customer may want ninety days of warning, another may only accept sixty. A hard-coded threshold will fail one of them.

I have seen the same failure three times in a second form: the expiry field exists but receiving can bypass it. Nobody notices until a customer complains about short-dated stock shipped by mistake, and by then the system holds a trail of empty fields. During the vendor demo, make them walk a real receiving transaction: scan a batch, enter the production date, watch the system calculate the expiry date, and see whether an error is blocked. A flow that cannot be demonstrated will not fix itself after go-live.

Ask one more question: can expiry standards sync with the customer's own quality system? Many cold-store customers define the standard, and if the WMS can only hold expiry by hand, every customer change becomes manual rework. Confirm the interface and the field mapping during selection, not after implementation has started.

Cold Storage WMS Checklist Three: Test Freezer Hardware in the Freezer

The third checklist is the one most easily hidden by a slide deck. Cold is physical. Batteries lose capacity, screens frost over, thick gloves miss small keys, and condensation attacks labels and barcodes. None of this appears in a meeting room. All of it appears at minus eighteen degrees.

My rule is simple: test in the real zone, for a full shift. Take the candidate handheld into the freezer and record battery life, first-scan success rate, and mis-tap rate while wearing gloves. Do not accept a laboratory datasheet as a substitute. Check printing too: does label stock turn brittle in the cold, where will the printer sit, and will labels fall off when condensation forms? A lost label breaks scanning, batch traceability, and expiry control in one stroke.

Check connectivity as well. Metal racking and thick walls are unkind to wireless signals. Ask whether the system supports offline task execution and how it resolves conflicts when data syncs back. A brief network drop should not stop the floor. In an ambient warehouse, asking someone to log back in is an annoyance. In a freezer, every extra minute standing still is a cost.

The Go-Live Night Checklist

On go-live night, my checklist fits on one page, and every line needs a signature. Zone rules configured per customer. Expiry thresholds configured per customer. Hardware tested for a full shift in the real zone. Offline work rehearsed once. Dwell-time alerts tested by triggering them on purpose. If one line is unsigned, we do not go live.

Here is the counterintuitive part: in cold storage, a longer feature list is a warning sign, not a selling point. A long list usually means every item is shallow. What a cold store actually needs is depth in three places: temperature control, expiry discipline, and freezer hardware. When a vendor says they can do everything, ask how many real freezer projects they have run, and ask to visit one. One walk around a live freezer tells you more than a hundred pages of proposal.

Take these three checklists into your next vendor meeting. Wherever the answer turns vague, that is where go-live will hurt. Cold storage has a much smaller margin for error than ambient warehousing. One extra question during selection saves more than one long night after go-live.

By Lin Xiao, WMS Implementation Consultant