The Invisible Operations Layer: Why Mid-Sized European Distributors Work Harder Than Their Systems Suggest.
If you walk into the operations floor of a mid-sized European distributor on a Tuesday morning, the first thing you notice is not the systems. It is the noise. A dispatcher is on the phone with a driver who took a wrong turn outside Lyon. Two operators are leaning over a shared screen trying to figure out why a delivery window in Munich slipped by ninety minutes. Someone is forwarding a WhatsApp screenshot to a customer service rep because a carrier replied on the wrong channel again. A printed sheet of stops sits on the corner of a desk, marked up in red pen, because the TMS does not reflect what actually changed at five in the morning.
None of this appears in any system of record. None of it is measured. None of it shows up in the operational dashboards that get presented to leadership on Friday afternoons. And yet, by my estimate from conversations with more than thirty operators across France, the DACH region, and Benelux, this invisible layer absorbs somewhere between forty and sixty percent of the actual coordination work that keeps the business running.
This is the operations layer that nobody talks about. It is the gap between what the systems say is happening and what is actually happening. It is where SLAs are saved, where penalties are absorbed, and where the cost of fragmentation gets paid every single day, almost entirely by people.
I want to make the case in this essay that surfacing this invisible layer is the first real step toward improving mid-sized operations. Not buying more software. Not adding more dashboards. Not running another digital transformation initiative. Just seeing, honestly, what is already happening underneath the official process.
The official story versus the operational reality
The official story of a modern logistics operation reads well on paper. A transport management system handles planning and dispatch. A warehouse management system handles inbound, outbound, and inventory. An ERP handles orders, billing, and finance. Visibility tools sit on top and track shipments in real time. Planning tools model the network and recommend optimisations. Communication tools route messages to carriers. The diagram is clean. The vendors are named. The integrations are budgeted.
The operational reality is different.
Information arrives through channels that no system was designed to handle. A carrier sends a delay notification by email at six forty in the morning, written in three lines of French with no reference number. A driver sends a WhatsApp voice note to the dispatcher explaining that the customer site is closed for an event nobody knew about. A warehouse supervisor texts a photo of a damaged pallet to the operations lead. A regional sales manager calls the head of operations directly because their largest customer is asking about a shipment that the customer portal still shows as on time.
In each case, the information is real. The signal is meaningful. The consequences are operational. But the system of record knows nothing. The TMS still shows the delivery as scheduled. The visibility platform has not received the carrier update because it came through a channel that does not feed back into the platform. The dashboard that leadership will look at on Friday is, in a precise and quiet way, wrong.
So what fills the gap?
People do. Specifically, a small number of experienced operators who have built personal mental maps of how the business actually runs. They know which carriers respond on email and which only respond on WhatsApp. They know which drivers need to be called and which prefer text. They know that the warehouse in Antwerp answers fastest before ten in the morning. They know that the customer in Stuttgart will accept a delay if it is communicated by eleven, but will impose a penalty if the notification comes at twelve. This knowledge lives in their heads. It is not written down. It is not in any handbook. And when those operators are sick, or on holiday, or leave the company, it walks out the door with them.
Why the invisible layer is invisible
There are three reasons this layer is so hard to see, and all three are worth taking seriously.
The first is that the work itself does not generate structured data. A phone call leaves no trace beyond a duration on a mobile bill. A WhatsApp thread is encrypted, personal, and locked inside an account that nobody else can search. A handwritten note on a printed manifest exists only on that one piece of paper. The work is real, but it is not legible to any system. When something is not legible to a system, it does not exist for measurement purposes. And when something cannot be measured, it cannot be managed, audited, improved, or budgeted for. It is operationally important and organisationally invisible at the same time.
The second reason is that the people doing this work do not describe it as work. If you ask a senior dispatcher how they spent their morning, they will not say “I performed twenty seven acts of cross system coordination across four communication channels.” They will say “I sorted out a few things.” The language of the work is casual, even apologetic. Coordinating across a broken landscape feels like firefighting, and firefighting feels like something that should not be happening, so people tend not to talk about it as a category of professional activity. They treat it as friction to be tolerated rather than a process to be designed.
The third reason is that leadership has very little incentive to look. The systems that were purchased to run the operation were sold on the promise that they would, in fact, run the operation. To acknowledge that forty to sixty percent of coordination still happens outside those systems is to acknowledge that the original investment was incomplete. That is a difficult conversation to have with a board, particularly when the systems themselves are functioning correctly within their own scope. The TMS is doing what a TMS does. The visibility platform is providing visibility. None of them are failing. They are simply not covering the part of the operation that lives between them, and the people who notice the gap most clearly are the ones least empowered to escalate it.
What the invisible layer actually costs
It is tempting to treat the invisible layer as an inconvenience rather than a cost. After all, things are getting done. The trucks are moving. The customers are, mostly, being served. The penalties are, mostly, manageable.
The cost shows up in four places, and only one of them is obvious.
The obvious cost is SLA penalties. In the conversations I had, operators consistently described penalties as something that happens, that is tracked, and that is accepted as part of the business. One head of operations described it as “part of the operating model now, not an exception.” When penalties run at two to five percent of revenue on key contracts, which is the range that came up most often in mid-sized accounts, that is a material number that no software vendor has been asked to compete with directly. The penalties exist because issues are detected late, escalated slowly, and resolved through informal channels that were not designed for speed.
The second cost is the senior person tax. The most experienced operators in the business spend a disproportionate share of their time on coordination work that, in a properly instrumented operation, would not require their attention. They are not doing strategic planning. They are not improving the network. They are not training their teams. They are answering messages, making calls, and chasing updates. The opportunity cost of having your most capable people absorbed by coordination is rarely calculated, but it is enormous.
The third cost is the resilience cost. Because the invisible layer lives in the heads of a few people, the business is fragile in ways that are not visible from the org chart. When a key dispatcher takes two weeks of holiday, performance degrades in ways that nobody can quite explain. When someone retires, the team needs six months to recover the rhythm. When the company tries to open a new site, the launch is slower than expected because the new site has not yet developed its own informal coordination layer. None of this appears in a risk register, because none of it is documented.
The fourth cost is the strategic cost. A business that cannot see how it actually operates cannot improve how it actually operates. Every transformation initiative, every process redesign, every system upgrade, is being designed against the official picture of the operation rather than the real picture. Decisions are made with incomplete information, which means that even well intentioned investments often fail to produce the expected return, because they target the wrong layer of the problem.
What surfacing the layer actually means
Surfacing the invisible layer does not mean buying yet another tool that sits on top of the existing stack. The mid-sized operators I spoke to have been sold that pitch many times, and the result has typically been more dashboards, not fewer.
What surfacing actually means is treating the unstructured signals as part of the operation, not external to it. The WhatsApp message about a delayed pallet is operational data. The phone call about a closed customer site is operational data. The email in three lines of French is operational data. The handwritten correction on the manifest is operational data. These signals are already being acted on by people. The question is whether they are also being captured, classified, and connected to the systems of record that everyone agrees are the source of truth.
There are some practical implications of this view.
The first is that integration is not enough. Connecting a TMS to a WMS to an ERP is necessary, but it does not address the layer that sits between systems and partners and people. The integrations make the official picture more coherent. They do not make the unofficial picture visible.
The second is that visibility is not enough. Seeing where a shipment is does not tell you what is happening around it. Knowing that a truck is delayed by forty minutes does not tell you whether the customer has already been notified, whether the carrier is responding, whether the driver is on the right route now, whether the warehouse needs to be informed. The work between systems is the work that determines whether the delay turns into a recovery or a penalty.
The third is that automation is not enough on its own either. Automating structured workflows is valuable, but most of the work that absorbs operator time is not happening inside structured workflows. It is happening in the spaces between them, where context has to be assembled from multiple channels, where priorities have to be balanced under pressure, where partners need to be coordinated. Automating a task that only takes thirty seconds anyway is less valuable than coordinating a sequence of actions that currently takes three people forty minutes to do informally.
What surfacing requires is a shift in posture. Operations teams need to stop treating informal coordination as something to be hidden and start treating it as a first class part of the workflow that deserves to be designed for. That means capturing the signals where they actually arrive, including in messaging apps and email. It means connecting those signals to the people and systems that need them. It means building a record of what actually happened, not just what was planned. It means giving the senior operator who currently holds the operation together in their head a way to externalise that knowledge so the business is not held hostage to their continued presence.
Why mid-sized operators in particular
I want to be specific about why this matters most for mid-sized European distributors and 3PLs, rather than for the largest enterprise operators or the smallest local ones.
The largest operators have resources. They have already invested in control towers, in custom integrations, in operations research teams, in dedicated coordination platforms. Their invisible layer still exists, but it has been partially formalised through scale and capital. They are not unaware of the problem. They have just bought their way into a partial solution.
The smallest operators do not need to surface the invisible layer because it is not invisible to them. A small family run distributor with four trucks and two dispatchers can hold the entire operation in two heads. The coordination is informal, but it is also fully observable to everyone in the room. The problem of the invisible layer is a problem of organisational scale, not a problem of work itself.
The mid-sized operator is caught in between. They are too large for everything to fit in one room, but too small to fund the kind of bespoke infrastructure that the largest players have built. They run on a stack of off the shelf systems that were each designed for a clean process, layered on top of an operation that is anything but clean. They have multi-site coordination, multiple carriers, multiple customer contracts with different SLAs, multiple languages, multiple regulatory environments. The official systems can handle perhaps half of the resulting complexity. The other half lives in the invisible layer.
This is also the segment where the consequences are most acute. A mid-sized operator with seventy five million euros of revenue and SLA penalties running at three percent is losing more than two million euros a year to a problem that nobody on the leadership team has assigned to anyone in particular. The penalties are tracked, accepted, and budgeted for, but they are not treated as a tractable problem, because the layer where they originate is not legible enough to be improved.
A modest proposal
I am not arguing that mid-sized operators need a new category of software. I am arguing for something both smaller and more demanding, which is a change in how leadership looks at the operation.
The proposal is this. Spend one week treating the invisible layer as the primary subject of attention. Ask the senior dispatchers to log, in whatever rough form they can manage, every coordination act that happens outside the systems of record. Every phone call. Every WhatsApp message. Every email that should have been a system update. Every printed sheet with a handwritten note. Do not try to fix anything yet. Just count.
What you will find is that the volume is far higher than the official picture suggests. You will find that a small number of people are doing a large amount of this work. You will find that certain customers, certain carriers, and certain corridors generate disproportionate coordination load. You will find that the same issue types recur, and that the same resolutions get reinvented every time, because nobody has captured the pattern.
Once you have that picture, the conversation changes. The question is no longer “do our systems work” but “what is the operation that our systems do not yet see.” That is a fundamentally different question, and it leads to fundamentally different answers. Some of those answers will be about process. Some will be about training. Some will be about how partners are managed. Some, eventually, will be about software that is genuinely designed to operate in the fragmented space between systems, teams, and partners, rather than trying to pretend that the fragmentation does not exist.
But all of those answers start with seeing the layer.
The invisible operations layer is doing the work that the visible layer cannot. It is doing that work expensively, fragilely, and without recognition. The first act of operational improvement, before any new investment, is to make it visible. Once it is visible, it can be discussed. Once it can be discussed, it can be coordinated. Once it can be coordinated, it can be executed against in real time, across the systems, the teams, and the external partners that the operation actually depends on. This is the gap that Certin was built for. We do not replace the TMS, the WMS, or the ERP, and we do not compete with the visibility platforms that sit on top of them. We operate in the space those tools leave open, the space where emails, WhatsApp threads, phone calls, and manual handovers currently absorb half of the working day.
Certin connects the structured and the unstructured, reads the signals as they arrive, decides what needs to happen next, and coordinates the response across every party that needs to act. The result is an operation that runs end to end instead of in fragments, and a leadership team that finally sees what their business actually does, rather than what their systems happen to record. Mid-sized European distributors have spent a decade buying tools that explain the operation. The next decade belongs to the ones that decide to run it.
Like to see what we are building? Its right here for you https://getcertin.ai