SAPFree calculatorPDF, Excel, Word exportSAP EWMWarehousing

SAP EWM Wave Release Sizing Calculator

Wave size is the main lever in outbound flow: big waves load the floor and risk missing cutoffs, small waves cause idle time and extra travel. This tool lets you test wave counts against labor and the time window before you change the wave templates.

Your numbers

orders
lines
4 waves

Number of releases created from your wave templates in a day.

lines/hr
people
hours

Time between wave release and the carrier cutoff or next wave.

Your results

Wave duration with current team
1 hrs
Time for the team to clear one wave.
Pickers to finish inside the window
6
Lines per day
4,200
Lines per wave
1,050
Slack against the window
1 hrs
Negative means the wave overruns its window.

Assumes work is spread evenly across waves and all pickers work every wave. Real waves vary by zone and pick type.

Save results:

Wave duration and pickers needed vs waves per day

Sweeps Waves per day from 1 to 12, holding your other inputs fixed.

Wave performance reporting from SAP

An optional review of how to report wave completion, cutoff misses and idle time from warehouse orders.

Optional. The tool and every export work without this. No spam.

How to use it

Enter daily orders and average lines per order, then choose how many waves you plan to release. Add the pick rate per picker and the number of pickers on shift, and the window you have from release to the cutoff. The tool returns the lines per wave, how long the current team needs to clear a wave and how many pickers you would need to finish inside the window. Slide the waves per day input to see the trade-off. The chart plots both duration and required headcount across one to twelve waves.

The math

Lines per day equal orders times lines per order, and lines per wave equal that divided by waves. Wave duration equals lines per wave divided by the combined pick rate of the team. Pickers needed for the window equal lines per wave divided by pick rate times window hours, rounded up. Slack is the window minus the duration. Because total work is constant, adding waves does not reduce total labor, it only smooths the peak and changes how many people must be busy at once.

  • Lines per wave = orders x lines per order / waves
  • Duration = lines per wave / (rate x pickers)
  • Pickers for window = ceiling of lines per wave / (rate x window)

Mapping to SAP EWM configuration

In EWM, wave templates define selection criteria, release methods and the maximum number of items or other limits for a wave, and the outcome is warehouse orders grouped for pickers. Use the lines per wave figure to set sensible item limits and the number of release times in your job schedule. For classic WM, the same reasoning applies to grouping of deliveries with group-based picking. Always test with a day of real volume before locking the template.

Common mistakes

Do not size waves on average days alone: carrier cutoffs create a fixed deadline, so late arrivals of orders compress the window. Avoid releasing a wave when the previous one is not yet half finished, which causes aisle congestion. Do not ignore replenishment: if pick faces empty in the middle of a wave, the effective pick rate drops. Finally, pick rate should come from measured data by zone, not from the picking vendor's brochure.

Frequently Asked Questions

More waves or fewer waves?

More waves smooth the workload and shorten the lead time for each order, but increase release overhead and can split orders across waves. Start from the window and carrier cutoffs, then pick the smallest number of waves that fits.

Does this replace EWM wave management settings?

No. It informs the settings. You still configure wave templates, release methods and limits in the system. The tool gives the target sizes to test.

How do I get the pick rate?

Use confirmed warehouse tasks per user per hour for the relevant pick type and zone from a normal week. Remove unusual days and split piece picking from case and pallet picking.

What if different zones have different rates?

Run the calculator once per zone with that zone's lines and rate. The slowest zone usually defines when the whole wave is complete.

If you want wave performance, cutoff misses and picker idle time reported from your SAP warehouse orders on your own servers, we can build that reporting layer.