1. Purpose
This policy outlines the responsibility of customers to monitor and manage order import errors within Mintsoft, ensuring orders are processed correctly and without delay.
The aim is to maintain smooth order flow from your webshop into the fulfilment system and avoid disruptions to dispatch.
2. Scope
This policy applies to all customers using integrations between their webshop / sales channels and Scale 3PL via Mintsoft.
3. Daily Monitoring Requirement
Customers are required to review the Mintsoft dashboard daily, specifically the:
Connect Import Summary
This section highlights any issues preventing orders from importing or processing correctly.
4. Responsibility for Order Import Errors
Customers are responsible for identifying and resolving any issues shown in the Connect Import Summary.
Common examples include:
- missing or incomplete address information
- country not recognised
- product not mapped or not found
- courier service not assigned
- order data formatting issues
Failure to resolve these issues may result in:
- delays in order processing
- orders not being dispatched
- customer delivery issues
5. Resolving Issues
In most cases, errors can be resolved by:
- Updating the order directly within your webshop or sales platform
- Correcting any missing or incorrect data (e.g. address, product mapping, shipping method)
- Allowing the integration to re-sync and re-import the order into Mintsoft
Once corrected, the system will typically process the order automatically.
6. When to Contact Scale 3PL
If you are unsure how to resolve an issue, or if the error persists after correction, please contact the Scale 3PL team.
We are happy to assist, but customers are expected to manage standard integration errors as part of their daily operations.
7. Impact of Non-Compliance
Failure to regularly monitor and resolve import errors may lead to:
- delayed order fulfilment
- missed dispatch deadlines
- increased operational issues
Scale 3PL cannot be held responsible for delays caused by unresolved order import errors.
8. Policy Review
This policy will be reviewed periodically to ensure it reflects system processes and operational requirements.
9. Version Control
Version | Date | Author | Change
1.0 | 06 March 2026 | Nick Coleman | Initial version
Help Center