The Complete Guide to Multi-Truck Load Consolidation

· 8 min read

Most TMS platforms assume one truck moves one load from origin to destination. That assumption is fine if you're a single-truck owner-operator. It breaks the moment your business model involves a local truck picking up freight, dropping it at a warehouse, an over-the-road truck taking it to another warehouse, and a last-mile truck running it to the consignee. Each segment has a different driver, a different pay structure, and sometimes a different MC — but the customer paid you one rate for the whole thing.

That's freight consolidation. It's how every cross-dock operator, regional 3PL, and asset-broker hybrid actually works. And it's why most of them are still running on spreadsheets and group texts: their TMS literally can't model what they do.

FreightBoard is built for this pattern. Every load is a master record. Underneath it, you can stack as many trucks as the move actually requires, each with its own assignment, pay, and POD. The customer still sees one invoice with one rate. The drivers still get paid for exactly the segment they ran. The dispatcher sees the whole chain in one screen.

The four-segment consolidator pattern

The most common consolidation flow has four physical pieces:

  1. Local pickup — a local truck (typically a straight truck or day cab) goes to the shipper, picks up the freight, runs it to your local warehouse for cross-dock or staging.
  2. Warehouse transload — the freight gets staged, possibly consolidated with other shipments going the same direction.
  3. Line-haul — your own asset truck or a brokered carrier runs the long-haul leg from your warehouse to the destination warehouse.
  4. Last-mile delivery — another local truck handles the final leg to the consignee's dock.

Each leg is a separate dispatch. Each driver gets paid separately. But the customer only knows about one load number, one rate, and one ETA. FreightBoard's features page walks through the data model — but the short version is that loads have stops, and trucks get assigned to the segments between stops.

Why this is hard in a normal TMS

Single-leg TMSs treat the truck and the load as the same thing. If you split the load, you have to either:

  • Create three separate loads in the system — different load numbers, different invoices to the customer, dispatch chaos. The customer is angry because they got three invoices for what was supposed to be one shipment.
  • Hide the local trucks off-system and pay them in cash or off-cycle — works for a while, blows up when one of the locals demands a 1099 reconciliation at year-end.
  • Eat the local cost as overhead — kills your margin on every consolidator move and makes the model unprofitable.

None of those are real solutions. The right answer is a TMS that understands one customer rate can correspond to multiple driver legs, and bills, dispatches, and pays accordingly.

The dispatcher workflow

Here's how a consolidator load actually flows through FreightBoard, end to end:

Step 1: Punch in the master load

Customer, customer reference, MC entity (which authority you're operating under), origin, destination, weight, pallet count, freight type, rate. Same as any other load. The Load Size selector at the top lets you tag it as Dedicated, Partial, or LTL — useful for downstream reporting and for the warehouse-inbound notification.

If you already know it's a consolidator move with a specific local pickup truck, check the Local Pickup toggle in the new load form. That expands a panel where you pick the local truck, the local driver, and the flat pay amount for the pickup. On save, that becomes a separate leg automatically — the local driver shows up in their A/P weekly settlement with the right pay, and the dispatch board doesn't think the line-haul truck is doing the pickup.

Step 2: Add stops

If the move involves a warehouse stop or two — or any extra pickup or extra drop — add stops directly on the load. Each stop gets an address, an appointment time, and a "Truck Preference" (Any, Local, OTR) that tells the dispatch board which kind of truck should service that stop. Multi-warehouse consolidator moves usually look like: shipper → extra_drop (warehouse A) → extra_pickup (warehouse A again, after consolidation) → receiver.

Step 3: Assign the line-haul truck

From the dispatch board, drag the master load onto the line-haul truck (or a brokered carrier). The system shows live capacity — pallets, weight, and current loads on that truck — so you can't accidentally over-assign. If you want to add a second local truck for delivery, the load detail's "Add Local Truck (Pickup / Delivery)" action handles that the same way as the pickup leg: pick truck, driver, flat pay, save.

Step 4: Dispatch + auto-notifications

Hit Dispatch on the master load. The system fires several things automatically:

  • Generates the master BOL number.
  • Sends the rate confirmation to any brokered carriers via email.
  • Emails the warehouse on the load's via-warehouse field with an inbound notice — load number, ETA, weight, pallets, carrier, truck/driver names. The dock prepares for the inbound without anyone making a call.
  • Tags the assigned trucks as on-load so the dispatch board reflects the true capacity of your fleet.

Step 5: Tracking

Generate a customer-facing tracking link from the load. The customer opens it on their phone — no app install — and sees the truck's progress on a map plus the route, ETA, and any en-route status updates. For multi-segment loads the tracking shows the relevant active segment. Your dispatcher's afternoon stops being half "where's my truck" calls.

Step 6: POD upload from the driver's phone

When the line-haul or last-mile driver delivers, you generate a POD upload link from the load detail and text it to them. They tap the link, snap photos of the signed BOL, hit upload. The POD attaches to the master load. The load auto-flips to "ready to invoice" the moment the first POD lands — no dispatcher intervention.

Step 7: Invoice

One click on the invoice action. The TMS pulls the customer rate, the master BOL, the POD photos, and any rate-confirmed accessorials into a single PDF. Send it to the customer's A/P, copy your factor, done.

Step 8: Driver A/P

Each driver's pay shows up in their weekly settlement automatically. The local pickup driver gets the flat amount you entered. The line-haul driver gets per-mile / flat / percentage pay based on their card setting and the actual road miles for their segment (Google Directions, not straight-line). The last-mile driver gets their flat. One Print Settlement click per driver hands off a clean remit.

The math that makes consolidation profitable

Here's a stripped-down example. You quote a customer $4,000 for a single move that requires:

  • Local pickup, $200 flat to a contracted local truck
  • Warehouse cross-dock, $50 in handling fees
  • Line-haul, 800 miles at $0.55/mi to your asset driver = $440
  • Last-mile delivery, $175 flat to a contracted local truck

Total cost: $865. Margin on the move: $3,135 / $4,000 = 78%. That's a number you literally can't run in a spreadsheet without an accounting headache, because the four pay events happen on different days, to different parties, with different pay structures. In a real TMS, every one of those numbers is a row that ties back to the master load. The margin per move is one screen.

Why customers like working with consolidators

From the customer's perspective, the consolidator pattern looks the same as a single-truck move: one rate, one tracking link, one invoice, one POD. They don't know or care that there were four trucks and three drivers involved. They just know their freight got picked up on time, moved without damage, and the invoice was clean.

The reason consolidators win on rate is they can pack a line-haul truck more densely than a one-customer dedicated move would allow, and they cover the local pickup/delivery cost using local trucks that don't have to deadhead back. The reason they keep customers is the customer experience is identical to a much simpler move.

That's the model FreightBoard is built for. Try the consolidator workflow with a sample load, or talk to sales if you want a walkthrough on a real flow you're running today.