A reefer trailer holds a setpoint temperature, either running continuously or cycling on and off, and logs the temperature throughout the trip. The load is only as good as that temperature record — a break in the cold chain can condemn the whole shipment.
Reefer freight carries more operational risk than dry van: the unit can fail, produce generates its own heat and needs airflow, wash-outs are required between incompatible commodities, and detention at packing houses and grocery DCs runs long. Rates are correspondingly higher.
Reefer trailers also haul dry freight when refrigerated volume is thin, which is one of the ways capacity shifts between segments.
Example
A carrier loads fresh strawberries at a cooler in California at a setpoint of 34°F, with the reefer on continuous run and a temperature recorder in the load. At the grocery DC four days later, the receiver checks the download before signing — a clean record means the load is accepted; a excursion above spec can mean rejection.
Why it matters
On a reefer load the temperature record, not just the POD, decides whether the carrier gets paid. Dispatchers price reefer lanes with the extra detention, wash-out, and claim risk built in.
How teams use this term
In a carrier operation, Reefer belongs in the conversation about dispatch, planning, execution, and driver coordination. The useful question is not only what the term means, but which record or decision it changes. A dispatcher may see it while planning a load, a driver may create evidence for it in the field, and accounting may need the same context before a customer invoice or carrier settlement can be finalized. Keeping the term attached to the related workflow prevents a definition from becoming disconnected vocabulary.
When reviewing Reefer, ask who owns the next action, what evidence supports the record, and what date or threshold makes the situation change. The answer can vary by equipment, lane, authority, customer routing guide, or contract. A small carrier should document the assumption it used rather than treating a general explanation as a universal rule. The related terms on this page are intended to help a team move from the definition to the operational decision.
A practical review starts with the example above, then compares it with the carrier's own settlement, dispatch, document, or compliance records. If the term affects a regulated filing, payment obligation, or customer requirement, verify the current primary source before acting. Trailflow can provide workflow context, but the carrier remains responsible for the policies, records, and professional advice that apply to its operation.