Waves built against your rules, released without a supervisor
Nearly every warehouse platform can batch orders. The question is what the batch is allowed to know - and for most of them the answer stops at sort order.
A sort is not a constraint
Typical batch settings let you group orders and sort them - by SKU, by bin, by order date, by required ship date. That is useful, and it is not the same thing as a rule. A sort decides the sequence of a batch that was already going to happen. A constraint decides whether the batch is allowed to exist at all: this picker should not be handed anything over 25lb, these two items must never travel in the same carton, this stock has to leave oldest-first. Sorting cannot express any of those.
What a wave can be told
Constraints the wave respects
- Maximum weight a single picker should be assigned
- Maximum orders in one wave
- Items that must never share a carton, per client
- Stock age, so the oldest cartons leave first rather than the newest
- Client-specific handling rules on a shared floor
What happens once it is built
- The wave accumulates as orders qualify for it
- It optimizes the pick path against the rules, not around them
- It releases itself when the release condition is met
- Short picks and exceptions surface against the wave, not a printed list
- Nothing waits on a supervisor noticing that it is time
Stock age is the one people underestimate
Shipping oldest-first sounds like a warehouse nicety until you carry anything dated, anything that discounts as it sits, or anything a client audits. Order date is the wrong proxy for it - the newest order can perfectly well be filled from the oldest carton, and usually should be. Driving release on stock age rather than order date is what makes first-in-first-out an actual property of the operation instead of an instruction on a laminated sign.
Why the enforcement matters more than the feature
Every warehouse already has these rules. They live in a supervisor's head, in a training session, and in the accumulated judgement of whoever has been there longest. That works until the person is on holiday, until volume doubles, or until a new client arrives with rules that contradict the old ones. Moving a rule from a person to the wave is not a nicer pick path - it is the difference between a rule your team remembers and a rule the system will not let them break. The ShipHero comparison goes through this row in detail, because it is the clearest gap between two platforms that otherwise overlap heavily.
Related capabilities
Wave and batch building: common questions
Batch picking groups orders so a picker collects several at once. Wave picking decides which orders may be grouped and when the group is released, against operational constraints such as picker capacity, item compatibility and stock age. Most platforms offer batching with sort options; far fewer let the grouping itself be governed by rules.
Yes, and on a shared floor that is usually the point. One client's items may never be co-packed while another has no such restriction, and the wave respects each client's rules within the same building without the picker needing to remember which is which.
They release themselves once the release condition is met. A wave accumulates qualifying orders, optimizes against the configured constraints and goes to the floor without a supervisor deciding it is time, which is what keeps throughput steady rather than lumpy across a shift.
Yes. Automatic release is the default behaviour rather than the only one, so an expedited order or a client escalation can be pushed through without unpicking the rules that govern the rest of the shift.
Wave building operates on the floor SKUPREME directs, so it comes with the warehouse layer rather than as a standalone module. Brands running another warehouse system usually adopt the two together when the batching in their current platform stops at sort order.
