Introduction
You invested in SAP expecting three things: efficiency, visibility, and lower transportation costs. The business case promised it. The implementation partner promised it. And yet, a year or two down the line, the freight bill looks stubbornly familiar.
Costs remain high. Planning still feels manual. Your logistics team spends its mornings firefighting instead of optimizing.
Across SAP TM optimization engagements over the years, I’ve seen the same pattern repeat itself. Within the first week of reviewing planning profiles, freight unit building rules, carrier selection logic, and planner workflows, it usually becomes clear that the problem isn’t SAP itself — it’s that many of its optimization capabilities were never fully activated or refined after go-live.
Section 1: SAP Is Not the Problem Utilization Is
Why SAP Alone Doesn’t Reduce Transportation Costs
SAP Transportation Management was built to optimize the entire transportation lifecycle — planning, execution, and settlement. Its VSR optimizer can evaluate consolidation and routing decisions across hundreds of shipments simultaneously, something no planner can do manually.
But the optimizer only creates value when it’s actually used — with rules and profiles designed around your network. In many organizations, planning still happens the way it did before SAP: shipment by shipment, based on individual experience. The capability is installed. It simply isn’t switched on.
Section 2: The 5 Hidden Gaps Driving High Transportation Costs
Where Most Organizations Lose Money Without Realizing It
Ask any CFO where the transportation budget goes, and they’ll point to freight rates. But in my experience, when costs refuse to come down after an SAP implementation, the rates are rarely the whole story. The money slips away quietly, through five gaps that almost never get noticed:
| Gap | What Happens | Cost Impact |
|---|---|---|
| Manual Planning | Planners build loads and routes shipment by shipment — the optimizer never gets a say | Costlier routes, decisions that depend on who planned that day |
| Poor Load Optimization | Nobody consolidates, so trucks leave the dock half full | You pay full-truck money for half-truck shipments |
| Lack of Visibility | No live tracking, no event management — you learn about problems after they happen | Delays, penalties, and constant firefighting |
| Inefficient Carrier Selection | Tendering happens over email and phone; no allocation or business-share logic in place | You overpay, and you don’t even know by how much |
| Disconnected Processes | Planning, execution, and settlement each live in their own silo | Errors slip through, invoices don’t match, money leaks |
And here’s the frustrating part — not one of these shows up as a line item in any report. A half-empty truck doesn’t trigger an alert. A carrier picked out of habit doesn’t look like a mistake. That’s exactly why these gaps survive year after year: they hide inside what everyone calls “normal operations.”
A Quick Self-Assessment
Before reading further, try this honestly. If two or more of these sound like your operation, there’s real money still sitting untouched in your SAP TM system:
- Does your planning day start with someone exporting SAP data into Excel?
- When a shipment needs a carrier, does someone pick one — or does a configured business rule?
- Be honest: how often do partially loaded trucks leave your warehouse? Weekly? Daily?
- Has anyone touched the optimizer configuration since go-live?
- Are your planners spending their day creating shipments — instead of just handling the exceptions?
None of this means SAP TM has failed you. It means a good part of what you paid for is still waiting to be used.
Section 3: What High-Performing Organizations Do Differently
From System Usage to System Optimization
The organizations that actually achieve low transportation costs with SAP don’t just run the system — they activate the parts most companies leave switched off.
In practice, that means freight units are created automatically from orders or deliveries through well-defined freight unit building rules. Planning runs through the VSR optimizer with tuned planning profiles, so the system proposes consolidations and routes instead of a planner building them from memory.
One configuration detail that’s frequently overlooked is freight unit building rule granularity. In many implementations, freight units are created immediately after order creation using broad default rules. That limits the optimizer’s ability to consolidate compatible shipments later in the planning cycle. Simply redesigning those building rules can create significantly better consolidation opportunities without changing the transportation network itself.
Beyond planning, carriers are selected through rule-based tendering — using allocations, business shares, or cost-based ranking — rather than a phone call to the usual contact. Execution is tracked through event management, and freight settlement runs automatically against agreed rates.
The result is what’s often called a touchless transportation model: humans handle exceptions, the system handles routine.
A Scenario From Project Experience
One manufacturing client operating multiple production plants and distributing products through a regional carrier network was managing more than 200 outbound shipments every month. Although SAP TM had been live for nearly two years, planners were still exporting orders into Excel before building shipments manually.
The review showed that freight unit building rules had been configured at a very basic level, the VSR optimizer was rarely used for production planning, and carrier assignments were still based largely on planner experience rather than configured business rules.
The improvements required no additional software. By refining freight unit building rules, tuning planning profiles, and introducing rule-based carrier selection, planning time dropped from several hours each day to less than an hour. Within the following quarter, transportation costs declined by approximately 12% as shipment consolidation improved and unnecessary partially loaded trips were reduced.
This is the difference between implementation and optimization.
At SCM CHAMPS, we see this pattern repeatedly across organizations that have implemented SAP but haven’t fully activated its transportation capabilities — and it’s almost always fixable with what they already own.
Section 4: What Is Transportation Automation in SAP TM?
Definition
Transportation automation in SAP TM refers to the system’s ability to automatically create freight units, plan routes and consolidate loads, select carriers based on predefined rules, track execution events, and calculate and settle freight costs — without manual intervention.
In practice, it means the work planners do today — checking orders, building loads, calling carriers, chasing invoices — is handled by the system, with the team stepping in only where human judgment is genuinely needed.
How Does SAP TM Reduce Transportation Costs?
There’s no single magic switch here — the savings stack up from several places at once. The optimizer finds routes and consolidations a planner would never spot under time pressure. Trucks leave fuller, so you stop paying full-truck rates for half-truck loads. Carrier decisions follow data instead of habit. Manual errors — and the rework they cause — fade out. And automated settlement quietly catches billing discrepancies that used to get paid without a second look.
How much does all this add up to? In the SAP TM optimization projects I’ve been part of, somewhere between 10% and 25% off transportation costs once planning automation, load consolidation, and rule-based carrier selection are genuinely running — not just configured. Where you land in that range depends on your shipment volume, how complex your network is, and frankly, how manual things were before. The more spreadsheet-driven the starting point, the bigger the jump.
Section 5: Why Most SAP TM Implementations Don’t Deliver ROI
Common Mistakes
If Section 1 describes what goes unused, this is why it happens. The causes are remarkably consistent: the project is measured on going live on time, so optimization gets pushed to a “phase two” that never arrives. Automation rules are left at defaults because designing intelligent ones takes workshops nobody scheduled. And once hypercare ends, no one owns getting more value out of the system.
One diagnostic I always check early is the optimizer profile. If it’s still using the same default configuration it had at go-live, I already know much of the story. SAP’s default planning profiles are intentionally generic — they aren’t designed around your fleet constraints, delivery priorities, loading restrictions, regional transportation rules, or consolidation strategy. Unless those profiles evolve with the business, the optimizer can only produce average results.
The system is technically live — the project was declared a success — but the freight bill disagrees.
5 Things I Check Within the First Hour of an SAP TM Health Check
When I sit down with a client’s system for the first time, these five checks tell me most of what I need to know before lunch:
- The optimizer profile settings. Are planning profiles still on defaults, or have they been shaped around the client’s actual fleet, constraints, and priorities?
- Freight unit building rule granularity. When and how are freight units created — immediately at order creation with broad rules, or in a way that preserves consolidation opportunities?
- The ratio of manually created to system-proposed freight orders. If planners are building most shipments by hand, the optimizer is decoration, not a tool.
- How carriers actually get assigned. Is there configured tendering logic — allocations, business shares, cost-based ranking — or does assignment follow habit and phone calls?
- Where planning data lives. If the answer to “how do you plan tomorrow’s loads?” involves the word Excel, the optimization journey stopped at implementation.
None of these checks requires touching a single transport order. But together, they usually explain exactly why the freight bill hasn’t moved.
Section 6: How SCM CHAMPS Approaches This
What an Assessment Actually Looks Like
SCM CHAMPS works with organizations that already have SAP in place but aren’t seeing the expected outcomes. Rather than describe that in broad strokes, here’s what our assessment actually covers:
- Planning review — how freight units are created, whether the VSR optimizer is in use, and how planning profiles are configured versus how they should be for your network
- Load factor analysis — actual utilization on recent shipments, to quantify what partial loads are costing you
- Carrier selection audit — how tendering happens today, and whether allocations, business shares, or cost-based rules could replace manual assignment
- Execution and settlement check — where tracking and freight settlement break away from the system into email and Excel
The output is a prioritized list of automation quick wins, each mapped to expected effort and impact — so you can decide what to activate first based on your own numbers, not ours.
Section 7: Expected Business Impact
What Organizations Can Realistically Achieve
What does this actually look like once it’s done? Ask the planning team first — the work that used to eat their entire morning now takes minutes, and their day shifts from building shipments to handling the handful that genuinely need a human. Deliveries arrive on time more often, because problems surface while there’s still time to act on them. Settlement stops being a monthly argument with carrier invoices. And when you put the 10–25% cost reduction next to what the assessment revealed about your current gaps, the business case tends to make itself — you won’t need to sell it internally; the numbers will.
Section 8: Frequently Asked Questions
Can transportation costs be reduced without replacing SAP?
Yes. In most projects I’ve seen, the savings come from activating and automating the SAP TM capabilities the organization already owns — not from replacing the system. Replacement is rarely the answer; activation usually is.
How long does it take to automate SAP TM processes?
It depends on process complexity and current system maturity, but targeted improvements — freight unit rules, tendering automation, optimizer tuning — can start delivering results within a few weeks to a few months. You don’t need a multi-year program to see the first savings.
Do we need SAP TM already implemented?
No. These strategies apply whether you run standalone SAP TM, SAP ECC, or S/4HANA, though capabilities differ. For organizations on S/4HANA without separate TM, the first step is often assessing whether the embedded TM capabilities can be activated.
What is a touchless transportation model?
A model where planning, execution, and settlement are handled automatically by the system, with minimal human intervention. People manage exceptions and strategy; the system handles the routine.
Is SAP TM automation suitable for all industries?
Yes. Industries with high shipment volumes — manufacturing, retail, consumer goods, logistics services — benefit most, but the approach applies wherever transportation is a meaningful cost line.
Ready to Find Out What’s Limiting Your SAP TM?
If your planners still export SAP data into Excel every morning — or if transportation planning depends more on individual experience than on system recommendations — your optimization journey may have stopped at implementation.
A focused SAP TM assessment can quickly identify where automation is breaking down, which standard capabilities are underused, and where the biggest opportunities exist to reduce transportation costs without replacing your existing system.
SCM CHAMPS reviews four critical areas:
- Freight unit building and planning configuration
- Load consolidation and vehicle utilization
- Carrier selection and tendering logic
- Transportation execution and freight settlement
You’ll receive:
- A clear view of where transportation costs are leaking
- Prioritized improvement opportunities based on business impact
- Practical recommendations that work with your existing SAP landscape
Book your SAP TM Assessment and discover how much value may still be hidden inside the SAP system you already own.