A logistics company can have an ERP, a TMS, a WMS, customer portals, carrier platforms and several other systems, and still run a surprising amount of the actual operation manually.
The problem is often not the absence of software. It is what happens between the systems.
Someone copies information from an email into an application. Someone checks three sources before answering a customer. Someone maintains an Excel file that everyone depends on. Someone calls a colleague because the information in the system is not enough to make a decision.
Individually, these things look small. Together, they can affect response time, margins, customer experience and the company's ability to scale.
This is not a marginal issue in the industry. In Descartes' 2025 study of freight forwarders and customs brokers, manual processes were identified as the top growth inhibitor by 25% of respondents, ahead of IT resource constraints.
So rather than asking whether a logistics company is “digital”, there is a more useful question:
Where are people still acting as the integration layer between systems?
Here are ten signs worth looking for.
01Customers wait too long for a quote, and sometimes buy elsewhere before you answer
This may be one of the most expensive manual workflows because the cost is not only operational. It can cost revenue.
A request for quotation arrives. Before the commercial team can answer, somebody may need to check the route, understand the requirements, find available capacity, obtain carrier prices, look at previous shipments, calculate margins, validate surcharges or special conditions and perhaps get an approval.
The company may already possess most of this information. The problem is that it sits in different places.
- Part of it is in the TMS.
- Part of it may be in the ERP or CRM.
- Some rates arrive through email.
- Some are available through carrier portals.
- Some commercial rules are in Excel.
- Others are simply known by experienced people.
And while all of this is being assembled, the customer is waiting.
Very often, the customer isn't waiting only for you. They have asked several providers for a quote. That changes the nature of the problem.
A quotation workflow that takes too long isn't simply an administrative inefficiency. It is a commercial bottleneck created by an operational workflow. You may have a competitive price, available capacity and a strong relationship with the customer, and still lose the opportunity because somebody else managed to answer first.
02The same information is entered more than once
An order arrives by email, EDI, customer portal or spreadsheet. Somebody puts it into one system. Then part of the same information is copied into another. Perhaps another colleague adds it to a planning sheet. Later, somebody updates the customer separately.
None of these actions feels particularly expensive. That is why they survive for years. But when the same process happens hundreds or thousands of times, skilled employees gradually become human middleware between applications.
The bigger problem is not even the time spent typing. Every manual transfer also creates another opportunity for incorrect quantities, addresses, reference numbers, dates or customer instructions.
03Exceptions are managed through calls, emails or messaging groups
A standard shipment is usually the easy part of logistics. The real process becomes visible when something goes wrong.
- A vehicle is late.
- A delivery slot changes.
- Capacity disappears.
- Documents are missing.
- The consignee cannot receive the shipment.
- A customer changes the requirements at the last moment.
If the response consists of somebody noticing the problem, calling another person, sending a message, forwarding an email and then remembering to follow up later, there isn't really an exception-management workflow. There is an experienced team compensating for its absence.
And good teams can compensate for weak processes for a surprisingly long time. That can make the problem difficult for management to see.
04Answering “Where is this shipment?” requires asking someone
A customer asks for an update. Sales asks operations. Operations checks the TMS. Then perhaps a telematics system. Then perhaps a carrier portal. Maybe somebody calls the driver or subcontractor. Eventually the customer receives an answer.
Technically, the company has the information. Operationally, it doesn't have visibility. That distinction matters.
Zebra's warehousing research found that 82% of warehouse decision-makers agreed that improvements in operational visibility can lead to better staff and asset utilization.
Good visibility is not simply having another dashboard. It means that the people who need an operational answer can obtain it without starting an investigation.
05There is an Excel file everyone is afraid to touch
There is nothing inherently wrong with Excel. It is probably one of the most useful business tools ever created. The warning sign is something else: the spreadsheet contains operational logic that exists nowhere else.
- Perhaps it determines which carrier should receive a shipment.
- Maybe it contains customer-specific pricing logic.
- Maybe it tracks capacity.
- Maybe it is the real dispatching system.
Or perhaps one person has built formulas and macros over several years that nobody else fully understands.
If losing that file, or the colleague who maintains it, would disrupt the operation, it is no longer just a spreadsheet. It has become part of the company's operational software architecture. It just isn't treated as such.
06Managers spend the first part of the day assembling reality
Export one report. Download another. Check yesterday's emails. Compare two spreadsheets. Call operations. Ask what actually happened. Adjust the numbers. Then start making decisions.
Companies often describe this as a reporting problem. Frequently it isn't. The reports may be perfectly correct. The problem is that no individual system represents the operational reality that management needs to see. The information exists, but it is fragmented across tools, teams and formats.
The result is that managers spend valuable time creating the view of the business before they can actually manage the business.
07Proof of delivery triggers another chain of manual work
Physically delivering the shipment should represent the end of one process. From an information perspective, it often starts another.
- Find the POD.
- Verify it.
- Associate it with the shipment.
- Upload it somewhere.
- Notify the customer.
- Update another system.
- Release the shipment for invoicing.
- Handle discrepancies.
- Archive the documentation.
None of these activities individually looks transformative enough to justify a major software project. But that is exactly why this kind of work is interesting. A relatively small amount of repetitive administrative effort, multiplied by thousands of transactions, can become a material cost.
08KPI reports require “data archaeology”
Ask a few seemingly simple questions:
- Which customers create the most operational exceptions?
- Which routes systematically lose margin?
- Which carriers generate the most problems?
- How many shipments required manual intervention last month?
- Where are people spending the most operational time?
- Which customer processes have become increasingly expensive to support?
In many organizations, answering these questions requires exporting data from several systems and reconstructing the story manually. The company has data. What it doesn't necessarily have is information that can be used easily for operational decisions.
That makes improvement difficult as well. You cannot reliably automate or optimize a process if it is difficult to understand what is actually happening inside it.
09Every new customer adds another special procedure
A new customer signs. Then come the adaptations.
- A particular Excel template.
- Different labels.
- A special document.
- Another email notification.
- A custom reporting format.
- A different booking procedure.
- A specific invoicing requirement.
- One more piece of knowledge someone needs to remember.
Customization can be an important competitive advantage in logistics. Descartes' 2025 research found tailored services becoming an increasingly important differentiator among freight forwarders and customs brokers.
But there is a significant difference between offering customized services and accumulating dozens of manual processes. One can differentiate the company. The other eventually makes growth increasingly expensive.
10Growing the business requires growing administrative headcount at almost the same rate
Shipment volume increases. So does the coordination team. More orders mean more copying. More customers mean more emails. More shipments mean more status checks. More documents mean more people processing documents.
Some operational work will naturally grow together with the business. But if transaction volume and administrative effort remain almost directly coupled, technology isn't creating much operating leverage. And that becomes especially relevant when margins are under pressure.
Before you reach for AI
The next stage of logistics technology will make this distinction even more important. DHL's September 2026 Logistics Trend Radar describes AI moving beyond simply providing information toward systems capable of planning, coordinating and acting across logistics processes, while still operating alongside human expertise and oversight.
That opens some very interesting possibilities. But be careful about jumping directly to “We need AI.” AI cannot magically repair a process nobody properly understands. And adding another platform on top of fragmented systems can sometimes make the situation worse rather than better.
So where should a logistics company start?
Probably not by replacing everything. Most established logistics companies already have substantial investments in their ERP, TMS, WMS and other operational systems. Those systems may be perfectly adequate at what they were designed to do.
The interesting opportunities are often in the gaps:
- Where information moves manually.
- Where decisions take too long.
- Where the same work happens repeatedly.
- Where customers wait.
- Where employees have created informal processes to compensate for missing integration or functionality.
And, most importantly, where those inefficiencies have a measurable business consequence.
A quotation process that loses opportunities is more interesting than automating something simply because it can be automated. A workflow that prevents the business from scaling is more interesting than replacing a spreadsheet because spreadsheets feel old-fashioned. An integration that removes two hours of coordination every day may be more valuable than a large transformation programme.
Where Convex Technologies fits
At Convex Technologies, we are not approaching logistics companies with the assumption that they need another large software platform. And we are not a TMS or WMS vendor. Our role is closer to that of a technical partner.
We look at the operational problem, the existing software landscape and the business outcome that needs to change. Then we determine whether targeted software, integration, automation or AI can meaningfully improve it.
Sometimes that could mean connecting systems that currently require people to transfer information manually. Sometimes it could mean building a focused internal tool around a process that existing platforms do not support well. Sometimes it could mean automating document-heavy workflows. Sometimes AI may have a role. And sometimes the right technical recommendation is to leave an existing process alone.
The objective should not be “digital transformation” for its own sake. It should be something much more concrete:
- Answer the quote faster.
- Reduce the number of manual interventions.
- Give operations better visibility.
- Remove unnecessary administrative work.
- Handle more business without creating proportionally more coordination.
Technology becomes interesting when one of those numbers changes.
A simple exercise
If you are a CIO, COO or General Manager in logistics, there is a relatively simple exercise worth doing: look at the ten signs above and count how many you recognize in your own operation.
Not because every manual process needs to disappear. It doesn't. But if several of them appear around the same workflow, there is probably something worth investigating. Particularly when that workflow sits between your systems, your employees and your customers.
Because manual logistics processes don't only cost time. Sometimes they cost the deal.
If you've identified one of these bottlenecks in your operations, we'd be interested to know which one has the biggest impact. We work with companies to identify exactly these points of friction and determine where a technical intervention can produce a measurable business result. Get in touch and we can compare notes.
