1.35.0 - Release notes 8 Dec 2025

Introduction

This release focuses on improving how locations, stock, and replenishment logic are managed across the platform. We introduce clearer separation between store and warehouse structures, smarter stock allocation for multi-channel operations, and new controls that give merchandisers more influence over replenishment behavior.

These enhancements streamline configuration, reduce manual work, and ensure that stock decisions reflect operational reality. In addition, new rules and API capabilities strengthen the flexibility and consistency of core workflows, helping teams work more efficiently and with greater confidence.

TL;DR:

Store & Warehouse Clusters
🏭 Warehouse Assignment in Locations – Assign warehouses or warehouse clusters directly from Locations, with filters and bulk actions to update multiple stores in one go.
📂 Separate Store vs Warehouse Cluster Views – Manage store clusters and warehouse clusters in dedicated views, keeping forecasting groups and routing hierarchies clearly separated.
🔗 Shared Stock Locations – Map multiple sales locations (e.g. webshops) to one physical stock location so targets are calculated centrally and virtually split per channel.

Replenishment
💶 Minimum Order Value by Cost – Enforce a minimum order value based on cost price per location, with Off / Ask / Force modes and alerts for proposals below the threshold.
📏 Maximum Style Capacity per Store – Set a max capacity per style and let the engine block or warn on proposals that exceed it, helping prevent overstocking.

API
🧩 SubTenant Management – New /api/v1/SubTenants GET & PUT endpoints to retrieve, insert, or update SubTenants programmatically.

Location Performance Overview (Beta)
📊 A new consolidated view showing key KPIs per location, including turnrate, markdowns, sales trends, and inventory insights. Rolling out gradually during the beta phase.

Store & Warehouse clusters

Warehouse & Cluster Assignment for Locations

Use Case

Operations managers and system administrators need a fast, centralized way to assign warehouses or warehouse clusters to multiple store locations. Until now, this setup required repetitive, manual updates per location, making routing configuration time-consuming and error-prone. You want to directly manage these assignments from the Locations overview, with the ability to filter and bulk-edit multiple locations at once.

Solution

We introduced full warehouse and warehouse-cluster assignment capabilities directly within the Data Enhancement → Locations. Each location now displays its current assignment and offers an inline selector to choose a warehouse or a warehouse cluster.

The new Store Cluster Filter enables users to quickly group and edit locations belonging to the same cluster. For large-scale changes, a Bulk Action menu allows assigning a warehouse, assigning a warehouse cluster, or removing the connected warehouse.

This update significantly reduces manual work and improves the accuracy and flexibility of routing configuration across the network.

Dedicated Store & Warehouse Cluster Management Views

Use Case

System administrators and retail operations planners need to manage store clusters and warehouse clusters separately to avoid confusion and ensure they are working in the correct operational context.

Solution

We introduced two separate cluster management views under Data Enhancement, replacing the old combined “Location Clusters” entry:

• Store Clusters – for managing store/location clusters used in forecasting, replenishment, redistribution, and automation.

• Warehouse Clusters – for managing warehouse-only clusters with ranked ordering used in routing and fallback logic.

Cluster UIs now clearly differentiate between store and warehouse contexts.
The “Connect Warehouse” button has been removed from cluster screens, as warehouse relationships are now fully managed in the Location Type screen.

Shared Stock Locations for Multi-Channel Sales

Use Case

Planners and system integrators need a way to assign multiple sales locations (such as webshops) to a single physical stock-holding location. These sales channels don’t store stock themselves, but they do generate demand and require stock targets. Without proper mapping, replenishment behaves incorrectly and creates unnecessary stock movements.

Solution

Locations can now be linked to a shared stock location.
A stock location can serve multiple sales locations, or a sales location may act as its own stock location when no mapping is set.

Please note that this currently is purely the mapping, the replenishment logic behind this will be released in the near future.

Replenishment

Minimum Order Value Based on Cost Price

Use Case

Merchandisers need to ensure that replenishment transfers meet a minimum order threshold based on cost price value rather than units alone. Certain locations require a minimum monetary value for shipments to be cost-effective. The current unit-based minimum cannot guarantee this, resulting in inefficient or financially non-viable transfers.

Solution

The Replenishment module now supports minimum order value based on cost price through enhancements to the delivery settings and alert logic:

• A new Min Cost Value column has been added to the Delivery Settings overview, allowing merchandisers to define the minimum required cost-value per location.

• A new replenishment alert option “Minimum Cost Value” validates proposals based on total cost value instead of units.

• In the Replenishment engine, users can select between three modes:

  • Off – ignore cost price minimum

  • Force – block proposals below the minimum

  • Ask – warn users and let them decide to continue though an alert

• Transfers that do not meet the required cost threshold will trigger alerts or blocking behavior depending on the selected mode.

Maximum Style Capacity per Store

Use Case

Merchandisers want to prevent stores from receiving too many units of a single style. Without a per-style limit, stores risk overstocking, poor presentation, and operational inefficiencies. Users need a simple way to set these limits and enforce them during replenishment.

Solution

A new Style Settings section is added to Replenishment Settings, allowing users to define a maximum store capacity per style.
The overview supports filtering and bulk editing to quickly update multiple styles.

A new rule in the replenishment engine ensures proposals respect these limits:

• Ask → show an alert when a proposal exceeds the style capacity

• Force → block creation of proposals that exceed the limit

• Off → ignore the rule

During proposal generation, the system automatically checks each style’s capacity and triggers the correct behavior based on the selected mode. This prevents overstocking and keeps store inventory levels aligned with merchandising guidelines.

Enhanced Location Overview (Beta)

Use Case

Planners, merchandisers, and retail managers need quick visibility into the health and performance of each location. Until now, key KPIs such as turnrate, markdown performance, sales trends, and inventory status were dispersed across separate screens, making it harder to assess store performance and prioritize actions.

Solution

A new Location Overview (Beta) is now available, bringing together the most important KPIs per location in a single, modernized view.
Users can now instantly monitor key KPIs such as:

• Turnrate

• Markdown 30d & Markdown rolling Year

• Inventory levels & Weeks of supply (WOS)

• Rolling year sales performance

• 6-week trend insights

The overview highlights outliers and issues (e.g., missing sales or stock updates) to help users take faster, more informed actions.
We will gradually roll out access to this view during the beta period to collect feedback and further refine the experience.

New API:

/api/v1/SubTenants GET & PUT--> Get, Insert or Update SubTenant(s)