XPO opens new terminals in Phoenix, Kansas City markets
XPO opened two new LTL terminals in Mesa, AZ and Cameron, MO, bringing its North American network to 300 locations with 99% U.S. ZIP code coverage. Phoenix and Kansas City corridors gain added capacity, targeting cross-border Mexico trade and Midwest freight lanes.
LTL carriers are aggressively expanding network density post-Yellow Corp collapse, creating a more competitive freight market that could stabilize or reduce inbound shipping costs for sellers with regional DC strategies.
Expanded LTL density in Phoenix and KC means potentially faster transit times and more competitive spot rates in those lanes — useful if you're routing FBA replenishment or 3PL transfers through the Southwest or Midwest. Sellers using freight brokers should benchmark XPO quotes against current carrier rates on these corridors in the next 30 days.
Operational Impact
This story may require teams to revisit workflows, monitoring, or platform assumptions.
Bottom Line
XPO's 300-terminal network means more LTL options for Southwest and Midwest replenishment lanes.
Source Lens
Industry Context
Useful background context, but lower-priority than direct platform, community, or operator intelligence.
Impact Level
medium
XPO's 300-terminal network means more LTL options for Southwest and Midwest replenishment lanes.
Key Stat / Trigger
300 terminals covering 99% of U.S. ZIP codes
Focus on the operational implication, not just the headline.
Full Coverage
Less-than-truckload carrier XPO announced Thursday that it has added new locations in Arizona and Missouri, increasing its terminal count to 300 across North America. A new 51,000-square-foot facility in Mesa, Arizona has 86 dock doors and over 100 employees.
The terminal gives XPO (NYSE: XPO) needed capacity to serve the Phoenix market, where it already operates a freight assembly center. The region is experiencing an increase in demand given recent industrial investments and growing cross-border trade with Mexico.
A 13,000-square-foot terminal in Cameron, Missouri (approximately 50 miles north of Kansas City) has 32 dock doors and over 30 employees. It sits near the intersection of I-35 and U. S. 36, serving both north-south and east-west freight corridors.
“These new service centers deepen our presence in two critical freight markets and reflect our strategic approach to investing in our network,” said Matt Carroll, president of XPO’s West Division. “We’ve added capacity where our customers need it most, positioning us to support their growth while delivering the world-class service they count on.”
The carrier has increased door capacity by 15% over the past five years through the opening of nearly 35 new locations. It inked a deal in 2023 to buy 28 terminals valued at $870 million from defunct Yellow Corp. With a network spanning 300 terminals, XPO provides direct coverage across 99% of U. S.
ZIP codes alongside cross-border service in and out of Canada and Mexico. Why it matters? XPO’s expansion enhances its network density and geographic reach, strategically positioning the carrier in high-demand corridors.
This increased infrastructure improves service reliability and competitive capacity, enabling XPO to better target high-yield local accounts and capture greater market share. More FreightWaves articles by Todd Maiden: Old Dominion pulls forward 4. 9% GRI as LTL carriers accelerate rate hikes Truckload carriers: Capacity exodus growing, not slowing J. B.
Hunt flags Q3 cost pressures, shares sink 12% The post XPO opens new terminals in Phoenix, Kansas City markets appeared first on FreightWaves.
Check your freight spend dashboard for Phoenix (AZ) and Kansas City (MO) lanes — if you're moving pallets through those corridors, request updated XPO LTL quotes to compare against your current carrier.
If you source cross-border from Mexico and route through Arizona DCs, add XPO as a backup LTL carrier in your logistics stack before Q4 peak season tightens capacity.
Original Source
This briefing is based on reporting from Freightwaves. Use the original post for full primary-source context.
Style
Audience