Supply Lens

Mintsoft setup and flows

Lesson 6 of 28 6 min read

Add a Mintsoft Integration, switch on the right Configurations and understand the two ways Mintsoft orders can flow.

Mintsoft is a warehouse management system used by many UK 3PLs. If your customer's 3PL runs Mintsoft, this module shows you how to connect it and set it up decision by decision.

By the end of this lesson you will have a Mintsoft Integration with the right Configurations, and you will know which settings group controls which flow.

What Mintsoft can do in Supply Lens

The Mintsoft settings guide has five groups, one per Document type:

Settings groupDirectionWhat it does
Mintsoft OrderSend and importCreates orders in Mintsoft, and can also import orders that already exist in Mintsoft
Mintsoft ShipmentReceiveImports despatched shipments
Mintsoft InventoryReceiveImports stock levels, optionally per warehouse
Mintsoft Goods InboundSendCreates goods-in records (ASNs) in Mintsoft
Mintsoft Goods Inbound ReceiptReceiveImports receipts against those ASNs
Rendering diagram...

Two ways orders can flow

The Mintsoft Order group holds settings for both directions, so it helps to separate them:

  • Creating orders in Mintsoft (Supply Lens sends): clientId, courierServiceMap, fallBackToDocumentCourierService, tagChannelMap, integrationKeyChannelMap, createOneLinePerBatchNumber, deliveryDateAdjustmentTagMap and automaticallyCancelOrders.
  • Importing orders from Mintsoft (Supply Lens receives): the import window (setupDate, lastImportDate, importDelay), the filterBy... settings, defaultCustomerId, completedOrderStatusIds, statusIdToFulfillmentStatusMap and tag generation.

Importing is useful when orders reach Mintsoft by another route and the ERP still needs to see them. Most 3PL setups only need the sending side.

Set it up

  1. Go to Settings → Integration setup → Integrations, click + ADD INTEGRATION and click ADD on Mintsoft.
  2. Complete the connection form with the details from the 3PL and click CONNECT.
  3. Expand the tile, open Configurations and add one per Document type you need, choosing Send or Receive. Click Create Default JSON for each, then Save.
  4. Add the master data: Mintsoft Warehouse or Mintsoft Warehouse Id identifiers on your Locations, and a Mintsoft Client ID on your Party.
  5. Create the Mappings for each flow.

Several Mintsoft clients

Mintsoft is multi-client. The clientId setting decides which Mintsoft client receives the orders you create, and every import group has a filterByClientId so you only bring back your own client's records.

Fernhill Teas on Mintsoft

Fernhill Teas sells on Shopify and in wholesale, with stock in a Mintsoft 3PL. Orders go from Unleashed to Mintsoft; shipments, receipts and stock come back. The implementer adds five Configurations: Order (Send), Shipment (Receive), Goods Inbound (Send), Goods Inbound Receipt (Receive) and Inventory (Receive). Fernhill never imports orders from Mintsoft, so the order import filters stay empty and unused.

Recap

  • Mintsoft has settings for orders, shipments, inventory, goods inbound and goods inbound receipts.
  • The Mintsoft Order group mixes sending (creating orders) and importing settings; most setups only need the sending side.
  • Locations carry Mintsoft warehouse identifiers and the Party carries the Mintsoft Client ID.
  • Mintsoft is multi-client, so set clientId when sending and filterByClientId when importing.
Complete and continue

Your progress is saved in this browser. Create a free account to keep it everywhere, take quizzes and earn certificates.