By Clarus Content Team · Published 20 November 2026
A cold store warehouse management system is a WMS that keeps chilled and frozen stock in the correct zone, rotates it by date and records every batch and movement so the site can show what it did. It controls the decisions the team makes all day: where a pallet goes, which pallet gets picked, whether stock is available and who handled it. It does not run the refrigeration plant or read the temperature probes, and a buyer should be clear about that line before signing anything.
Buyers search for this as a cold storage WMS or cold storage warehouse management software, and the question behind each search is the same. A chilled or frozen site has a food safety regime to meet, less room for date errors and staff who work in the cold for part of every shift. The rules sit in law and in standards. The Food Safety (Temperature Control) Regulations 1995 set the duties for food that must be kept at controlled temperatures. The Food Standards Agency’s HACCP guidance treats temperature as a critical control point. The Cold Chain Federation is the UK trade body for temperature-controlled storage and distribution.
A WMS cannot make a site compliant on its own. What it can do is make the compliant way of working the easy way of working, and make the records exist when an auditor asks for them.
What a cold store WMS controls, and what it does not
A cold store WMS needs zone rules for every product, date rotation that respects each customer’s terms, holds with reason codes, batch capture at receipt and a timestamped audit trail. Those features change outcomes on the floor. The table separates what the software owns from what belongs to the building or to your procedures.
| Job | What the WMS does | What stays outside the WMS |
|---|---|---|
| Keeping product in the right zone | Blocks putaway, replenishment and picks that break the zone rule | Setting and holding zone temperatures |
| Recording a temperature at goods-in | Stores a typed entry, timestamped against the receipt line | Taking the reading with a calibrated probe or thermometer |
| Continuous temperature monitoring | Not a WMS function | Monitoring system, probes and alarms |
| Date rotation and holds | Allocates by rule and keeps held stock out of picks | Deciding whether held stock is released or destroyed |
| Recall scoping | Shows where batches went, if those movements were captured | Withdrawal decisions and customer contact |
| Refrigeration plant | Not a WMS function | Facilities and plant maintenance |
The gap between the middle and right columns is where cold stores get caught out. If a vendor says the system “handles temperature”, ask how the reading gets into the system, who takes it and who checks it. A typed entry is a manual process with a timestamp. It is not a sensor feed.
Temperature zones: binding products to the right location
The core rule of a cold store WMS is that a product is only allowed in a location in its own zone. Temperature-controlled storage in Clarus WMS works this way. Each product carries a required zone, chilled, frozen or ambient. Each location belongs to a zone group. Scanners check the pairing at putaway, replenishment and pick, and block any move that breaks the policy. Zone groups can be reassigned in the system, and every movement is timestamped with the user, the location and the zone.
Segregation helps too. Products can be grouped so that putaway only suggests locations that are compatible with them. Ask any vendor what the system does when the correct zone is full. The answer you want is a blocked move with a clear message, not a chilled pallet quietly placed in the nearest free space.
Expiry dates, date rotation and bulk stacks
A WMS can rotate stock in two different ways, and the terms get mixed up in sales conversations. FIFO in Clarus WMS is based on the creation date of the stock record, to the millisecond. First-expiry-first-out is a sell-by rule set separately as a pick rule. On most chilled and frozen lines, the date on the pallet should decide the pick, not the day the pallet arrived. That is the job of FEFO, and stock rotation in the system should be checked against it.
Bulk stacking is where date rules break down. The oldest pallet can sit at the back of a stack, and reaching it means moving several others first. Mathew Buttar, Head of Solutions at Clarus WMS, puts the point plainly: “If you were using sell by dates, you shouldn’t bulk stack them. They should be easily accessible pallet by pallet.”
Clarus has a switch function for bulk locations. The operator scans the pallet at the front, and the system checks that it is the same product, the same date and the same batch before it allows the swap. The limit is that the system cannot switch to a pallet already allocated to another pick. Test that in your own racking before you rely on it.
Use by and best before are not the same thing, and the rotation has to follow the right one. The Food Standards Agency explains the difference. Batch, sell-by and best-before control can be switched on as account-level flags and overridden per product. When they are on, the handheld shows the date and batch screens, and it warns the operator if the wrong batch is scanned. Out of the box, Clarus does not flash up a warning when stock is close to its date, so your own check process has to cover that.
Holds come before picks. Clarus can put received and put-away stock on hold automatically through an account automation, routing it to a quarantine location where it cannot be allocated to any task. Hold reason codes can be enforced, and the system records what the hold was for, who placed it and when, with the same detail for release. Note the default: unless you configure otherwise, received goods are immediately available. Decide that before go-live, not after the first failed check.
Minimum life on receipt is the date rule buyers most often forget. Different end customers accept different remaining shelf life. One may take stock with five days left, another only with three. Ask any vendor how the system records a minimum life for each customer, and how it stops a pick for the stricter customer from coming off stock that does not meet their rule. Get the answer in writing, because systems differ on this.
Batch traceability and the recall sequence
A recall in a cold store is a timing problem. The Food Standards Agency’s guidance on withdrawals and recalls sets out what the business must do. The WMS decides how fast the team can find the stock. Traceability starts at goods-in, where the batch is captured from the pallet label. GS1 application identifiers tell the scanner what each number on the label means, such as batch, best before and use by.
Lot and batch are used differently by different teams, so agree the terms before you configure anything. Our guide to lot and batch tracking in the warehouse sets out the difference. For batch control in the system itself, see batch and lot control.
The recall sequence in Clarus WMS, as Mathew Buttar described it, runs like this:
- Identify what went to which order and on which vehicle, if that dispatch data was captured.
- Put the remaining stock from the affected batch on hold in the stock list, so nothing else can be allocated from it.
- Find stock already on orders that have not left the building, stop those picks and reallocate the stock to a batch that is good.
- Once the reallocation is done, put any affected stock that remains on hold.
The speed of that sequence depends on what was captured. Not every site records every dispatch step, and a recall is only as quick as the trail behind it. The system also cannot control what happens once a load leaves the back door, so the trail ends at the dispatch record.
BRCGS Storage and Distribution: what the audit looks for in the WMS
Many cold stores are audited against the BRCGS Storage and Distribution standard. An auditor will not accept a WMS screenshot as a procedure. They will ask to see the records the procedure produces: who received a load, what was checked, where the stock went and whether a hold was applied. A WMS makes those records consistent and timestamped. It does not write your procedures or certify your site.
Clarus has no built-in HACCP or GDP module. Checks are added as typed fields in the handheld flow, such as vehicle condition, pest ingress or damage, and each entry is stored against the transaction line with the time and the user. Campeys, a food business, earned an AA BRCGS grade working with Clarus WMS. Their story is about food-grade warehousing rather than chilled or frozen stock specifically, so read it for what changed in their records. For the wider chain from supplier to shopper, see our guide to cold chain management.
Dock dwell and goods-in checks
Pallets sitting on an ambient dock are a cold store problem. Product that has not been put away sits outside the zone rules, and it is easy for it to wait longer than it should. The fix starts with process: a booking-in diary, scheduled arrivals and a goods-in routine that puts pallets away in the same shift. Dock scheduling supports the booking side, and our goods-in guide covers the receiving routine. Yard management is not part of the system, so trailer positions in the yard stay outside it.
The checks belong at the dock. One BRC-accredited food 3PL configures its scanner flow with a vehicle condition check on arrival, then pest and damage checks on unload, and a frozen or chilled check that the product is still in condition for its zone. The operative answers each check and the system timestamps it. For temperature, the reading is typed by hand into a generic field. It records the operative’s reading. It does not measure the product.
Freezer labour: handhelds, gloves and short exposure
Labour in a freezer is a safety question before it is a system question. The HSE guidance on cold stress covers the controls an employer needs for work in low temperatures, and it is the place to start. A WMS helps by reducing time on the handheld. A flow that shows only the screens a product needs means less to tap in the cold, because the batch screen does not appear for products that do not need one.
Scanner validation catches errors at the shelf. If an operative scans the wrong location, the handheld shows the correct location with a red arrow. Clarus handheld workflows are configurable on Android devices, so the flow can match the job rather than the other way round.
Test the whole flow with gloves on, in the real freezer, with the real labels, before you sign off the design. A label that cannot be scanned at the freezer door stops the process, so that is the first thing to check. Shift planning, break times and rotas sit outside the WMS, and so does the risk assessment for cold work.
What to ask a WMS vendor before you buy
Clarus WMS is a purpose-built 3PL system, so it keeps each client’s stock, rules and records apart within one warehouse. If your operation is food or chilled, read our guide to the best WMS for food and beverage and the food and beverage solution. Clarus WMS has a platform fee from £1,000 a month, priced on sites and users rather than on order volume, plus users and one-off implementation, as set out on our pricing page.
Whichever system you look at, ask for a demonstration with your own products and zones, and check these points:
- How does a product get its zone, and what happens when the correct zone is full?
- Does FIFO mean the stock record date, the expiry date, or both?
- How is a minimum life on receipt held for each customer, and how does a pick respect it?
- Can a received pallet go straight to quarantine, and is it blocked from picks until released?
- Which batch and date fields are captured at receipt, and what does the handheld do with the wrong batch?
- How long does a recall take in the demo, and which dispatch steps must be captured to make it fast?
- Which temperature checks are typed entries, and does any value come from a device? If it does, who installs and maintains that link?
- How are ancillary steps such as blast freezing recorded when stock moves in and out of them?
- Where does the system stop, and what runs outside it?
The last question matters most. A vendor who can name the limits clearly is usually a vendor you can plan around.
Speak to a warehouse expert
If you’re evaluating your options and want to see how a purpose-built WMS works in practice, Clarus is worth a conversation. We work with 3PLs and distributors across the UK to implement warehouse management software that fits the way you operate, not the other way around.
Get in touch with our team to talk through your requirements.