Picking, packing, and shipping is where a Dynamics 365 Supply Chain Management warehouse either flies or stalls. It is the highest-volume, most labor-intensive part of the operation, and a poorly tuned configuration shows up immediately as long pick walks, stuck shipments, and frustrated floor staff. Here is how I think about an outbound wave and load strategy that holds up as volume grows, framed entirely around general use cases rather than any one operation.
Design from the shipment back to the waveIt is tempting to start with wave templates, but I find it more reliable to reason in the opposite direction: decide how you want to ship, then how loads should be built, and only then how waves release and structure the work. A shipment is goods leaving for a single delivery; a load groups shipments that travel together; the wave turns released order lines into pick work, replenishment, and allocation. Answer the physical questions first (full pallets to a dock or mixed cases to a parcel zone, cutoff times, carrier constraints) and the configuration follows naturally.
Keep a small number of clearly purposed, non-overlapping wave templates rather than a sprawling list nobody understands six months in. Each template's assignment query, automation settings, and ordered wave methods all matter, and the order matters most: replenishment has to run before work is created against forward pick locations. Many "no inventory available" errors are really a replenishment step sitting in the wrong place in the sequence.
Load building and consolidationLoad templates define the target vehicle and its weight and cube, so the system can build and consolidate loads automatically instead of relying on dock-side judgment. Define capacity honestly, decide where consolidation happens (by address, route, or carrier), and align wave scheduling with carrier pickup windows. An optimized load is worthless if its work releases after the truck has left.
Allocation, picker efficiency, and testingOutbound problems often trace back to when and how inventory is allocated, so align your reservation hierarchy, batch and serial rules, and FEFO with the location directives. When the directive and the allocation disagree, work cannot be confirmed on the device. Use work templates and location directives to group pick work by zone along a logical travel path, and validate everything against a realistic order mix (full pallets, mixed cases, parcels, near-expiry batches, short-shipped lines) before go-live. The bottlenecks you find in testing are far cheaper than the ones you find on day one.
Get these foundations right and the outbound process scales gracefully with volume. I would love to hear how others have approached wave and load tuning, especially where you have landed on automatic versus manual wave release.
Picking, packing, and shipping is where a Dynamics 365 Supply Chain Management warehouse either flies or stalls. It is the highest-volume, most labor-intensive part of the operation, and a poorly tuned configuration shows up immediately as long pick walks, stuck shipments, and frustrated floor staff. Here is how I think about an outbound wave and load strategy that holds up as volume grows, framed entirely around general use cases rather than any one operation.
Design from the shipment back to the waveIt is tempting to start with wave templates, but I find it more reliable to reason in the opposite direction: decide how you want to ship, then how loads should be built, and only then how waves release and structure the work. A shipment is goods leaving for a single delivery; a load groups shipments that travel together; the wave turns released order lines into pick work, replenishment, and allocation. Answer the physical questions first (full pallets to a dock or mixed cases to a parcel zone, cutoff times, carrier constraints) and the configuration follows naturally.
Keep a small number of clearly purposed, non-overlapping wave templates rather than a sprawling list nobody understands six months in. Each template's assignment query, automation settings, and ordered wave methods all matter, and the order matters most: replenishment has to run before work is created against forward pick locations. Many "no inventory available" errors are really a replenishment step sitting in the wrong place in the sequence.
Load building and consolidationLoad templates define the target vehicle and its weight and cube, so the system can build and consolidate loads automatically instead of relying on dock-side judgment. Define capacity honestly, decide where consolidation happens (by address, route, or carrier), and align wave scheduling with carrier pickup windows. An optimized load is worthless if its work releases after the truck has left.
Allocation, picker efficiency, and testingOutbound problems often trace back to when and how inventory is allocated, so align your reservation hierarchy, batch and serial rules, and FEFO with the location directives. When the directive and the allocation disagree, work cannot be confirmed on the device. Use work templates and location directives to group pick work by zone along a logical travel path, and validate everything against a realistic order mix (full pallets, mixed cases, parcels, near-expiry batches, short-shipped lines) before go-live. The bottlenecks you find in testing are far cheaper than the ones you find on day one.
Get these foundations right and the outbound process scales gracefully with volume. I would love to hear how others have approached wave and load tuning, especially where you have landed on automatic versus manual wave release.
No replies yet. Be the first to respond!