Here is the verdict up front: wave release timing is not a race to release as early as possible, and it is not a game of waiting until the last minute to squeeze in more orders. The release point has to sit between two boundaries. The early boundary is when orders and inventory are mostly ready. The late boundary is when picking, packing, and shipping can still make the carrier pickup. My method is to work backward from the pickup time, subtract real pick and pack time, add a buffer, and hold the wave behind an order-completeness threshold until that threshold is met. I have watched this go wrong three times, always the same way: someone optimized for one metric and the other side of the operation fell apart.

What Goes Wrong When You Release a Wave Too Early

In October 2024, I was supporting a go-live at a 3PL warehouse in Ontario, California, moving a few thousand orders a day on two-hour waves. One morning the operations manager released the 9 a.m. wave half an hour early because pickers looked idle. Two or three hundred orders went out, and dozens of them had stock that had not been put away yet. The previous night's receipts were still sitting in the receiving area, uncounted. Pickers pushed carts to the locations, found nothing to scan, and came back empty-handed, while the system held those tasks open and the next wave piled in behind them.

The worse damage was fragmentation. Orders from the same customer were split across two or three waves, so the pack bench had to find the same boxes and labels over and over, and more than a dozen orders nearly shipped without a proper verification step. We froze the rest of that wave, rebuilt it around what was actually complete, and only then caught the day's cutoff. After that, the site set a hard rule: check completeness before release and accept a smaller wave rather than sending pickers on empty trips.

Early release costs are easy to miss. An empty trip still counts as a completed task in the system, so the report looks fine while real picks per person quietly drop. The most dangerous part is that early release hides the real problem: stock that is not put away should surface as a receiving issue, but early release spreads it into picking instead, so nobody owns it and nobody fixes it at the source.

What Goes Wrong When You Release a Wave Too Late

Late release fails louder: you miss the carrier pickup. In the summer of 2023, a home-goods e-commerce warehouse had a 5 p.m. carrier pickup every day, and the team habitually released the last wave at 3:30 p.m. to collect more orders. The logic sounded right; the math was wrong. Picking and packing needed well over two hours, so a 3:30 release finished after 5:30. The truck left on time, and the rest of the freight waited until the next day. During a promotion week the backlog rolled for three days, customer service was overwhelmed, and the client paid out of pocket for expedited shipments to make it right.

I have seen this same script three times. Day one, overtime covers the gap. Day two, overtime stops working. Day three, the delivery promise breaks. Overtime is not a fix: after two or three extra hours, picking errors climb visibly, and the next day someone calls in sick, so staffing is even tighter. Late release also poisons the next morning, because every order past the cutoff piles into the first wave and overloads the whole day from the start.

How to Set Wave Release Timing: Four Inputs, Worked Backward

I set release timing from four inputs: the order cutoff, the carrier pickup time, real pick and pack capacity, and the shape of the order pool. Pickup time is the hard boundary, the cutoff is the softer one, capacity decides how big a wave can be, and order shape decides how early a wave should go.

Input How to set it What happens if you get it wrong
Carrier pickup time Use the contracted pickup time, minus loading and handover time You miss the truck and today's freight becomes tomorrow's
Order cutoff Use the published cutoff, with time for the system to process it Orders past cutoff pile up and overload the first wave next day
Pick and pack capacity Use measured hourly pick lines and pack volume, not vendor theory Waves too big never finish; waves too small leave people idle
Order structure Look at lines per order, completeness rate, and large-order share Fragmented orders released early mean empty trips and split waves

The calculation runs in four steps.

Step one, set the late boundary. Take the pickup time, subtract pick and pack time, then subtract a half-hour buffer. Example: pickup at 5 p.m., two hours of pick and pack, half an hour of buffer — the wave must go by 2:30 p.m. Releasing after that means accepting overtime or a missed truck, and the client should hear about it before the truck leaves, not after.

Step two, set the early boundary from completeness and order arrival. My threshold is that more than eight in ten order lines in the target wave are complete and the stock is on the shelf before release. If completeness is short, wait for the next wave. Do not comfort yourself with "pick what we have and backfill the rest" — a backfilled order costs an extra pick trip and an extra verification pass, far more than waiting half an hour.

Step three, size the wave by capacity: only what picking and packing can actually finish between release and pickup. Use measured output from the same time of day over the past two weeks, and take the conservative end of that range. Oversized waves spill into the next wave; undersized waves leave people and equipment idle.

Step four, lay out the daily wave schedule between the early and late boundaries, with handover gaps between waves. I usually plan three or four waves a day, with the first wave slightly later so overnight and morning orders have time to become complete, and the last wave pinned to the late boundary. Post the schedule at the control station. Nobody changes it on a feeling, because ad-hoc wave changes are where the chaos starts.

Here is the counterintuitive part: releasing waves more often does not mean higher efficiency. Many warehouses think an hourly wave is lean, but the more fragmented the waves, the more pick paths repeat and the more verification and packing switchovers cost. For a warehouse moving a few thousand orders a day, a two- to three-hour wave often costs less in total than an hourly one. People push back on this every time I say it, and the numbers usually settle the argument.

The Night-Before-Go-Live Checklist

This is the checklist I run on the night before every go-live. On wave timing, do not launch with any of these ten items missing.

  1. Carrier pickup time confirmed in writing, with a working channel for delay notices.
  2. Cutoff time published to customers, and the system cutoff configured to match it.
  3. Latest release time calculated, posted at the control station, and known by the shift lead.
  4. Completeness threshold configured in the system, so incomplete orders roll to the next wave automatically.
  5. Measured pick and pack capacity from the past two weeks on file, with theoretical vendor numbers removed.
  6. Daily wave schedule laid out in full, with handover gaps between waves.
  7. A separate backfill process for short picks that does not consume normal wave picking labor.
  8. Overtime triggers defined: when it starts, who approves it, and when it stops.
  9. Someone assigned to watch wave health, with authority to stop a wave if completeness drops half an hour after release.
  10. A rollback path: if the timing configuration is wrong, it can be reverted to the previous version within ten minutes.

One last practical point: a release schedule is not permanent. When the order mix changes, the carrier moves its pickup, or peak season arrives, recalculate it. I review the timing table monthly and build a separate version before peak. The sheet on the wall expires. The day pickers start running empty trips again, or the truck starts waiting on the warehouse, go back to that table first — it has probably expired.

By Lin Xiao, WMS Implementation Consultant