Mintsoft order settings by decision
Lesson 7 of 28 8 min read
Work through the Mintsoft Order settings as a series of decisions, from courier services and channels to batches, bundles, cancellations and imported orders.
The Mintsoft Order group is the largest in the Mintsoft guide. Rather than reading it top to bottom, work through it as the decisions a 3PL go-live actually needs.
By the end of this lesson you will be able to configure order creation in Mintsoft and, if needed, order import from it.
Decision 1: which client and channel?
| clientId | The Mintsoft client that receives the orders Supply Lens creates. |
|---|---|
| tagChannelMap | Maps order tags to Mintsoft channel names. The first matching tag decides the channel; only that one is applied. |
| integrationKeyChannelMap | Maps the source Integration's key to a Mintsoft channel, so orders from different systems land in different channels. Has a default fallback. |
Use integrationKeyChannelMap when the channel follows the system the order came from
(Shopify orders in one channel, B2B orders in another). Use tagChannelMap when it follows
something about the order itself that is expressed as a tag.
Decision 2: which courier service?
| courierServiceMap | Maps courier service names from the source system to Mintsoft courier service codes. Evaluated in order, with a default fallback when nothing matches. |
|---|---|
| fallBackToDocumentCourierService | When true, and the map gives no value (no match and no default), the document's own carrier service is sent to Mintsoft unchanged. When false or unset, the courier service is left empty. |
Fallback helps when names already match
If the storefront already uses Mintsoft's service names for most services, turn on the fallback and only map the exceptions.
Decision 3: lines, batches and bundles
| createOneLinePerBatchNumber | When true, one order line is created for each batch number on a line, for batch-level tracking. Off by default. |
|---|---|
| skipBundleProcessing | When true, bundle products are sent as-is instead of being expanded into their component lines. When false or unset, bundles are expanded. |
Ask the 3PL how bundles are set up in Mintsoft. If Mintsoft holds the bundle as a product it builds itself, you may want it sent as-is; if Mintsoft only knows the components, leave expansion on.
Decision 4: delivery dates and cancellations
| deliveryDateAdjustmentTagMap | Maps order tags to a delivery date adjustment, so the date can shift per order type. For example, orders tagged rush might have the date brought forward. |
|---|---|
| automaticallyCancelOrders | Default true. Cancelled orders in the source system are cancelled in Mintsoft. When disabled, cancellations are not synchronised. |
Turning off cancellations
If you disable automaticallyCancelOrders, someone must cancel orders in Mintsoft by hand
when they are cancelled upstream, or the warehouse may still pick them.
Decision 5 (only if importing): which Mintsoft orders, and how?
If you also import orders from Mintsoft, these settings apply:
| filterByOrderStatusId, filterByClientId, filterByChannelId, filterByCourierServiceId, filterByWarehouseId | Each limits the import to the listed Mintsoft ids. Empty includes everything. |
|---|---|
| defaultCustomerId | The customer used when none can be identified from the order. |
| alwaysSetDefaultCustomerId | When true, the default customer is always applied, overriding any customer found on the order. |
| completedOrderStatusIds | Mintsoft status ids that mean complete. Orders in these statuses are imported as fulfilled. |
| statusIdToFulfillmentStatusMap | Translates Mintsoft status ids into Supply Lens fulfilment statuses. |
| orderNumberReferenceType, externalOrderReferenceType | The reference types that carry the Mintsoft order number and the original source order reference. |
| documentLevelTagGeneration, documentLevelAdvancedTagGeneration | Rules that create tags from Mintsoft order fields; the advanced version supports conditional logic. |
| disableExpectedPayableTag | Stops the expected payable tag being added. That tag is used to check the calculated order total matches the expected amount, so disabling it skips the check. |
Fernhill Teas' courier and channel decisions
Fernhill ships retail orders by Royal Mail Tracked 48 and wholesale orders by pallet. Shopify orders and B2B orders reach Unleashed from different Integrations.
integrationKeyChannelMap: the Shopify Integration's key →Shopify, default →Wholesale.courierServiceMap:Tracked 48→ Mintsoft's Tracked 48 code;Pallet→ the 3PL's pallet service; no default, because an unknown service should be noticed.fallBackToDocumentCourierService: off, for the same reason.automaticallyCancelOrders: left at the default,true.
Recap
- clientId picks the Mintsoft client; channels come from the source Integration's key or from the first matching tag.
- courierServiceMap translates services in order with a default; the fallback can pass the original service through.
- Decide on batch lines and bundle expansion with the 3PL.
- Cancellations sync by default; switching that off means cancelling in Mintsoft by hand.
- Import filters, status maps and default customers only matter if you import orders from Mintsoft.
Quick guides for this topic
Your progress is saved in this browser. Create a free account to keep it everywhere, take quizzes and earn certificates.