Spreadsheet vs. system in foreign trade: the complete guide
When the follow-up spreadsheet becomes a bottleneck, how to spot the 5 signs, why migrating seems bigger than it is and how to structure the transition without stopping the operation.
The follow-up spreadsheet was born to solve a real problem: giving visibility into what was happening. It worked for years. The problem is that it grew along with the operation (more tabs, more macros, more people feeding it) until it became the operation itself. When the analyst who “knows where everything is” goes on vacation, the operation grinds to a halt.
That isn’t a spreadsheet problem. It’s a model problem: the information lives in people, not in the process. And when the information lives in people, the operation scales with them, not with the volume.
FollowNet One is e.Mix’s foreign trade software for importers, exporters, manufacturers and freight forwarders: it centralizes events, documents and alerts so the information comes to the analyst, instead of the analyst going to look for it. This guide explains when the spreadsheet becomes a bottleneck, why migrating seems bigger than it is, and how to structure the transition without trauma and without an endless project.
- → The problem: the spreadsheet shows everything with the same weight, and depends on someone to keep it up to date
- → The cost and risk: decisions based on outdated data, an operation stalled while an analyst is on vacation and demurrage invisible until the invoice arrives
- → The mechanism: centralized events + automatic alerts + information that reaches the analyst without follow-up
- → How to start: one trade lane, one spreadsheet, a 2-week migration without stopping the operation
When the spreadsheet stops working
The spreadsheet doesn’t break overnight. It gradually stops working, and the operation adapts to each new limitation without noticing the accumulated cost.
Five signs that the spreadsheet has become a bottleneck:
- The most experienced analyst is the only one who “knows where everything is”. When they go on vacation or leave the company, the knowledge goes with them. The operation doesn’t fail; it slows down until someone learns where things are.
- The S&OP meeting starts with status updates. The first 20 minutes are spent asking “how is shipment X going?” instead of deciding on the shipments that need action. The spreadsheet doesn’t answer in real time; it answers as of the moment it was last updated.
- The team spends more time feeding it than managing. Every new column, every extra field, every added tab means more manual updating. When filling in the spreadsheet becomes the priority, it has stopped being a management tool.
- Two analysts have different versions of the same shipment. The spreadsheet has no native version control. Whoever saved last has the “right version”, and nobody knows which is which.
- Demurrage shows up on the invoice, not before. The spreadsheet shows what was typed in. If the free time wasn’t calculated and recorded, it doesn’t show up. The system calculates it automatically and alerts you before it expires.
| Dimension | Spreadsheet | System (FollowNet One) |
|---|---|---|
| How information arrives | The analyst goes looking for it | The information comes to the analyst |
| Updating | Manual: depends on whoever fills it in | Automatic: events recorded in the system |
| Deviation alerts | None: the analyst has to notice | Automatic: before the impact |
| Dependence on people | High: whoever knows how to use it controls it | Low: the process lives in the system |
| Scaling with volume | Linear: more shipments, more spreadsheet time | Sub-linear: alerts absorb the growth |
| Manager’s visibility | Depends on what was typed in | Real-time dashboard |
Why migrating seems bigger than it is
The most common fear among those considering a migration is: “we’ll lose what works today”. That fear is legitimate, but it rests on a wrong premise: that the current spreadsheet is working well and that any change is a risk.
The spreadsheet works despite the problems it causes, not because of its virtues. Migration doesn’t replace the spreadsheet; it removes the need for it to exist, because the system starts doing what the spreadsheet tried to do, but with reliable data and automatic alerts.
Three common objections and what lies behind them:
- “Our spreadsheet has years of configuration.” The time invested in the spreadsheet is real. But so is the maintenance cost; it just doesn’t show up as a line in the budget. Configuring the system doesn’t start from scratch: it starts with what the spreadsheet already does and evolves from there.
- “We’ll have two systems at the same time during the transition.” Yes, for a few weeks. But the transition happens by trade lane, not by the entire operation. One lane migrates, works, earns trust and expands. It’s never everything at once.
- “The ERP should already solve this.” The ERP records what happened. FollowNet One alerts you to what is about to happen. They’re complementary; one doesn’t replace the other.
Proof from the field: from spreadsheet to system
Before: Manual follow-up, Excel spreadsheets, the whole morning spent finding out how the shipments were going, and an avalanche of information with no triage.
After: Instead of chasing the information, the information comes in. The system alerts whoever needs to act, in the right chain, with automatic escalation. Time recovered, risk eliminated.
Edmilson Sala, Customs Clearance Supervisor, GEODIS
Video (in Portuguese): https://www.youtube.com/watch?v=2Eu_Oeo0wSU&t=44s
How FollowNet One replaces the follow-up spreadsheet
FollowNet One isn’t a more sophisticated spreadsheet. It’s a different model of how information flows: instead of the analyst checking the status of each shipment, the system monitors every shipment and calls on the analyst when something goes off standard.
In practice: the analyst opens the exception dashboard, not the list of 200 shipments. Those within the standard stay green and need no action. Those with a yellow or red light reach the analyst with context: what happened, what the risk is and who the owner is.
If your team still starts the day checking a spreadsheet to find out what needs attention, the information is still in the spreadsheet, not in the process. See how FollowNet One works for importers:
How to migrate without trauma and without an endless project
Owner: Foreign Trade Manager or Coordinator, responsible for choosing the first trade lane to migrate and making sure events are being recorded in the system, not in the spreadsheet.
Cadence: daily in the first 2 weeks, reviewing the migrated lane’s exception dashboard to confirm the alerts are calibrated; weekly afterwards, reviewing KPIs and expanding to the next lane.
Traffic-light KPI: number of manual updates in the old spreadsheet, with a target of zero on the migrated lane by the end of the first month. If the spreadsheet is still being filled in, the migration isn’t finished.
First scope: the spreadsheet with the most tabs, the most people feeding it or the most complaints about outdated data. That’s the one that hurts most, and the one with the biggest impact once migrated.
Learn more
Questions & Answers
When does the follow-up spreadsheet become a bottleneck in foreign trade?
The spreadsheet becomes a bottleneck when knowledge of where things are is concentrated in one person, when the S&OP meeting starts with status updates, when two analysts have different versions of the same shipment or when demurrage only shows up on the invoice, because nobody calculated the free time in the spreadsheet. FollowNet One removes these points by centralizing events and sending automatic alerts before the impact.
Why doesn't the ERP replace the follow-up spreadsheet in foreign trade?
The ERP records what happened: invoice issued, payment posted, inventory updated. The follow-up spreadsheet monitors what is happening now: updated ETA, pending document, assigned channel. FollowNet One does this with automatic alerts. They're complementary systems: the ERP records the result, FollowNet One monitors the process.
How do you migrate from the spreadsheet to the system without stopping the operation?
By trade lane, not by the entire operation. The first step is to pick the spreadsheet with the most problems: the most tabs, the most people feeding it or the most outdated data. That lane migrates in 2 weeks. It works, earns trust and expands to the next one. The operation never stops, because the system runs in parallel until the lane is calibrated.
Does FollowNet One completely replace the spreadsheet?
For controlling import and export shipments, yes. FollowNet One centralizes events, documents, alerts and history for every shipment, which is what the spreadsheet tried to do, with the difference that the information comes to the analyst instead of the analyst going to look for it. Spreadsheets for financial analysis or specific reports can coexist, fed by the system's data.
How long does it take to replace the spreadsheet with FollowNet One?
The first trade lane is operational in 2 weeks. The return shows up in the first month: less follow-up time, fewer status emails, fewer demurrage surprises. The full operation migrates progressively, lane by lane, with no abrupt cutover date.
What is the escalation model in FollowNet One?
Escalation is a chain-of-responsibility logic: if the analyst doesn't handle an exception within the deadline, the system automatically escalates it to the supervisor. If the supervisor doesn't act, it escalates to the manager. Each level has a configurable SLA. Instead of the manager chasing the team, the system does the chasing, and records the history of each escalation.
How does FollowNet One alert you to events without the analyst checking the spreadsheet?
The system monitors every active shipment against the alert criteria configured for each trade lane. When an event doesn't arrive on time (booking not confirmed, DI not registered, free time about to expire), the traffic light changes automatically. The analyst opens the dashboard and sees only what needs action, without going through the list of every shipment.
Can years of spreadsheet history be migrated to the system?
The history of completed shipments can be migrated through a structured import: FollowNet One has a data load module that accepts Excel spreadsheets in the mapped format. The focus of the migration is the active shipments: as soon as the lane is configured, new shipments go straight into the system and the active ones are transferred progressively.
Does the spreadsheet still have value once the system is live?
For shipment follow-up, no. The system replaces it completely. For specific analyses (one-off extractions, financial cross-checks, customized executive reports), the system generates the data that feeds the spreadsheet. The difference is that the spreadsheet stops being the primary source and becomes an output of the system's data.
How do you convince the team to adopt the system instead of the spreadsheet?
By starting with the biggest pain point, not the entire operation. When the most problematic trade lane works in the system, the team itself starts asking for the others to be migrated. Resistance drops when the alternative is better, not when someone decrees a change. FollowNet One was designed to be adopted progressively for exactly this reason.
How to migrate from spreadsheets to a system in foreign trade
A practical guide to moving away from manual spreadsheet control and setting up event-based management, automatic alerts and real-time visibility. Applies to importers, manufacturers, freight forwarders and customs brokerage firms running their operation on follow-up spreadsheets.
- 1
Step 1: Identify the most critical spreadsheet
Pick the spreadsheet with the most tabs, the most people feeding it or the longest history of outdated data. That's the one that costs the operation the most and has the biggest impact once migrated. Don't start with the simplest one; start with the one that hurts most.
- 2
Step 2: Map the events the spreadsheet controls
List the milestones the spreadsheet records: shipment confirmation, vessel arrival, file opening, channel, release, pickup. For each event, identify who fills it in, when and from which source of information. This mapping is the basis for the configuration in the system.
- 3
Step 3: Configure the trade lane in the system in parallel
For 2 weeks, the migrated lane runs in both places: spreadsheet and system. The goal is to calibrate, confirming that events arrive at the right time and that the alerts make operational sense. After calibration, the spreadsheet stops being fed for that lane.
- 4
Step 4: Declare the spreadsheet closed for that lane
Once the system is calibrated, set the cutover date: from that day on, the lane is managed only in the system. Any update to the old spreadsheet is a sign that someone doesn't trust the system, and that's the point to investigate, not ignore.
- 5
Step 5: Expand lane by lane
After the first lane has stabilized, repeat the process for the next one. Use the alert and exception history of the previous lane to calibrate the new one with more precise criteria from the start. The full migration takes months, not weeks, and without a single day of the operation stopped.
FollowNet One reverses the flow: information reaches the analyst before the problem turns into cost, with no spreadsheet, no manual follow-up and no dependence on whoever knows where everything is. Request a 30-minute demo.
Does your team still start the day checking a spreadsheet to see what's late?
Request a demoLearn about FollowNet One or see all our foreign trade software