June 2025

Core

Usage of tenantFacilityId in API request paths

Users are no able to leverage tenant-defined IDs in API requests. For the start, the tenantFacilityId can be used to identify a facility entity.

Key Benefits:

• Improved interoperability with third-party services utilizing their own identifiers

• Enhanced user experience by supporting familiar, business-specific IDs

• Streamlined integration and reduced complexity in ID mapping

• Alignment of API operations with business logic for intuitive resource management

Inventory management

Performance improvements article search

Thanks to technical optimizations carried out in the background, the article search in the Backoffice now offers optimized performance (even with large amounts of data). The article searches on the stock overview and the listing views benefit from this.

Order routing & management

Facility groups can be used to define routing rules

Facility groups allow multiple facilities to be bundled together. These groups can now be used when configuring new routing strategies, toolkit ratings, or fences.

Order fulfillment

Mandatory short-pick reasons

Short-pick reasons can now be made mandatory through remote configuration. If this configuration is active, users must provide reasons for every short-pick before they can finish the picking task.