April 23, 2026
Multi-site companies with decentralized freight management — where each plant, distribution center, or business unit manages its own carrier relationships, rates, and processes — consistently overpay for freight and lack the data visibility to know how much. Every site has different contracted rates, different brokers, and different invoice processes. The combined freight spend is never visible to anyone, and the combined volume never gets used as leverage. Standardizing freight operations across multiple sites does not require centralizing everything — it requires a common carrier network, common rate structure, and common reporting that each site uses while retaining day-to-day operational control. Learn more about Freight Management After an Acquisition: What Changes and What Needs to Be Fixed (2026 Guide).
| Site autonomy pattern | Result |
|---|---|
| Each site negotiates its own carrier contracts | Rate variation: same lane, different rates, no one aware of the gap |
| Each site uses preferred local brokers | Carrier network fragmentation: 40+ active relationships with no centralization |
| Each site has its own invoice AP process | Invoice audit is site-specific; no combined error tracking or recovery |
| No cross-site freight reporting | Finance can't see combined spend; operations can't benchmark performance |
Identify 2–4 primary carriers per lane type (dry van FTL, LTL, specialized) that are approved across all sites. Each site routes to these carriers first; exceptions require documented justification. This eliminates the "preferred local broker" pattern without eliminating flexibility.
A single rate master document with contracted rates by lane, carrier, and mode — accessible to all logistics and AP staff across sites. When a carrier bills differently from the rate master, it's a billing error regardless of which site received the invoice.
A routing guide specifies: for each lane, which carrier is primary (use first), which is backup (use when primary can't cover), and which is the exception option (use when backup can't cover). Sites follow the routing guide for all standard loads; exception situations are routed to the central logistics contact for approval.
| Lane | Primary carrier | Backup | Exception |
|---|---|---|---|
| Chicago → Dallas (FTL) | Carrier A | Carrier B | Spot market (log reason) |
| Chicago → Atlanta (FTL) | Carrier B | Carrier A | Spot market (log reason) |
| All sites → Northeast (LTL) | LTL Carrier X | LTL Carrier Y | LTL Carrier Z |
A monthly freight report from each site in a standard format — total spend by lane, carrier, and mode; invoice exceptions by carrier; OTP by carrier — that rolls up to a cross-site view for logistics and finance leadership.
Present the combined-volume leverage case: "Site A is paying X more per load on this lane than Site B. If we combine our volume under a single contract, both sites save." The economic argument is usually more persuasive than an operational mandate. Starting with 2–3 willing sites as a proof of concept builds momentum.
Standardize the parts that are common (carrier network, rate structure, reporting format) and accommodate site-specific needs in the routing guide (Site C needs reefer; Site D needs flatbed). A standard framework doesn't require identical freight profiles — just shared infrastructure on the common lanes.
90–120 days for a phased implementation: 30 days to collect data and build the common carrier list and rate master, 30 days to validate the routing guide with site logistics leads, 30–60 days to implement and run the first full reporting cycle. This timeline assumes strong sponsorship from operations or supply chain leadership.
A managed transportation provider is essentially a pre-built multi-site standardization program: they deliver a common carrier network, common contracted rates, and common reporting across all sites immediately upon onboarding. For companies that lack the internal logistics function to build and maintain the standard, managed transportation is the faster path.
Track three metrics 90 days post-implementation: rate variance across sites on common lanes (should drop below 5%), invoice error rate (should decline as common rate master enables audit), and combined freight cost as a percentage of revenue vs. pre-standardization baseline.