Menu Close

When Lower Freight Rates Don’t Deliver Lower Freight Costs

 

A carrier tender that delivers a lower headline rate can still leave total freight spend unchanged by quarter end. That is usually where a true procurement led logistics optimisation example becomes useful – not as a sourcing success story, but as a case of aligning procurement, logistics and finance around the actual cost to serve.

For multinational organisations, freight cost control rarely fails because rates are too high in isolation. It fails because rates, service commitments, shipment profiles, invoice data and operational behaviours sit in different systems and are managed by different teams. Procurement may secure improved contractual terms, while logistics continues to route urgent moves outside policy and finance receives invoices that are difficult to validate against contracted conditions. The result is familiar: limited visibility, weak contract compliance and savings that look stronger during negotiation than they do in the P&L.

This article sets out a practical enterprise example, focused on procurement leaders and finance stakeholders who need measurable logistics improvement without creating additional operational friction.

A procurement led logistics optimisation example in practice

Consider a manufacturer operating across Europe, Asia and North America with a decentralised transport model. Regional teams managed local carrier relationships, while group procurement ran strategic tenders for major parcel, road freight and air freight lanes. Finance had central responsibility for spend reporting, but invoice and shipment data came from multiple ERPs, local transport systems and carrier billing feeds.

On paper, the business had already done the right things. It had framework agreements in place, approved carrier lists and annual tender activity. Yet freight spend continued to rise faster than shipment volumes. Senior stakeholders wanted to know whether the issue sat with carrier pricing, weak operational discipline or poor financial control.

Procurement began by reviewing the carrier portfolio and renegotiating selected contracts. The initial result looked positive: lower base rates on core lanes, revised fuel surcharge schedules and improved rebate terms. But six months later, realised savings were materially below target.

The problem was not the tender itself. It was that sourcing decisions had been made using incomplete cost data. Procurement had negotiated against historical spend categories rather than verified shipment-level behaviour. Once post-tender data was reviewed in detail, several issues emerged.

A significant share of shipments had moved outside agreed lane assumptions. Premium services were used more often than expected by local operations teams trying to protect customer service. Accessorial charges varied by country and by carrier billing practice. Some business units were still using incumbent carriers that had not been awarded volume. In a number of markets, invoice coding did not map cleanly to the new contracts, making contract compliance difficult to monitor.

This is where logistics optimisation became procurement led rather than procurement limited. The focus moved from buying transport more cheaply to controlling how contracted transport was actually used and billed.

What changed when procurement, logistics and finance worked from the same data

The turning point came when the business created a shared freight cost baseline using audited invoice data matched to shipment attributes and contract terms. That sounds straightforward, but in complex international networks it is often the missing layer.

Instead of relying only on carrier spend by supplier or region, the company analysed cost by mode, lane, service level, site, business unit and exception type. Procurement could then see where contracted rates were performing as expected and where non-rate factors were eroding value. Logistics teams could identify operational habits that drove avoidable premium spend. Finance gained a clearer line of sight between contracted commitments and actual invoice outcomes.

The exercise exposed three high-impact issues. First, contract leakage was more expensive than expected. Roughly one in five shipments in selected regions moved outside preferred carrier allocation rules. Second, accessorials had become a major source of uncontrolled spend, particularly where local site practices generated repeated waiting time, re-delivery or manual handling charges. Third, service selection rules were inconsistent. Some sites were shipping next-day by default, despite customer requirements allowing deferred delivery.

None of these issues would have been solved by another tender. They required governance, controls and reporting discipline built around procurement decisions.

The procurement actions

Procurement did not simply reopen negotiations. It refined carrier awards based on verified lane profitability, tightened service schedules and standardised charge definitions where local contracts had drifted over time. It also introduced clearer compliance rules for when non-preferred carriers could be used.

This matters because many enterprise logistics contracts fail at the point where exceptions are tolerated but not measured. If local teams have broad discretion and no consistent reporting, contract compliance becomes an aspiration rather than a control.

The logistics actions

Operations teams reviewed shipment planning and service selection at site level. In several countries, premium service usage was reduced through revised order cut-off times and better alignment between warehouse processes and carrier collection windows. That is a useful reminder that logistics cost is often shaped by internal operating design as much as external carrier pricing.

The business also identified sites generating repeated accessorial charges and addressed the underlying causes. In some cases it was poor booking discipline. In others it was packaging, loading or documentation quality. Procurement could support these changes, but logistics had to own execution.

The finance actions

Finance established a tighter closed-loop process between contracted rates, shipment records and carrier invoices. This improved contract compliance reporting and made it easier to challenge disputed charges quickly. More importantly, it turned logistics optimisation from a one-off sourcing programme into an ongoing cost management discipline.

For CFOs and finance directors, that distinction is critical. A tender can deliver a point-in-time rate improvement. A controlled process can protect margin over multiple reporting periods.

What the example shows about enterprise freight strategy

The most useful lesson from this procurement led logistics optimisation example is that procurement should set the commercial framework, but it cannot deliver full value alone. Freight is not a static category. Shipment profiles shift, local behaviours vary and carrier billing structures create complexity that standard sourcing methods do not always capture.

That is why verified freight data matters. If the baseline is weak, tender decisions may still improve rates while missing the bigger cost drivers. If reporting only shows total spend by carrier, teams will struggle to see whether the issue is poor buying, poor compliance or poor operational execution.

This is particularly true in multinational organisations. Currency variation, fragmented systems, local carrier agreements and regional operating differences can make spend visibility appear stronger than it really is. A global contract is useful, but only if invoice coding, shipment references and service definitions are consistent enough to monitor against it.

Where organisations usually get stuck

Most enterprises do not struggle with the concept. They struggle with ownership.

Procurement sees the category through sourcing and supplier management. Logistics sees network performance and service execution. Finance sees invoice accuracy, accruals and budget control. Each function is correct within its own remit, but freight savings often disappear in the gaps between them.

A common example is fuel and surcharge management. Procurement may negotiate a revised mechanism, but finance cannot validate it consistently if carrier invoices are not matched to the relevant contract logic. Another is mode shift. Logistics may support moving volume from air to road or road to consolidated movements, but procurement needs accurate lane and service data to reflect those changes in future sourcing events.

There is also a timing issue. Procurement programmes often work to annual sourcing cycles, while logistics issues surface weekly and financial leakage appears monthly. Without integrated reporting, corrective action arrives too late.

What good looks like for procurement leaders

For procurement leaders, the objective is not simply lower rates. It is a transport category strategy that stands up under invoice scrutiny and operational pressure. That means working from verified spend data, defining measurable compliance rules and reviewing exceptions as part of supplier governance rather than treating them as site-level noise.

It also means accepting trade-offs. The cheapest carrier is not always the right carrier if service failure triggers more premium expedites later. Standardisation can improve control, but over-standardisation may ignore legitimate local market constraints. Central governance is valuable, yet local operations still need practical routes for justified exceptions.

The strongest programmes usually combine three things: contract discipline, operational accountability and financial visibility. Where those are connected, procurement has a much better chance of converting negotiated value into realised value.

For organisations managing complex international freight, that is where specialist audit, reporting and cost analysis support can add real weight. Not as an administrative afterthought, but as the mechanism that shows whether procurement strategy is working in practice.

A good logistics strategy does not end when the contract is signed. It starts proving itself when real shipments, real invoices and real operational constraints begin to test it.