To ensure peak performance during high-volume operations, Logiwa IO has introduced two significant enhancements to the Wave Rule engine: Pre-Flight Inventory Checks and Max Orders per Wave Caps. These updates reduce processing time and prevent system bottlenecks.
1. Pre-Flight Inventory Availability Check
The Pre-Flight Check is a filtering layer that identifies out-of-stock orders before the system performs heavy resource calculations.
How It Works
SKU Gathering: The system identifies all SKUs required for the eligible batch of orders.
Availability Check: A rapid query checks if the required SKUs are in stock.
Immediate Skipping: If a required SKU has zero (0) availability, the order is "skipped" immediately.
Optimized Processing: Only orders with available stock proceed to allocation and routing logic.
Tracking "Fast Skipped" Orders
When an order is bypassed by the Pre-Flight check, you can track it in two primary locations:
A. Allocation Exceptions
Orders that do not pass the initial availability check will appear here with a clear explanation.
Path:
Home > Orders > Allocation Exceptions.Explanation Column: Displays "Insufficient Inventory - Fast Skipped".
B. Shortage Report
For a more detailed view of the specific products causing the skip, refer to the Shortage Report.
Path:
Home > Reports > Shortage Report.Shortage Reason Column: Displays "Insufficient Inventory".
Functionality: This allows you to quickly see which SKUs are blocking the orders from being waved.
2. Max Orders per Wave (Processing Caps)
To maintain system stability, Logiwa now implements a hard limit on the number of orders evaluated during a single wave run.
How It Works
Prioritization: The system generates a candidate list based on your Wave Rule "Order By" logic (e.g., Ship Date).
Capping: A default limit of 15,000 orders is selected for evaluation per run.
Automatic Rollover: Remaining eligible orders beyond the cap are automatically deferred to the next scheduled run.
Merge Order Wave Rules — Fixed Ordering
For Order Merge Wave Rules, the 15,000 order cap always selects the oldest eligible orders first, based on order created date — regardless of the wave rule's configured "Order By" setting. This guarantees older orders are never repeatedly passed over in favor of newer ones.
This matters because Order Merge Wave Rules must complete before Picking Waves or AI Job Optimization Waves can run — they can't execute at the same time. Keeping each merge wave's processing bounded and predictable helps avoid delaying downstream picking work.
This cap is independent of the existing limit of 50 original orders per merged order. The 15,000 cap controls how many orders enter the wave; the 50-order limit controls how many of those can be grouped into a single merged order. Both apply, but at different stages, and neither overrides the other.