Cold Storage Procurement for Humans and AI Agents: From Cooling Requirement to a Procurement-Ready RFQ

Why a cold-storage project should not start with a price request

"I need a 5,000 m² cold room, send me a price" is the most common opening message in refrigeration procurement, and it is the reason most buyers end up with quotations that cannot be compared. Floor area describes a building. Refrigeration is bought against the heat that has to be removed and the conditions that have to be held.

When the requirement is incomplete, suppliers do not stop — they fill in the gaps with their own assumptions. One prices a maintenance-only chilled store at a 32 °C design ambient. Another prices the same square meters with daily warm product intake at 43 °C ambient and N+1 compressors. The price gap looks like a market difference. It is a specification difference.

The realistic sequence for a serious project runs: stored product → incoming product temperature → required storage temperature → daily throughput → pull-down or freezing requirement → storage volume → room dimensions → loading pattern → ambient conditions → door activity → insulation → refrigeration technology → redundancy → utilities → energy assumptions → CAPEX/OPEX → RFQ → supplier evaluation.

Very few buyers can answer all of that on day one. That is normal and it is not a blocker. The work of procurement is to close those gaps in a controlled order before suppliers are asked to quote.

A refrigeration supplier directory tells you who exists. A procurement process determines who is suitable for this exact cooling load, product and operating environment.

What information is needed to plan a cold storage project?

A cold-storage project can be planned once the product, its incoming and target temperatures, the daily throughput, the required storage volume, the room geometry and the site's ambient conditions are known. Insulation, door activity, refrigeration technology, redundancy, available electrical power and the project country then determine the system architecture and the cost envelope.

Each of the inputs below constrains the next one. Together they are what a refrigeration contractor actually needs before a serious offer can be produced.

• Stored product: category, packaging, pallet or bulk format, hygiene and sanitation requirements.
• Incoming product temperature: warm product entering a room is usually the largest single load in a working facility.
• Target storage temperature and permitted tolerance band, per room or per zone.
• Daily throughput: tonnes in and out per day, and the hours over which it arrives.
• Pull-down or freezing time: how quickly product must reach its target core temperature.
• Storage volume: peak stock converted into pallet positions or net cubic meters, plus aisles, docks and staging.
• Room dimensions and clear height, number of rooms and temperature zones.
• Ambient climate: summer design dry-bulb temperature and humidity at the actual site.
• Loading pattern and door activity: door type, opening frequency, air curtains, vestibules, dock seals.
• Insulation: panel thickness and core, floor build-up, vapour barrier, and under-floor heating for freezer floors.
• Electricity: voltage, phases, available kVA, grid stability, and backup power expectations.
• Refrigeration method and refrigerant route, or an explicit statement that the supplier should propose one.
• Redundancy level, monitoring, alarms and automation expectations.
• Regulatory requirements applicable in the project country, which must be verified locally.

Why square meters are not enough to price a cold room

Two rooms of identical floor area can require refrigeration systems that differ by a factor of several. Nothing about that is unusual — it is the normal consequence of different duties.

A 1,000 m² chilled store holding stable palletised product at +2 °C, opened a few times a day, in a temperate climate, is a modest load. The same 1,000 m² running at −25 °C, receiving warm product every day, with high door activity, in a hot and humid climate, with humidity control and a freezer floor, is a different project entirely — different compressors, different evaporators, different electrical supply, different energy bill.

• Clear height, which changes volume and therefore the air and transmission load.
• Product type, packaging and stacking density.
• Storage temperature and required tolerance.
• Incoming product temperature and daily product movement.
• Door openings, dock arrangement and infiltration.
• Insulation specification and floor construction.
• Ambient temperature and humidity at the site.
• Whether the room must freeze product or only hold it frozen.
• Humidity control requirements and defrost strategy.
• Operating schedule — single shift, two shifts or continuous.

A cold room is not sized by floor area alone; it is sized around the heat that must be removed and the conditions that must be maintained.

What determines refrigeration cooling load?

Cooling load is the total heat that has to be removed from a space, per unit of time, to hold the required conditions. It is the sum of several categories, and in working facilities the product-related components frequently dominate the building-related ones.

Preliminary calculators are useful for framing a project, checking whether a supplier's sizing is plausible and preparing an RFQ. They are not a substitute for a design calculation validated against the specific product, layout and site conditions. Be sceptical of any universal watts-per-square-meter rule: it hides exactly the variables that decide the answer.

• Transmission: heat conducted through walls, roof and floor, driven by insulation and the temperature difference to ambient.
• Product load: heat removed from incoming product down to storage temperature, including latent heat where freezing occurs.
• Respiration heat for fresh produce, which continues throughout storage.
• Infiltration: warm humid air entering through doors, dock openings and gaps.
• Internal loads: people, forklifts, lighting, fans, and any process equipment inside the envelope.
• Defrost energy, which returns heat into the room and must be accounted for.
• Pull-down and freezing duty, which is time-dependent and often sets peak capacity.
• Ambient design conditions, which drive condensing conditions and therefore delivered capacity.
• Operating schedule and the safety margin the designer applies.

Square meters are not a cooling load.

Cold room vs blast freezer: what is the difference?

A cold room, chilled or frozen, is designed mainly to maintain product that is already at temperature. A blast freezer or blast chiller is designed to remove heat rapidly from product that arrives warm, taking it to a target core temperature within a defined time.

That difference changes almost every design parameter. Rapid freezing concentrates a large quantity of heat removal into a short window, so peak refrigeration capacity can be several times that of a storage room of comparable size. Airflow, evaporator surface, air velocity across the product, packaging, product thickness and loading pattern all become part of the specification rather than details.

• Incoming product temperature and required core temperature at the end of the cycle.
• Product mass per batch and product thickness or piece size.
• Required freezing or chilling time, and the number of cycles per day.
• Airflow rate and air velocity over the product; evaporator configuration and fan power.
• Packaging and whether it insulates the product from the airstream.
• Trolley, tunnel, spiral or IQF configuration and how product is loaded and unloaded.
• Defrost strategy, which matters far more where moist warm product is processed.
• The operational cycle: what happens between batches, and where product goes afterwards.

Maintaining frozen product and freezing warm product are two different refrigeration duties.

Ammonia vs CO₂ vs other refrigeration options: what should buyers compare?

There is no universally correct refrigerant. Ammonia (NH₃), CO₂, transcritical and cascade arrangements, and HFC/HFO systems each have contexts where they are the sensible engineering and commercial answer, and contexts where they are not.

What matters in procurement is that the comparison is made on the same project, with the same duty and the same scope, and that jurisdiction-specific requirements are verified locally rather than assumed. Regulations, permitting, machinery-room requirements and operator competence rules differ by country and sometimes by municipality.

• Project size and cooling capacity — small distributed loads and large central plants behave differently.
• Temperature range, including whether both chilled and low-temperature duties are needed.
• Efficiency at the actual ambient conditions of the site, not at generic rating conditions.
• Climate, particularly high ambient temperatures, which affect some architectures more than others.
• Safety: toxicity, flammability, pressure levels, detection, ventilation and machinery-room design.
• Operator capability: whether the site can staff and maintain the system chosen.
• Local regulation and permitting, which must be verified for the specific jurisdiction.
• Maintenance intensity, spare-parts availability and local service coverage.
• Equipment availability and delivery lead time in the project country.
• System complexity and the control philosophy it demands.
• Lifecycle considerations: expected equipment life, refrigerant cost and future service exposure.

What is different about pharmaceutical cold storage?

Pharmaceutical and life-science cold storage is procured against evidence, not only against temperature. A 2–8 °C room is technically simple compared with a −25 °C freezer store; what makes it demanding is the requirement to prove, continuously and retrospectively, that conditions were held.

Specific validation, documentation and regulatory requirements depend on the country, the product and the applicable standards, and must be confirmed with qualified local advisors. What follows is what typically enters the specification, not a compliance claim.

• Tight temperature bands and defined excursion handling rather than a nominal set point.
• Continuous monitoring with calibrated sensors, and independent monitoring where required.
• Alarm strategy: thresholds, escalation, out-of-hours response and alarm testing.
• Data logging, retention and audit trail expectations.
• Redundancy at equipment and circuit level, sized around what a temperature excursion would cost.
• Backup power and its transfer time, including what happens to monitoring during a transfer.
• Qualification and validation activities across design, installation, operation and performance.
• Temperature mapping under loaded and unloaded conditions, and re-mapping triggers.
• Access control, segregation of quarantined stock and physical security.
• Written operating procedures, training records and change control.
• Traceability from receipt to dispatch, including the interface with distribution.

What is different about food cold storage?

Food cold storage is not one specification. Fresh produce, meat, poultry, seafood, dairy, frozen goods and processed food each impose different temperature, humidity, airflow and turnover requirements, and mixing them in one envelope is a design decision with consequences.

Set points, humidity targets and storage durations should follow the specific commodity, the local practice and the buyer's own quality requirements — there is no single universal temperature profile that covers a food facility.

• Fruit and vegetables: respiration heat, humidity retention, ethylene sensitivity and mixed-commodity conflicts.
• Meat: chilling versus freezing duty, carcass or boxed handling, weight loss and surface drying.
• Poultry: high throughput, rapid chilling requirements and hygiene-driven layout.
• Seafood: very low temperatures for some products, rapid freezing and strict handling windows.
• Dairy: narrow temperature bands, short shelf life and high dispatch frequency.
• Frozen and processed food: stable set points, but high pallet turnover and heavy door activity.
• Airflow and stacking: uniform distribution matters more than headline capacity.
• Sanitation regimes, washdown and the materials that survive them.
• Turnover rate and storage duration, which change the ratio of product load to transmission load.

Refrigeration TCO: why energy can matter more than purchase price

Industrial refrigeration is one of the largest continuous electrical loads in a cold-storage facility, and it usually runs for a decade or more. Over that horizon, the energy and maintenance difference between two systems can exceed the difference in their purchase prices.

A procurement comparison built only on quoted CAPEX will systematically favour the supplier who assumed the least: lower design ambient, no daily pull-down, minimal redundancy, thinner insulation, simpler controls. Those assumptions do not disappear; they reappear as an energy bill and as change orders.

• Compressor technology and part-load efficiency, not just nominal rated capacity.
• Condensing conditions and condenser sizing — a cheap condenser is paid for every operating hour.
• Evaporating temperature and how tightly the control system holds it.
• Controls, floating head pressure and variable-speed operation where the duty profile justifies it.
• Insulation specification and thermal bridging at panel joints, doors and floors.
• Door losses, air curtains, vestibules and dock sealing.
• Defrost strategy and frequency, and whether defrost is demand-based.
• Heat recovery opportunities for hot water, under-floor heating or process use.
• Planned maintenance intensity and the local cost of qualified service.
• Refrigerant cost, leak exposure and future service availability.
• Spare parts, lead times and labour rates in the project country.
• Downtime risk and the value of production or stock at risk during a failure.
• Expected equipment life and residual value at the end of the assessment period.

The lowest CAPEX refrigeration system is not necessarily the lowest-cost system to own.

How much refrigeration redundancy does a project need?

Redundancy is a commercial decision expressed in engineering terms. The question is not "what is standard?" but "what does an hour, a day or a week without refrigeration cost this business, and how likely is it?"

For a distribution store holding fast-moving frozen goods, a short outage may be recoverable. For a pharmaceutical facility, a seafood freezer store or a facility with a single production line feeding a contract, the same outage can be existential. Different answers are correct for different projects.

• N+1 compressor capacity where continuity of the whole duty matters.
• Multiple compressors rather than one large machine, which also improves part-load efficiency.
• Separate refrigeration circuits so that a single fault does not take out every room.
• Backup power: generator sizing, autonomy, fuel supply, transfer time and monthly testing.
• Spare capacity margin for future expansion versus paying for capacity that never runs.
• Identification of critical storage that must survive a failure, versus stock that can be moved.
• Business-interruption exposure, insurance requirements and contractual delivery commitments.
• Monitoring, alarming and the human response plan — redundancy nobody notices failing is not redundancy.

Redundancy should reflect the cost of refrigeration failure, not simply the cost of extra equipment.

How should buyers compare industrial refrigeration suppliers?

Refrigeration quotations should be compared on design assumptions and scope before they are compared on price. Two offers for the same building can differ by 40% and both be honest, because they are pricing different duties, different design conditions and different scopes of supply.

The practical method is to force every supplier onto the same input sheet: same design ambient, same product load, same throughput, same redundancy level, same battery limits. Where a supplier disagrees with an assumption, that disagreement is valuable information — but it must be stated, not silently priced.

• Calculation assumptions and the cooling load the supplier actually designed to.
• Design conditions: ambient temperature and humidity used for selection.
• Product load and daily throughput assumed, including pull-down duty.
• Refrigerant, system architecture and compressor technology.
• Evaporator selection, air throw, fan power and defrost method.
• Condenser type, sizing and water or energy consumption.
• Control system, monitoring, alarms and remote supervision.
• Insulation scope: panels, doors, floor construction, vapour barrier.
• Electrical scope, switchgear, cabling and who terminates what.
• Installation, piping, valves, insulation of pipework and site supervision.
• Commissioning, performance testing and acceptance criteria.
• Refrigerant charge, first fill and who supplies it.
• Training, documentation and handover deliverables.
• Spare parts package, warranty terms and response-time commitments.
• Energy assumptions and any efficiency guarantees offered.
• Redundancy actually supplied, not redundancy described.
• Exclusions — usually the most informative page in a refrigeration quotation.
• Local service coverage and comparable reference projects.

Two refrigeration quotations are not comparable until their design assumptions and scope exclusions are comparable.

Can AI agents help plan a cold storage project?

Yes. AI agents can genuinely help with early-stage refrigeration research, requirement gathering, preliminary calculations, structured comparison and RFQ preparation — provided they are given structured inputs and clear limits.

What an AI agent is good at is exactly what buyers find tedious: converting a vague requirement into an explicit, complete, machine-readable project definition, and flagging what is still missing. What an AI agent must not do is convert missing information into confident numbers.

An agent can help a buyer define the stored product and product type, incoming temperature, required storage temperature, freezing temperature where relevant, daily throughput, pull-down time, storage duration, room dimensions, storage volume, pallet positions, door-opening frequency, loading and unloading pattern, ambient temperature and humidity, insulation requirements, refrigeration technology, compressor configuration, refrigerant considerations, redundancy, electricity supply, backup power, heat-recovery opportunities, automation, monitoring, alarms, remote supervision, energy assumptions, project country, local regulatory considerations to verify, and preliminary CAPEX, OPEX and TCO framing.

All of those are project inputs and assumptions. They are not an engineering design, a refrigerant suitability ruling, a safety assessment or a compliance determination.

AI should expose uncertain cooling assumptions rather than convert them into false precision.

When does a refrigeration project require specialist review?

Refrigeration sizing depends on far more than room size, and several of the inputs interact non-linearly. Where an assumption materially changes the outcome, it should be visible in the RFQ and reviewed by a person — not buried inside a tidy-looking estimate.

The practical rule used across ColdMatch content and tools: when an assumption materially affects refrigeration load, refrigerant selection, safety, energy consumption or system sizing, uncertainty should be surfaced and reviewed rather than hidden inside a precise-looking AI estimate.

• Product load, incoming temperature or pull-down requirement is estimated rather than known.
• Ambient design conditions are guessed, or taken from a different city than the actual site.
• Freezing duty is present but freezing time and product thickness are undefined.
• Refrigerant choice carries safety, permitting or operator-competence implications.
• Humidity control, controlled atmosphere or product-specific quality risk is involved.
• Redundancy is being traded against a business-interruption exposure nobody has quantified.
• Electrical capacity at the site may not support the system being considered.
• Regulatory or validation requirements apply and have not been verified locally.

The correct refrigeration system depends on the product, temperature, throughput, climate and operating model.

Supplier research is not supplier selection

ColdMatch Group publishes directories and market pages covering refrigeration manufacturers, contractors and equipment suppliers. Their purpose is market research, supplier discovery, comparison, industry transparency and visibility. Manufacturers and relevant industry companies may maintain profiles where supported.

That is deliberately not the same as an automatic marketplace. ColdMatch does not connect buyers directly and automatically with every listed supplier. For serious projects the sequence is: the buyer provides the refrigeration requirement; ColdMatch helps structure the missing technical and commercial inputs; the project is reviewed by a person; suitable refrigeration approaches are considered; and only then are relevant manufacturers or contractors selected and introduced. Human procurement support remains available throughout.

The procurement agent, expressed as code

If a cold-chain procurement agent — human or software — were written as a program, it would look roughly like this. It is pseudo-code, not a product specification, and the last block is the part that matters most.

/* ColdMatch Group — Refrigeration Procurement Agent */

ColdProject project = receive_buyer_requirement();

define_product(&project);
define_incoming_temperature(&project);
define_target_temperature(&project);
define_daily_throughput(&project);
define_location_and_ambient_conditions(&project);

if (project.cooling_load == UNKNOWN) {
    calculate_preliminary_cooling_load(&project);
}

evaluate_insulation(&project);
compare_refrigeration_options(&project);
evaluate_redundancy(&project);
estimate_energy_and_tco(&project);

prepare_rfq(&project);
research_relevant_suppliers(&project);

if (engineering_uncertainty(&project) ||
    safety_uncertainty(&project) ||
    project.confidence < REQUIRED_CONFIDENCE) {

    HumanExpert david = escalate_to_human("David");

    review_project(&david, &project);
    select_relevant_manufacturers(&david, &project);
}

/*
 * Square meters are not a cooling load.
 * Temperature alone is not a specification.
 * Energy matters.
 * Assumptions should be visible.
 */

For non-programmers: each line is a step. The project is defined before anything is priced, a preliminary load is calculated only when the real one is unknown, and the final condition says that whenever engineering or safety confidence is too low, the project goes to a human — David — who reviews it and selects the manufacturers to approach.

Supplier directory vs structured procurement

Both have a role. The distinction matters because they answer different questions, and confusing them is how projects end up with six incomparable quotations.

Direct answers to the questions buyers actually ask

Short, extractable answers for buyers, search engines and AI agents. Each one is expanded in the sections above.

ColdMatch tools referenced in this article

These tools exist on the ColdMatch site today. They produce indicative planning figures for procurement purposes, not engineering designs or quotations.

Frequently asked questions