From Route Assignment to Goods Issue: A Cleaner Outbound Story in SAP EWM

Overview

A well-designed outbound process is less about isolated transactions and more about a sequence that warehouse and shipping teams can actually follow without friction.

Outbound is a chain, not a list of tasks

In the process model, outbound delivery orders are assigned to routes, grouped into waves, planned for cartonization, linked to transportation units, picked into pick-HUs, repacked into shipping HUs, staged, loaded, and finally posted for goods issue. What I like about this sequence is that it shows how EWM connects planning and execution instead of keeping them separate.

Where projects usually break

The first break is often between shipping office planning and warehouse execution. The second is between packing and staging. If a warehouse knows how to pick but does not receive the right packaging proposal, or if staging area and door determination are weak, the process technically works but operationally feels messy. Users start bypassing the design.

Why the TU step deserves more attention

Transportation unit creation is sometimes treated as a minor shipping detail. It is not. The TU provides the operational anchor for route, external identifier, door coordination, and departure control. If you want a disciplined outbound process, the TU step has to be visible in the design workshop and not buried in a later configuration discussion.

What good design looks like

Good design means that each handoff answers the next team's question. Shipping knows which truck capacity is needed. Picking knows which work list to execute. Packers know what shipping HU to build. Loaders know which door and TU to use. That is the standard I use when reviewing an outbound blueprint.

Quick takeaways

• Route, wave, TU, packing, and loading should be designed as one narrative.
• Weak handoffs cause more pain than missing transactions.
• A strong TU design improves door control and departure discipline.