Unleashed - FAQ

This article answers frequently asked questions about integrating Unleashed with Mintsoft, covering stock synchronisation, order processing, product data management, and troubleshooting common integration issues.

The Unleashed integration on Mintsoft supports serial number and batch number synchronisation for products. Logging batch numbers is supported for the integration.

If you see the following error in Mintsoft: "Error: {"Description":"The batch number quantity and the shipment quantity for batch tracked products must match. Please select the required quantity of batch numbers.","DebugInformation":null}", this occurs when some of the stock on the order is batch or serial tracked, but the serial or batch numbers don't exist in both Mintsoft and Unleashed. To fix this issue, make sure that Mintsoft and Unleashed have matching serial or batch numbers for the relevant products.

If you see products in Mintsoft showing as Unleashed-NDP against their alt code, please ensure Never Diminishing is disabled against the product within Unleashed. Without this disabled, we won't synchronise the product stock level.

If there's insufficient stock available for us to complete the stock adjustment on Unleashed, the stock updates will go into Parked status.

We recommend committing stock adjustments using the Stock Level in Mintsoft, as this corresponds to the Onhand level in Unleashed.

To submit a stock adjustment to Unleashed, you must provide a cost price.

This will be sent from the Mintsoft cost price field against the product. If the item doesn't have a cost price, the value will default to 1.

If you encounter the following error in Mintsoft: "Stock Update failed API Error: {"Items [{"Field":"AdjustmentReason","Description":"Invalid AdjustmentReason. Could not find AdjustmentReason Mintsoft.","ErrorCode":0}]}", please verify that you've correctly set up a Stock Adjustment Reason in Unleashed. More information can be found in our Unleashed integration help guide.

If orders from Unleashed aren't importing into Mintsoft but all other aspects of the integration are working, please ensure the Order Status To Import (alternatively, Custom Order Status To Import) field is populated with at least one status. If the field is left blank, it will only import orders in Open status.

When you split an Unleashed order in Mintsoft, the despatch update is still sent back to Unleashed. The system processes orders with despatch dates and creates or updates the shipment in Unleashed with "Dispatched" status, regardless of whether the order was split.

Amendments to shipments on Unleashed (item quantities etc.) can be picked up from Mintsoft, provided the related orders in Mintsoft haven't gone into any picking statuses.

Once an order has been exported to Unleashed from Mintsoft, no further amendments can be posted to the order from Mintsoft. Because of this, we recommend the trigger status to be despatched in Mintsoft.

Yes, all split parts must be marked as despatched in Mintsoft before the order status will update back to Unleashed. The system waits until every part of the split order is completed before sending the completion update.

Data and information from Products (SKUs) can be imported from Unleashed into Mintsoft. The product data initially imported from Unleashed into Mintsoft is:

Changes made to products in Unleashed after the initial import can also be synchronised into Mintsoft. The following attributes can synchronise from Unleashed into Mintsoft after the initial import:

We recommend not using special characters (&, %, #, etc.) for the SKU as this can cause issues with stock syncing and orders importing into Mintsoft.

If you're moving from a Sandbox or Trial Environment of Unleashed to a Live Environment and a Mintsoft connection is already in place, please speak with the Mintsoft support team or raise a support ticket and request the Product GUIDs be cleared, as this can cause issues with stock syncing to Unleashed and orders importing from Unleashed.

Amendments to POs in Unleashed are not picked up in Mintsoft once they've been imported as an ASN.

POs cannot be over-receipted. If the ASN is under-receipted on Mintsoft, this will create an additional PO on Unleashed for the balance of the stock. The PO won't be completed for you as part of this process—this will need to be done manually.

Purchase orders created on Unleashed containing a Bundle will not be imported to Mintsoft. The PO can only contain the components, not the actual bundle.

POs must have a creation date within the 60-day lookback window. POs created more than 60 days ago won't be imported, even if the delivery date is current.

Ensure the PO status in Unleashed matches the import settings selected for ASNs in Mintsoft. Commonly used statuses include "Placed."

If you receive the error "You cannot complete this assembly, as it contains the following product(s) on a receipted purchase order: . Please complete the purchase order first.", do the following:

Warehouse transfers on Unleashed can be imported to Mintsoft as two separate workflows:

Once the ASN part of the transfer has been Booked on Mintsoft, this will update and complete the Unleashed Warehouse Transfer. Updates and changes to Warehouse Transfers on Unleashed are not picked up in Mintsoft once imported to Mintsoft.

When a user cannot update orders even after their user roles have been updated, follow these steps:

Determine if the issue is specific to Unleashed orders or applies to all orders. Verify if the issue occurs with orders from other sales channels (for example, Shopify) or manual entries. For instance, if users can update Shopify orders but not Unleashed orders, the problem is specific to Unleashed.

Investigate whether the user encounters an unauthorised access error when updating Unleashed orders.

We recommend setting up External Courier Service Names for Unleashed orders when despatching from Mintsoft.