LTL shipments typically run from one pallet up to about six to twelve pallets, or roughly 150 to 15,000 pounds. Below that, parcel carriers are usually cheaper; above it, a full truckload is usually cheaper.
LTL freight moves through a hub-and-spoke network. A shipment is picked up locally, taken to a terminal, sorted, line-hauled to a terminal near the destination, sorted again, and delivered. That handling is why LTL transit takes longer and why damage and reweigh/reclass disputes are more common than in truckload.
LTL pricing depends on freight class (a standardized measure of density, stowability, handling, and liability), weight, distance, and accessorials such as liftgate, residential delivery, and inside delivery. Misdeclaring class or dimensions leads to a corrected invoice after the fact.
Example
A manufacturer ships four pallets of machine parts, 2,800 pounds total, from Grand Rapids to Charlotte. Rather than pay for a full 53-foot trailer, it books an LTL carrier. The shipment shares the trailer with freight from several other shippers, moves through two terminals, and delivers in three business days at a fraction of a truckload rate.
Why it matters
Choosing LTL versus truckload versus partial truckload is a cost-and-transit tradeoff that changes with pallet count, weight, and how time-sensitive the delivery is. The wrong choice either overpays for space or adds days of transit.
How teams use this term
In a carrier operation, Less-Than-Truckload (LTL) 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 Less-Than-Truckload (LTL), 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.