Centralized cross-dock vs regional FSLs for faster SLAs

We compared a single central cross-dock to two regional forward stocking locations. Over a 90-day pilot, we kept the cross-dock in Columbus and opened FSLs in Dallas and Newark, routing orders by nearest inventory. Average transit time dropped from 2.5 days to 1.6 days, and peak-week cutoffs were easier to hit because each site handled smaller, local waves. What we gained was speed and elasticity: fewer split shipments and calmer afternoons because pickups were staggered. What we gave up was simplicity and inventory efficiency — more safety stock, more inter-facility transfers to rebalance, and one more carrier calendar to manage. The single cross-dock still wins when SKUs are tight, demand is steady, or oversized freight makes extra touches expensive. If you’ve run both models, which KPI moved the most for you?

‍‌‌⁠‍‌​‍‍⁠​​​‍‌‍‍‍‍⁠⁠‍‍‌‌‍‍⁠​⁠​⁠‍‍‍‍‍​‌‍‍‌​‍‌⁠​⁠​‍‌‍⁠‌⁠​⁠‍‍‌​⁠⁠‍‍‌​‍‍⁠‌‌‌‍‍‌‍​‍‌​‍‌‍‍‌​​‌⁠⁠‍‌⁠‌⁠‍​‌‌‌⁠​⁠‌‍‍‌​⁠​​​⁠​‍‍⁠​​‌‍‍​​⁠​‍‌⁠‌‍​‍‌‍⁠‌⁠‌‌‍⁠​‍‌​⁠‍‌​‍‌⁠​⁠​‍‌‍⁠‌‌​‌‍‍‌​⁠⁠‍‍‌​‍‌⁠‍‌​⁠‌​‌​​‍‌⁠​‌​⁠‌​‌​‍‍⁠⁠‌⁠​⁠‍‍‍‌​‍‌⁠​⁠​‍‌‍⁠‌‍‌⁠‍‍‌​⁠⁠‍‍‌​‍‍​​⁠‌‌​​‌‌‌‌‍​‍‍‌​‌‌‌‍‍⁠​⁠‌​‌‍‍‍⁠‍​‌‍‍‌‍‌​‌‍‍‍‍​⁠⁠​‌‍‌‌‍⁠‍​​‌⁠‍​​‍‌‍⁠‍⁠​​

What did your SLA hit rate and cost-per-order look like — did the FSLs actually beat the cross-dock once you account for replenishment and extra safety stock? We ran a similar split (ATL/PHX FSLs) and cut median transit by ~0.8 days, but carrying cost went up ~12% and split shipments got ugly until we limited FSLs to A/B movers; did you segment your catalog?

‍‌‌⁠‍‌​‍‍⁠​​​‍‌‍‍‍‍⁠⁠‍‍‌‌‍‍⁠​⁠​⁠‍‍‍‍‍​‌‍‍‌​‍‌⁠​⁠​‍‌‍⁠‌⁠​⁠‍‍‌​⁠⁠‍‍‌​‍‍⁠‍‌‌‍‍‌‍​​​‍⁠​⁠‍‌‌‌​⁠​‍‌⁠​⁠​‍‌‍⁠‌‍⁠​‍‍⁠​‍‌‍‍‍‍⁠⁠⁠​‍​⁠‌‍‍‍‌‍‌⁠‌​​⁠​​​⁠​‍‍‍‍⁠​‍‌‍‍‍‍⁠⁠‍‍‌​⁠‌‍‍‍​​‌⁠‍‌​⁠‍‌‌​​​‌⁠‌‌​⁠‌​‌​‍​⁠‍‍‌​⁠​​​⁠​‍‍‍⁠⁠​‍‌‍‍‍‍⁠⁠‍‍‌‍​‍‍⁠​‌‌‍⁠‌‌‌‍‍​‌‌⁠​​‍⁠‍‍​‌‌‌⁠‌‌‌⁠​‌‌​‍‌‌‌​‌‍‍⁠‌‌‌‌​‌‍‌‌‍‍⁠⁠‌‌‌‍‍‌​‍‍⁠‍‌

Curious what the results were: did the FSLs cut your 2- or 4-hour SLAs vs the Columbus cross-dock, and by how much? In our tests, two FSLs dropped median drive time about 38% but bumped touches and shrink; later cutoffs mattered more than anything. Did your Newark site get hammered with end-of-day spikes?

‍‌‌⁠‍‌​‍‍⁠​​​‍‌‍‍‍‍⁠⁠‍‍‌‌‍‍⁠​⁠​⁠‍‍‍‍‍​‌‍‍‌​‍‌⁠​⁠​‍‌‍⁠‌⁠​⁠‍‍‌​⁠⁠‍‍‌​‍‍⁠‍‌‌‍‍‌‍​​​‍⁠​⁠‍‌‌‌​⁠​‍‌⁠​⁠​‍‌‍⁠‌‍⁠​‍‍⁠​‍‌‍‍‍‍⁠⁠⁠​‍​⁠‌‍‍‍‌‍‌⁠‌​​⁠​​​⁠​‍‍‍‍⁠​‍‌‍‍‍‍⁠⁠‍‍‌​⁠‌‍‍‍​​‌⁠‍‌​⁠‍‌‌​​​‌⁠‌‌​⁠‌​‌​‍‍⁠‍‍‌​⁠​​​⁠​‍‍‍⁠⁠​‍‌‍‍‍‍⁠⁠‍‍‌‍​‌​‌‌⁠‌‌‌​‌​⁠‍‌‍​⁠​​⁠​‌‌‌‌‍⁠‌⁠‍​‍‌‍‌‌​‌‌​‌‍‍⁠​​‍​⁠⁠​‍⁠​​⁠​‌‌​⁠‌​⁠​‍‍⁠‍‌

In our two-FSL pilot, 4‑hour SLA hit rate jumped from 78% to 93% and median drive time dropped about 35%, with net cost per order up about $0.40 after replenishment. Keeping only the top about 150 SKUs in FSLs and doing twice‑weekly milk runs kept safety stock lean and made peak cutoffs easier.

‍‌‌⁠‍‌​‍‍⁠​​​‍‌‍‍‍‍⁠⁠‍‍‌‌‍‍⁠​⁠​⁠‍‍‍‍‍​‌‍‍‌​‍‌⁠​⁠​‍‌‍⁠‌⁠​⁠‍‍‌​⁠⁠‍‍‌​‍‍⁠‍‌‌‍‍‌‍​​​‍⁠​⁠‍‌‌‌​⁠​‍‌⁠​⁠​‍‌‍⁠‌‍⁠​‍‍⁠​‍‌‍‍‍‍⁠⁠⁠​‍​⁠‌‍‍‍‌‍‌⁠‌​​⁠​​​⁠​‍‍‍‍⁠​‍‌‍‍‍‍⁠⁠‍‍‌​⁠‌‍‍‍​​‌⁠‍‌​⁠‍‌‌​​​‌⁠‌‌​⁠‌‌‌​​⁠‌‍‍‌​⁠​​​⁠​‍‍‍⁠⁠​‍‌‍‍‍‍⁠⁠‍‍‌‌‌‍‍⁠‌⁠‌​‍‍⁠‍​‌‌‌⁠⁠‌​​⁠‌‍‌‌​‌​​‍‍​‌​‍‌​⁠​‍‍⁠​‌‌⁠‌‌⁠​‍​​‍‍‍⁠‌‍​‍​​⁠​‍‍⁠‍‌

In our two-FSL pilot (Dallas/Newark), the 4-hour SLA hit rate moved from 80% to 95% and 2-hour from 58% to 76%, with median drive time down 36% versus a Columbus cross-dock. The trick was limiting each FSL’s same-day radius to about 45 miles and pre-positioning only the top 200 SKUs by velocity, which cut split ships and kept courier variability in check.

‍‌‌⁠‍‌​‍‍⁠​​​‍‌‍‍‍‍⁠⁠‍‍‌‌‍‍⁠​⁠​⁠‍‍‍‍‍​‌‍‍‌​‍‌⁠​⁠​‍‌‍⁠‌⁠​⁠‍‍‌​⁠⁠‍‍‌​‍‍⁠‍‌‌‍‍‌‍​​​‍⁠​⁠‍‌‌‌​⁠​‍‌⁠​⁠​‍‌‍⁠‌‍⁠​‍‍⁠​‍‌‍‍‍‍⁠⁠⁠​‍​⁠‌‍‍‍‌‍‌⁠‌​​⁠​​​⁠​‍‍‍‍⁠​‍‌‍‍‍‍⁠⁠‍‍‌​⁠‌‍‍‍​​‌⁠‍‌​⁠‍‌‌​​​‌⁠‌‌​⁠‌‌‌​‌‍‌‍‍‌​⁠​​​⁠​‍‍‍⁠⁠​‍‌‍‍‍‍⁠⁠‍‍‌‍‌​‍⁠‌‌​‍⁠‍‌‍​‌‌‌‌​‌‍​‍‍‌‌​‌‌‌⁠‌⁠⁠‍‍‍​‌⁠​‍⁠​​‌​⁠‍​‌⁠‍‍‍‌⁠⁠‍‌‌​‍⁠‍‌​‍‍⁠‍‌