1.41.0 - Release notes 2 March 2026
Introduction
This release focuses on strengthening operational control, integration accuracy, and automation reliability across the platform. We are introducing intelligent safeguards that ensure replenishment behavior aligns precisely with strategic inventory movements, while simultaneously improving the integrity of stock data flowing into WAIR.
With the introduction of automated recall handling, replenishment can now be intentionally and systematically halted during end-of-season transitions, eliminating manual intervention and preventing unintended reactivation. At the same time, enhanced stock API capabilities enable more accurate full-load processing and historical stock corrections, ensuring your inventory positions remain consistent, auditable, and aligned with ERP reality.
Together, these improvements reduce operational risk, increase trust in automation, and provide greater precision in both strategic inventory decisions and system integrations.
TL;DR:
🔁 Automatic Style Deactivation for Recall Transfers – Automatically deactivate styles for shipping locations when transfers to configured recall destinations are imported, ensuring replenishment stops immediately and cannot be reactivated by existing automation rules.
📦⏱️ Full-Load & Time-Based Stock Corrections on POST /Stock – Interpret missing SKU/location combinations in full ERP exports as zero stock and align inventory levels to a specific historical moment using stockDateTime for precise, auditable corrections.
Replenisher:
Use case
As a replenishment manager, you regularly execute end-of-season recalls where inventory is transferred from stores to a central recall location (e.g., DC or clearance hub). Once a recall starts, replenishment must stop immediately for the affected shipping locations. Previously, this required manual deactivation of styles and manual adjustment of stock targets per location. During large recalls, this process was time-consuming and prone to errors, with the risk of incomplete updates or unintended reactivation later on.
Solution
We introduced Recall Automation within the Replenisher settings. This feature allows you to define one or more recall destination locations. When a transfer to one of these configured recall locations is imported into WAIR, the system automatically deactivates the entire style for the shipping location
This ensures replenishment stops immediately and intentionally, giving you full control during seasonal transitions and strategic inventory moves.
How it works
Navigate to Replenisher → Context.
Enable the Recall Automation toggle and select one or more Recall Destination Locations.
From that moment onward, whenever a transfer to one of the selected recall locations is imported into WAIR:
The style is automatically deactivated for the shipping (from) location
Previously set Activation Automation rules will not overwrite the Activation status
The logic applies at location/style level, ensuring the entire style is stopped for that location, even if only part of the inventory is recalled.
A dedicated Recall History page is available when the feature is enabled, providing a clear, read-only overview of all automated recall actions for audit and review purposes.
.png?sv=2022-11-02&spr=https&st=2026-04-05T07%3A33%3A19Z&se=2026-04-05T07%3A46%3A19Z&sr=c&sp=r&sig=gEvNtNDnBZBKBZTHZEL2B0YVSoa1qzEZIagGCcgsbuQ%3D)
API
Full-Load & Time-Based Stock Corrections on Stock API
Use case
In many ERP systems, full stock exports do not include SKU/location combinations with zero stock. Without special handling, this can result in outdated stock levels remaining active in WAIR.
Additionally, there are scenarios where stock needs to be corrected retroactively based on a specific moment in time. Without time-based correction logic, it is difficult to ensure stock levels are aligned precisely to a historical reference point.
Solution
We enhanced the POST /Stock endpoint with two major improvements:
Support for full-load stock updates
Time-based stock corrections using a stockDateTime reference
With full-load support, missing SKU/location combinations in an import are interpreted as zero stock. If a SKU/location currently has stock in WAIR but is not included in a full-load update, the system will automatically correct it back to zero — whether the current stock is positive or negative.
With time-based corrections, stock levels are aligned to the provided stockDateTime. The system recalculates stock positions up to that specific moment and adjusts only the relevant quantities.
Coming Soon 🎉
🎨 Initial Distributor Redesign & Improvements – We are currently working on a major design update and functional enhancements for the Initial Distributor. In the coming weeks, you can expect a more intuitive workflow, improved usability, and stronger decision support to streamline your initial allocation process even further.