v2026.3.13 Release Notes | Mintsoft Help Centre

We're pleased to announce the v2026.3.13 release version of Mintsoft, which will be made available on the 1st October 2026. To ensure a smooth transition we may implement some of the below through a phased rollout. This release includes the following improvements and fixes.

New Features and Improvements

Royal Mail / Sapient

Improved handling of failed manifest responses to remove blocking shipment IDs and allow new manifests to proceed.
Enhanced tracking number logic so that tracking is only saved when supported by the service.
Return address and return client name are now driven by the API ReturnToSender section, defaulting to the address configured on the shipping location screen if not provided.

Cartons & Pallets

Added a new toggle in Customer Account Settings (ASNs tab) labelled "Remove SSCC 18 Character Validation". When enabled, the 18-character SSCC validation is removed on the Create ASN screen and in the mobile Goods In flow, allowing inbound pallet IDs or references of any length to be entered or scanned. The setting is disabled by default and only visible for customers with the Cartons and Pallets module.
This gives customers who receive pre-advised pallet IDs that do not conform to the standard 18-character SSCC format the flexibility to use the SSCC field without being blocked by character length rules.

Mobile App - Production

Version: X

No production update this week as no beta last week

Mobile App - Beta

Version: beta.2026.10.01

Transfer Inventory	We have added the ability to do a cross-warehouse transfer on a single transfer, not in bulk.
Picking Skipped	We have implemented a new feature where you can skip an aisle or product for now and come back to it at the end of the pick.

Bug Fixes

Stock Levels API	We have resolved an issue where calling the Stock Levels API call was failing with a server error.
Stock Allocation	Resolved an issue where some stock was being picked from Replen-only locations without a replen task being triggered.
Custom Dashboard	Resolved issue where a Custom Dashboard was not retrieving the relevant information.