Key findings from Dragonfly’s new whitepaper, “Logistics That Works for the People Running It”, a practitioner’s view of SAP Logistics Management.
Most logistics improvement programmes focus on the wrong problem. Investment concentrates on the flagship distribution centre, the primary SAP environment and the most visible team. Meanwhile, the facilities doing the daily work of receiving, storing, picking and shipping, often smaller operations or satellite sites, inherit legacy tools, manual processes and systems that were never designed for them.
That is the central finding of our new whitepaper, drawn from the pattern we see in most of the SAP supply chain audits we conduct. Here is a summary of what the paper covers, and why it matters.
A network running at two speeds
The flagship operation tied directly into S/4HANA is usually well managed: configured systems, documented processes, a team that knows how to navigate exceptions. Go one step further out, to the satellite facility, the regional depot or the warehouse run by a third-party logistics provider, and the picture changes. Spreadsheets. WhatsApp messages between the warehouse floor and the office. Paper-based picking lists. A manually maintained carrier contact list.
This isn’t a failure of intent. The enterprise tools available were either too expensive to deploy at that scale, too complex to implement without a lengthy project or too rigid to fit how the site actually operates. The result is a network where head office runs on best practice and the rest of the business runs on familiarity and improvisation, and suppliers, carriers and customers rarely see the difference until something goes wrong.
What a modern logistics platform needs to do
The whitepaper sets out five selection criteria that matter more than feature checklists. A single view across warehousing and transportation, because most logistics problems are handoff problems. Carrier collaboration that doesn’t depend on email, phone calls and spreadsheet tracking. AI assistance that supports operators rather than replacing them, helping a warehouse operative find the right storage bin or flagging an exception while it can still be resolved. Deployment that doesn’t require a transformation programme. And clean, native integration with the existing SAP estate, with no custom middleware that needs its own maintenance programme.
That last point is more than a preference. Gartner predicts that through 2027, systems and technical architecture will equal functionality in importance for new WMS buyers seeking flexibility, adaptability, composability, usability and affordability.
When the system earns its keep
The operational case is clearest in the day-to-day. Inbound, carriers book their own dock slots, gate check-in is shared across systems as it happens, and goods receipt flows back to the ERP without a separate manual step. Outbound, rules-based carrier selection with digital tendering handles standard shipments automatically, routing exceptions to a human decision only where judgement adds value. Joule, SAP’s embedded AI assistant, supports the tendering process directly. On the floor, mobile-first task management replaces paper picking lists, with barcode scanning and exception handling built into one interface. The value-adding work stays with the people closest to it; the coordination overhead reduces substantially.
What IT needs to know
SAP Logistics Management is a fully cloud-native SaaS solution built on SAP Business Technology Platform, using microservices architecture with bi-weekly feature releases. Integration with SAP Cloud ERP Private runs through SAP Integration Suite and published REST APIs, with no custom middleware. The platform operates at a 99.7% SLA with 24/7 threat and vulnerability management, and pricing is subscription-based on transaction volume with no significant upfront infrastructure investment.
The more useful cost question, though, isn’t “what will this subscription cost?” It’s “what are we already paying for in manual coordination, custom integrations, support overhead and avoidable delays?” In many cases, that comparison changes the economics quickly.
The question worth asking
SAP Logistics Management isn’t the right answer for every operation. For highly complex warehouses with significant automation investment, SAP Extended Warehouse Management remains the appropriate platform. But for the significant proportion of operations that sit below that complexity threshold and above the capability of a basic WMS, unified warehousing, transportation and carrier management in a rapidly deployable cloud-native solution is a meaningful shift.
If your satellite sites, regional warehouses or partner-run facilities are carrying too much manual overhead, the next step is simple: assess where time is being lost, where data is being rekeyed and where exceptions are being managed outside the system. That is usually where the case for change becomes clear.
Download the full whitepaper, Logistics That Works for the People Running It or get in touch to talk through what we’re seeing in operations like yours.
