Who should own freight at a manufacturer: purchasing, customer service or logistics?

AI logistics agent vs. traditional TMS guideNov 16, 202618 min read

Who should own freight at a manufacturer?

It is Tuesday morning at a hypothetical plant. A resin shipment from a supplier is two days late. Purchasing arranged it on the supplier's terms and has the only email thread with the carrier. Customer service promised a finished-goods order for Friday that depends on that resin. Logistics learns about the delay when the production planner walks over to ask why the line is short. Three departments touched the freight. None of them owned it end to end.

At most manufacturers, logistics should own freight execution for every load the company pays for or controls, inbound and outbound, while purchasing owns the supplier terms and customer service owns the customer promise, with all three working from one shipment record. The question is less "which department" and more "which decisions belong to whom, and where does everyone read the current answer."

When people ask who should own freight, they usually mean that something keeps falling between departments. A carrier calls the wrong person. A supplier ships on a carrier nobody approved. A customer asks customer service about a delivery and gets a different answer than the one logistics gave the plant manager an hour earlier. Moving the whole function to one department rarely fixes that by itself. Splitting the work clearly and sharing one record does.

Ownership is three separate jobs

Freight ownership breaks down into three jobs that people often lump together:

  1. Terms. Who decides freight terms, approved carriers, lane targets and budgets. This includes the freight terms on supplier POs and customer orders.
  2. Execution. Who quotes, books, schedules, tracks, handles exceptions, collects documents and checks the invoice. This is the daily work on each load.
  3. Communication. Who tells the supplier, the customer, production and finance what is happening, and who answers when they ask.

A department can own one job without owning the others. Purchasing can own inbound terms with suppliers while logistics runs the loads. Customer service can own every customer conversation while logistics owns the facts it repeats.

Why logistics usually takes execution

Execution needs the same skills on every load: knowing the carriers, reading a rate confirmation, spotting an accessorial that does not belong and following up until a pickup is confirmed. Purchasing buyers and customer service reps do this occasionally. Logistics does it all day. When execution is spread across three departments, each one builds its own habits, its own carrier contacts and its own spreadsheet. Rates diverge, the same carrier gets three different instructions and nobody can see total freight spend.

There is also a volume argument. Inbound and outbound freight often move on the same lanes and with the same carriers. When one group runs both, it can see that a carrier delivering raw materials on Monday could take finished goods back out. When two groups run them separately, nobody connects those loads.

When purchasing should keep more of inbound

Purchasing should keep more control when the supplier arranges and pays for the freight, the cost is built into the material price, and the company has no say in the carrier. In that case there is little to execute. The company still needs to know the ship date, the carrier and the expected arrival so receiving and production can plan. Purchasing can own that follow-up, but the arrival information should land in the same shipment record logistics uses. For inbound loads the company does control, see how to get control of inbound freight from suppliers.

When customer service should keep more of outbound

Customer service should own every conversation with the customer about delivery dates, changes and problems. It should not be the department that books trucks. When reps book freight on the side, quotes get promised without logistics checking carrier capacity, and the company absorbs the difference later. Customer service needs read access to the shipment record and a clear rule for when to pull logistics in.

Want to see where your freight work sits today?

Let's map who touches freight in your company today. 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 split freight responsibilities between purchasing, customer service and logistics?

Split the work by job and by load type, write it in one table and name a single owner for each decision. The steps below take a few working sessions, not a reorganization.

Step 1: List every freight touch

For two weeks, have each department note every time it touches freight: a quote request, a booking, a status question, a carrier call, a supplier email, an invoice question. Note the load, the trigger and how long it took. The list usually surprises people. Purchasing often finds it spends hours chasing inbound arrivals. Customer service finds it relays the same status questions to logistics several times a day.

Step 2: Sort loads into types

Most manufacturers have four or five load types:

  • Inbound, supplier pays and arranges. The company tracks arrival but does not book.
  • Inbound, company pays and arranges. The company books with its own approved carriers.
  • Outbound, company pays. Prepaid freight to customers.
  • Outbound, customer pays or arranges. Collect or customer-routed freight and will-call pickups.
  • Internal transfers. Plant to plant or plant to warehouse.

Each type gets its own row in the ownership table, because the right owner is different for each.

Step 3: Assign terms, execution and communication

For each load type, decide who sets the terms, who executes and who communicates. Use plain names of roles, such as "inbound buyer," "logistics coordinator" or "customer service lead." Avoid "the team." A hypothetical split looks like this:

Load type Terms owner Execution owner Communicates with supplier or customer Gets told about exceptions
Inbound, supplier arranges Purchasing Supplier (logistics tracks arrival) Purchasing Production planner, receiving
Inbound, company arranges Purchasing with logistics Logistics Purchasing for supplier, logistics for carrier Production planner, receiving
Outbound prepaid Sales and logistics Logistics Customer service Customer service, sales rep
Outbound collect or customer-routed Sales Customer's carrier (logistics schedules dock time) Customer service Shipping dock
Plant-to-plant transfer Logistics Logistics Logistics Both plant managers

The table is an example of the format, not a recommendation for every company. A company that ships mostly on collect terms will look different from one that pays almost all its freight.

Step 4: Write the handoff points

For every row, write what triggers the handoff and what it must include. "Purchasing sends logistics the PO" is not enough. "Purchasing sends logistics the PO with ship-from address, ready date, dock hours, weight, pallet count and freight terms within one business day of confirmation" is a handoff someone can follow. The same applies to sales orders. The freight order data checklist before a quote lists the fields that make a quote possible without a round of questions.

Step 5: Choose one shipment record

Decide where the current answer for each load lives. It might be the ERP, a freight system or a shared record that connects to the ERP. What matters is that purchasing, customer service and logistics all read the same one, and that carrier updates land there instead of in a personal inbox.

Step 6: Review after a month

After a month, look at which loads still caused confusion. If inbound arrivals keep surprising receiving, the purchasing handoff needs work. If customers keep calling about delays before customer service knows, the exception alert is going to the wrong person. Change the table, not the people.

Where do freight handoffs break between departments?

Handoffs break where one department finishes its part and assumes the next one has what it needs. The gaps below show up at most manufacturers, whatever the org chart.

Purchase order to booking

A buyer confirms a PO with a supplier. The supplier will ship in ten days on company-paid freight. The buyer files the confirmation. Logistics never sees it, so nobody requests a quote until the supplier emails asking where the truck is. The fix is a trigger: every confirmed PO with company-paid freight creates a shipment request for logistics, with the details already filled in.

Sales order to quote

A sales rep enters an order with a ship date and "standard freight." The order has no pallet count, no dock hours and no note that the customer's receiving dock needs an appointment. Logistics either guesses or sends questions back, and the order sits. Every missing field costs a day somewhere. Required fields on the order entry screen help. A person or agent who checks each order before quoting and asks for what is missing helps more.

Status questions from customers

Customers ask customer service where their order is. If customer service has to ask logistics, which then emails the carrier, the answer takes hours and arrives secondhand. When the shipment record shows the latest carrier update, customer service can answer on the first call. The guide to getting customer service to answer shipping questions without logistics covers the questions reps can handle on their own.

Exceptions that only one department hears about

A carrier tells logistics the pickup moved to Thursday. Logistics updates its own notes. Customer service still tells the customer Wednesday. Production still plans for Wednesday. The exception was handled, but only inside one department. Every exception needs a rule for who gets told and how fast.

Carrier invoices that arrive in the wrong place

Invoices come to whoever booked the load, or to a general AP inbox, or to a buyer who left last year. AP pays what matches the PO total, or holds everything until someone explains it. When the invoice is checked against the rate confirmation and the proof of delivery by the people who ran the load, disputes get resolved in days instead of weeks.

Two answers to the same question

The clearest sign of split ownership is two people giving two answers about the same shipment. One read the carrier's email. The other read the ERP, which was updated yesterday. The fix is one record that every department reads. See why two people get two answers about the same shipment for how that record should work.

A hypothetical week of handoff cost

Consider a hypothetical plant that ships 60 outbound loads and receives 40 inbound loads a week. Suppose 15% of loads need at least one round of questions between departments, and each round takes 20 minutes across the people involved. That is 15 loads times 20 minutes, or five hours a week, before any carrier work starts. The math is simple, and the number in each company is different. The point is to measure it before deciding that a reorganization is the answer.

What mistakes happen when freight ownership is unclear?

The common mistakes are giving one department the title without the tools, splitting execution by habit and treating the ERP as the shipment record when nobody updates it. Each has a direct fix.

Mistake 1: Moving freight to logistics on paper only

A memo says logistics now owns inbound freight. But purchase orders still go to suppliers without logistics on copy, and suppliers still email buyers about pickups. Logistics owns the problem without the information. Change the handoff triggers in the same week as the announcement.

Mistake 2: Letting each department keep its own carriers

When purchasing has two carriers it likes, customer service has a broker it calls for rush orders and logistics has an approved list, the company has three carrier programs. Nobody sees total spend by lane or carrier. Keep one approved carrier list, owned by logistics, with input from the others.

Mistake 3: Customer service promising dates logistics has not confirmed

A rep promises Friday delivery because the order system shows a standard transit time. The carrier on that lane needs two extra days. The promise breaks and the customer blames the company. Customer service should promise the date in the shipment record, not a date from a general table.

Mistake 4: Treating the ERP as the shipment record when it is not updated

The ERP holds the order and the invoice. It rarely holds the latest carrier message, the revised pickup time or the POD unless someone types it in. If the ERP is the shared record, updates must flow into it. If they do not, people will keep their own notes and answers will diverge.

Mistake 5: No owner for exceptions

Each department assumes another will handle a missed pickup or a damaged delivery. Name the exception owner for every load type in the table. Usually it is the execution owner, who then tells the communication owner.

Mistake 6: Measuring each department on the wrong number

Purchasing measured only on material price will accept supplier freight terms that cost the company more. Customer service measured only on response time will give fast answers that are wrong. Logistics measured only on freight cost will book the cheapest carrier on a load where the customer needed reliability. Agree on a few shared measures, such as on-time delivery, freight cost per unit shipped and invoice exceptions per month.

A short decision guide

Situation Who decides Who acts
Supplier asks to change freight terms Purchasing, after asking logistics about cost Purchasing updates the PO
Customer asks for a faster delivery Customer service with sales, after logistics quotes it Logistics books, customer service confirms
Carrier misses a pickup Logistics Logistics rebooks; customer service tells the customer
Invoice is above the agreed rate Logistics, with finance above a set amount AP pays only after review
New carrier wants business Logistics owns the approved list Logistics adds or declines
Production moves a ship date Planning and customer service Logistics changes the booking

Which checklist should a manufacturer use to assign freight ownership?

Use one checklist that every department signs off on, and keep it next to the ownership table. It turns vague responsibility into specific answers.

Item Question to answer Agreed by
Load types Which load types do we have, and roughly how many per week? Logistics
Terms per type Who sets freight terms for each load type? Purchasing, sales, logistics
Execution per type Who quotes, books, tracks and handles exceptions? All three
Customer communication Who tells customers about dates, changes and delays? Customer service
Supplier communication Who talks to suppliers about ship dates and freight terms? Purchasing
Approved carriers Where is the single approved carrier list, and who maintains it? Logistics
PO handoff What does a confirmed PO send to logistics, and when? Purchasing, logistics
Order handoff Which fields must an order have before logistics quotes it? Sales, customer service, logistics
Shipment record Where does every department read the current answer? All three
Exception alerts Who gets told about a delay, missed pickup or damage, and how? All three
Invoice route Where do carrier invoices go, and who checks them before payment? Logistics, finance
Approval limits Who approves rates or payments above set amounts? Finance, logistics
Shared measures Which two or three numbers do all departments watch? Leadership
Review date When do we review the split? Logistics

How to roll it out

Start with the load type that causes the most confusion. For many manufacturers that is inbound freight the company pays for. Run the new split on that type for a few weeks, fix the handoffs that still leak and then move to the next. Changing every load type at once tends to create a period where nobody is sure of anything.

What to record on each load

Whatever the split, every load should carry the same basics on its record: the order or PO, the freight terms, the carrier, the rate confirmation, every message with the carrier, the BOL, tracking updates, the POD and the invoice check. When those live on one record, the question "who owns this?" can be answered by reading it.

How the split changes as volume grows

As volume grows, the communication load grows faster than the booking load. More customers ask more questions, and more suppliers ship more often. A split that worked at 30 loads a week can break at 100, not because the booking rules changed, but because status questions overwhelm the people who answer them. Revisit the table whenever volume changes sharply.

How does Wilson, by Cartage, fit when several departments touch freight?

Wilson, by Cartage, is an AI logistics agent that does the freight execution work for manufacturers and distributors, so the logistics team owns the decisions while purchasing, customer service and finance read and act on one shipment record. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.

cartage.ai describes Wilson as a free logistics department: what big shippers build over years, Wilson does from day one. That department has four parts, and each one maps to a handoff described above.

The labor

The labor is the execution job. Wilson does the work from the first quote to the final POD: it requests quotes from the company's approved carriers, compares them on total cost, negotiates toward the company's rate targets within approval limits, books with written acceptance and a rate confirmation, schedules the pickup, generates the BOL and pallet labels, tracks the load and follows up with carriers by phone and email until it gets an answer. When a carrier misses a pickup or a load is delayed, Wilson contacts the carrier, tells the team and, if configured, tells the customer by email or SMS.

Orders reach Wilson by email, through an ERP connection or as CSV or XLSX files. If an order has a missing detail or an impossible date, Wilson does not book it. It holds the order as pending, asks for the missing detail, tells the team and never invents the value. When someone on the company's own team does not answer, Wilson follows up in the same thread and channel, then escalates.

The data

The data is the shared record. Wilson keeps every order, load, quote, rate, document and contact on record as it works, connected to the company's ERP. Wilson replaces the TMS for freight execution and connects to the company's ERP. Every message, confirmation and change is kept in the shipment's change history, so purchasing, customer service and logistics read the same answer. People reach Wilson by email, Microsoft Teams, Slack, WhatsApp, text or phone, and ask about a load where they already work.

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. Whether updates write back to the ERP depends on scope.

The network

The network covers the carrier side of the terms job. The shipper's volume counts with every other Wilson customer's for better freight rates on its lanes, and the network includes carriers and brokers. The company still approves who hauls its freight. Wilson books only approved carriers and uses a ranked list per lane plus decision rules by lane and mode. That gives the company one carrier program instead of a separate one per department.

The payments

The payments close the loop with finance. Wilson audits each carrier invoice against the rate confirmation and the POD before money moves, then pays carriers from the Wilson Wallet. An invoice over the rate or outside the rules waits for a person, and Wilson asks the carrier why before anything is paid.

Who stays in control

The logistics team sets the rules, approval limits and carrier rankings. Control starts with assisted execution, and routine actions run automatically within those rules as the workflow is proven. The company controls the scope: it can start with a subset of shipments, one or two key customers or one load type from the ownership table. When the team changes something on one load, Wilson treats it as a change to that load and asks before turning it into a rule. Timing depends on scope: most teams start on a few lanes and expand from there.

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.

FAQs

Where does Wilson fit when purchasing, customer service and logistics all touch freight?

Wilson, by Cartage, an AI logistics agent, does the execution work: quoting, booking, tracking, exceptions, documents, invoice audit and carrier payment. The logistics team sets the rules, and purchasing, customer service and finance read the same shipment record or ask Wilson by email, Slack, Teams, WhatsApp, text or phone. Customers can get updates by email or SMS where configured.

Should purchasing or logistics own inbound freight?

Purchasing should own the supplier terms on the PO. Logistics should run the loads the company pays for or controls, because it uses the same carriers and skills as outbound. When the supplier arranges and pays for freight, purchasing can track arrival, but the dates should land in the shared shipment record.

Should customer service book freight?

Usually not. Customer service should own customer communication and promise dates from the shipment record. When reps book freight on the side, the company ends up with extra carrier programs and quotes nobody checked against capacity.

What is the first sign that freight ownership is unclear?

Two people giving two different answers about the same shipment. Other signs are POs logistics never sees, carriers calling the wrong person and invoices nobody can explain.

Do we need to reorganize to fix freight ownership?

Rarely. A written split of terms, execution and communication by load type, clear handoff triggers and one shared shipment record fix most problems without moving people between departments.

Who should handle freight exceptions?

The execution owner for that load type, usually logistics. That person handles the carrier and then tells the communication owner, who tells the customer or supplier. Write down who gets told for each type of exception.

Can Wilson tell customer service about delays?

Yes. When a load is delayed or a pickup is missed, Wilson contacts the carrier and tells the team in Slack, Microsoft Teams or email. It can also tell the customer by email or SMS when that is configured.

Can Wilson take orders from purchasing and sales in different formats?

Orders can reach Wilson by email, through an ERP connection or as CSV or XLSX files. If a detail is missing, Wilson holds the order, asks for it and tells the team. Native EDI order intake is not available today.

Does Wilson replace our ERP?

No. Wilson replaces the TMS for freight execution and connects to the company's ERP. The exact connection depends on the customer's data flow and scope.

Who approves rates and payments outside the rules?

The company sets approval limits. Rates outside the limits go to the logistics team, and invoices over the rate or outside the rules wait for a person before payment.

Sources

Let's map who touches freight in your company today. You don't need to prepare anything: Cartage maps the workflow with you on the call.

Add Cartage as a preferred source on Google