According to market experts, only 22% of companies measure savings after spending actually occurs. In an industry where margins run at 1–2% for FTL operators and groupage networks routinely bleed on lanes nobody is actively monitoring, that measurement gap alone represents a significant portion of unrealized value.

Circular Economy and Circular Supply Chians

Understanding exactly where the gap opens, how it compounds, and what the operational infrastructure required to close it actually looks like is more useful than any individual cost-reduction initiative.

In case you want to jump ahead

The Architecture of the Saving Gap

The savings gap is not a single failure point. It is the compound effect of three structural mechanisms that operate simultaneously in almost every logistics organization and understanding them precisely matters, because each one requires a different intervention to close.

Monitoring Towers VS Execution Towers

The dominant mental model of a supply chain control tower is a visibility tool, a centralized dashboard aggregating shipment data, flagging exceptions, and surfacing performance metrics across lanes and carriers. This architecture is genuinely useful, but it also does not close the savings gap.

A monitoring control tower tells a dispatcher that a shipment is running at 61% truck utilization and that a consolidation-eligible load exists on the same lane with 18 hours of remaining SLA buffer. An execution-connected control tower holds the first shipment, triggers the consolidation, and routes both under the preferred carrier rate automatically, within defined rules, without requiring a human decision at the transaction level.

The practical implication is that two organizations can purchase identical control tower software and achieve fundamentally different margin outcomes, because one has connected the tower’s output to automated routing logic and the other has connected it to a dashboard that someone checks in the morning.

Organizations using AI-enabled supply chain control towers have reported up to 30% reduction in inventory and 8% lower logistics costs.

Static Planning VS Continuous Planning

Most logistics cost-saving analysis is conducted on a periodic basis, which creates an inherent structural problem: the findings reflect a snapshot of a market that continues to move. A consolidation opportunity identified in a September lane review may not exist in the same form in January when the planning assumptions have shifted.

Cost management is the most critical priority for one-third of corporate leaders globally in 2025, according to BCG, but the majority of logistics operators are still managing cost through planning cycles that update annually or quarterly rather than continuously. The result is that identified savings have a decay curve: a saving found in Q1 is partially realizable by Q3 and may be substantially eroded by Q4, precisely when the implementation that was meant to capture it completes. 

The technical shift required is from planning as a periodic project to planning as a continuous operational function, where optimization algorithms run against live TMS and ERP data, route logic updates when carrier availability changes, and consolidation rules adjust dynamically when SLA buffer patterns shift. 

The Compliance Enforcement Gap

Even when a saving is correctly identified, implementation timelines are respected, and routing logic is updated in the TMS, the final failure point is compliance enforcement: the systematic, measurable assurance that eligible shipments are actually moving under the conditions the analysis prescribed.

A contracted carrier rate is a potential saving that becomes actual only when that carrier is consistently selected for eligible shipments rather than spot alternatives. In most TMS environments, the routing guide exists, the preferred carrier is defined and a meaningful percentage of eligible volume moves outside it for reasons that are never tracked. Those reasons range from carrier capacity unavailability to dispatcher preference to system configuration errors. All of them represent the gap between the rate the procurement team negotiated and the cost that appears on the freight invoice.

According to Deloitte research, 76% of manufacturers report limited visibility across their supply chains and that is precisely the condition that allows compliance failures to compound below the threshold of detection. The compliance enforcement gap is the last and most operationally tractable expression of the savings gap.It requires measurement infrastructure that almost no organization has built.

Maersk: The Custom Control Tower & The Execution Distinction

The Maersk Customs Control Tower case is the clearest documented illustration available of the difference between a monitoring architecture and an execution architecture and of what that difference produces in financial terms.

data exist, action does not

Customs is a cost category that most global shippers treat as a compliance necessity rather than a margin lever. The operational pattern is familiar: multiple third-party brokers manage different segments of the customs process, a separate agent handles import clearance, and no single system holds a complete picture of the total customs cost profile. Data exists, but it is fragmented across parties that have no integrated view of each other’s decisions.

One of Maersk’s global clients had many stakeholders running different customs processes, with low visibility of customs data and limited ability to understand the business implications and make the right corporate decisions. This is an exact description of all three mechanisms operating simultaneously: 

monitoring gap

No unified view across customs operations.

periodic planning problem

Decisios made reactively when exceptions surface.

compliance enforcement gap

No systematic duty or broker control.

The architecture Maersk implemented centralises customs operations with automatic validation of data and documents to identify discrepancies before distributing orders to brokers, identifies and resolves exceptions automatically based on pre-defined business rules, and logs all exceptions continuously for further analysis and ongoing process improvement. 

The operational significance of that architecture is in what it removes from the human decision loop. Document validation, exception identification, broker routing, and duty classification consistency are not decisions that a dispatcher or customs coordinator reviews case by case, but enforced by rules that apply to every declaration, automatically. The compliance enforcement gap closes, because the system architecture does not permit non-compliance on the decisions it governs.

Visibility without enforcement produces insight. Enforcement without visibility produces rigidity. The combination produces realized savings.

$16M

annual savings

$250K

implementation

64x

roi in one year

With a $250,000 investment in the Customs Control Tower, the client achieved $1.5 million in reduced annual spend on customs services and $15 million in reduced duties paid in the first 12 months

Customs is a specific process domain, but the mechanism it illustrates is universal. The same logic applies to carrier selection in FTL networks, consolidation decisions in groupage operations, and inbound call-off timing in manufacturing supply chains. In each case, the saving is present in the data before any new analysis is commissioned. What is typically absent is the enforcement architecture that captures it.

Additional Industry Cases

The execution distinction illustrated by Maersk is not specific to customs or to shipping. The same structural gap and the same architectural response appears across industrial manufacturing and road freight operations, each with its own operational expression of the same underlying problem.

Click on the use case you want to learn more about:

Industrial Manufacturing

BMWAI Planning Layer

In complex industrial manufacturing, the largest logistics costs are determined not at the carrier selection stage but weeks earlier, in inbound planning decisions that commit freight cost before a truck has been booked.

the challenge

  • €90 billion annual purchasing volume across a 140-country supplier network
  • Reactive premium freight triggered by late detection of supplier risk
  • Manual purchasing decisions at a volume that human processes cannot consistently optimize
  • Planning cycles that update periodically rather than continuously against live data

$90BN

annual purchasing volume managed

4 months

earlier anomaly detection 

140

countries in supplier network

Daily

ai-supported purchasing decision cadence

what bmw did

  • Deployed AI agents to support purchasing and supplier risk decisions at operational scale
  • Built AI systems identifying component anomalies up to four months earlier than conventional methods
  • Participated in Catena-X, connecting supplier-level risk data to internal planning systems in near real-time
  • Embedded AI as part of daily operational reality across the purchasing division, not as a strategic overlay

In complex manufacturing supply chains, the majority of freight cost is determined at the planning stage, not the carrier selection stage. Optimising carrier rates without optimising the planning decisions that determine what volume moves, when, and in what configuration addresses a secondary lever while leaving the primary one unchanged.

FTL & Groupage

European Road FreightStructural Load Factor and Consolidation Gap

The savings gap in FTL and groupage networks has a specific expression that sector-level data documents more precisely than most operators’ own internal reporting, because most internal reporting aggregates away the information required to see it.

the challenge

  • Average load factor reporting obscures the distribution of individual movement performance
  • SLA buffer data not integrated into dispatch decisions at the transaction level
  • Consolidation opportunities evaluated periodically rather than at each departure window
  • 68% of shippers request control tower visibility as their most frequent technology ask from 3PLs

50%

european trucks empty or partially empty

$160BN

annual economic losses created

68%

shippers requesting control tower visibility from 3PLs

8%

lower logistics costs with ai-enabled control towers

what data reveals

  • The fixed cost of a truck movement is committed regardless of load factor, margin difference is asymmetrically larger than the percentage gap suggests
  • Groupage shipments with 48–72 hour SLA windows frequently dispatched in hours of booking, each a consolidation candidate not evaluated
  • The compliance gap compounds the load factor gap: dispatcher-level routing overrides occur without documentation or measurement
  • Shippers requesting control tower visibility already understand: the savings gap is a visibility and execution problem, not a rate problem

Organizational Readiness Check

Before committing to control tower investment, planning automation, or optimization tooling, supply chain leaders should assess their current architecture across four dimensions. Most LSPs and manufacturers in 2025–2026 sit at the Developing stage on data infrastructure and Early Stage on compliance enforcement and it is the enforcement gap that is hardest and most consequential to close.

DimensionEarly Stage
Starting point
Developing
In progress
Advanced
Savings realised
Cost VisibilityP&L granularityTotal transport cost visible only. No lane, truck, or customer-level P&L. Margin leakage invisible below portfolio level.Lane-level cost reporting available on request. Some customer-level profitability modelled quarterly.Real-time P&L at lane, truck movement, and customer level. Unprofitable lanes surface automatically before losses compound.
Control Tower ArchitectureMonitoring vs. executionMonitoring dashboards only. Exceptions identified after the fact. All resolution decisions manual.Exception alerting with defined resolution workflows. Some carrier substitution automated within narrow parameters.Execution-connected: tower triggers routing decisions, consolidation holds, and carrier selection automatically. Full decision audit trail maintained.
Planning IntegrationStrategy to dispatchOptimisation runs periodically. Outputs not connected to daily dispatch. Planning and execution operate in separate systems with manual handoff.Planning outputs feed TMS with a lag. Optimisation recommendations require manual implementation. SLA buffer modelled for major lanes only.Continuous planning loop against live data. SLA buffer visible at shipment level in dispatch system. Inbound call-off planning connected to freight cost model.
Compliance EnforcementContracted rate adherenceContracted rate adherence not measured. Routing guide exists but compliance not tracked. Savings initiatives reported at go-live and not revisited.Routing compliance tracked for top-volume lanes quarterly. Ad-hoc investigation of major non-compliance events.Contracted rate adherence measured weekly at lane level. Autonomous decision boundaries formally defined. Savings realisation tracked at 6, 12, and 18 months post-implementation.

Key Implementation Steps: Choose Your Perspective

The developments described above are not sequential innovations. They are converging simultaneously.

Click on the perspective you want to analyze – executives or analysts.

Key Implementation Steps (Executive View)  

1. Require a Routing Compliance Report Before Commissioning Any New Cost Analysis

✔ If contracted rate adherence is below 85%, the problem is insufficient enforcement architecture

✔ Ask your analytics team to produce contracted rate adherence by lane. If it takes more than one week, the measurement infrastructure does not exist

✔ That single measurement creates more organisational pressure to close the savings gap than any strategic initiative

2. Separate a Monitoring Budget from Execution Budget

✔ A control tower that monitors and alerts is a reporting investment. A control tower that triggers routing decisions is a margin investment

✔ Before approving any investment, require the team to specify which decisions the system will make autonomously, which need human approval, and which it only reports

✔ ROI modelling should be built on the execution layer, not the visibility layer. Require the business case to distinguish between the two

3. Connect Planning & Execution Systems Before Optimizing

✔ For industrial manufacturers, the largest logistics cost savings are upstream of the freight invoice, embedded in inbound planning decisions 

✔ Prioritise data connectivity between planning outputs and your TMS before investing further in either layer independently

✔ Define a maximum acceptable lag between a planning decision and its appearance in the dispatch system

4. Govern Savings Realization as a Standing Operational Measurement

✔ Require savings realisation to be measured at 6, 12, and 18 months post-implementation

✔ Build realization measurement into governance as a standing operational report, not a retrospective review

✔ Present this to operational leadership monthly. The savings gap closes when it is visible in the room where operational decisions are made

Key Implementation Steps (Analyst View)  

1. Build a Contracted Rate Adherence Model at Lane Level & Update Weekly

✔ Join TMS shipment data to rate card data for every lane where a preferred carrier holds a contracted rate. Break down by origin-destination, weight band, and week

✔ Where adherence is below 80%, classify root cause: system routing logic gap, capacity availability failure, or manual override pattern. 

✔ Run weekly, not quarterly. At 1–2% FTL margins, 90 days of routing non-compliance on a major lane is not a rounding error

2. Replace Average Load Factor with a Distribution Analysis

✔ Build a load factor histogram by lane, departure day of week, and time window. Networks reporting 82% average utilisation frequently contain a tail of movements at 60–65%

✔ Cross-reference low load-factor departures against SLA buffer data. A departure at 64% utilisation whose shipments had 40 hours of remaining SLA buffer is a documented consolidation failure

✔ For groupage networks, model the cost differential between current departure pattern and a defined consolidation hold scenario.

3. Build an SLA Buffer Consumption Rate Metric by Shipment Category

✔ For each shipment category, measure the proportion of available SLA window consumed before dispatch. Shipments using less than 30% of buffer before dispatch were consolidation candidates not evaluated

✔ High buffer availability with early dispatch is the direct measurement of urgency inflation, standard freight moving on non-standard timelines because buffer data is not in the dispatch decision

✔ Lanes with low buffer consumption and low load factors are your highest-priority consolidation targets

4. Create a Saving Initiative Realization Tracker with Automated Decay Flagging

✔ Track projected versus actual savings at 6, 12, and 18 months post-implementation. Apply a 15% variance decay flag at the 6-month mark to trigger investigation

✔ Represent each initiative’s realisation trajectory as a line against its projected savings curve. Divergence point is the investigation starting point

✔ Present this tracker to operational leadership monthly. Savings measurement is an operational signal, not a finance function

Conclusion: The Infrastructure of Realisation

Traditional cost programmes were designed to identify savings. The organisations closing the savings gap are designed to capture them. The difference is whether the conclusions of analysis are encoded into the operational system that processes every shipment, automatically, with audit trails that prove the encoding is holding.

The Maersk case makes this concrete at the LSP level: $16 million in annual return from a $250,000 investment, not because new savings were discovered, but because existing ones were finally built into the architecture processing every customs transaction. The BMW case makes it concrete at the manufacturing level: premium freight costs reduced not by renegotiating carrier rates, but by making supply risk visible early enough to respond through planning rather than emergency logistics.

For a structured view of where the specific cost leakages most commonly occur across Groupage, FTL & 4PL  explore the Log-hub Cost Savings Initiative.

In case you missed it – Previous Pulse Editions

Recieve the Literature by e-mail!

Recieve the Literature by e-mail!

Share with us your e-mail address in order to receive the resource.

You have Successfully Subscribed!