The most expensive point in an SAP logistics project is the fortnight after go-live, when the system is correct and nobody can use it. Training is usually where that gets decided, and it is usually the workstream that gets compressed when the timeline slips.
How we approach it
Three principles shape everything we deliver:
- Train on your configuration, not a demo system. A planner who learns on standard SAP and then meets your charge structures, your lanes and your document types has been taught the wrong system. We build training on your quality environment with representative data.
- Train by role, not by module. A transportation planner, a settlement clerk, a customer service agent and a support analyst need different things. A single "SAP TM course" for all of them wastes most people's time and undertrains everyone.
- Train close to go-live, then again after. Training delivered three months early is forgotten. We schedule the main sessions near cutover and run a follow-up two to four weeks after go-live, when people have hit real problems and know what to ask.
Training programmes
SAP TM for transportation planners
Freight unit and freight order handling, manual and automatic planning, working with the optimiser, carrier selection and tendering, and the exception handling that occupies most of a planner's day. This is the highest-value session in most programmes, because planner adoption determines whether the system is used at all.
SAP TM for freight settlement and finance
Charge calculation, freight settlement documents, accruals, invoice verification and dispute handling — including how to trace a charge back to the agreement that produced it.
SAP Business Network for carrier-facing teams
Managing tenders and responses, onboarding a new carrier, and troubleshooting when a carrier says they cannot see a load. Frequently extended to a shortened session delivered to the carriers themselves.
Global Track and Trace for customer service and operations
Reading the shipment timeline, interpreting predicted arrival times, responding to exception alerts, and answering a customer's question without escalating it.
Yard and dock teams
Check-in and check-out, yard moves, appointment management, and handling late or unbooked arrivals.
Support and key-user enablement
The deeper session for the people who will support the system internally — configuration awareness, common failure patterns, monitoring stuck documents and failed interfaces, and knowing where the boundary of internal support sits.
Delivery formats
| Format | Best for | Typical shape |
|---|---|---|
| Onsite workshops | Planners and operational teams at go-live | Small groups, hands-on, one to three days |
| Live virtual sessions | Distributed teams and multi-site rollouts | Shorter sessions across several days |
| Train-the-trainer | Large or repeated rollouts | Intensive key-user sessions plus materials you keep |
| Recorded walkthroughs | Onboarding new joiners after go-live | Short task-based clips on your own system |
| Post-go-live clinics | Weeks two to six after cutover | Open sessions built around real questions |
Documentation — role-based quick reference guides written against your configuration — is produced as part of the engagement and remains yours to maintain and reuse.
Frequently asked questions
Do you provide official SAP certification training?
No. Official SAP certification courses are delivered through SAP Training and Adoption and its authorised partners, and we would point you there if certification is your goal. What we deliver is enablement on your own implementation — teaching your team to operate your configuration, which is a different objective and generally the one that determines whether go-live succeeds.
When in the project should training happen?
Key users should be involved from fit-to-standard workshops onward, so they learn the system as it is built. End-user training belongs close to cutover — typically two to four weeks before go-live — because anything delivered earlier is forgotten by the time it is needed. We then strongly recommend a follow-up session two to four weeks after go-live, which is when people have encountered real problems and the questions become specific and useful.
Can you train our carriers as well as our own staff?
Yes. Where a Business Network rollout depends on carrier adoption, a short carrier-facing session — usually virtual, usually under an hour — makes a measurable difference to how many actually start using the portal. We normally deliver this as part of the onboarding programme rather than as separate training.
How many people can attend a session?
For hands-on operational training we cap groups at around eight to twelve, because beyond that people stop practising and start watching. Awareness sessions and overviews can run considerably larger. For a big rollout, train-the-trainer is usually more effective and less expensive than us delivering to every user directly.