Skip to main content

v2026.4.4 Release Notes

Written by Alyssa Reynolds

We're pleased to announce the v2026.4.4 release version of Mintsoft, which will be made available on the 29th 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

UPS (PID Requirements)

We now send EU product identifiers (PIDs) via their InternationalForms.Product.ProductIdentifier list for B2C shipments to the EU.

Mapping as follows:

  • ProductID: SKU = ProductIDTypeCode: "0100" (MerchantPID)

  • ProductID: ManufacturerProductId = ProductIDTypeCode: "0200" ( non-standardised Manufacturer)

  • ProductID: valid EAN/UPC = ProductIDTypeCode: "0300"} ] (standardised Manufacturer)

Norsk (PID Requirements)

We now send EU product identifiers (PIDs) to Norsk Global for all EU imports (B2C and B2B) as follows:

  • MPID = SKU.

  • NSPID = ManufacturerProductId

  • SPID = the valid EAN/UPC

Spring Global/ MyParcel (PID Requirements)

We have added the following mapping for B2C shipments to the EU:

  • eu_customs.merchant_id

  • eu_customs.manufacturer_id

  • eu_customs.standardized_id

Scurri (PID Requirements)

Added the following Product Identifier mapping for all shipments to the EU:

  • manufacturer_product_id

  • standardised_product_id

  • standardised_product_id_type

The Delivery Group (PID Requirements)

We now send EU product identifiers (PIDs) to The Delivery Group for all EU imports (B2C and B2B) as follows:

  • MerchantProductId = SKU

  • NonStandardisedProductId = ManufacturerProductId

  • StandardisedProductId = valid EAN/UPC

DHL Parcel UK (PID Requirements)

We now send EU product identifiers (PIDs) to DHL Parcel UK for all EU imports (B2C and B2B) as follows:

  • productIdentifiers.merchant = SKU

  • productIdentifiers.nonStandardised = ManufacturerProductId

  • productIdentifiers.standardised = valid EAN/UPC

EasyPost (PID Requirements)

We now send EU product identifiers (PIDs) to EasyPost for all EU imports (B2C and B2B) as follows:

  • code = SKU

  • item.manufacturer_product_id = ManufacturerProductId; 64-character limit enforced

  • item.standardized_product_id = valid EAN/UPC; 64-character limit enforced

SendCloud (PID Requirements)

We now send EU product identifiers (PIDs) to SendCloud for all EU imports (B2C and B2B) as follows:

  • SendCloud has no separate merchant-ID field. The existing sku already sends Product.SKU.

  • manufacturer_product_id = ManufacturerProductId

  • manufacturer_product_id_std = valid EAN/UPC

StarShipIt (PID Requirements)

We now send EU product identifiers (PIDs) to StarShipIt for all EU imports (B2C and B2B) as follows:

  • merchant_product_id = SKU

  • manufacturer_product_id = ManufacturerProductId

  • standardised_product_id = valid EAN/UPC

OCS Worldwide (PID Requirements)

We now send EU product identifiers (PIDs) to OCS Worldwide for all EU imports (B2C and B2B) as follows:

  • mpid = MerchantProductId (SKU)

  • nspid = ManufacturerProductId (no fallback)

  • spid = StandardisedProductId (valid EAN/UPC only)

  • spid_standard = StandardisedProductIdType ("EAN" / "UPC")

GFS (PID Requirements)

We now send EU product identifiers (PIDs) to GFS for all EU imports (B2C and B2B) as follows:

  • SKU = SKU

  • ManufacturerProductID = ManufacturerProductId
    StandardisedProductID = valid EAN/UPC

Shopify

Shopify product import now populates ManufacturerProductId from Shopify variant barcodes on API version 2026-10+.

NS_PID barcodes are mapped to ManufacturerProductId, and EAN is taken from typed standard barcodes rather than the first barcode.

AusPost

  • Mapped item_contents[].sku which is now mandatory for EU destinations for AusPost from 23 Oct 2026.

  • Also added improved per-parcel item_contents regrouping so we send SKU1 QTY 3, as apposed to 3 lines of SKU1 QTY 1, to reduce the €3 per line charge.

Commercial Invoice

Added EU product identifiers (PIDs) to both the Mintsoft default commercial invoices and customer custom templates when shipping to the EU. New merge fields: NS_PID and S_PID.

FedEx

For international shipping, when Extra Code 1 is set to "SENDER" and Extra Code 4 is populated, duties are now billed to the account number in Extra Code 4 instead of the default account number.
​Why it's useful: Allows correct sender account to be charged for FedEx duties.

Product Labels

Label generation requests for 50 products or fewer (with 100 labels or fewer in total) now generate instantly instead of via background job.

API

We have enhanced API role enforcement, so your roles will reflect what you can access on the API.


Mobile App - Production

Nothing in production release this week.


Mobile App - Beta

Version: beta.2026.10.29

ASN

Fixed an issue where units could be booked in twice after a network interruption .

Stock Take

  • Fixed an issue where spot checks raised during bulk and Multi-Order Multi-Tote picking did not account for the stock just picked.

  • Fixed an issue where a location could be reassigned to another user during long counts or while the device was in the background.

  • Improved handling when the remaining locations are being counted by other users: "No locations left" is now displayed instead of a location being counted twice .

General

  • Fixed an issue where a thick white bar was displayed above the header on Android devices.

  • Improved security and stability.


Bug Fixes

Returns

We have resolved an issue where returns were showing as processed on Returns - Overview without the customer processing the return.

Subscriptions

Resolved issue where the permission "AdminCreateSubscription" was not working as expected.

Quarantine

We have fixed an issue when bulk quarantining stock.

Inventory Report

Resolved issue where Inventory Report was not displaying Default Picking Location.

Reports

We have resolved an issue where users were unable to extract reports if there were more than 50k results.

Courier Service Mapping

Resolved issue where Courier Service Mapping was being bypassed at random.

ASN

Resolved issue where ASN Breakdown Column showed "Invalid Location -" on completed ASNs.


Did this answer your question?