1.37.0 - Release notes 6 Jan 2026

Prev Next

A simple black shape resembling a partial circle or crescent moon. WAIR - Customer portal

Introduction

This release focuses on improving day-to-day operational efficiency and clarity across Replenishment, Redistribution, and Location monitoring. We introduce bulk and cluster-based delivery setting management, cleaner and more actionable location and style insights, and greater control over what information is shown in operational views.

In addition, usability improvements such as contextual tooltips, clearer navigation through renamed Context sections, and enhanced style-level actions help users work faster and with more confidence. Together, these updates reduce manual effort, improve focus during operational decision-making, and support more consistent configuration and data management across the platform.

TL;DR:

⚙️ Bulk edit delivery settings – Update delivery settings for multiple locations in one action, reducing manual work and ensuring consistent configuration across large location networks.

🗂️ Filter delivery settings by location cluster – Narrow down delivery settings to specific store clusters (e.g. regions, channels, store types) for faster, more focused management.

ℹ️ Informational tooltips on Location Insights – Added in-context explanations for key KPIs, making location performance metrics easier to understand and act upon.

📍 Improved Location Style view – A larger, clearer style detail view with per-style actions, infinite scrolling, cleaner size matrices, wider modals, and visible color codes for faster analysis and decision-making.

🔀 Toggle Net Sales & Distribution Probability in Redistribution – Control the visibility of Net Sales and Distribution Probability graphs to keep the redistribution overview clean and focused (hidden by default).

🧭 Settings renamed to Context – Solution-specific settings are now labeled as Context, making their purpose clearer and reducing confusion for administrators.

🔌 API delete endpoints added – New DELETE endpoints allow programmatic removal of Location Clusters and Subtenants for cleaner master data management.

Replenisher:

Bulk edit delivery settings for multiple locations

Use case
As an operations manager, you manage delivery settings for many locations. Updating values such as storage capacity, shipment limits, or transfer days one location at a time is time-consuming, repetitive, and increases the risk of inconsistencies—especially during onboarding, reorganisations, or seasonal changes.

Solution
We introduced a bulk edit capability in the Delivery Settings overview. Users can now select multiple locations and update delivery settings in one single action, ensuring faster and more consistent configuration across the network.

How it works

  • Select multiple locations directly from the Delivery Settings list

  • Use Select all visible based on the active filters or Clear selection when needed

  • Open the Bulk Update panel and choose which fields to update

  • Apply the changes to all selected locations at once

Filter Delivery Settings by location cluster

Use case
As an operations user, you often manage delivery settings for specific groups of stores, such as regions, outlets, webshops, or franchise locations. When all locations are shown in one long list, it becomes hard to focus on the relevant stores, increasing the risk of mistakes and slowing down operational work.

Solution
We added Store Cluster as a filter to the Delivery Settings overview. This allows users to quickly narrow down the list of locations to a specific cluster and manage delivery settings in a more structured and efficient way.

How it works

  • Use the new Store Cluster filter in the Delivery Settings view

  • Select one or multiple clusters

  • The list updates instantly to show only the locations within the selected clusters

This makes it easier to manage delivery settings for logical groups of locations and ensures a faster, less error-prone workflow.

Informational tooltips on Location Insights

Use case
As a user, you want to better understand the metrics shown in Location Insights without leaving the page or consulting external documentation. When KPIs such as Sales per m², Turnrate, or Rolling Year Performance are not fully clear, interpretation can differ and insights become less actionable.

Solution
We added informational tooltips to key metrics in Location Insights v2. These tooltips explain what each metric represents and how it should be interpreted, providing immediate context directly in the interface. This makes insights easier to interpret, reduces ambiguity, and helps users make faster, more confident decisions based on location performance.

Improved Location Style view in the new Location Overview

Use case
As a merchandiser or operations user, you work with the Location Overview to analyse and manage styles at a specific location. The previous Location Style view was compact and required extra clicks, scrolling, and interpretation, making it harder to quickly take action or read size-level data.

Solution
We enhanced the Location Style view to improve readability, usability, and actionability, making it easier to analyse styles and act directly from the overview.

How it works

  • Larger Location Style view
    The style detail panel has been expanded to better display sales, inventory, and size-level information.

  • Actions per style

    • Added a three-dot menu per style in the scrolling list with:

      • Deactivate style: deactivates the location–style combination

      • Create push strategy: redirects to the push strategy flow

    • These actions are also available directly in the style detail overview.

  • Cleaner size matrix

    • Zero values are no longer shown as 0

    • Empty cells are displayed instead, improving visual clarity.

  • Infinite scrolling

    • Removed the Load more button

    • Styles now load automatically while scrolling.

  • Improved modal layout

    • Pop-up modals have been widened to use more screen space, making complex information easier to read.

  • Color code visibility

    • Added the color code alongside the color description, giving clearer product identification at a glance.

Redistribution:

Toggle Net Sales and Distribution Probability visibility

Use case
As a merchandiser, you use the Redistribution (RD) operations overview to make fast, short-term decisions. Depending on your workflow, detailed graphs like Net Sales and Distribution Probability can add noise and reduce focus. You want control over what is shown, so you can keep the overview clean and relevant.

Solution
We added visibility toggles for Net Sales and Distribution Probability in the settings. This allows merchandisers to decide whether these graphs are shown in the RD operations overview. Please note that both graphs are currently hidden by default.

How it works

  • Navigate to the Context → General → Operation View for Redistribution

  • Toggle Show Net Sales card on or off

  • Toggle Show Distribution Probability card on or off

  • The RD operations overview updates immediately based on your selections

This gives users a cleaner, more focused redistribution view while keeping advanced insights available when needed.

General:

Rename solution settings to Context

Use case
As an administrator, you manage configuration per solution (Replenisher, Redistribution, Initial Distributor, Product Describer). The label Settings was ambiguous and did not clearly reflect that these configurations define the operational context in which each solution runs.

Solution
We renamed Settings to Context for each individual solution. This makes it clearer that these sections control solution-specific assumptions, inputs, and behavioral configuration rather than general system settings.

How it works

  • The rename applies only to settings per solution

  • Each solution now contains a Context section instead of Settings

API:
Delete endpoints added for Location Clusters and Subtenants

Change
New DELETE endpoints have been added to support the removal of Location Clusters and Subtenants via the API.

Added endpoints

  • DELETE /api/v1/LocationCluster

    • Query parameter: StoreClusterId

  • DELETE /api/v1/SubTenants

    • Query parameter: SubTenantId