Here's the downside; if you should batch is often dependent on a ton of factors. As a silly and simple example, this SQL would return all skus, including those with 2 orders, even if it's 5 minutes before cutoff. This is where a tool like Lully comes in; automatically decides with context of the warehouse and equipment state what your best methods are- then provides grouping and routing to optimize not just the an individual trip, but the entire operation

@Cedric Corbett Lully looks at all of the orders in the pool, available resources, and available methods/equipment- optionally in a continuous way- to construct real time operating plans that the WMS consume. Even in the simplistic deployment scenario, we'll prevent you from "over batching", not just through the lens of SLA adherence, but also efficiency. In a continous deployment, the scenario you described is one we can help operations mitigate.