1.43.0 - Release notes 30 March 2026

WAIR - Customer portal

Introduction

This release focuses on making the Customer Portal more flexible, scalable, and easier to manage for both daily operations and larger retail networks. In Replenisher, we are improving proposal quality by removing low-value stop proposals, giving teams more control over when replenishment jobs run, expanding push strategy flexibility, and making reserved stock easier to manage. We are also introducing stronger group-based workflows through style groups, location clusters, and bulk location handling, helping users maintain automation and location structures more efficiently at scale.

Alongside these operational improvements, user access has also been simplified. Key Users can now work across the main workspace and assigned workspaces within a single account, reducing the need for duplicate user setups and making workspace access easier to manage

TL;DR:

🧭 Style Groups and Location Clusters in Replenishment Automation — Replenishment automation rules can now be configured using style groups and location clusters, making automation easier to maintain at scale.

⚙️ Per-Job Calculation Day Offset — Each replenishment engine job can now use its own calculation day offset, making it easier to align proposal timing with different delivery schedules.

📉 Prevent Stop Proposals Without DC Stock — Stop proposals are no longer generated for SKUs with no DC stock, helping users focus on proposals where action can make a real difference.

📈 Expanded Push Strategy Levels — Two additional push levels have been added, giving merchandisers more flexibility to push stock more aggressively where needed.

🗂️ Bulk Paste for Large Location Clusters — Large predefined location lists can now be handled more efficiently when building and managing location clusters.

🔒 Has Reserve Stock Filter — A new filter in Replenishment Overview makes it easy to find styles that have reserved stock.

🔑 Key User Access Across Workspaces — Users with the Key User role can now access the main workspace and assigned workspaces within the same account.

Replenisher:

Per-Job Calculation Day Offset for Replenishment Engine Jobs

Replenishment managers sometimes need different replenishment engine jobs to generate proposals for different delivery days at different moments. Previously, all jobs shared one global calculation day offset, which meant that customers with mixed delivery schedules could not align proposal generation correctly for every job.

This became especially problematic when combined with the 16-hour cancellation window: proposals generated too early could be cancelled before the team had a chance to review them.

Solution

The replenishment engine now supports a separate calculation day offset per job.

How it works

Each replenishment engine job can now store its own calculation day offset value.
When a job runs, the engine first checks whether that specific job has its own offset configured:

If a job-specific offset is set, the engine uses that value
If the field is left empty, the engine falls back to the existing global setting

The engine settings screen in the portal now includes this offset field per job, alongside the existing schedule and timezone settings.
This allows customers to configure different jobs for different delivery rhythms. For example:

a Friday evening job can use an offset for Monday delivery proposals
a Monday evening job can use a different offset for Tuesday delivery proposals

Prevent Stop Proposals for SKUs Without DC Stock

Use case

Merchandisers want stop proposals to focus on situations where a decision can actually make a difference. Previously, stop proposals could still be generated for SKUs with no DC stock. In those cases, approving or rejecting the proposal had little practical impact, because there was no available stock to replenish anyway.

This created unnecessary clutter in the proposals view and made it harder to identify the proposals that were truly relevant.

Solution

Stop proposal generation has been refined so that SKUs without any DC stock are no longer included in stop proposals.

How it works

When the system evaluates SKUs for stop proposal creation, it now checks whether DC stock is available.
If the DC stock for a SKU is 0, no stop proposal will be generated for that SKU.
This keeps the proposals view cleaner and helps merchandisers focus on proposals where action can have a real operational effect.

Expanded Push Strategy Intensity Levels

Use case

Replenishment managers sometimes need to push stock more aggressively for specific styles than the existing push strategy levels allow. Previously, the available push levels could be too limited in situations where customers already used elevated push settings broadly and needed an even stronger push for selected products.

Solution

Push strategy intensity levels have been expanded to provide more flexibility when increasing stock targets.

How it works

Two additional push levels have been added on top of the existing levels, giving replenishment managers a wider range of intensity options when configuring push strategies. The impact preview has been updated to show the projected stock target effect for all available levels, including the newly added higher options.
The push strategy overview also displays the correct label and visual indicator for the expanded intensity range, so existing and newly created strategies remain easy to interpret. This gives replenishment managers more flexibility to apply stronger push settings where needed, while keeping the setup and monitoring experience consistent across the portal.

Bulk paste for Large Location Clusters

Use case

Some retailers operate very large store networks with thousands of locations. In these environments, users often work with predefined lists of store codes from external systems or spreadsheets when grouping locations into store clusters. Previously, workflows that required selecting stores one by one could become slow, cumbersome, and error-prone, especially when working with large location sets.

Solution

Location management now better supports bulk workflows for large predefined location lists, making it easier to associate many stores with a cluster in a single process.

How it works

Users can now work more efficiently with large groups of store codes when defining store clusters.
This makes it possible to match large predefined location lists against existing locations in the system and use them within a single workflow, instead of relying on individual manual selection.
As a result, cluster management becomes faster and more scalable for retailers with large store networks, while reducing the risk of mistakes when handling long location lists.

Has Reserve Stock Filter in Replenishment Overview

Use case

Merchandisers and planners sometimes need to review styles that have a reserve quantity set, so they can quickly manage stock that has been excluded from replenishment. Previously, there was no easy way to identify these styles in the Replenishment Overview, which meant users had to scroll through the full list to find them.

Solution

A new Has Reserve Stock filter has been added to the Replenishment Overview

How it works

Users can now filter the Replenishment Overview to show only styles that have reserved stock.
When the filter is set to Yes, the overview only shows styles where at least one variant has a reserve quantity configured.
When the filter is not applied, the overview continues to behave as it did before.
The filter works together with the existing overview filters, such as brand, category, and season, and can also be saved as part of a custom or quick filter. This makes it much easier to review and manage reserved stock without having to search through the full overview manually.

Style Groups and Location Clusters in Replenishment Automation Rules

Use case

Replenishment automation rules are often managed around business groupings rather than individual styles or locations. Previously, users could only configure these rules with individual filters such as locations, styles, brands, or categories. This made automation more difficult to set up and maintain, especially when group membership changed over time.

Solution

Replenishment automation rules now support both style groups and location clusters as filter options.

How it works

When creating or editing a replenishment advanced automation rule, users can now select one or more style groups and one or more location clusters as part of the rule definition. These can be used alongside the existing replenishment automation filters, allowing users to combine group-based and individual criteria in a single rule.

The rule automatically follows the maintained membership of the selected style groups and location clusters. This means that when styles or locations are added to or removed from those groups, future automation runs automatically reflect the updated membership without requiring the rule to be rebuilt. This makes replenishment automation easier to manage at scale and aligns rule configuration more closely with how assortments and store groupings are already organized elsewhere in the portal.

General:

Key User Access Across Main and Assigned Workspaces
Use case

Users sometimes need access to both the main workspace and one or more assigned workspaces. Previously, this was not possible within a single account setup, which meant that some users had to work with multiple accounts depending on where they needed access.

Solution

User access management has been updated so that users can now access both the main workspace and assigned workspaces within the same account, provided they have the Key User role assigned in the user management view.

How it works

When a user is assigned the Key User role, that user will also receive access to the main workspace in addition to any assigned workspaces.
This makes it possible to work across the main workspace and assigned workspaces without needing separate accounts, reducing account duplication and making user access easier to manage.

1.43.0 - Release notes 30 March 2026