How Many QFMs Do I Really Need?

How Many QFMs Do I Really Need?

Enter the loads you receive each day of the week, your product mix, room air temperature, and operating hours. The calculator simulates your week and sizes the smallest QFM system that keeps loads from holding for an open QFM — run continuously, as QuickFreeze recommends, and as batch zones for comparison — next to the spreadsheet rule of thumb.

Sizing a new system. Already have QFMs installed? Check what they can do with the continuous or batch throughput calculators. The same scenario link works on all three.

Size Your System

Results update as you type (sizing runs a few seconds of simulation). Use Copy link to share a scenario with your team or with QuickFreeze.

How the Calculation Works

Three numbers, and the gap between them is why “really” is in the question.

1

Rule of thumb

Pallets per day × hours to temperature ÷ 24. It is what a sizing spreadsheet gives you, and it quietly assumes level receiving around the clock, every position always busy, and every pallet taking the whole load’s time. It is a floor, not a plan.

2

What you really need: continuous

The week is simulated pallet by pallet at your day-of-week receiving shape and operating hours, then the position count is reduced until one load in ten would hold for an open QFM longer than your wait target. Each pallet is placed when a position opens and pulled the moment it is to temperature.

3

The same week as batch zones

Zones loaded as a unit and pulled only when the slowest pallet is done. The extra positions this needs are the price of batch operation: idle positions while a zone loads and unloads, and every position in the zone waiting on its slowest pallet.

The “What moves the number” table re-sizes the system with and without WMS API Integration, with leveled receiving, at higher volume, and in colder rooms, so you can see which lever is worth pulling before buying positions. Retention time matters as much as any of them: a static timer on every unit must be long enough for the slowest product, so every faster pallet holds a position it no longer needs. The WMS API Integration checkbox lets each unit run its own product’s cycle time (AutoSense has the same effect) and gives those positions back.

Throughput FAQ

Batch or continuous: what is the difference?

In batch operation a zone of positions is loaded together and nothing is pulled until the last pallet in the zone is to temperature, so every position in the zone runs on the slowest pallet’s clock, and the zone sits partly empty while it is being loaded and unloaded. In continuous operation each pallet is placed when a position opens and pulled the moment it is done. The same positions turn more often, the average pallet finishes sooner than the slowest one, and a load can start freezing before the whole truck is unloaded. QFM AutoSense makes continuous operation practical by calling each pallet individually. Use the two calculators with the same scenario link to see the difference for your mix.

What is varying versus static retention time?

Retention time is how long a unit holds its pallet before the cycle ends. With a static setting every unit gets the same cycle time, and to be safe it is set for the slowest product, so a 24-hour product sits in a 40-hour cycle and its position is lost for the difference. With varying retention each unit runs the cycle time its own product needs. Two ways to get there: WMS API integration, where your warehouse system tells the unit what is on the pallet and sets the cycle time when the pallet is placed, and AutoSense, which ends the cycle when the pallet itself reaches temperature. The WMS API Integration checkbox switches between the two and always shows both results, so the positions a static timer costs are visible before you buy them. For what the integration involves on your side and the documented gains, see WMS & API Integration in the Engineering Guide; developers can go straight to the QFM API reference.

Why does the simulated size differ from the rule of thumb?

The rule of thumb (pallets per day × hours ÷ 24) counts position-hours as if every hour of the week were equally usable. It is not: loads bunch on certain days, pallets can only be placed and pulled during shifts, and cycle times vary. All of that needs more positions than the average suggests. Continuous operation claws some back, because the average pallet finishes sooner than the slowest one and positions turn the moment a pallet is done. The sizing calculator counts both effects; the rule of thumb counts neither.

Where do the product hours come from?

Use validated time-to-temperature for each product at a stated room air temperature: hand-temp tests, QFM AutoSense cycle records, or your own qualification runs. Enter the time for the whole load to reach 0 °F, not the average pallet, because a zone is only pulled when its last pallet is done. If you only have a target cycle time, enter that and treat the result as an upper bound.

How does room air temperature change the result?

Freezing time grows as the air at the QFM intake warms, and not in a straight line. The calculator’s physics curve blends two effects: the freezing plateau, which follows Plank’s equation (time scales with 1 ÷ (freezing point − air temperature)), and the pull-down of the core from the freezing point to 0 °F, which depends on how far the air sits below 0 °F and climbs steeply as the room warms. The blend weights the pull-down at 35% of the cycle, typical for boxed poultry. The result is asymmetric: a room 5 °F colder than −10 °F shortens cycles about 15%, a room 5 °F warmer lengthens them about 25%, and the curve goes vertical approaching the no-freeze limit. Enter the product freezing point (about 27 °F for poultry and meat, 30 °F for high-water products). If you have a measured sensitivity of your own, switch to the linear model and enter it as % per °F. Above the no-freeze limit the product core cannot reach 0 °F at all, so the calculator reports zero throughput instead of a long cycle.

Why does spreading loads across the week add capacity?

A QFM system is a fixed number of position-hours per week. Every empty zone on a Monday is throughput that cannot be recovered on Friday. When receipts bunch, loads hold for an open QFM while zones sit idle elsewhere in the week. The leveled number shows what the same equipment could do with a flatter receiving schedule.

What does “acceptable wait for an open QFM” mean?

It is how long a load may hold, from arrival until it is placed in a QFM, before you would call it a problem. Capacity is reported as the largest weekly volume at which 90% of loads are placed within that wait. Tighten it for a food-safety-driven answer, loosen it if staging space and product temperature allow loads to wait longer.

What is not in this model?

Forklift and crew limits, re-cool positions, refrigeration capacity (room temperature is an input, not a result), partial loads that share a zone, and seal quality. QuickFreeze can run a facility-specific version against your QFMonitoring data; see the contact options below.

Validate Your Numbers With QuickFreeze

We can calibrate this model to your facility from QFMonitoring cycle history and your receiving log.