There’s a scenario that plays out in distribution centers around the world, more often than anyone wants to admit. A carrier arrives at an outbound gate on time. The freight order says the load is ready. But inside the warehouse, picking is still in progress, the staging lanes are partially occupied with goods from a different order, and no one in the transportation team has visibility into any of it. The truck waits. Detention charges accrue. And somewhere in the gap between two systems that were never truly speaking the same language, your logistics costs quietly climb.
This isn’t a technology failure in the narrow sense. It’s an architecture problem, one that the industry has been patching with middleware, APIs, and manual workarounds for years.
The integration illusion
Most enterprises today run a warehouse management system (WMS) and a transportation management system (TMS) that were designed independently, by different vendors, for different operational audiences. They’re connected usually through batch interfaces, file transfers, or brittle point-to-point integrations but they don’t share a common business object model. They don’t speak in the same transaction. When one side changes, the other often doesn’t know until it’s too late.
The consequences are well documented: missed dock appointments, shipments released before cargo is truly ready, detention fees, manual reconciliation work, and warehouse teams making decisions without knowing what the carrier has already committed to. These aren’t edge cases. They’re the predictable result of systems that were never designed to share a single version of the truth.
This is the problem that Advanced Shipping and Receiving (ASR) spanning SAP Extended Warehouse Management (EWM) and Transportation Management (TM) was built to solve, not by connecting two separate systems more cleverly, but by eliminating the boundary altogether.
One business object, not two conversations
ASR is the result of a deliberate architectural decision, the warehouse (managed by EWM) and transportation (managed by TM) work directly on the same business object, the Freight Order. There’s no handoff. No translation layer. No status reconciliation across systems.
That design choice unlocks a set of capabilities that aren’t simply “nice to have” but they address real, recurring execution failures.
Cross-delivery handling units let you consolidate items from multiple outbound delivery orders into a single physical handling unit. With ASR, the freight unit merge happens automatically and consistency checks across carrier, ship-to party, and loading point are enforced in real time. Transportation capacity is used more fully. Load preparation is faster.
Change management for outbound deliveries sounds procedural, but it’s one of the most operationally painful gaps in traditional WMS-TMS setups. A delivery quantity changes. Incoterms get updated. A batch number shifts. In a disconnected landscape, every such change requires manual communication and reconciliation across both systems. This is a leading cause of shipment delays and invoice disputes. ASR introduces structured change management. EWM and TM each evaluate whether a change is permissible at the current process state, and the system enforces consistency throughout.
Stock transport order (STO) integration extends ASR across your own network. Whether goods are moving from an IM-managed warehouse to an EWM-managed one, or between any combination of warehouse types, ASR now supports the full STO inbound scenario. That’s particularly valuable for companies managing distribution networks across multiple facilities. The warehouse and transportation processes stay synchronized regardless of which warehouse system is managing each leg.
Kit-to-order (KTO) processes in assembly-based fulfillment models where products are built from components at order time are fully supported across all three process variants: warehouse-driven, transportation-driven, and late transportation-driven delivery order split triggered at loading completion, with item hierarchies remaining consistent end-to-end. Configure-to-order operations can now benefit from the same unified execution model as standard shipments.
Cargo Ready for Loading introduces a precise status signal at the loading point level of the freight order, one that bridges the operational world of the warehouse floor with the compliance world of customs. When cargo at a loading point reaches this status, SAP Global Trade Services (GTS) can be triggered automatically initiating customs invoice requests and export declarations without waiting for the full truck to be loaded. For businesses dealing with complex multi-leg or multi-country shipments, this dramatically reduces dwell time at outbound gates while maintaining regulatory compliance. Extensibility options give businesses with complex compliance requirements more precise control over this process, governing which product items enter the GTS compliance check and how the aggregated result is determined.
What to ask when evaluating logistics platforms
The capabilities described in this post aren’t the result of integration engineering. They’re the result of an architectural decision made at the foundation. If you’re in the process of evaluating logistics platforms, the vendor selection question worth holding onto isn’t, “how tightly can your WMS and TMS be connected?” It’s, “do these two systems share a common execution model or are they still, at their core, resolving the same data in two different places?”
Any roadmap built on “better connections between separate systems” is, by definition, building on the seam that creates the problem. Tighter integration reduces friction; it doesn’t remove the architectural gap. That distinction determines not just how the system performs on day one, but how it holds up when conditions change, delivery quantities shift, and decisions need to be made in real time across warehouse and transportation simultaneously.
With ASR, the answer is built into the architecture, and the story doesn’t end at the warehouse gate.
Coming in Part 2: Beyond the four walls
SAP Product
Your truck is waiting. Here’s why?
Why tighter integration is not the answer and what unified execution looks like.
manual
link-target-same
secondary