Our logistics team switches between email, the ERP, carrier websites and spreadsheets all day. How do we cut the tools?

AI logistics agent vs. traditional TMS guideNov 17, 202617 min read

Short answer

Start by mapping every tool your team opens for one load, from order to paid invoice. Most switches happen because the same facts live in many places. Pick one shipment record that holds the order, quotes, carrier messages, documents and invoice. Then remove the copy-paste steps one at a time. Wilson, by Cartage, an AI logistics agent, keeps that one record as it works and connects it to your ERP.

Book 15 minutes with the team →

How do we cut the number of tools our logistics team switches between?

It is 10:15 on a Tuesday. A logistics coordinator at a manufacturer gets a new order in the ERP. She copies the ship-to address and pallet count into an email to three carriers. Two quotes come back in the inbox, and one carrier asks her to use its website. She opens the website, logs in and types the same details again. She books the cheapest carrier by email, then types the PRO number into a spreadsheet so the team can see it. The next day, sales asks where the load is. She opens the spreadsheet, then the carrier website, then her email, and finds that the pickup slipped. Nobody updated the ERP.

Cut the tools by mapping every switch your team makes on one load, then moving the work onto one shipment record that holds the order, quotes, booking, messages, documents and invoice, connected to your ERP. The goal is not to delete email or the ERP. Those will stay. The goal is to stop copying the same facts between them by hand.

Most logistics teams did not choose their tool mix. It grew. The ERP holds orders and invoices. Email holds carrier conversations. Carrier websites hold quotes and tracking. A spreadsheet fills the gaps. Each tool does its own job well. The trouble is the space between them, where a person copies, checks and re-checks.

Why the switching costs more than it looks

Each switch is small. Open a tab, find the load, copy a number. But the switches add up across every load, every day. They also cause three problems that are worse than lost time:

  • Mistakes. A pallet count typed three times will be wrong once.
  • Stale answers. When the facts live in four places, the one someone checks may be out of date.
  • Single points of failure. When only one person knows which spreadsheet tab tracks which customer, the work stops when that person is out.

What "cutting tools" really means

You will likely keep email, because carriers and customers use it. You will keep the ERP, because finance and sales depend on it. What you can cut is the copying, the second logins and the side spreadsheets. In practice, that means one place where each shipment lives, and work that updates that place as it happens.

Want to see your own switches?

Let's map the tools your team opens for one load. 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.15 minutes with the team behind Wilson. No prep needed.

Book 15 minutes →

How do you map the tools your team uses for one load?

Take one real, recent load and follow it from the order to the paid carrier invoice. At each step, write down the tool, what was copied in or out and who did it. Do this for two or three loads of different types, such as an LTL load, a truckload and a load with a problem.

Step 1: Pick the loads

Choose loads that are normal, not special. One clean load shows the base workflow. One load with a delay or a missing document shows where the switching gets worse. If you ship more than one mode, include one of each.

Step 2: List every step

Use a simple list. For each step, write:

  • What the person was trying to do.
  • Which tool they opened.
  • What they read from it.
  • What they typed into it.
  • Whether the same fact already existed somewhere else.

Step 3: Count the copies

A copy is any time a person moves a fact from one tool to another by hand. Addresses, pallet counts, weights, dates, PRO numbers, rates and appointment times are the usual ones. Count how many times each fact gets copied on one load.

Step 4: Mark the risky steps

Mark any step where a mistake would cost money or a customer. For example: the rate typed into the ERP, the address on the bill of lading or the delivery appointment time sent to the carrier.

Step 5: Mark the one-person steps

Mark any step only one person knows how to do. These are often the most important, because they stop when that person is out.

A hypothetical map

Consider a hypothetical map for the Tuesday load from the opening:

Step Tool What was copied Copy of a fact that already existed?
Read the order ERP Address, pallets, weight, dates No, this is the start
Request quotes Email Address, pallets, weight, dates Yes
Quote on a carrier website Carrier website Address, pallets, weight, dates Yes
Compare quotes Spreadsheet Rates from email and website Yes
Book the carrier Email Load details, agreed rate Yes
Record the booking Spreadsheet Carrier, PRO, pickup date Yes
Create the bill of lading Carrier website or template Address, pallets, weight, class Yes
Track the load Carrier website, email, phone PRO number Yes
Answer sales Spreadsheet, email Status Yes
Get the POD Email PRO number Yes
Enter the freight cost ERP Rate, carrier Yes
Check the invoice Email, spreadsheet, ERP Invoice total, rate Yes

In this example, the address and pallet count are typed four or five times, and the rate three times. Every row after the first is a copy of something the ERP already had.

Where does tool switching hurt most in a normal week?

Tool switching hurts most where a fact changes after it was copied: a new pickup date, a new rate, a new appointment or a new document. The first copy is slow. The update is where things break, because nobody knows every place the old fact went.

When the carrier changes something

A carrier emails at 3 p.m. to say the truck will come tomorrow instead of today. The coordinator reads it in the inbox. Now the new date has to reach the spreadsheet, the warehouse, the customer and, ideally, the ERP. If she updates two of the four, the warehouse still plans a truck that will not come, and the customer still expects the load tomorrow. One change in one tool turns into four switches.

This is the main reason teams feel busy without moving more freight. Most of the day goes to keeping copies in line with each other, not to the freight decisions themselves.

When someone asks a question

Sales asks, "Did the order for this customer ship?" Customer service asks, "When will it deliver?" Finance asks, "Did we get the POD?" Each question sends a person to look across several tools for the latest answer. If two people look in two places, they can give the customer two different answers. That is worse than a slow answer.

A useful exercise: for one week, count the status questions the logistics team gets from inside the company. Note who asked and which tool the answer came from. The count shows how much switching happens for people who do not even do the freight work.

When a person is out

On a normal day, the person who built the spreadsheet knows which tab is current, which carrier answers by phone and which customer needs a call before delivery. When that person is out, the rest of the team switches between even more tools to rebuild what they knew. If the work depends on one person's memory of where things are, the tools are not doing their job.

When the month ends

Finance needs freight costs for the month. Someone goes through the ERP, the spreadsheet and the carrier invoices in email to find what was delivered, what was billed and what was paid. Loads with a changed rate or an extra charge take the longest, because the change lives in an email, not on the order.

How to measure the cost without guessing

You do not need a study. Use three simple counts for two weeks:

What to count How to count it What it tells you
Copies per load Follow three loads and count each fact typed by hand How much work is just moving facts
Status questions per week Tally questions from sales, service, warehouse and finance How much switching happens outside logistics
Fixes per week Count corrections to dates, rates, addresses or documents How often copies go wrong

Write the numbers down before you change anything. Count again a few weeks after the change. Real numbers from your own team are more useful than any general figure, and they help you explain the change to the people who approve it.

What the numbers usually show

Most teams find the same pattern. A small set of facts, such as the address, pallet count, date, rate and PRO number, gets copied many times. A few people answer most of the status questions. And most fixes happen after a carrier changes something. That points straight at what to fix first: the facts that move most, the updates that get missed and the questions that interrupt the team.

Which switches should you remove first?

Remove the switches that happen on every load, that cause mistakes, or that depend on one person. Leave rare edge cases for later. A short list of fixes in the right order does more than a big project that tries to change everything at once.

The switches that usually cost the most

  • Order to quote request. The details on the order get typed into each quote request. This happens on every load and is the first place for mistakes.
  • Quotes from many places. Some quotes come by email, some from websites, some by phone. Comparing them means putting them side by side by hand.
  • Booking to record. After booking, someone types the carrier, PRO number and rate into a spreadsheet or the ERP.
  • Tracking. Checking each carrier's website one by one, or calling, then updating the record.
  • Status questions. Sales and customer service ask the logistics team because they cannot see the record. Each question is a switch for both sides.
  • Documents. The POD arrives in an inbox and has to be saved to the right order.
  • Invoice check. The carrier invoice is compared with an email, a spreadsheet and the ERP.

A simple scoring method

For each switch, ask three questions and give one point for each yes:

  1. Does it happen on most loads?
  2. Has it caused a mistake in the last few months?
  3. Does only one person know how to do it?

Start with the switches that score three, then two. If you need to pick between two, choose the one closest to the start of the load. A mistake at quoting carries through every later step.

Common mistakes when cutting tools

Mistake 1: Adding a dashboard. A screen that pulls data from all your tools can help you see the mess. It does not remove the copying, and someone still has to do the work behind each line.

Mistake 2: Building a bigger spreadsheet. A master spreadsheet feels like one record, but people still copy into it by hand. It becomes one more tool to keep current.

Mistake 3: Replacing the ERP to fix freight. The ERP is rarely the problem. The problem is the freight work around it. Keep the ERP and connect the freight record to it.

Mistake 4: Moving everything at once. A big switch on every lane and every customer at the same time is risky. Start with a few lanes, prove the record works, then add more. For more on this, see how to switch logistics software without disrupting shipping.

Mistake 5: Forgetting the people who ask. Sales, customer service, the warehouse and finance all ask logistics for status. If the new record does not reach them, they keep asking and the switching moves to them.

What a good end state looks like

At the end, each shipment has one record. The record starts from the order. It holds the quotes, the booking, the carrier messages, the tracking, the documents and the invoice. It updates as the work happens, not when someone has time to type. And the facts the ERP needs, such as the carrier and freight cost, flow back where the connection allows it.

What should one shipment record hold?

One shipment record should hold every fact, document and message about a load from the order to the paid invoice, with a history of who changed what and when. Use the checklist below to test any system or process you are considering.

Item on the record Why it matters Test question
Order details The start of every load Does it come from the ERP without retyping?
Quotes from every carrier To compare on total cost Are email, website and phone quotes in one place?
Booking and rate confirmation The agreed price and terms Is the carrier's written acceptance saved?
Pickup and delivery appointments To plan the dock and tell the customer Does a change by the carrier show up on the record?
Carrier messages To know what was said Are emails and call notes on the load, not in one inbox?
Tracking updates To answer "where is it?" Is the last update and its source shown?
Exceptions To act on problems Is the team told, and is the action recorded?
Bill of lading and labels To ship correctly Are they made from the record, not retyped?
POD To prove delivery and bill Is it requested and filed on the load?
Carrier invoice To pay the right amount Is it checked against the rate confirmation and POD?
Payment To close the load Is the payment recorded on the load?
Change history To answer "who changed this?" Can anyone see every change and message?
ERP connection So finance and sales see the same facts Which fields go back to the ERP?

The ERP's role

The ERP stays the place for orders, customers, inventory and invoicing. The shipment record handles the freight work and connects to it. Decide early which facts the freight record reads from the ERP and which ones it should write back. Common write-backs are the carrier, the ship date, the tracking number and the freight cost. What can be written back depends on your ERP and on the scope of the connection.

If carrier emails are the hardest part to tie to orders, see how to connect carrier emails to the right ERP order.

Do you need a TMS to get one record?

Not always. A traditional TMS can hold loads and rates, but someone on your team still does the quoting, booking, follow-up and invoice checks, often switching between the TMS and email. The question to ask is whether the work itself moves to the record, or just the data. For a closer look at what manual handoffs cost on each load, see what manual freight handoffs cost per load.

How to start

Pick the lanes or customers with the most switching. Move them first. After a few weeks, check whether the team still opens the side spreadsheet or the carrier website for those loads. If they do, find out why and fix that step before adding more lanes.

How does Wilson, by Cartage, cut the tools a logistics team switches between?

Wilson, by Cartage, is an AI logistics agent that does the freight work for manufacturers and distributors and keeps the result on one shipment record connected to the company's ERP. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.

Most of the switching in a logistics team comes from people doing the work across tools. Wilson works as the company's logistics department and removes that switching through four parts:

  • The labor. Wilson does the work from the first quote to the final POD. It reads the order, requests quotes from the company's approved carriers by email, API, EDI or phone where configured, compares them on total cost and negotiates toward the company's rate targets within approval limits. Rates outside the limits go to the logistics team. It books with written acceptance and a rate confirmation, schedules the pickup and generates the bill of lading, packing slips and pallet labels. It tracks each load with the best source available for that carrier: carrier API or EDI, GPS or ELD data where the carrier shares it, the carrier's website by PRO number, and email or phone calls when nothing else is current. The team does not log in to each carrier website.
  • The data. Wilson keeps every order, load, quote, rate, document and contact on record as it works. Every message, confirmation and change is kept in the shipment's change history. Wilson replaces the TMS for freight execution and connects to the company's ERP. Write-back to the ERP depends on scope.
  • The network. The shipper's volume counts with every other Wilson customer's to get better rates on each lane. The network includes carriers and brokers, and the company still approves who hauls its freight.
  • The payments. Wilson requests and files the POD, then audits each carrier invoice against the rate confirmation and the POD before money moves. It pays carriers from the Wilson Wallet. Invoices over the rate or outside the rules wait for a person.

Where the team talks to Wilson

The team reaches Wilson where it already works: email, Slack, Microsoft Teams, text, WhatsApp or phone. Orders reach Wilson by email, an ERP connection or CSV or XLSX files. When an order is missing a detail, Wilson does not guess. It holds the order, asks for the missing detail and tells the team. Exceptions such as a missed pickup or a delay go to the team with what Wilson already did: it contacted the carrier and, if configured, the customer, and it can start rebooking from the approved carrier list within the rules or after approval.

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.

Control starts with assisted execution. The company sets the approval limits, and routine actions can run automatically within those rules as the workflow is proven. 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.

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.15 minutes with the team behind Wilson. No prep needed.

Book 15 minutes →

FAQs

Can Wilson replace the tools our team switches between?

Wilson, by Cartage, an AI logistics agent, replaces the TMS for freight execution and connects to the company's ERP. It does the quoting, booking, tracking, document and invoice work, and keeps it all on one shipment record, so the team stops copying between email, carrier websites and spreadsheets. Email and the ERP stay, because carriers, customers and finance still use them.

Why does our team switch between so many tools?

Because each tool holds part of the shipment. Orders sit in the ERP, carrier talks in email, quotes and tracking on carrier websites, and the gaps in a spreadsheet. A person has to move facts between them by hand.

Should we get rid of email for freight?

No. Carriers and customers use email, and that will not change. What you can remove is the need to search inboxes for load details. Messages should be saved on the shipment they belong to.

Is a master spreadsheet a good fix?

It helps for a while, but people still type into it by hand. It becomes one more tool to keep current, and it often depends on one person. A record that updates as the work happens is a better long-term answer.

Do we have to replace our ERP?

Usually not. The ERP keeps orders, customers and invoicing. The freight work connects to it. Decide which facts the freight record reads from the ERP and which ones it writes back.

What should we fix first?

Fix the switch that happens on every load and has caused mistakes. For many teams that is turning the order into quote requests, or tracking across carrier websites. Start close to the beginning of the load, because early mistakes carry through.

How do we know the change worked?

Check whether people still open the side spreadsheet or the carrier website for loads that moved. Count status questions from sales and customer service. Look at how often a fact is wrong on the bill of lading or the invoice.

What about carriers that only work by phone?

Some carriers answer only by phone. The call still needs to end up on the record. Wilson can call carriers where configured, and phone calls are supported in English and Spanish.

Can sales and customer service see the record?

They should, or they will keep asking logistics. Wilson can update the team in Slack, Microsoft Teams or email, and customers by email or SMS where configured. What flows back into the ERP depends on scope.

How long does it take to move to one shipment record?

It depends on how many lanes, carriers and customers you move, and on how the ERP connection is set up. With Wilson, timing depends on scope: most teams start on a few lanes and expand from there. Starting small lets the team check that the record is complete before more loads move onto it, and it keeps the old process in place for everything else in the meantime.

Sources

Let's map the tools your team opens for one load. You don't need to prepare anything: Cartage maps the workflow with you on the call.

Add Cartage as a preferred source on Google