Overview
This reference guide covers the character limits and field mappings that apply to the DeltaWMS and Mintsoft integration. It also explains how the integration handles unrecognised data and the specific sync behaviours you should be aware of when configuring or troubleshooting the integration.
Field character limits
The integration applies character limits to several fields. Data that exceeds the limit for the DeltaWMS export is silently truncated — often without any error message. Review these limits when setting up your integration or diagnosing unexpected failures.
Field | Mintsoft stores up to | Exported to DeltaWMS as | Impact if exceeded |
Order Reference | 250 characters | 20 characters (truncated) | Reference mismatch or silent duplicate import failure in DeltaWMS |
External Order Reference | 250 characters | 20 characters (truncated) | Reference mismatch or silent duplicate import failure in DeltaWMS |
Account Code (Short Name) | 30 characters | 8 characters (truncated) | Account code mismatch between systems |
Haulier / Courier Code | Full name | First 8 characters (including spaces) | Haulier not matched in DeltaWMS; orders fail to process |
Order Type / Channel Name | Full name | First 12 characters | Order type not matched; orders fail to export |
Delivery Notes | 1,000 characters | 500 characters (DeltaWMS CSV spec) | Notes beyond 500 characters may be cut off in DeltaWMS |
Post Code | 20 characters | 20 characters | Order fails validation if exceeded |
EORI Number | 20 characters | 20 characters | Order fails validation if exceeded |
VAT Number | 50 characters | 50 characters | Order fails validation if exceeded |
Product SKU | 75 characters | 50 characters (DeltaWMS CSV spec) | Auto-creation may fail or cause SKU mismatches between systems |
Product Name | 99 characters | 99 characters | Auto-created product record fails if name exceeds 99 characters |
⚠️ Order reference truncation: Even though Mintsoft stores order references up to 250 characters, only the first 20 characters are sent to DeltaWMS. If your order references are longer than 20 characters, the truncated value is used as the identifier in DeltaWMS. A reference that appears unique in Mintsoft may match an existing truncated reference in DeltaWMS, causing a silent duplicate import failure.
Key field mappings
The table below shows how key fields from DeltaWMS map to fields in Mintsoft when orders and shipments are sent across.
DeltaWMS field | Maps to in Mintsoft | Notes |
DeliveryName | Order → Company Name | Populates the company name field in Mintsoft, not the recipient's personal name |
DeliveryContact | Order → First Name | The full contact string maps into the first name field only — it is not split into first and last name |
SiteCode | Warehouse → Code | Matched against the warehouse code in Mintsoft. If blank or unmatched, defaults to the pre-configured warehouse for the integration account |
HaulierName | Courier Service → Name | Matched by exact name first, then by courier service mapping. Only the first 8 characters are sent from DeltaWMS |
AccountCode | Client → Short Name | Must exactly match an existing Mintsoft client Short Name. If no match is found, a new client is automatically created — see below |
UserCode | Admin username (label printing) | Controls whose credentials are used to print labels and documents. If not set or not recognised, the API key's default user is used |
📌 DeliveryName and DeliveryContact: Because DeliveryName maps to Company Name in Mintsoft (not the recipient's personal name), and DeliveryContact maps to First Name only, it is important that your DeltaWMS data is configured with this mapping in mind. If you see company names or contact details appearing in unexpected fields in Mintsoft, this mapping is the likely cause.
How the integration handles unrecognised data
Unknown account code — Mintsoft client not found
If DeltaWMS sends an account code that does not match any existing client in Mintsoft, Mintsoft will automatically create a new client record using that code. The new client defaults to infinite stock, GBP currency, and UK country. No error is raised, so this can result in duplicate or incomplete client records going unnoticed. To prevent this, verify that all account codes in DeltaWMS exactly match the Short Name of existing Mintsoft client records before processing orders.
Unknown SKU — product not found in Mintsoft
If DeltaWMS sends a product SKU that does not exist in Mintsoft, Mintsoft automatically creates a new product record for that SKU. The product name is set to: PRODUCT INFO INCOMPLETE - MORE DETAILS REQUIRED. You will need to update the product record in Mintsoft manually after it has been created. To avoid incomplete product records, ensure all product SKUs are pre-configured in Mintsoft before sending orders through the integration.
ASN sync and stock sync behaviour
ASN quantity updates overwrite — they do not accumulate
When DeltaWMS sends an ASN item update with a quantity, Mintsoft replaces the existing expected quantity on that ASN item — it does not add to it. If you re-send ASN data to correct a quantity, the new value will fully overwrite the previous value.
Resetting the sync watermark
The integration tracks three sync watermarks — Last Stock Sync, Last ASN Sync, and Last Product Sync — to determine which records have changed since the last sync. Resetting a watermark causes all records of that type to be re-exported on the next sync cycle. If you believe a stock, ASN, or product sync has missed records, contact support and request a sync watermark reset for the relevant data type.
Automatic order tags in Mintsoft
When DeltaWMS creates or exports an order to Mintsoft, two tags are automatically applied to the order:
DeltaCourier
DeltaWMSExported
You can use these tags in Mintsoft to identify, filter, or report on orders that originated from DeltaWMS.
📌 Need help? If you experience any issues with the DeltaWMS and Mintsoft integration, raise a support case with us. Include as much detail as possible — for example, affected order references, account codes, and a description of the unexpected behaviour you are seeing.