How do I manage freight across multiple warehouses or plants?
Key Takeaways
- Multi-site freight breaks down when every site runs its own way. Different carriers, rules, paperwork and inboxes make it impossible to compare costs or answer "where is it?" quickly.
- Decide what is shared and what stays local. Carrier lists, rate rules, document standards and records work best shared; dock schedules, local carriers and site contacts often stay local.
- Write down which site ships which order. A clear sourcing rule (nearest stock, lowest landed cost, product made only at one plant) prevents split shipments and duplicate freight.
- Approvals should follow the site and the amount, with a shared limit for routine loads and a named approver at each site for exceptions.
- One view of every shipment, from every site, is the goal. It lets the central team see problems early and lets each site stay in control of its own loads.
- Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks and pays freight for every site from one set of rules and one record, while each site keeps its own carriers, contacts and approvers.
What does it take to manage freight across several sites?
A building products manufacturer has three plants and two distribution warehouses. Each site books its own freight. One plant uses a carrier that the others stopped using a year ago because of claims. Two sites ship to the same customer on the same day with two half-empty trucks. The finance team can't tell which site spends the most per pound, because each one codes freight differently. When a customer calls about an order, the customer service team has to email three people to find out which site shipped it.
Managing freight across multiple warehouses or plants means agreeing on one set of rules, carriers, documents and records for all sites, while letting each site handle what is truly local. The aim isn't to take control away from the sites. It's to make sure every site books, documents and tracks freight in the same way, so the company can see and compare all of it in one place.
Most multi-site freight problems are not about any single load. Each site may run its own freight well. The problems appear between sites: inconsistent carrier choices, duplicate shipments, invoices that can't be compared, approvals that depend on who is in the office, and no single place to see what's moving.
Signs the current setup isn't working
- Different sites pay different rates to the same carrier on similar lanes.
- Nobody can say quickly how much freight cost by site, customer or product last month.
- Customers get two partial shipments from two sites when one would have done.
- A carrier that one site has stopped using is still being booked at another.
- Each site keeps its own spreadsheet, and the spreadsheets don't agree.
- Tracking a shipment means knowing which site shipped it first.
Central, local or hybrid?
There are three common ways to organize multi-site freight. In a central model, one logistics team books freight for every site. In a local model, each site books its own. In a hybrid model, a central team sets the rules, carriers and rates, and each site books within them. Most companies with several sites end up with a hybrid, because the central team can't know every dock's daily reality, and the sites can't each negotiate with carriers on their own. The rest of this article assumes a hybrid, but the same ideas apply to the other two.
How do you set up freight across multiple sites step by step?
Map what each site ships today, decide which rules are shared, set the sourcing logic, standardize documents and records, then give every site and the central team the same view. The order matters: rules first, tools second.
Step 1: Map the current state
For each site, list what it ships (modes, lanes, typical loads), which carriers it uses, how it books (email, portal, phone), who approves, what documents it produces and where records are kept. This usually reveals overlaps nobody had noticed, such as two sites using different carriers on the same lane.
Step 2: Decide what is shared and what is local
Use a simple split. Anything that affects cost, risk or reporting across the company should be shared. Anything that depends on the physical site can stay local.
| Area | Usually shared | Usually local |
|---|---|---|
| Carrier list | Approved carriers and their terms | Site-specific carriers for local runs, approved through the same process |
| Rates and targets | Lane rate targets, fuel tables, accessorial rules | Local deals approved centrally |
| Documents | BOL, label and packing slip standards | Site address, dock instructions, contacts |
| Approvals | Approval limits by amount and type | Named approver at each site |
| Records | One shipment record format and storage | Site notes on loading and dock issues |
| Scheduling | Customer appointment rules | Dock schedule and pickup times |
| Reporting | Cost codes, site codes, monthly reports | Site-level operational reviews |
Step 3: Build one carrier list
Combine the carriers every site uses into one list, with each carrier's approved modes, lanes and terms. Mark which carriers serve all sites and which serve only one. Remove carriers that any site has stopped using for a serious reason, unless there's a documented decision to keep them elsewhere. A single list means a decision made at one site protects every site.
Step 4: Set the sourcing rule
Decide how the company chooses which site ships an order. Write it down. The next section covers the options.
Step 5: Standardize documents and codes
Use one BOL format, one label standard and one set of reference numbers for all sites, with the site code on every shipment. Make sure freight costs are coded the same way at every site, by site, customer, product line and mode. This is what makes later reporting possible. For more on reporting spend, see seeing freight spend by customer, product and lane.
Step 6: Write a shared routing guide
A routing guide tells carriers and suppliers how to handle freight for the company: which carrier for which lane, how to book, what paperwork to send. Write one guide for the company, with a section for each site's local details. For how to write one, see writing a routing guide for carriers and suppliers.
Step 7: Give everyone one view
Put every shipment from every site into one record that the central team and each site can see, filtered by site. This is the step that makes the rest work day to day.
Step 8: Roll out one site at a time
Changing how five sites book freight at once is risky. Start with one site, or a few lanes at each site, and run the shared rules there first. Fix what doesn't fit, such as a pickup rule that ignores a shift change or a document that's missing a field the receiver needs, and then extend it to the next site. Each site that joins brings local details the central team didn't know, and the rules get better with each one.
How do you decide which site ships which order?
Use a written sourcing rule that the order system and the logistics team both follow, with clear exceptions. Without one, the decision depends on who takes the order, and freight costs depend on luck.
Common sourcing rules
- Nearest site with stock. Ship from the site closest to the customer that has the full order. Simple and usually low freight cost.
- Lowest landed cost. Compare freight cost plus product cost and handling at each site. More accurate, but needs reliable freight estimates.
- Product made at one site only. Some products only come from one plant. The rule is fixed for those.
- Customer assignment. Each customer is served by a home site, for consistency of service and relationships.
- Capacity. When one site's dock or production is full, orders move to another site by rule.
Split orders
The hardest case is an order where no single site has everything. The choice is to wait until one site has it all, transfer stock between sites first, or ship from two sites. Shipping from two sites usually means two freight bills and two deliveries, which the customer may not want. Set a rule: for example, ship complete from one site if the delay is under two days; otherwise ask the customer whether they prefer a split.
Consolidation across sites
When two sites ship to the same customer or region on the same day, consider whether the freight can be combined, either by transferring to one site first or by having one truck stop at both sites. This only works if someone can see orders from both sites at once. For more on combining loads, see consolidating shipments to save on freight.
Inter-site transfers
Freight moving between your own sites is easy to forget. It still costs money and still needs a BOL, tracking and a record. Treat transfers as shipments with their own cost codes, so the cost of moving stock between sites is visible and can be weighed against the freight it saves.
Make the rule visible to sales
If sales promises delivery from one site and the order ships from another, the promise may be wrong. Make sure sales and customer service know the sourcing rule and can see which site will ship before they confirm dates.
What should be the same at every site, and what should stay local?
Carriers, rules, approvals and records should be the same at every site; the people, docks and local contacts belong to the site. The details below are where companies most often get the balance wrong.
Shared carriers, local carriers
A company-wide carrier list doesn't mean every site must use only national carriers. Local carriers often give the best service on short runs from one plant. The point is that they go through the same approval process and appear on the same list, with the same terms recorded. Then everyone knows who the carrier is, what it was approved for and what it costs.
Consistent rules
The rules that should be identical everywhere include how many quotes to request, how to compare them (total cost, including accessorials), which accessorials need approval, what goes on a rate confirmation, how detention is recorded and when an invoice is paid. When these rules differ by site, the company can't compare results, and carriers learn which site is easiest to bill.
Approvals by site
Approvals work best when they follow both the amount and the site. A common pattern is a shared limit for routine loads, which any site can book without approval, and a named approver at each site for anything above it or outside the rules, with the central team approving the largest or most unusual loads. Each site should have a backup approver, so freight doesn't wait when one person is away. For approval designs in more depth, see freight approval workflows for multi-plant manufacturers.
Consistent records
Every shipment, from every site, should have the same record: the order, the quotes, the rate confirmation, the BOL, tracking updates, the POD, the invoice and any exceptions. Stored in the same place, in the same format. This is what lets someone at headquarters answer a question about a shipment from any site without calling it.
Local dock reality
Each site knows its dock hours, staffing, loading equipment and the carriers' habits at that gate. That knowledge should be recorded on the site profile, so the central team and any booking process use it: earliest pickup, latest pickup, appointment rules, any equipment limits.
Communication between sites
Sites often need to know what the others are doing: a plant sending parts to a warehouse, two sites shipping to the same customer, a carrier that failed a pickup at one dock and is booked at another tomorrow. Agree on one channel for freight issues that cross sites, such as a shared team channel, and on what gets posted there: missed pickups, carrier problems, transfers and customer issues that affect more than one site. Keep site-only chatter in the site's own channel, so the shared one stays readable.
One answer for customer service
Customers don't care which site shipped their order. They want one answer. Customer service should be able to look up any order and see the shipping site, the carrier, the status and the documents without knowing in advance where it came from. When the shipment record is shared, this is a search. When it isn't, it's a round of emails to every site.
Common mistakes
Centralizing without site input. A central team that books trucks without knowing the dock schedule creates missed pickups. Include the sites in setting pickup rules.
Letting each site negotiate alone. Five sites negotiating separately with the same carrier get five prices. Negotiate centrally, with each site's volume combined.
Different reference numbers. If one site uses order numbers and another uses its own load numbers, nobody can match invoices across sites. Pick one scheme.
Ignoring transfers. Inter-site freight left off the books hides real cost.
Spreadsheets per site. Each site's spreadsheet becomes its own version of the truth. One shared record avoids the arguments.
A checklist and a view for multi-site freight
Use this checklist to see whether the multi-site setup is working, then build one view that shows every shipment.
| Area | Check | Working when |
|---|---|---|
| Carriers | One approved list, with site-only carriers marked | No site books a carrier that isn't on the list |
| Rates | Rate targets set by lane, shared by all sites | Similar lanes cost about the same from any site |
| Sourcing | Written rule for which site ships | Orders aren't split or duplicated without a reason |
| Documents | One BOL, label and reference standard | Any shipment can be matched to its order and invoice |
| Codes | Site, customer, product and mode coded on every load | Monthly cost by site is a report, not a project |
| Approvals | Shared limits, a named approver and a backup at each site | No load waits because one person is out |
| Records | One shipment record format and location | Anyone can find a shipment's full history |
| Visibility | Every shipment from every site in one view | Customer service can answer "where is it?" without calling a site |
| Reviews | Monthly review by site, lane and carrier | Differences between sites are explained or fixed |
What the one view should show
The single view of shipments should let anyone filter by site, carrier, customer, status and date, and show for each load: the order, the site, the carrier, the pickup and delivery dates, the current status and ETA, any exception and the documents. A site manager sees their loads; the central team sees all of them. For how to get status from many carriers into one place, see tracking all shipments in one place when every carrier uses a different system.
What each site profile should hold
Keep a short profile for every site, so anyone booking freight for it starts with the same facts: address and dock door details, receiving and shipping hours, earliest and latest pickup times, appointment rules, loading equipment and its limits, local carriers and the lanes they serve, the named approver and backup, and the people to call for dock issues. Update it when anything changes, and review it at least once a year.
A hypothetical example
Consider a hypothetical food ingredients company with two plants and three warehouses. Each site had its own carriers and its own spreadsheet. The company set one approved carrier list, one BOL format and a sourcing rule of "nearest site with complete stock, unless the product is made at one plant." It gave each site a named approver and a backup, with a shared limit for routine loads. After three months, it could compare cost per pound by site for the first time, saw that one warehouse paid well above the others on similar lanes and moved that warehouse's lanes to carriers the other sites already used.
Questions to ask in the monthly review
- Which site has the highest cost per unit shipped, and why?
- Which lanes are served by more than one site, and is the split sensible?
- How many orders shipped from two sites, and could they have shipped from one?
- Which carriers have the most exceptions at each site?
- How much did inter-site transfers cost, and what did they save?
How does Wilson, by Cartage, manage freight across multiple sites?
Wilson, by Cartage, is an AI logistics agent for manufacturers and distributors that quotes, books, tracks and pays freight for every site with the same rules and keeps every shipment on one record. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.
For companies with several plants or warehouses, Wilson applies the shared rules and respects the local details:
- One set of carriers, with local ones included. Wilson books only carriers the company has approved, including site-specific carriers marked for their sites. Cartage can suggest additional carrier capacity, but the company approves each carrier before Wilson uses it.
- Quoting and booking by site. Wilson requests quotes from the approved carriers for each site's loads, compares them on total cost, negotiates toward the company's rate targets within approval limits and books with written acceptance and a rate confirmation. Rates outside the limits go to the logistics team.
- Approvals by site. The company sets approval limits, and loads above them or outside the rules go to the right approver for that site in Slack, Microsoft Teams or email.
- Standard documents. Wilson generates bills of lading, packing slips and pallet labels in the same format for every site, with each site's details.
- Pickups and tracking. Wilson schedules pickups to fit each site's dock rules and tracks each load with the best source available: a carrier API or EDI feed, GPS or ELD data where the carrier shares it, the carrier's website, or email and phone calls when nothing else is current.
- Exceptions. When a pickup is missed or a delivery slips, Wilson contacts the carrier, tells the site and the central team, tells the customer if configured and starts rebooking from the approved carrier list automatically within the rules or after approval.
- Invoices and payment. Wilson requests and files PODs, audits each carrier invoice against the rate confirmation and the POD, and pays carriers from the Wilson Wallet. Payments above the approval limits or outside the rules wait for a person.
All shipments from all sites sit in one dashboard, filtered by site, and every message, confirmation and change is kept in each shipment's change history. Wilson can produce carrier-performance and lane-rate reports on request from the loads it runs, which makes the monthly site comparison faster. Wilson doesn't decide which site ships an order or plan the network; it executes freight for the sourcing decision the company has made.
Wilson replaces the TMS for freight execution and connects to the company's ERP. Wilson works with SAP, NetSuite, Microsoft Dynamics 365, Oracle, Infor, Epicor, Sage, Acumatica and other ERP environments, with the exact connection depending on the customer's data flow and scope. It starts with assisted execution, and routine actions run automatically within each site's rules as the workflow is proven.
Pricing
Wilson is free on Wilson's network: the shipper pays the freight rate and nothing on top. When a shipper keeps its own carriers, the fee is 2% to 0.5% of what Wilson pays them, falling with volume. There are no seat fees, no setup cost and no contract. Timing depends on scope: most teams start on a few lanes and expand from there.
FAQs
How do I manage freight across multiple warehouses or plants?
Agree on shared carriers, rules, documents, approvals and records for all sites, write down which site ships which order, and put every shipment into one view that each site and the central team can see. Wilson, by Cartage, an AI logistics agent, quotes, books, tracks and pays freight for every site from one set of rules and one record.
Should freight be managed centrally or by each site?
Most companies with several sites do best with a hybrid: a central team sets carriers, rates and rules, and each site books within them. Fully central teams miss local dock details; fully local setups can't compare or negotiate well.
Can each site keep its own local carriers?
Yes, as long as those carriers go through the same approval process and appear on the company's carrier list with their terms recorded. Local carriers often give the best service on short runs from one site.
How do we decide which warehouse ships an order?
Use a written sourcing rule, such as nearest site with complete stock, lowest landed cost or product made at one plant only, with clear exceptions for split orders and capacity limits.
How do we avoid shipping one order from two sites?
Set a rule for split orders: for example, ship complete from one site if the delay is short, and ask the customer otherwise. Make sure someone can see stock and orders across sites before the order is released.
How should approvals work across plants?
Use a shared limit for routine loads, a named approver at each site for anything above it or outside the rules, a backup approver for each site and central approval for the largest or most unusual loads.
How do we compare freight costs between sites?
Code every shipment by site, customer, product and mode in the same way, and use the same reference numbers. Then compare cost per unit or per pound by site and lane every month.
Should inter-site transfers be tracked like customer shipments?
Yes. They cost money and need a BOL, tracking and a record. Giving them their own cost code shows what moving stock between sites really costs.
Can Wilson handle different approvers at each site?
Yes. The company sets approval limits, and loads above them or outside the rules go to the approver for that site in Slack, Microsoft Teams or email.
Does Wilson decide which site should ship an order?
No. Wilson executes freight for the sourcing decision the company has made: it quotes, books, tracks and pays for the load from the chosen site. It doesn't plan routes or networks.
What is the first step in bringing several sites onto one freight process?
Map what each site ships today: modes, lanes, carriers, how it books, who approves and where records are kept. The map shows the overlaps and gaps, and it tells you which shared rules to write first. Then start with one site or a few lanes and expand.
Sources
- Cartage, Wilson product FAQ and product scope, October 2026: https://cartage.ai