Resolving Courier Service Issues in Mintsoft
Mintsoft offers robust tools for managing courier integrations, but occasional issues may arise, such as conflicts in service rules, missing service codes, or errors encountered during dispatch, like restricted delivery areas or invalid postcodes. This article provides step-by-step guidance to address these common challenges and ensure smooth operation of courier services.
Identifying and Resolving Conflicts in Courier Service Rules
Conflicting or duplicate courier service rules can impede the allocation of orders to appropriate services. To resolve these conflicts:
Locate the conflicting rule in the courier service setup under Shipping Management.
Remove any duplicate or conflicting rules, such as rules that span overlapping attributes (e.g., conflicting weight ranges).
Example: If duplicate service rules exist for the same courier, delete the unnecessary rule.
After cleanup, select the affected orders and recalculate the courier service.
By recalculating, Mintsoft will apply the correct service rule that best fits the specified criteria, ensuring the proper allocation of orders.
Mapping and Activating Missing Courier Service Codes
Unmapped or inactive service codes in Mintsoft can disrupt the functionality of courier services. To address this issue:
Navigate to Shipping Management then Couriers.
Find the affected courier then click Manage Courier Services.
Check the list of inactive services by clicking Show Inactive.
If the required service is listed, activate it directly.
If the service is not available, contact your courier provider to obtain the appropriate service codes.
Use the Mintsoft platform to map these new codes following guidance from the Mintsoft support documentation.
If additional support is needed, Mintsoft's customer service can assist with the mapping process after you provide the necessary service codes from your courier provider.
Resolving Dispatch-Time Errors in Mintsoft
Common Causes of Errors
Errors such as 'Code 10159: Country/Postcode is not covered' often stem from courier service restrictions or system configuration issues. Common issues include:
Service restrictions: The courier may not support shipments to the requested postcode or country, or the parcel might exceed weight/size limits.
Configuration errors: Mismatches between Mintsoft's selected services and the courier's supported services.
Recommended Actions
Verify Destination Eligibility:
Check if the courier services operate for the specific postcode or country.
Review courier documentation for logistical limitations.
Review Mintsoft Service Mappings:
Compare the selected Mintsoft courier service with the courier's permitted options. Correct any mismatches.
Adjust Shipment Details:
Revise shipment weights or dimensions to comply with the courier's specifications.
Seek Further Assistance:
Contact the courier to confirm shipment compatibility.
Consult Mintsoft customer support to address persistent mapping or configuration issues.
Resolve courier integration setup errors
If you encounter errors during initial courier integration setup â such as API authentication failures, missing posting locations, or permission errors that prevent the connection from being established â work through the steps below before contacting support.
API authentication and credential errors
Authentication errors during courier setup typically appear as 'Invalid credentials', 'Authentication failed', or '401 Unauthorised'. These occur when the credentials stored in Mintsoft do not match those on the courier account.
Verify the credentials entered in Mintsoft exactly match your courier account â check for extra spaces, incorrect account numbers, or expired passwords.
Check whether Test Mode is enabled on the integration. If Test Mode is on, you must use test credentials. Production credentials will not work in Test Mode, and test credentials will not work in Production Mode.
Re-enter your credentials by clicking Connect then Courier Integrations, selecting the courier, clicking Edit, and updating the Username, Password, or API key fields.
If the error persists, contact your courier account manager to confirm your account is active and that API access is enabled on your account.
Missing posting location or account number errors
Some couriers â including Royal Mail, DPD, and APC â require a posting location or account number to be configured separately from your login credentials. If label generation fails with errors referencing a missing location or account number:
Click Connect then Courier Integrations and select the affected courier.
Click Edit and check for Posting Location, Account Number, or Collection Location fields.
If these fields are blank, enter the values from your courier account portal or contact your courier account manager to obtain them.
Carrier-specific setup and troubleshooting guides
For courier-specific service codes, configuration steps, and error troubleshooting, refer to the dedicated integration guide for your carrier. Each guide lists the exact service codes and account fields required for that courier.
Tip: If your service code is not listed in Mintsoft, check your carrier's integration guide before contacting the courier. Many carriers use multiple service codes for different regions, product types, and service levels, and the integration guide lists the correct values to use.