Window hit rate
Appointment-driven dispatch beats LTL slot variance — Warp tracks 98.2% on-time against committed delivery dates.
Pool distribution consolidates multi-shipper freight at a regional cross-dock then breaks it into store-level deliveries. Cheaper than dedicated when no single store has truckload volume, faster and more reliable than LTL when you have 6+ stops in a regional cluster and 10+ pallets per region per week. Below those thresholds, LTL wins on cost.
50+ cross-docks across the United States · 98.2% on-time delivery · 30 LTL carriers + 20K FTL, box truck, and cargo van assets · 24% lower landed cost than legacy pool networks
Inbound freight from multiple shippers — LTL pickups, full truckloads, vendor consolidation drops — converges at one regional cross-dock. The cross-dock sorts by store, builds a single pool truck, and runs a route-optimized multi-stop delivery. One truck, many shippers, many stops.
Two variables determine the right mode: stops per regional cluster (x-axis) and weekly pallet volume per region (y-axis). Pool distribution beats LTL only when both axes cross the threshold.
Legacy pool providers ran on static schedules, paper PODs, and weekly status emails. The four levers a modern pool network pulls — and the metrics each one moves:
Appointment-driven dispatch beats LTL slot variance — Warp tracks 98.2% on-time against committed delivery dates.
Pickup, in-transit, dock-arrival, and POD scans — every shipment, every node. No black-box pool legs.
Open a store, close a store, shift an appointment — the network re-plans inside 48 hours. Static pool schedules can't.
Pool ↔ LTL ↔ partial truckload ↔ dedicated on the same network. Volume shifts don't require a new RFP.
Five buyer scenarios that drive most pool distribution conversations. If two or more apply, the math almost always favors switching.
Locked into static schedules, opaque billing, paper PODs. Modernization without losing day-one coverage.
Walmart OTIF, Target VCP, Costco scorecard. Need appointment discipline pool-grade execution delivers.
Stores rejecting late drops, charging chargebacks, blocking inventory. Need OTD lift fast.
Truck disappears at the cross-dock and reappears at the store. Need scans at every handoff.
Promo cycles, seasonal peaks, store openings. Need pool that bridges into LTL and dedicated.
Pool distribution beats LTL on landed cost only when the network has enough density to justify the consolidation overhead. The math is not theoretical. Three thresholds tell you whether pool wins or LTL wins for a given footprint.
Below 6 stops in a cluster, the cross-dock handling cost exceeds the per-shipment savings. LTL is cheaper. At 6+ stops, pool starts winning on cost AND beats LTL on appointment reliability.
Below 10 pallets, you cannot fill a pool truck efficiently and per-pallet cost rises. Above 10, pool consolidates the run cleanly and unit cost drops below LTL all-in including reclass and accessorials.
When stores enforce 2-hour appointment windows or retailer scorecards (Walmart OTIF, Target VCP), LTL delay variance becomes a cost center. Pool execution beats LTL on appointment hit rate, which makes the landed-cost calculation favor pool even when raw rate looks higher.
Industry-typical pricing ranges for the comparison. These are not Warp-quoted rates — actual numbers depend on lane density, stop count, retailer compliance, and dock dwell.
Compare these thresholds against your store footprint before you commit. If you are running a freight RFP, the freight RFP template gives you the bidder questions to score pool vs LTL vs partial truckload providers on the same axes. For the pricing-model comparison across modes see the LTL vs partial truckload vs FTL breakdown.
A pool network looks similar from the outside. The differences show up in cross-dock SLAs, scan capture, and how the network responds when something changes. Score every provider on the same five axes.
List every store, weekly drop count, appointment constraints, and current cost per stop. Pool wins on density. Without density you are better off with LTL or partial truckload.
Ask for a list of cross-dock facilities by region, dock SLAs, scan capture rates, and the contingency plan when a dock backs up.
Demand pickup, in-transit, dock-arrival, and proof-of-delivery scans for every shipment. If the provider cannot show a sample dashboard, you do not have visibility.
Ask how the network responds to a store opening, a route consolidation, or an appointment shift inside 48 hours. Static schedules cannot absorb modern retail variability.
Compare per-stop cost against LTL all-in including reclass, reweigh, accessorials, and missed-window penalties. Use the reclass + reweigh fee guide to baseline LTL leakage before you compare.
For a broader view of regional and middle-mile carriers that compete on this profile, see best middle-mile freight companies.
Six steps from data pull to weekly scorecard. Most shippers see on-time delivery lift in the first cluster within two weeks.
Export every shipment to every store: weight, pallets, appointment, current carrier, current cost, and on-time outcome. The data tells you which regions actually have density.
Group stores within ~150-mile drive radii of a candidate cross-dock. Stores in the same cluster share a pool truck. Single-store outliers stay on LTL or dedicated.
Confirm appointment SLAs, dock capacity, scan capture, and contingency at each cross-dock that anchors a cluster. A weak dock kills the whole region.
Single rate that bundles pickup, line haul, dock handling, and standard appointment. Reject unbundled accessorial menus that erode the savings.
Start with the densest cluster. Track OTD, scan capture, claim rate, and cost per stop daily. Use the pilot to refine appointment workflows before scaling.
Roll out to remaining clusters. Run a weekly scorecard with the carrier covering OTD, scan capture, exception count, and cost variance. Adjust routing or carrier mix as volume shifts.
Most shippers compare pool distribution against incumbents in the same regional footprint. The competitive frame for the four most common comparisons:
ODFL is asset-heavy LTL with terminal handoffs. Pool with Warp moves the same regional freight through a cross-dock without classifying it as LTL — no NMFC, no reweigh, faster appointment hit.
Estes runs a strong regional terminal network. Warp pool layers on dynamic routing and scan-level visibility that Estes' legacy pool product does not match.
Hub and JBH are intermodal-led with regional truck arms. Warp covers the same store-delivery footprint with a single-source pool + LTL + truckload network and per-stop pricing.
RXO last-mile is built for residential big-and-bulky. Warp pool is B2B store delivery — appointment windows, dock loading, OTIF compliance — a different product for a different buyer.
Warp runs pool distribution across the United States. Each chip links to the regional cross-dock page with appointment SLAs, dock capacity, and lane-specific rates.
Quick links to concepts that come up in pool distribution conversations — the pricing terms, network architecture, retailer compliance frameworks, and tools you'll want when running an RFP or migrating a program.
Pool distribution consolidates freight from multiple shippers at a regional cross-dock and breaks it into smaller deliveries to nearby stores or accounts. It sits between LTL and dedicated: cheaper than dedicated when no single store has truckload volume, faster and more reliable than LTL when route density is high.
Pool typically beats LTL when you have 6+ stops in a regional cluster, total weekly volume of 10+ pallets to that region, and tight delivery-window requirements. Below those thresholds LTL wins on cost. Above them pool wins on cost AND service.
A dedicated route is one truck assigned to one shipper on a fixed schedule. Pool distribution shares trucks across multiple shippers with overlapping store footprints, lowering cost per stop while preserving most of the service-window control of dedicated.
Warp runs pool distribution across 50+ cross-docks across the United States with dynamic routing, scan-level visibility, and the ability to flex between pool, LTL, partial truckload, and dedicated as store volume changes. Most legacy providers are locked into static pool schedules.
On-time delivery to store appointment, scan capture rate at every node, dock-arrival accuracy, claim rate, and cost per stop. Warp targets 98.2% OTD across the network and full scan capture as the baseline.
Yes, when the network has the appointment-management discipline. See the shipping pallets to Walmart, Target, and Costco guide for retailer-specific OTIF and scorecard constraints.
Most providers price per stop with a linehaul component, a stop fee, and accessorials. The cleanest pricing model is a flat per-stop or per-pallet rate that bundles linehaul, dock handling, and standard appointment scheduling. Beware of unbundled accessorial menus that erase the savings versus LTL.
Pool distribution is built for B2B store delivery. DTC parcel uses a different network. Brands that run both can share the underlying cross-dock footprint, which is how Warp customers consolidate B2B and DTC operations.
Pool distribution moves multi-shipper freight from a regional cross-dock to multiple stores in that region. Zone skipping moves freight directly into a destination region, bypassing parcel sortation hubs to lower cost on long-haul ecommerce. Pool is B2B store delivery; zone skipping is parcel injection. Many shippers run both on the same network — see the zone skipping use case for the parcel-injection variant.
Hub-and-spoke is the underlying network architecture used by traditional LTL carriers — freight moves to a hub, gets re-sorted, then to a spoke terminal. Pool distribution uses one regional cross-dock (the spoke) without the hub re-handle, dropping transit time and damage risk. Pool is a hub-and-spoke variant optimized for store delivery density.
Master pool runs through a single national consolidation hub before regional break — common in retail apparel and big-box vendor programs. Regional pool skips the master hub and consolidates directly at the regional cross-dock. Regional pool is faster and cheaper for shippers with consistent regional volume; master pool is preferred when origin volume is fragmented across many vendors.
Industry-typical pool distribution stop fees run $40 to $80 per stop, with per-pallet rates of $25 to $60 inside a regional cluster. The cleanest pricing model bundles linehaul, dock handling, and standard appointment scheduling into a single per-stop rate. Below 6 stops or 10 weekly pallets per region, LTL is usually cheaper.
Score candidate carriers on five axes: cross-dock coverage in your regions, scan-level visibility (pickup, in-transit, dock-arrival, POD), flexibility under volume change, pricing transparency (bundled per-stop rather than unbundled accessorial menus), and on-time delivery performance against retailer scorecards. Run all candidates against the same store footprint and compare landed cost — not raw rate.
Pool distribution can support cold-chain when the cross-dock has refrigerated handling capability and the carrier runs reefer-equipped pool trucks. Most legacy pool networks are dry only. Cold-chain pool distribution is most viable for retail dairy, frozen, or pharma replenishment where volume justifies the temperature-controlled lane.
Start with a 90-day store-delivery data pull, cluster stores into candidate pool regions, validate cross-dock SLAs, lock per-stop pricing, pilot the densest region for 30 days, then scale with a weekly scorecard. Most shippers see OTD lift in the first cluster within two weeks. The setup HowTo on this page walks the full sequence.
If your current pool provider is too rigid, too opaque, or too slow to adapt, Warp can help map a better structure. Share a recent store delivery profile and we will show where the current model is creating friction, where visibility is weak, and how a more modern pool distribution network can improve execution.