We track shipments in a spreadsheet. How do we know we've outgrown it?
Short answer
You have outgrown the spreadsheet when copying data into it takes hours and nobody trusts it. Other signs are many versions and no history of changes. Another is that only one person knows how it works. Move the daily carrier follow-ups out first, then the shipment history. That follow-up work is what Wilson, by Cartage, an AI logistics agent, takes on, starting from your CSV or XLSX order files.
Book 15 minutes with the team →How do we know we've outgrown our shipment tracking spreadsheet?
It is Monday at 8:15 a.m. The logistics coordinator opens the shipment file. There are 64 rows. Twelve have a yellow cell that means "check with carrier." Four have a red cell, but nobody remembers what red means this month. Sales has a copy of the file from Friday. The plant has its own tab. The coordinator who built the file is out today, and the column called "Status 2" is a mystery to everyone else.
A team has outgrown its shipment tracking spreadsheet when keeping the file current takes more time than it saves, and when people stop trusting it enough to act on it. At that point the spreadsheet is not tracking shipments. It is a copy of answers that someone found somewhere else, often by phone or email, and typed in by hand.
Spreadsheets are a good place to start. They are free, flexible and everyone knows how to use them. Many logistics teams run for years on one, and that is not a mistake. The problem starts slowly. Volume grows, more people touch the file, more customers ask for updates and the file turns into a second job.
The five signs
Most teams see the same signs, in about the same order:
- Copy-paste is the main task. People copy order lines from the ERP, tracking numbers from carrier emails and dates from carrier websites into the file. Each copy is a chance to type the wrong number.
- There are many versions. Sales, the plant and finance each keep their own copy, saved on different days. Two people look at the same load and see two answers.
- There is no history. The cell says "delivered," but nobody can see when it changed, who changed it or what it said before. When a customer disputes a date, the file cannot help.
- One person holds it together. One coordinator knows what every color, column and note means. When that person is sick or on vacation, the file goes stale in two days.
- The file does not do anything. It never asks a carrier for an update, never warns that a pickup was missed and never reminds anyone to chase a POD. It only shows what someone typed.
Why the signs matter
Each sign has a cost. Copy-paste mistakes send a truck to the wrong dock or bill a customer the wrong freight. Old versions cause a sales rep to promise a delivery that already slipped. Missing history makes it hard to dispute a detention charge or a late delivery. A single owner is a risk the business carries every day without seeing it.
The fifth sign matters most. A spreadsheet is a passive record. All the work that moves a shipment forward happens outside it: the emails, the calls, the follow-ups, the document requests. The file just stores the result. When the volume of that outside work grows, the team does not need a better spreadsheet. It needs the work done.
What "outgrown" does not mean
Outgrowing a spreadsheet does not mean every column was wrong. It does not mean the team needs a large, complex system with a long setup. And it does not mean the spreadsheet must disappear on day one. Many teams keep a file for a while as a view or a backup. The change is about where the real record lives and who does the work around it.
Let's review your shipment spreadsheet together. 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 move off a shipment spreadsheet without breaking anything?
Move one kind of work at a time, starting with the daily follow-ups, and keep the spreadsheet running beside the new process until the team trusts it. A big switch on a Monday morning is how loads get lost. A step-by-step move lets the team check each part before the next one.
Step 1: Read the spreadsheet as a requirements list
Before changing anything, look at what the file actually holds. Every column exists because someone needed that answer. Write down each column, what it means and who uses it. A typical file has:
- Order or PO number, customer and ship-to address.
- Ready date, pickup date and requested delivery date.
- Carrier, mode, PRO or tracking number.
- Quoted rate and booked rate.
- Status and last update.
- Notes, such as "call before delivery" or "dock closes at 2."
- POD received, invoice received, invoice paid.
This list is valuable. It shows what any new process must keep. If a column has no clear owner or nobody reads it, drop it now.
Step 2: Find where each value comes from
For each column, write down the place the value really comes from. The order number comes from the ERP. The PRO number comes from the carrier's confirmation email. The status comes from the carrier's website, an EDI message or a phone call. The POD comes from the carrier by email.
This step shows how much work hides behind the file. A status column that looks simple may need three sources and a phone call on a busy day. These are the steps to move out of the spreadsheet first.
Step 3: Move the follow-ups first
The follow-ups are the questions someone asks every day: Did the carrier accept? Did the truck show up? Where is the load? Where is the POD? These take the most time and cause the most stale rows. Move them to a process where the follow-up happens on its own schedule and the answer lands on the load record, not in someone's inbox.
Step 4: Move the history
Once follow-ups run on the load record, the history builds itself. Every reply, date change and document is saved with the load. Now when a customer asks "when did you know it would be late?", the answer is on the record with a time and a source. For more on why that history matters, see how one freight record can survive from quote to payment.
Step 5: Move the reports last
Reports are the easiest part to rebuild, because they come from the record. Once the record is complete, a list of open loads, late loads or loads without a POD is a simple filter. Teams often try to rebuild reports first. That is backward: a report built on an incomplete record is just a nicer version of the old spreadsheet.
Step 6: Retire the old file
When the team has worked a few weeks without opening the spreadsheet for real answers, freeze it. Save a copy for the history it holds. Then stop updating it, so nobody trusts an old version by mistake.
What should a shipment record hold once it leaves the spreadsheet?
A shipment record should hold the current answer, where that answer came from, when it changed and every document and message tied to the load. The spreadsheet held only the first of those. The others are what make the record trustworthy.
Current state
The basics are the same as the spreadsheet columns: order, customer, addresses, dates, carrier, mode, reference numbers, rates and status. The difference is that each value has one home. There is no second copy that can drift.
Source and time
Each status should show its source and time. "In transit, per carrier website by PRO, 9:40 a.m." is far more useful than "in transit." The team can see if the answer is fresh or old, and whether it came from the carrier's system, an email or a phone call.
Change history
Every change should be kept, not overwritten. If the pickup date moved from Tuesday to Wednesday, the record should show both dates, who changed it and why. This is the part a spreadsheet almost never does well. A cell has one value. A record can have a timeline.
Documents
The BOL, rate confirmation, POD and carrier invoice should live on the load. In a spreadsheet, these sit in email folders or a shared drive, and the file only says "POD: yes." When finance needs the POD to bill the customer, someone has to search for it.
Messages
Carrier emails, notes from phone calls and updates to the customer belong on the load too. This is what lets a second person pick up the load when the first person is out. It also answers "who told the customer what, and when?" without a search through three inboxes.
Example: one load, before and after
Consider a hypothetical LTL load from a plant to a distributor. In the spreadsheet, the row reads: "PO 44817, Carrier B, PRO 7712039, in transit, ETA Thu." In a shipment record, the same load shows:
| Field | Spreadsheet | Shipment record |
|---|---|---|
| Status | In transit | In transit, from the carrier website by PRO, checked at 9:40 a.m. |
| ETA | Thu | Thursday, moved from Wednesday after a terminal delay, changed at 2:15 p.m. Tuesday |
| Rate | $412 | $412 on the rate confirmation; quote from two other approved carriers kept |
| BOL | (in email) | Attached, with the time it was sent to the carrier |
| POD | No | Requested Thursday 4:00 p.m., follow-up set for Friday morning |
| Customer update | (unknown) | Email sent Tuesday 2:30 p.m. with the new ETA |
The row in the spreadsheet is not wrong. It is just thin. The record holds the answer to the next question, and the one after that.
Where the record lives
The record can live in a TMS, in an ERP add-on or in an AI logistics agent that keeps it as it works. The right choice depends on who does the work. If people still do every follow-up by hand, a new system becomes another place they have to type into. If the follow-ups are done for them, the record fills itself. That is the difference to test. The guide on one shipment record when two people get different answers looks at the same problem from the team's side.
What mistakes do teams make when they leave the spreadsheet?
The common mistakes are moving the file without moving the work, rebuilding every column, switching all at once and keeping two records alive. Each one makes the new process feel worse than the old one.
Mistake 1: Moving the file but not the work
Some teams move their spreadsheet into a new tool and call it done. The columns are the same, the copy-paste is the same, and people still call carriers for every update. The new tool is just a nicer screen. Ask a simple question of any option: who asks the carrier for the update? If the answer is still "the coordinator," the main problem has not moved.
Mistake 2: Rebuilding every column
Old spreadsheets collect columns nobody uses. "Status 2," "Old ETA" and "Check?" were useful once. Copying all of them into a new process adds noise. Use the list from Step 1 and keep only what someone reads and acts on.
Mistake 3: Switching everything on one day
A full switch on one day means every load, every carrier and every customer changes at once. If something breaks, it breaks everywhere. Start with a few lanes or one customer, check the results and then add more.
Mistake 4: Keeping two records alive for too long
Running the old and new side by side for a few weeks is smart. Running both for months is not. People pick the one they trust, and it may not be the new one. Set an end date for the old file and stick to it.
Mistake 5: Forgetting the people who read the file
Sales, the plant, customer service and finance all used the spreadsheet, even if they never edited it. If the new record does not reach them, they will ask logistics, and the interruptions will grow. Decide early how each group gets its answers: a message at each milestone, a shared view or a short list each morning.
Mistake 6: Treating the spreadsheet owner as the problem
The person who built the file usually kept the team running for years. Their knowledge of carriers, customers and odd rules is the most useful input to the new process. Ask them to write down the rules the colors and notes stand for. Those rules should become settings the whole team can see and change.
When a spreadsheet is still fine
Not every team needs to move today. A spreadsheet can still work when:
- One person handles all loads, and volume is low enough to update by hand without falling behind.
- Few people outside logistics need shipment answers.
- Customers rarely ask for documents or history.
- Disputes about dates, charges or delivery are rare.
When two or more of these stop being true, start planning the move.
Which checklist shows whether your spreadsheet is outgrown?
Score your spreadsheet against the checklist below. Each "yes" is a sign the file is costing more than it saves. The questions are simple on purpose. A team can answer them in 15 minutes.
| Question | Yes means |
|---|---|
| Does someone spend more than an hour a day copying data into the file? | Copy-paste is now a job, not a task |
| Are there two or more copies of the file in use? | People will get different answers |
| Can you see who changed a status and when? | If no, disputes have no record |
| Would the file go stale if one person were out for a week? | The process depends on one person |
| Do people still call or email carriers to check what the file says? | The file is not trusted |
| Do sales or customer service ask logistics for status every day? | The file does not reach the people who need it |
| Are BOLs, PODs and invoices stored somewhere else? | Documents are separate from the load |
| Has a wrong value in the file caused a missed pickup or a wrong bill? | Copy mistakes are already costing money |
| Is the file too large or slow to open easily? | Volume has outgrown the format |
| Does month-end take a day of matching the file to invoices? | Finance is rebuilding the history by hand |
How to read the score
- 0 to 2 yes answers: The spreadsheet still fits. Clean up unused columns and write down what each one means.
- 3 to 5 yes answers: The file is starting to cost time and trust. Plan to move the follow-ups first.
- 6 or more yes answers: The team is already working around the file. Move the follow-ups and the history soon, starting with the busiest lanes.
These ranges are a rule of thumb, not a standard. The point is to see the cost clearly enough to make a decision.
What to measure before and after
Pick a few simple numbers before the move, so the team can see if things got better:
| Measure | How to count it |
|---|---|
| Time spent updating the file | Ask the team to log it for one normal week |
| Status questions from other teams | Count emails and messages asking "where is it?" for one week |
| Loads without a POD after five days | Count from the file or from finance |
| Wrong values found | Count fixes made to the file in one week |
| Time to answer a customer question | Time a few real questions from ask to answer |
Measure again a few weeks after the move. If the numbers did not change, the work did not really move.
What to keep from the spreadsheet
Keep the column list, the notes about customers and the rules hidden in colors. Keep a frozen copy of the file for history. Do not keep the habit of typing answers in by hand once the new record fills itself.
How does Wilson, by Cartage, help a team that has outgrown its shipment spreadsheet?
Wilson, by Cartage, is an AI logistics agent that does the work the spreadsheet only recorded: it quotes, books, tracks and follows up on each load, and keeps the full record as it goes. Traditional logistics software gives teams information. Wilson executes the work required to move shipments forward.
Wilson works as a free logistics department in four parts.
The labor
The labor is the work that kept the coordinator updating rows all day. Wilson does it from the first quote to the final POD. Orders reach Wilson by email, through an ERP connection or as CSV or XLSX files, so a team can start from the spreadsheet it already exports. If an order has a missing detail or an impossible date, Wilson does not guess. It holds the order as pending, asks for the missing detail and tells the team.
Wilson requests quotes from the company's approved carriers, compares them on total cost and negotiates toward the company's rate targets within approval limits. It books with written acceptance and a rate confirmation, schedules the pickup and creates the BOL. It tracks each load with the best source available: a 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. It follows up with carriers by phone and email until it gets an answer, and it requests and files the POD.
The data
The data is what the spreadsheet tried to be. Wilson keeps every order, load, quote, rate, document and contact on record as it works, connected to the company's ERP. Every message, confirmation and change is kept in the shipment's change history, so the team can see what changed, when and from which source. 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. Write-back to the ERP depends on scope.
The team reaches Wilson in Slack, Microsoft Teams, email or text, so sales and the plant can get answers from the record without asking logistics for a copy of the file. Wilson can produce carrier-performance and lane-rate reports on request from the loads it runs.
The network
The network gives the shipper better freight rates on every lane, because its volume counts with every other Wilson customer's. The network includes carriers and brokers. The company still approves who hauls its freight, and Wilson books only carriers the company has approved.
The payments
The payments close the loop that the spreadsheet tracked with a "paid" column. Wilson audits each carrier invoice against the rate confirmation and the POD before money moves, then pays carriers from the Wilson Wallet. Invoices over the rate or outside the rules wait for a person.
Control
Control starts with assisted execution. The company sets approval limits, 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 or one or two key customers. 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 work from our shipment spreadsheet?
Wilson, by Cartage, an AI logistics agent, can take orders as CSV or XLSX files, as well as by email or through an ERP connection. From there it quotes, books and tracks each load and keeps the record on the shipment. The team can keep its spreadsheet as a backup while it checks the new process.
What is the first sign a shipment spreadsheet is outgrown?
Usually it is time. When someone spends a large part of the day copying data into the file, the file has become a job. The second sign is trust: people call carriers to check what the file says.
Should we move to a better spreadsheet first?
A better spreadsheet can help with layout and formulas. It does not ask carriers for updates, chase PODs or keep a history of changes. If those are the problems, a new file will not fix them.
What should move out of the spreadsheet first?
The daily follow-ups: carrier acceptance, pickup confirmation, tracking updates and POD requests. They take the most time and cause the most stale rows. History and reports can move after.
How long should we keep the old spreadsheet?
Keep it running beside the new process for a few weeks, then freeze it. Save a copy for the history it holds. Running two live records for months leads people to trust the wrong one.
Does Wilson need a TMS to replace our spreadsheet?
No. Wilson replaces the TMS for freight execution and connects to the company's ERP. It keeps every load, rate and document on record as it works.
Can sales see shipment status without the spreadsheet?
Yes, if the record reaches them. Wilson updates the team in Slack, Microsoft Teams or email at milestones, and people can ask Wilson about a load in the same channels.
What happens to the notes and color codes in our file?
They are rules the team has been following by habit. Write them down. In Wilson, they can become rules and preferences the team can see and edit, such as a dock that only takes appointments in the morning.
Can Wilson send us a list of open loads like our spreadsheet did?
Wilson can produce carrier-performance and lane-rate reports on request from the loads it runs, and every record is searchable and exportable with its change history. The exact format of a daily list depends on the setup.
Do we have to move every load at once?
No. The company controls the scope. Most teams start on a few lanes or one or two customers and expand from there.
Sources
- Cartage, Wilson product FAQ and product scope, October 2026: https://cartage.ai
Let's review your shipment spreadsheet together. You don't need to prepare anything: Cartage maps the workflow with you on the call.
