1.38.0 - Release notes 19 Jan 2026

WAIR - Customer portal

Introduction

This release focuses on improving operational control, clarity, and consistency across Replenishment, Redistribution, and core platform configuration. We introduce stronger warehouse capacity controls, clearer monitoring alerts, richer proposal filtering and exports, and streamlined workflows by removing redundant views.

In addition, this release improves day-to-day efficiency for merchandisers through smarter state persistence in Redistribution, clearer terminology with the introduction of Workspaces, and expanded API capabilities for more flexible data modeling and document automation. Together, these updates reduce operational friction, prevent configuration issues, and support more scalable integrations and workflows across teams.

TL;DR:

🏭 Warehouse outbound capacity limits – Define a maximum outbound transfer capacity per warehouse (DC) via a new Warehouse Settings tab to prevent operational overload and ensure executable replenishment plans.

🚨 Missing warehouse link alerts – Clear alert cards in Replenisher Monitoring highlight locations without a warehouse or cluster link, with the ability to assign one directly or mark No warehouse required.

📦 Merchandise category in proposals export – Added merchandise category to the Replenishment Proposals export for faster validation, filtering, and cross-team operational alignment.

🗂️ Filter proposals by Season & Collection – New filters allow merchandisers to focus on relevant assortments using season and collection codes and descriptions.

🧹 Initial Activation removed – All functionality is now consolidated into Replenishment Operations and the Stock Targets pop-up for a single, consistent workflow.

🔁 Redistribution view remembered – The last selected redistribution view is retained when switching styles, reducing repetitive toggling and speeding up reviews.

🏷️ Sub-tenants renamed to Workspaces – Clearer terminology across the platform, with no functional changes.

🧬 SKU-level season, brand, theme & collection – Extended data model supports these attributes at SKU level with full backward compatibility.

📄 Redistribution PDFs via API – New API endpoints allow integrators to list and download redistribution proposal PDFs for automated logistics and ERP workflows.

Replenisher:

Define maximum outbound transfer capacity per warehouse (DC)

Use case
As a supply chain planner or operations manager, you want to control how much stock can leave a warehouse on a given day. Without clear limits, outbound transfers can exceed operational capacity, leading to congestion, delays, and reduced warehouse performance.

Solution
We introduced the ability to define a maximum outbound transfer capacity per warehouse (DC) in the Delivery Settings. To support this, a dedicated Warehouse Settings tab has been added. This allows teams to manage outbound capacity limits per warehouse in a clear, structured way, helping prevent operational overload and ensuring more realistic, executable replenishment plans.

How it works

• Navigate to Replenisher → Delivery Settings

• Open the new Warehouse Settings tab

• Set the Max Outbound Capacity per warehouse

• The replenishment engine respects this cap when creating outbound transfers

This gives operations teams better control over warehouse throughput, reduces the risk of overloading DCs, and aligns replenishment execution with real operational constraints.

Please note the Max capacity per replenishment engine job has been removed

Alert when no warehouse or warehouse cluster is linked to a location

Use case
As a planner or admin, you want immediate visibility when a location is not linked to a warehouse or warehouse cluster. Missing links block replenishment proposals & stop replenishment proposals and often go unnoticed until transfers fail or data looks incomplete, causing unnecessary delays and manual follow-up.

Solution
We added a clear alert card in the Replenisher Monitoring that highlights locations without a warehouse or warehouse cluster link. The alert not only explains what is missing, but also allows users to resolve the issue directly from the alert itself. For locations that do not require replenishment from a warehouse, users can explicitly indicate that no warehouse is needed.

How it works

• An alert appears in Replenisher Monitoring when a location has no warehouse or warehouse cluster linked

• Each alert clearly states what is missing and why it blocks replenishment

• Users can assign a warehouse or warehouse cluster directly from the alert card

• Users can also select No warehouse required for locations that do not need a warehouse link

• When No warehouse required is selected, the alert is resolved and no longer shown

• A shortcut to Location Settings is available for managing links in bulk

This ensures configuration issues are resolved quickly, avoids unnecessary alerts for non-replenished locations, and keeps the monitoring view clean and actionable.

Merchandise category added to Replenishment Proposals export

Use case
As a merchandiser, you use the Replenishment Proposals export to review, validate, and operationally manage proposed transfers together with the merchandising planning team. Without the merchandise category included, proposals lack important context, making analysis, filtering, and alignment across teams more time-consuming.

Solution
We added the merchandise category to the Replenishment Proposals export. This provides additional product context directly in the exported data, enabling faster validation, clearer communication, and more efficient operational follow-up within merchandising and planning workflows.

How it works

• Export Replenishment Proposals as usual

• The export now includes a Merchandise Category column per proposal

• The category can be used for filtering, grouping, and validation in external tools (e.g. Excel or BI)

This improvement makes replenishment exports more informative and easier to use in cross-team operational processes.

Filter Replenishment Proposals by Season and Collection

Use case
As a merchandiser, you want to quickly focus on replenishment proposals that are relevant for the current assortment. When proposals for different seasons or collections are mixed together, it becomes harder to review, validate, and act on the right items in a timely manner.

Solution
We added Season and Collection filters to the Replenishment Proposals page. These filters make it easy to narrow down proposals based on assortment context, allowing merchandisers to work more efficiently and with better focus.

How it works

• Open the Replenishment Proposals page

• Use the new Season filter, which includes both season code and season description

• Use the Collection filter, which includes both collection code and collection description

• The proposals list updates instantly based on the selected filters

This helps merchandisers quickly isolate relevant proposals, reduces noise from out-of-scope assortments, and speeds up operational decision-making.

Initial Activation view removed

Use case
As a user, you want a consistent and streamlined way of working within Replenisher. Having multiple entry points for the same actions—such as the Initial Activation view alongside Replenishment Operations and Stock Targets—created overlap and confusion about where certain functionality should be used.

Solution
We removed the Initial Activation view. All functionality that was previously available in Initial Activation is now fully supported within the Replenishment Operations view and the Stock Targets pop-up. This ensures a single, consistent workflow for managing replenishment-related actions.

How it works

• The Initial Activation view is no longer available

• All related functionality can now be found in:

  • Replenishment Operations overview

  • Stock Targets pop-up

• Users perform the same actions through these unified entry points, without loss of functionality

This change reduces duplication, improves clarity, and ensures that all users follow the same operational flow when working with Replenisher.

Redistribution:

Remember last selected redistribution view across styles

Use case
As a merchandiser, you work through many styles in the Redistribution flow and frequently switch between different views (e.g. Future vs Current state, Current stock, Sales last 6 weeks). When the view resets for each style, you have to repeat the same toggle over and over, which slows down decision-making and breaks your workflow.

Solution
We improved the Redistribution experience by remembering the last selected view while you navigate between styles within the same redistribution session. This effectively allows users to work with a consistent “default” view without having to reselect it for every style.

How it works

• Select your preferred view from the view selector (e.g. Future vs Current state)

• When switching to the next style within the same redistribution session, the system keeps your last selected view

• The chosen view is automatically loaded for each subsequent style, until you change it again

This reduces repetitive toggling, keeps the workflow consistent, and helps merchandisers move faster through style reviews.

General:

Sub-tenants renamed to Workspaces

Use case
As an administrator, you want clearer terminology when managing environments within the platform. The term sub-tenant was technical and not always intuitive, making it harder to understand its purpose and explain it to other users.

Solution
We renamed Sub-tenants to Workspaces across the platform. This change clarifies that these entities represent separate working environments or operational scopes, without altering any underlying behavior or permissions.

How it works

• The term Sub-tenant has been replaced by Workspace throughout the application

• This includes UI labels, navigation, and references in configuration and management screens

• Functionality remains unchanged; only the naming has been updated

This improves clarity for administrators and users, while keeping existing setups and workflows fully intact.

API / Data model:
Season, Brand, Theme, and Collection moved to SKU level

Use case
As a merchandiser, you want to manage, filter, and display styles correctly when the same item code exists across multiple seasons or collections. When attributes such as season, brand, theme, and collection are only stored at item level, this limits flexibility and leads to incorrect grouping or filtering in the portal.

Solution
We extended the data model to support season, brand, theme, and collection at SKU level. This allows styles with the same item code to belong to different seasons, brands, themes, or collections, while remaining fully compatible with existing integrations.
If a field is not provided at SKU level, the system automatically uses the value from item level, as before

Retrieve redistribution proposal PDFs via API

Use case
As a logistics integrator or ERP partner, you want to automatically retrieve redistribution proposal PDFs for internal routing, documentation, or operational follow-up. Without an API-based way to list and download these files, teams must rely on manual portal actions, which slows down integrations and creates operational friction.

Solution
We added API support to retrieve redistribution pickrequest documents and download the associated PDF files from blob storage. Integrators can now query available redistribution pickrequests and programmatically fetch the PDFs for downstream processing.

• List available redistribution pickrequests (incl. document references)
  GET /api/v1/Communication/Pickrequests

• Download the PDF file from blob storage
  GET /api/v1/DownloadBlob