We're pleased to announce the v2026.2.13 release version of Mintsoft, which will be made available on the 2nd July 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
Custom Reports | Added Order Tags as an available field in Custom Order Reports. |
Orders | Performance improvements to the Order Details page, reducing loading times particularly for larger orders. |
Fedex | Added support for one-label-at-a-time printing for multi-piece shipments (MPS). |
Descartes E-Customs | A new file export version added which supports additional fields including airwaybill/tracking number and customisable removal type codes. As well as a manual export trigger button. |
Mobile App - Production
Version: Mintsoft.MobileApp-prod.2026.07.02
Multi Tote | Fixed an issue with Multi Tote where picking would assign different totes to one order. |
Stock Take | Added the ability to log a count of 0 when the role StockTakeManuallyConfirm is disabled, which prevented a user being able to tap on a product. |
Mobile App - Beta
Version: Mintsoft.MobileApp-beta.2026.07.02
Product Search | Improvements to the Product Search function. Users can scan or search for a product, and drill down into stock levels and locations by either location or attribute, depending on what they need. |
Bug Fixes
Stock | Resolved issue where batch IDs were missing for quarantined and unquarantined stock. |
Order Rules | Resolved issue where the split address order rule was overwriting address line 2. |
Stock Take | Resolved issue where a spot check was prompted but could not be logged due to an outstanding second count. |
Box Packing | Resolved issue where client packaging instructions were missing from box packing instructions. |
Linked Products | Resolved issue where linked product rules were creating duplicate order lines instead of consolidating them. |
Shopify | Resolved issue where an additional connection could not be added. |
PalletWays | Resolved issue where the PalletWays integration was storing the response ID as both the shipment ID and tracking number. |