The Four Pillars
These are the areas we go deep on. Each has its own page with detail on scope, approach and the questions clients ask most.
SAP Transportation Management (TM)
Full lifecycle SAP TM — freight order management, carrier tendering, route and load optimisation, freight settlement, and integration with SAP S/4HANA and EWM.
- Freight Order & Booking Management
- Carrier Tendering & Rate Management
- Route & Load Optimisation
- Freight Settlement & Invoicing
- S/4HANA & EWM Integration
SAP Business Network for Logistics (BN4L)
Connect your freight ecosystem on SAP's cloud logistics collaboration network — digital collaboration between shippers, carriers and logistics service providers.
- Carrier & LSP Network Onboarding
- Digital Freight Collaboration
- Electronic Booking & Tendering
- SAP TM ↔ BN4L Integration
- Real-time Status & Exception Sharing
SAP Global Track & Trace (GTT)
Real-time end-to-end shipment visibility. Track freight events, predict arrival times, and detect exceptions before they become customer problems.
- End-to-End Shipment Tracking
- Predictive ETA & Exception Management
- IoT & Telematics Integration
- Carrier & 3PL Event Feeds
- Customer-Facing Visibility Portals
Logistics Management Solutions (LMS)
Yard management, dock appointment scheduling and fulfilment orchestration — the operational layer between your transportation plan and what happens at your sites.
- Inbound & Outbound Orchestration
- Yard Management & Dock Scheduling
- Intelligent Fulfilment & Order Management
- Freight Cost Management & Allocation
- S/4HANA & TM Integration
Everything Around the Core
The work that makes an implementation stick — before, during and long after go-live.
Integration
SAP logistics implementations are largely integration projects. We build and support connections between TM, EWM, S/4HANA and ERP, out to carrier EDI, freight networks, telematics providers and third-party logistics platforms — using standard interfaces where they exist and SAP BTP where they do not. Integration monitoring is included, because an interface nobody watches is an interface that fails silently.
Migration & upgrades
Moving from SAP TM 9.x to S/4HANA embedded TM, consolidating a sidecar instance, or upgrading to a current release. The work covers landscape analysis, custom code remediation, data migration and a cutover plan built around your shipping calendar rather than the project's convenience. We treat regression testing of charge calculation as non-negotiable — it is where upgrades most often go wrong quietly.
Managed support & AMS
Ongoing application management once you are live: incident handling, monitoring of stuck documents and failed interfaces, release regression testing, and continuous optimisation. Support agreements are scoped to your actual operating hours, and can extend to after-hours or weekend coverage where freight movement justifies it. We would rather agree realistic coverage than promise round-the-clock support we cannot staff properly.
Freight analytics & reporting
Reporting on freight cost per lane and per unit, carrier performance against agreed service levels, transit time variability, tender acceptance rates and detention exposure — built in SAP Analytics Cloud or embedded TM reporting. The useful version of this work starts by identifying the three or four decisions the reporting should drive, rather than building every chart the data permits.
Staffing
Contract, permanent, embedded and fractional SAP logistics consultants, screened by practitioners who do this work. See our staffing page.
Training & enablement
Role-based training delivered on your own configuration, close to go-live and again after it. See our training page.
Frequently asked questions
Do you only work on SAP, or other transportation systems too?
Only SAP. Our practice is built around SAP Transportation Management and the logistics modules around it. If your requirement is better served by a different platform, we will tell you rather than propose SAP for its own sake — but we would not be the firm implementing the alternative.
Can you take over support of an existing SAP TM implementation?
Yes. Taking over an existing landscape is a common engagement. We start with an assessment of the current configuration, integration points, open incidents and any custom code, then propose a transition plan and a support model scoped to your operating hours. We would not commit to a support agreement without that assessment first.
What size of organisation do you typically work with?
Mid-market and enterprise organisations moving meaningful freight volumes — typically shippers, manufacturers and logistics service providers where transportation is a material cost line. Below a certain volume, SAP TM is usually more system than the problem warrants, and we will say so.
Do you work remotely or onsite?
Both, and most engagements mix the two. Discovery, workshops, training and go-live support benefit from onsite presence; configuration, integration and ongoing support work well remotely. We agree the pattern at the start of the engagement rather than defaulting to one model.