Every mid-market shipper has a weekly stack of LTL invoices that should not exist. Shipments that moved as LTL because a dispatcher had 45 minutes to plan and defaulted to the carrier they know. Pallets that shipped separately on Monday and Thursday when they could have consolidated into one Tuesday FTL load at 60% of the combined LTL cost. The LTL versus FTL decision involves freight class, density, lane economics, time sensitivity, and minimum charge thresholds — too many variables for a dispatcher to evaluate per shipment under morning planning pressure. This playbook walks through the decision logic that should be running automatically.
The NMFC Freight Class Problem
Before you can model LTL cost accurately, you need accurate freight classification. The National Motor Freight Classification (NMFC) system uses 18 freight classes — 50, 55, 60, 65, 70, 77.5, 85, 92.5, 100, 110, 125, 150, 175, 200, 250, 300, 400, 500 — to determine linehaul pricing. The class is determined by four characteristics: density (weight per cubic foot), stowability, handling difficulty, and liability. Class 50 is dense, easy-to-handle commodity freight; Class 500 is low-density, high-liability, difficult-handling freight like ping pong balls or fresh flowers.
The problem mid-market shippers face is that many commodities have class determined by density calculation, not by item category alone. A pallet of machine parts might be Class 70 based on its actual density — but if the shipper is entering it as Class 85 because that is what the legacy NMFC lookup said when they set it up five years ago, they are overpaying on every LTL shipment. Carriers will reweigh and reclass shipments on dock, and if the actual density is lower than the declared class, the carrier will reclassify upward and bill the difference plus a reweigh fee. If the actual density is higher, the shipper was overpaying.
A working LTL consolidation model requires accurate density-based class calculation as a prerequisite. For shippers moving mixed commodity loads, this means per-line-item weight and cube data in the TMS — not pallet-level estimates.
The FTL vs. LTL Breakeven: Where the Math Lives
The core consolidation decision is a cost comparison between two options: ship multiple small shipments as LTL, or hold them and consolidate into a truckload. The breakeven calculation requires four inputs:
- Combined cubic feet and weight of the shipments being considered for consolidation
- LTL rate per hundredweight (CWT) for the lane, based on origin-destination pair and freight class
- FTL all-in rate for the lane (linehaul + fuel surcharge + any accessorials)
- Time sensitivity of the shipments — can they wait for a consolidation window?
The standard consolidation heuristic is: when combined LTL charges exceed 70–80% of the FTL rate for the same lane, consolidation makes economic sense if the time window allows. Below 50% of FTL cost, LTL moves individually. The 50–70% range is where lane economics, density, and timing must all be evaluated together.
For a concrete scenario: a food and beverage co-packer in Cincinnati is moving product to three Chicago-area DCs on Tuesday and Thursday each week. Tuesday: 4,200 lbs across three pallets to DC Alpha, 2,800 lbs across two pallets to DC Beta. Thursday: 3,600 lbs to DC Gamma. Separately, these ship as three LTL moves per week. Combined, Tuesday's freight fills 68% of a 53-foot trailer cube. If the FTL rate for the Cincinnati-Chicago lane is $1,850 and the combined LTL invoices for Tuesday are $1,420, the case for Tuesday consolidation is not yet clear at $430 savings — but when you include the Thursday move, the combined weekly LTL cost is $2,100 against a single Wednesday FTL of $1,900, and the math favors consolidation by $200 before accessorial savings.
Hub Bypass vs. Point-to-Point: The Network Geometry Decision
Standard LTL moves through a hub-and-spoke network. Freight from Cincinnati to Chicago runs from the origin terminal, through a linehaul run to a Chicago hub, then on a P&D (pickup and delivery) run to the final destination. Each hand-off adds transit time, handling damage risk, and — because carriers charge for handling — cost. The linehaul leg is typically priced at a CWT rate per 100 miles; the P&D legs carry a separate handling charge.
For freight that meets FTL density thresholds on a direct lane, hub bypass (also called "volume LTL" or "spot truckload") eliminates the hub handling charges and reduces transit time to one leg. The LTL carrier quotes a volume rate rather than a per-CWT class rate. Volume LTL typically applies for shipments over 5,000–10,000 lbs that do not quite justify a full truckload rate — they fall in the "tweener" zone where neither pure LTL pricing nor FTL pricing is clearly optimal.
Mid-market shippers often do not know volume LTL exists as a pricing tier. Their TMS queries the standard LTL rate engine and returns the class-based rate; the volume LTL option requires a separate carrier inquiry that most dispatch teams do not have time to pursue per shipment. Automated rate shopping that queries both the class-based LTL rate and the volume LTL rate for shipments above 5,000 lbs is a straightforward automation that can save 8–15% on shipments in that weight range.
The Milk-Run Alternative to LTL
For shippers with multiple delivery points in a geographic cluster — and this describes most regional grocery distributors and building materials shippers in dense metro areas — a private fleet milk-run route is often cheaper than individual LTL moves to each stop. The milk-run is a multi-stop FTL route where the driver delivers to 4–8 stops in sequence, returning the truck to the depot at the end of the day rather than the freight traveling through an LTL hub network.
The milk-run versus LTL decision depends on three factors: total stop density within a drivable radius, time window compatibility across stops, and the private fleet's cost-per-mile (CPM) relative to the LTL rates for those lanes. For a regional distributor with 18 stops within 60 miles of their DC, the milk-run CPM is typically $1.60–$2.10 per loaded mile, which beats LTL by 20–35% for Class 70–100 freight on those short lanes. The milk-run breaks down economically when stops are spread over more than 150 miles — at that point, the driver deadhead on the return trip erodes the savings.
We are not saying milk-runs always beat LTL — the economics depend heavily on freight class and lane distance. What we are saying is that many mid-market shippers default to LTL for the convenience of not managing the routing complexity, not because the math favors it. When the routing complexity is managed by a solver rather than a dispatcher, the milk-run option gets evaluated on its merits per lane rather than defaulted away.
Accessorial Costs: The Hidden Multiplier in LTL Math
Standard LTL rate comparisons often understate actual LTL cost because they omit accessorials. The typical accessorial stack for a mid-market shipper's LTL moves includes:
- Fuel surcharge: LTL carriers index fuel surcharges weekly to the DOE diesel price index. At current diesel levels, fuel surcharge adds 22–28% on top of the linehaul rate.
- Liftgate service: $50–$150 per shipment if the delivery location does not have a dock. Mid-market shippers with customer locations that lack dock doors pay this regularly and often do not account for it in mode-selection math.
- Limited access delivery: Schools, construction sites, military installations, and residential addresses trigger limited access surcharges of $75–$200 per delivery.
- Detention and redelivery: If the driver arrives and the receiver is unavailable or not ready to unload, detention charges ($75–$150 for the first hour) and redelivery fees ($100–$250) compound the base rate significantly.
A mode selection model that uses only the base LTL rate without accessorial estimation will consistently understate LTL cost and trigger false negatives on consolidation decisions. For accurate comparison, the model needs an accessorial profile per stop — which requires stop-level data including dock availability, appointment history, and any known receiver access limitations.
Consolidation Windows: The Operational Trade-Off
Consolidation creates a timing tension. To fill a truck, you need enough freight volume — which means holding some shipments for a consolidation window rather than shipping them the moment they are ready. Customers who expect next-day or two-day delivery on their LTL orders will not accept a two-day hold for consolidation. Customers with more flexible delivery windows — DC replenishment orders, bulk materials with multi-day lead time buffers — may not notice a one-day hold.
Practical consolidation windows for mid-market shippers run 24–48 hours. Beyond 48 hours, the downstream inventory carrying cost and the relationship risk with the customer typically outweigh the freight savings. The consolidation optimization model should evaluate time-sensitivity by customer and order type, not apply a blanket hold policy. Applying a 48-hour consolidation hold to every shipment is the kind of blunt instrument that generates carrier cost savings on paper and customer relationship damage in practice.
The operational teams who get consolidation right are the ones who build it into their order management process — flagging which orders qualify for consolidation windows at the time of order entry, based on customer SLA agreements, rather than deciding at dispatch time whether to hold a shipment that may already be time-critical. Getting that flag upstream, from order management to TMS to dispatch, is the process change that makes automated consolidation logic work at scale.