How should we manage freight between our own plants and warehouses?

Freight pickups guideNov 17, 202617 min read

How should we manage freight between our own plants and warehouses?

It is Monday morning. A manufacturer has two plants 300 miles apart and a warehouse near its largest customer. Every Tuesday and Thursday, a truck moves components from plant A to plant B and finished goods from plant B to the warehouse. The same carrier has done it for four years. Nobody remembers the last time the rate was compared. Plant B says the Thursday truck is late half the time. The warehouse says it never knows what is on the truck until it arrives. Finance books all of it to a general freight account, so no site sees what its transfers cost.

Freight between a company's own plants and warehouses should be managed with the same rules as customer freight: quoted and booked on purpose, tracked to a promised time, documented with a BOL and POD, checked against the invoice and charged to the site that caused it. The fact that both ends belong to the same company does not make the freight free or the delays harmless.

Internal freight is easy to neglect because there is no customer complaining. The receiving site absorbs the delay. Finance absorbs the cost. The carrier keeps the lane because nobody asks for a new quote. Over time, the transfer lanes become some of the most expensive and least examined freight the company moves.

Why transfer freight drifts

A few patterns show up again and again:

  • The lane is set up once and never reviewed. A rate agreed years ago stays in place, or creeps up with each invoice, because the lane is "handled."
  • No one owns it. The shipping site thinks the receiving site manages the inbound. The receiving site thinks the shipping site books it. Corporate logistics thinks the plants handle it.
  • The paperwork is thin. Some transfers move with a handwritten BOL or no packing list, so the receiving site cannot check what arrived.
  • The cost lands in the wrong place. If transfers are booked to one shared account, nobody can see that one site's habit of late orders is causing expedited transfers.
  • Delays are not counted. A late customer delivery gets noticed. A late transfer shows up as a production delay, a stock shortage or overtime at the receiving site, and the freight is rarely blamed.

What makes transfer freight different

Transfers do have a few real differences from customer freight. The company controls both docks, so appointment times can be set by internal agreement. The volume is often steady and predictable, which makes it a good fit for scheduled or dedicated capacity. Returnable racks, totes or pallets may come back on the return trip. And the cost does not get billed to a customer, so it has to be allocated internally.

These differences are reasons to manage transfers well, not reasons to skip the basics. The steadiness of the volume is exactly what makes a better rate or a better schedule possible.

A first look at your transfer lanes

Before changing anything, list every transfer lane: origin site, destination site, what moves, how often, which carrier, what it costs per load and who books it. Most teams have never seen this list in one place. It usually shows at least one lane that nobody can explain.

Let's review your transfer lanes between sites. You don't need to prepare anything: Cartage maps the workflow with you on the call.

See it on your own loads. Wilson, by Cartage, is an AI logistics agent that quotes, books, tracks, audits and pays for freight with your approved carriers.

Book a demo →

How do you set up transfer freight step by step?

Set up transfer freight as a short, repeatable workflow with a named owner for each step. The steps match customer freight, with a few internal rules added.

Step 1: Decide who owns each transfer lane

Pick one owner per lane. In most companies, the shipping site owns the outbound transfer because it controls the release, the loading and the paperwork. The receiving site owns the receiving check and reports what arrived. Corporate logistics, if it exists, owns the carrier choice and the rate.

Write it down. "Plant A books the Tuesday and Thursday transfers to plant B. Plant B confirms receipt and reports shortages within 24 hours. Logistics reviews the rate each quarter."

Step 2: Create a transfer order, not just a truck

Every transfer should start with an order: what moves, how much, from where, to where and by when. In many ERPs this is a transfer order or an internal sales order. Whatever the format, the order is what the freight record hangs on. Without it, the truck is booked against nothing, and nobody can check what should have arrived.

Step 3: Choose the capacity model

Transfers usually fit one of three models:

  • Dedicated: a truck and driver assigned to the company's lane on a fixed schedule.
  • Scheduled with an approved carrier: set pickup days with one or more approved carriers, booked load by load at an agreed rate.
  • Spot or as needed: quoted and booked each time, like customer freight.

The next section shows how to choose. Many companies use a mix: scheduled loads for the steady base and spot loads for the extra.

Step 4: Quote and book with the same rules as customer freight

Even when one carrier runs the lane, the booking should follow the company's rules. Collect a quote or confirm the agreed rate, check it against the lane limit, get written acceptance and a rate confirmation, and schedule the pickup. If the lane has a ranked list of approved carriers, the second carrier on the list should be ready when the first cannot cover a load.

Step 5: Send the paperwork with the freight

A transfer needs a BOL, a packing list and the transfer order number. If returnable racks or pallets go back, note them on the BOL for the return trip too. The receiving site uses these to check what arrived and to report shortages or damage.

Step 6: Track to the time the receiving site needs

The receiving site does not care that the truck "picked up." It cares when the freight will be at its dock. Track against that time, and tell the receiving site early if a load will be late. A plant that knows at 9:00 a.m. that components will arrive at 4:00 p.m. instead of noon can change its schedule. A plant that finds out at noon cannot.

Step 7: Close the load with a POD and an invoice check

The receiving site signs the POD. The carrier invoice is checked against the rate confirmation and the POD before payment, just like customer freight. Then the cost is charged to the right site.

Receiving checks and returnables

The receiving site should check every transfer the way it checks a supplier delivery. Count the pallets or units against the packing list. Look for damage before the driver leaves. Write any shortage or damage on the POD, and report it within an agreed time, such as one business day. If the receiving site signs a clean POD and finds a problem later, it is much harder to show that the freight was short or damaged in transit.

Returnable racks, totes and pallets need the same care. Decide who counts them at each end, where the count is written down and how often the two sites compare numbers. A rack that leaves plant A and never comes back is a real cost, and it often goes unnoticed until a production line runs out of racks. Put the returnables on the paperwork for both legs of the trip, so each site can see what it sent and what it received.

Keep internal and customer freight on the same rules

Some teams run transfers in a separate spreadsheet, with separate carriers and separate habits, because the freight feels internal. That split makes everything harder. The same coordinator ends up working from two lists, the transfer carrier gets no comparison with the carriers used for customer loads, and nobody can see total freight on a lane that carries both. One set of rules, one list of approved carriers and one record format for all freight is simpler to run and simpler to review.

How do you choose between dedicated, scheduled and spot capacity?

Choose the capacity model by looking at how much moves, how steady it is, how far it goes and what a late load costs the receiving site. There is no single right answer, but the decision should be made on purpose and reviewed.

What to look at

  • Volume per week. How many full or partial loads move on the lane in a normal week?
  • Steadiness. Is the volume the same every week, or does it swing with production or season?
  • Distance and timing. Can a truck make a round trip in a shift or a day? Does the freight need to arrive by a set time?
  • Return freight. Is there anything to bring back, such as empty racks, totes or a second transfer?
  • Cost of a late load. Does a late transfer stop a line, delay a customer order or just sit in a warehouse a day longer?

A comparison

Model Fits when Watch out for
Dedicated truck High, steady volume on a short lane with a round trip; late loads are costly Paying for idle time when volume drops; harder to change
Scheduled loads with approved carriers Steady but not full-time volume; set pickup days work for both sites Rates drifting without review; no backup when the main carrier is short
Spot loads Low or uneven volume; dates can flex Booking late and paying more; less priority with carriers
Mix of scheduled and spot A steady base with peaks Making sure peaks are actually quoted, not just added to the main carrier
LTL or consolidated Small transfers that do not fill a trailer Handling damage and longer transit; check whether waiting a day to fill a truck is cheaper

Partial loads between sites

Many transfers are not full truckloads. Before shipping a half-empty trailer twice a week, check whether one fuller load a week works for the receiving site. Or check whether the transfer can share a truck with a customer shipment going the same direction. The guide on when to use volume LTL or full truckload explains the trade-offs for partial loads.

When to review the model

Review the capacity model at least once a year, and any time something changes: a new product line, a plant moving work to another site, a new warehouse, or a steady pattern of late loads. A lane that needed a dedicated truck three years ago may now fit two scheduled loads a week, or the other way around.

How should transfer freight costs be charged to the right site?

Decide in advance which site or cost center pays for each kind of transfer, and put that on the load when it is booked. Month-end allocation by guesswork hides the very patterns the company needs to see.

Why allocation matters

When all transfer freight goes to one shared account, the numbers cannot answer basic questions. Which plant's late orders are causing the most expedited transfers? Is it cheaper to make a part in plant A and ship it, or make it in plant B? Is the warehouse near the customer paying for itself once freight is counted? These are real decisions, and freight is part of the answer.

Common allocation rules

Pick one rule per kind of transfer and write it down:

  • Shipping site pays. Simple. Works when the shipping site controls the decision to send.
  • Receiving site pays. Works when the receiving site pulls the freight, such as replenishment orders from a warehouse.
  • Product line pays. Works when transfer freight is part of the cost of a product, such as components moving to an assembly plant.
  • Cause pays. For expedited or extra transfers, the site or team that caused the need pays. This is the hardest rule to run but the most useful for changing behavior.

Put the cost code on the load

The cost center, site code or product line should be on the transfer order and carry through to the freight record and the invoice. When the invoice is approved, finance can post it to the right place without asking anyone. If the code is added only at month-end, it will be wrong some of the time.

Measure cost per unit, not just per load

A load cost tells part of the story. Cost per unit moved, per pound or per pallet shows whether a lane is getting more or less efficient. The method in how to calculate freight cost per unit works the same way for internal lanes.

Track expedited transfers separately

Every extra or rushed transfer should carry a reason: a late production run, a forecast miss, a quality hold, a customer pull-in. Over a quarter, the reasons show which internal problems cost the most in freight.

What should every site agree on for transfer freight?

The sites should agree on a short list of rules so transfers run the same way no matter who is on shift. The list also shows where the gaps are.

The transfer freight checklist

Item Question to answer Owner
Lane owner Who books each transfer lane? Logistics
Transfer order Does every load start from an order in the ERP? Shipping site
Capacity model Dedicated, scheduled, spot or a mix? Logistics
Approved carriers Which carriers are approved on each lane, in what order? Logistics
Rate and limit What is the agreed rate or lane limit, and when was it last checked? Logistics and finance
Pickup days and times When does each lane pick up? Both sites
Receiving window When can the receiving site take the freight? Receiving site
Paperwork BOL, packing list and order number on every load? Shipping site
Returnables How are racks, totes or pallets tracked both ways? Both sites
Late notice How early must the receiving site hear about a delay? Logistics
Receiving check Who confirms what arrived and reports shortages? Receiving site
Invoice check Is each invoice checked against the rate and POD? Finance
Cost allocation Which site or cost center pays for each kind of transfer? Finance
Review How often are rates, models and late loads reviewed? Logistics

Common mistakes

Treating the lane as "set." A lane with no review becomes a lane with an old rate and no backup. Put a date on the next review.

Skipping the paperwork because "it's our own freight." A missing packing list means the receiving site cannot check the load. Shortages turn into inventory mysteries.

No backup carrier. When the main carrier cannot cover a load, someone scrambles. A ranked list of approved carriers on each transfer lane removes the scramble.

Letting each site book its own way. Two sites using different carriers, rates and rules on the same lane is a sign nobody owns it. The guide on managing freight across multiple warehouses or plants covers which rules should be shared and which can stay local.

Paying invoices without the POD. Transfer invoices often get approved on trust. Check them like any other invoice.

What one record per load looks like

For each transfer, the shipping site, the receiving site and finance should see the same shipment: the order, the carrier, the rate confirmation, the pickup and delivery times, the documents, the POD and the invoice. When the receiving site asks "where is it?", and finance asks "what did it cost?", they should get the same answer from the same record, not two different answers from two different inboxes.

How does Wilson, by Cartage, manage freight between a company's own sites?

Wilson, by Cartage, is an AI logistics agent that runs transfer freight between a company's plants and warehouses with the same rules it uses for customer freight: it quotes, books, tracks, audits and pays each load and keeps it on one record. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.

Wilson works as a free logistics department, built on four parts.

The labor. Wilson does the labor from the first quote to the final POD. Transfer orders reach Wilson by email, an ERP connection or CSV/XLSX files. Wilson requests quotes from the company's approved carriers or confirms the agreed rate, compares options on total cost and books from the ranked list of approved carriers for that lane. It collects written acceptance and a rate confirmation, generates the BOL and packing list, and schedules the pickup. If an order is missing a detail, Wilson holds it, asks for the missing detail and tells the team; it never invents the value. During transit, it tracks the load and tells the receiving site if the freight will be late. It follows up with carriers by phone and email until it gets an answer, and with people on the company's own team in the channel they normally use.

The data. Wilson keeps the data on record as it works: every order, load, quote, rate, document and contact, connected to the company's ERP. The shipping site, the receiving site and finance see the same shipment. 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. Wilson can produce carrier-performance and lane-rate reports on request from the loads it runs, which makes the yearly lane review a request rather than a project.

The network. Wilson gives access to the network: the shipper's volume counts with every other Wilson customer's, which helps get better rates on every lane, including transfer lanes that have run on an old rate for years. The network includes carriers and brokers. The company still approves who hauls its freight, and it can keep its own carriers on any lane.

The payments. Wilson handles the payments. It requests and files the POD, then audits each carrier invoice against the rate confirmation and the POD before money moves. Invoices over the rate or outside the rules are held and flagged for a person. Payments that pass go out from the Wilson Wallet. The cost stays on the load, so finance can post it to the right site.

Control stays with the company. Wilson starts with assisted execution, the company sets the approval limits and routine actions run automatically within those rules as the workflow is proven. The company also controls the scope: it can start with transfer lanes only, or with one pair of sites. Every message, confirmation and change is kept in the shipment's change history.

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

Can Wilson manage freight between our own plants and warehouses?

Wilson, by Cartage, an AI logistics agent, runs transfer freight between a company's sites the same way it runs customer freight. It quotes or confirms the agreed rate with approved carriers, books, tracks, requests the POD and audits the invoice before paying. Every load stays on one record connected to the ERP.

Should transfers between our own sites have a BOL?

Yes. A BOL and a packing list let the receiving site check what arrived and give the company a record if freight is short or damaged. Include the transfer order number so the load matches the ERP.

Who should pay for transfer freight?

Decide by rule. Common choices are the shipping site, the receiving site, the product line or the site that caused an extra transfer. Put the cost code on the load at booking so finance does not have to guess later.

Is a dedicated truck cheaper for transfers?

It can be, when volume is high and steady on a short lane with a round trip. When volume drops or swings, a dedicated truck can sit idle. Compare it with scheduled loads from approved carriers before deciding.

How often should we review transfer lane rates?

At least once a year, and whenever volume or sites change. Lanes that run on one carrier without review tend to keep old rates long after the market has moved.

What if the main transfer carrier cannot cover a load?

Keep a ranked list of approved carriers on each transfer lane. When the first carrier declines, the next one on the list is asked. Wilson works from that ranked list and books only carriers the company has approved.

How do we stop late transfers from stopping production?

Track each transfer to the time the receiving site needs it, not just to pickup. Tell the receiving site early when a load will be late so it can adjust its schedule. Look at the reasons for late transfers each quarter.

Can Wilson start with transfer lanes only?

Yes. The company controls the scope and can start with a subset of shipments, such as one pair of sites or only transfer lanes. Most teams start on a few lanes and expand from there.

What should the receiving site check on a transfer?

It should check the count and condition against the packing list and BOL, sign the POD with any shortage or damage noted, and report problems within an agreed time. Those notes are the evidence if the carrier is responsible.

Sources

Let's review your transfer lanes between sites. You don't need to prepare anything: Cartage maps the workflow with you on the call.

Add Cartage as a preferred source on Google