When creating a planned outbound load/truck in advance, gradually add sales orders with identical shipping details to the same load, and release those orders to warehouse as they become available.

In the current standard behavior, later-added sales orders can consolidate into an existing shipment only while the original shipment remains Open and eligible for consolidation. This was validated in a controlled repro: when wave auto-processing/release was disabled and the first shipment remained Open with no Wave ID or Work ID, the second sales order was successfully added to the same load and consolidated into the existing shipment, resulting in one load, two load lines, and one shipment.

However, this flow is not practical for customers who use Warehouse Management Mobile App execution and need warehouse workers to begin picking shortly after the first release. When the first sales order is released and the wave template automatically processes/releases the wave, the shipment moves into warehouse execution. At that point, later-added sales orders are no longer automatically consolidated into the existing shipment; instead, D365 creates a separate shipment even when the sales orders share the same customer, address, warehouse, shipment consolidation policy, and load.

The requested enhancement is to support a standard WMS-compatible flow where additional sales orders can be added to an existing planned load/shipment after initial wave/work execution has started, with the system either creating additional wave/work for the newly added lines or providing a controlled setup option to determine how follow-up wave/work should be generated for consolidated additions.

This results in multiple shipments and potentially multiple delivery notes for what the business considers one physical truck delivery to the same customer/address, creating additional manual effort for warehouse and shipping teams, because users must either delay wave/work creation until all orders are known, manually review/consolidate shipments where possible, or handle separate shipments for the same truckload. Delaying wave/work creation is not always operationally practical because warehouse workers may need to start picking through the Warehouse Management Mobile App before the full truckload is finalized.

The current limitation therefore creates a gap between shipment/load planning and WMS execution. The business needs a supported process that allows incremental order additions to planned truckloads while still maintaining accurate, traceable wave/work execution for warehouse users.