Load's in, unit's dialed, truck's rolling. Last piece: choosing the right setpoint, understanding the temperature wobbles that are perfectly normal, and being able to prove you held temperature if anyone asks.

Setpoints for frozen food

As product cools past freezing (32°F), more of its free water turns to ice — and freeze points vary by product. For frozen foods the USDA recommends 0°F or lower (USDA HB 669).

Even at 0°F, long holds can still bring fat oxidation and enzymatic changes that are hard to spot. Below 0°F there's an additional, if unquantified, shelf-life gain.

Setpoints for perishable (fresh) food

Fresh commodities are individual — each has a recommended storage temperature, and other factors like handling damage affect quality on top of temperature. Don't guess; lean on the references: the USDA's recommended transit temperatures by product (HB 669, Appendix III, Table III-1), and for mixed loads the "Load Compatibility Groups" (Appendix II) so you don't pair products that shouldn't travel together.

Defrost cycles are normal — don't panic at the graph

The unit periodically runs a defrost cycle to clear ice off the evaporator, on a timer or when it senses icing. During defrost it isn't cooling or circulating air, so the air temperature briefly fluctuates. The key: those are short-duration air swings. Thanks to thermal mass, the actual product temperature doesn't meaningfully change. On a 24-hour graph you'll see clean spikes at each defrost over a nearly flat product line — that's healthy.

What FSMA says about defrost and door openings

FSMA has shippers specify an operating temperature in writing, but the FDA was clear that briefly exceeding it doesn't automatically make food unsafe. Operating temperatures are generally set to allow for normal activity — defrosting and opening/closing doors — and are often set to minimize product deterioration, which is stricter than the safety threshold. So temperature affects quality more than safety, and defrost plus reasonable door openings are acceptable.

Proving temperature: data recording

Units with Advance or APX controllers include an integrated data recorder that captures a full trip history.

It logs far more than temperature: setpoint and changes, alarms, refrigeration and engine operation, fuel level and tampering, door openings, battery voltage, engine hours, modes, and remote sensors. Download it (PCMCIA on Advance, authorized USB on APX), view on a PC, export to Excel or PDF — or view day-by-day graphs right on the controller.

What FSMA requires for verification

The relief: FSMA does not require continuous monitoring or routine proof for every load. A carrier must demonstrate it held temperature only when requested by the shipper or receiver — for example, if the receiver suspects a material temperature failure on arrival. The FDA explicitly isn't looking for warehouses of strip charts. Demonstration can be by any appropriate means agreeable to both parties: written logs, temp recorders, controller downloads or displays, strip prints, or telematics.

Bringing it all together

Across the series the same principles keep returning: a reefer maintains temperature, so load cold and saturated; airflow around all six sides is make-or-break; inspect the box, load cold and fast, and kill the unit while doors are open; set mode and setpoint to spec, trust normal defrost, and keep data so you can prove it on request. Do those consistently and you've covered the fundamentals from dock to delivery.

General reference based on AVRO field experience, Carrier Transicold service guidance, FSMA (21 CFR Parts 1 & 11), and USDA Handbook 669. This is not legal advice and is not a comprehensive FSMA summary. Specs and procedures change — confirm current requirements with your authorized dealer and shipper specifications before servicing or shipping. © 2026 AVRO Parts. All rights reserved.

• Operation
• FSMA
• Maintenance
• Tech Tip