Overview
If Mintsoft is failing to generate courier labels for orders dispatched in DeltaWMS, the cause is usually a missing parcel or weight field, a mismatched haulier code, or an order that was never exported from Delta. Work through the checks below to identify and fix the issue.
Check 1: Parcel count and weight fields
Mintsoft requires the parcel count and weight to generate a label. If these fields are blank in Delta at the point of dispatch, label generation will fail.
In DeltaWMS, locate the affected order and check the dispatch record for the parcel count and weight fields. Both must have a value greater than zero.
If either field is blank, go to Setup, then Hauliers, and open the relevant haulier record.
Click the Labels tab, then ensure the Enabled checkbox is ticked for both the Labels (parcel count, data type INTEGER) and Weight (data type FLOAT) rows. When enabled, Delta will prompt the user for these values at the point of despatch and pass them to Mintsoft for label generation.
⚠️ Important: This is the most common cause of label failures. Even if the dispatch appeared to complete successfully in Delta, blank parcel or weight fields will silently block Mintsoft from generating the label.
📌 Note: If weight is not supplied at despatch, Mintsoft will fall back to the default product weight configured in Mintsoft, if one is set. If neither is provided, label generation will fail.
Check 2: Haulier code matches Delta's 8-character limit
When Mintsoft sends a haulier or courier code to Delta, it only sends the first 8 characters of the code (including spaces). If the haulier record in Delta doesn't match those exact 8 characters, the order will not be linked to a valid haulier and labels cannot be generated.
In Mintsoft, find the courier service name assigned to the failing order and take the first 8 characters (including any spaces). This is the code Mintsoft sends to Delta.
In DeltaWMS, go to Setup, then Hauliers, and confirm a haulier record exists with that exact 8-character code.
If no matching record exists, create one. See Create Haulier codes for steps.
📌 Note: If the Mintsoft courier service is named PRINSTAN EXPRESS, Mintsoft will send PRINSTAN to Delta (8 characters). You need a haulier record in Delta with the code PRINSTAN, not PRINSTAN EXPRESS.
For orders that originated in Delta (not from Mintsoft), the haulier code in Delta is sent directly to Mintsoft and must either match a Mintsoft courier service name exactly, or have an entry in the Courier Service Mapping in Mintsoft. Go to Picking and Packing, then Courier Service Mapping to manage mappings.
📌 Note: Because Delta haulier codes are 8 characters, Delta-originated orders will usually need a Courier Service Mapping entry in Mintsoft unless the Mintsoft courier service name has already been shortened to 8 characters.
Check 3: Confirm the order was exported from Delta to Mintsoft
If labels are failing for a specific haulier code but all the settings above appear correct, the order may not have been exported from Delta to Mintsoft at all. This can happen if the required haulier details are not included in Delta's export configuration for that account.
In Mintsoft, check the order history for the affected order references. If there is no record of the order arriving in Mintsoft, it was not exported from Delta.
Check whether the haulier code is included in your Delta export configuration for the relevant account. If it is missing, the export for that courier will be silently skipped.
📌 Note: If the order is not appearing in Mintsoft at all, also see Orders from Mintsoft failed to import into DeltaWMS for further guidance.
⚠️ Important: If the courier service on an order was changed in Mintsoft after the order was sent to Delta, Mintsoft will use the updated service , not the one recorded on the Delta order. Similarly, changing the haulier code in Delta after the order arrives will have no effect. If the haulier code appears correct in Delta but labels are still failing, check the current courier service set on the order in Mintsoft.
Check 4: Find and resolve label rejection errors
When Delta despatches an order and the courier rejects the label request, the rejection message is recorded in the Delta Import and Export Exception Pool. These are the same error messages shown in Mintsoft when you try to generate a label manually, for example, address line too long, or missing EORI or VAT number.
In Delta, check the Import and Export Exception Pool for rejection messages on the affected order and note the error message shown.
In Mintsoft, go to Picking and Packing, then Order Pick and Pack.
Search for the affected order by Order ID or Order Number, then resolve the courier service or address issue shown in the error message.
📌 Note: To find your order in Mintsoft:
If the order originated from Delta, use the Delta Goods Out Number as the order number.
If the order originated from Mintsoft, use Reference1 on the order in Delta as the order number. The Order ID will be in the Order Code field in Delta.
Still seeing failures?
If you have worked through all four checks and labels are still not generating, raise a support case with the following information:
The affected order reference(s) and account code
The haulier or courier service name as it appears in Mintsoft
Screenshots of the parcel count and weight fields in the dispatch record
Whether the issue affects all orders for this haulier or only specific ones
Including this detail upfront allows us to investigate without needing to ask follow-up questions.