Everything you need to connect the LataSys 3PL Connector to MintSoft (Mintsoft OMS/WMS): prerequisites, connection setup, mappings, capabilities and provider-specific behaviour.

What this adapter provides

Prerequisites

• The LataSys 3PL Connector (core app) installed and licensed.
• A MintSoft account with API access, and from your fulfilment house:
• the username and password of an API-enabled MintSoft user;
• on 3PL multi-client accounts, your numeric Client ID (skip it if your login is already scoped to your client);
• the weight unit their MintSoft account is configured in (kg or g) - product pushes send the Odoo weight as-is.

Installation

Install the LataSys 3PL Connector: MintSoft Adapter module. The provider then appears in the provider list when creating a 3PL instance, along with its provider card (API operations reference) under Configuration - Providers.

Connection setup

Authentication is username/password exchanged for a MintSoft API key (valid 24 hours, sent as the ms-apikey header). Keys are obtained and renewed automatically - only the username and password are stored. On the instance's Connection tab:

1. Enter the MintSoft username and password.
2. The API root URL is https://api.mintsoft.co.uk for every account - MintSoft has no separate sandbox host; use a separate MintSoft account (and a separate instance) for testing.
3. Press Test Connection. The instance moves from Draft to Connected and the full HTTP exchange is captured in the Sync Log.

Mappings

• Warehouses - press Fetch Warehouses: MintSoft warehouses are numeric ids, offered on the mapping lines. The remote code must hold the numeric id.
• Carriers - press Fetch Carriers to pull the courier service list, then map each remote service to your Odoo delivery methods.
• Statuses - press Load Missing Defaults. MintSoft statuses are account data (fulfilment houses rename and add their own); the adapter seeds the stock names and reads the live table from /api/Order/Statuses while polling - add any account-specific statuses on the Statuses tab with the right canonical meaning.
• Requested Methods - press Load Requested Methods to pull the courier service names MintSoft accepts and map every requested-delivery-method value your orders use. Mapped values decide the CourierService requested on each order; unmapped orders fall back to the carrier mapping, and an empty service lets MintSoft's own order rules choose.

MintSoft Options tab

Provider-specific behaviour

• Order references - MintSoft's order key is the integer OrderId returned on creation. The configured order reference (Odoo order number or customer reference) travels as OrderNumber, with the Odoo document name always in ExternalOrderReference. Order creation returns an array because MintSoft may split an order; the first successful row is tracked.
• Despatch - tracking comes from the order header; batch/lot lines come from the per-order allocations feed. Orders with a stamped DespatchDate count as despatched even under account-specific status names.
• Weight unit - MintSoft requires a Weight on every product but does not expose the account's unit; the Odoo weight is sent unconverted. Confirm the unit with your fulfilment house.
• Stock measure - the sync reads StockLevel (MintSoft's sellable level). Allocated units are not subtracted: they are still on the shelf, and Odoo's own reservations account for open orders.
• Returns - MintSoft has no label generation: Create Return registers the RMA at the 3PL (return + lines + confirm) so the warehouse expects the goods; no label document is produced. Returns discovery sweeps /api/Return/List; MintSoft has no viewed/acknowledged flag, so deduplication happens on the Odoo side.
• IOSS - where the instance is IOSS-registered, the number is passed on non-UK orders (GB, NI, Channel Islands and Isle of Man count as UK).

Troubleshooting

See also: MintSoft adapter - process maps for the end-to-end flow diagrams.

MintSoft (Mintsoft) is a trademark of its respective owner; the name is used solely to identify the service this module interoperates with.